Xbe launcher that initializes all 128MB on modded consoles?

I think this has been discussed before but I don't know if it exists or if anyone has bothered with it. We all know of the now classic 128MB modded retail consoles that can play Virtua Cop 3. Hell, I have one myself.

There's just one problem though. When these modded systems start they seem to only initialize the first 64MB like a stock console. I tried launching VC3 straight from the dash and while it starts everything is cold molasses slow just like on a 64MB console. Most people just launch MAMEoX128 Plus, return to dash, then launch VC3. MAME seems to somehow get all of the RAM initialized and available for use.

So my question is this: any way to figure out exactly what MAMEoX128 Plus does to get all the RAM working and pull it out? Then it would be simple to use that bit of code in any of the numerous shortcut xbe launchers. My thinking is this can be used to launch VC3. The xbe launcher is started, it initializes all the RAM, then it launches VC3.

Does this exist or am I asking about something that was solved long ago? I know launching MAME first then VC3 is a small thing but I tend to like things to be as simple as possible and a single xbe launch would be simpler than running MAME first then VC3.

 

I think you can have XBMC initialize all the ram.

 

XBMC does show all the ram

 

yeah im not sure, I just launch mame first myself. It's annoying basically, I would love a fix

 

Id be curious to know what would happen if you, say, used Ram Delimit on the dashboard.

 

I couldn't find a download for some reason...

From what I did find I don't think it would help. Ram Delimit just hunts for .xbe executables and removes the 64MB limit some of them have. I don't have this problem. Even with all 128MB active from launching MAME all my games run fine. I guess it's something in the IND-BIOS.

 

It comes down to what is causing the other 64mb to not be seen on launch. It could very well be a bios problem, or it could be something else.

 

Methinks it has something to do with the dash. XBMC seems to be capable of using all the RAM at start up whereas UnleashX was designed with only 64MB in mind. So while the BIOS allows for it the dash doesn't. No problem. I'm going to see about switching over to XBMC if I can get the classic stock dash skin to work on the latest release. Should fix the problem once and for all.

 

Maybe MAMEoX128 stores any additional information in eeprom? in this case, more RAM? For me, the problem occurs in all programs, games and emulators that can take advantage of additional RAM. My xbox recognizes full 128MB without running mame128 but when a program starts to use the extra RAM everything is running very very slow. MAMEoX128 solves the problem until a hard reset.