Problem with 128MB mod on Xbox

You can hit Programs then Games. Not sure what the issue is

 

I've heard of it. I have yet to come across anything that fails to run when all 128MB is active. But then again most of the games and apps I run are built to use the full 128MB. The few retail games I have run fine with all RAM active. I guess that tool was used back in the early days when the mod was just getting started. I haven't found it either.

 

Wonder what would happen if you simply dumped VC3 onto C and ran it's XBE at boot.

 

The point of RAM Delimit isn't to make games run on a 128mb box, but rather to allow them to use all 128mb of ram. Supposedly helps quite a bit on games like GTA, as it can keep more car locations, etc in the RAM, although I never did any scientific tests

 

They merely removed the default folders from the configuration files. You can permanently add whatever directory you want either through the UI or by editing the configuration files and FTPing them over.

Also, check your PMs.

Unless they left in code that allows the game to use whatever it finds I'd find it unlikely that games would really benefit from the extra RAM. I'd imagine there might be a case where a crash can be avoided by having more memory available. Is there some way to remotely monitor RAM usage while ingame?

 

Its supposedly a simple flag. It was used for MAME to some success initially, plus works on other XBEs. The best way is to find a program that has some debugging functionality left, Ill see if GTA has it sometime.

I've attached the program to this post for those who want it.

 

Cool. Thanks. I'll mess around with it at some point and see if it helps any resource heavy games.

 

The older version of XBMC I had installed did not have the menu point called Programs. Didn't have any obvious way of adding it either from within XBMC.

The new version I installed today has the Program menu by default, so no worries.

 

The latest version I grabbed had the same UI from the Android version I've been using. Changed the skin back to PM3 and it was like the good ol days.

 

Thanks for the delimit program, Borman. I just did the 128mb mod on an Xbox 1.0, and "Need for Speed Most Wanted: Black Edition" is running pretty damn slow.
I'm using "X2 5035" by the way. Weird, it runs fine when I switch the bios to "Evox M8", but then there's only 64mb available... I'll test the program to see if it helps.

 

I haven't had my 128mb xbox out in years, but I remember one of the NFS games having the same issue. I'm not sure if I'm remembering right, but the menus were fine, but once you tried to race it was practically a slideshow, running single-digit fps. I believe my box had the complex bios on it, and had the xdk dash set up. I couldn't be bothered to try other bioses (or see if it had the same issue on a 64mb with a debug bios), and just played the game on another xbox I had at the time. I'm curious to know what specifically caused it though...

Semi-related, I have a review/beta copy of Forza (was a pressed dvd with a printed build number and date, unusual for pre-retail discs we got) that requires the xdk dash, and crashes with out of memory errors on the DIY 64mb retail to debugs I had. On my 128mb xbox, it ran but suffered a similar problem - races were a slideshow, worse than whatever retail NFS I had problems with. Unfortunately, out of all our reviewers I had the only 128mb system, and it was a DIY from retail. We did have at least one legit debug system, but it was only 64mb and had the same out of memory crash. I never did find out if it ran properly on an official 128mb system. I didn't want to spread it at the time, but now I really need to track down which storage box it's in and dump it.

Because of my NFS and beta Forza issues, I wondered if I hadn't damaged my ram in the install. I recycled ram from a dead system, removed and added with a hot air rework setup, and I'm quite sure there are no bridges or bad solder joints. At the time MAME was one of the few things that could use 128mb, and it worked flawlessly, running games that didn't work on a 64mb system, so in the end I assumed my system was fine and it was two game-specific issues with my hackjob xdk. Hearing someone else have the same issue with a different bios makes me even more curious now.

 

benny's new xblast os can test the extended ram chip by chip not bank by bank so you can tell what chip is faulty as other tools just tell you the ram is faulty not which one.

It would be nice if benny made it tell you what pin is not soldered on the ram but i guess it is a big task to implement there is a lot of pins to lift up on the 4 ram chips to test out the mapping.