Print

[Mc2Elite]

I currently have XDI installed on my v1.6 'box and am using XIG 1.3, however when I run X8RD Xbox Image Grabber and Load Halo 2 1.0 I can not load any maps. I can go through the menus but otherwise I got nada.

Help please.

This post has been edited by Mc2Elite: Mar 26 2006, 07:38 AM

[Drilus]

the debug bios for 1.6 is too big. Halo2 can't allocate enough memory. Your out of luck right now. only way i see it is if someone released a new smaller 1.6 debug bios.

[Mc2Elite]

Okay. Thanks anyway.  

[Mc2Elite]

Wait CowFromMars has a BIOS that lets him load the maps. I can load Halo 2 and take pics with XIG while in the menus I just can't load any maps.

[Drilus]

he's using the exact same bios you are. also, yes he can load maps but it's not perfect. the bfm debug bios is simply too big. but don't let me stop you from trying.

[noselessmonk]

It might also depend on the specific xbox unit. Some get better/more stable RAM chips in them than others.

[Mc2Elite]

Well, I guess you can not inform on what to do in order to load the maps. Even if it isn't perfect?

[noselessmonk]

Well, I just tried it on my bro's 1.6. It would seem that it won't load right. With autoupdates on, it doesn't load anything(stays at black screen). With them off, it goes to the mainmenu, but all the profiles are missing and it doesn't load any of the maps. I guess the adouber bios is too big for 64Mbs RAM...

[Mc2Elite]

Hmm, I am still confused. I just need to load a map in Halo 2. The BIOS is too big, but Cow' can run the maps? I do not see how he could do this. Do I need a different BIOS, or is there something that I can change to let it load the maps?

[noselessmonk]

Does Cow run it on a 1.6 box? Because at the moment, there is only one BFM debug bios that'll work on a 1.6. And it doesn't work for Halo 2 as far as I've been able to see. Either Cow has a different bios that's not been released yet, he is not running a 1.6 box or he has a modchip flashed with another debug bios(are there any flashable debug bioses for 1.6 that are small enough for Halo 2? ; I don't have a chip).

[deadparrot]

It's not down to the BIOS.  It's XBDM.DLL which is being over written in memory.  There is a thread in the Development forum dedicated to which versions of XBDM.DLL perform better under 64MB of RAM.

[pdottz]

the good news here is that no matter what xbdm.dll you're using, debug mode in the ind-bios will always allow halo2 to run perfectly with no memory issues. i've been running it like this since ind-bios was released with debug mode. no problems.

now for the sad news. ind-bios doesn't support 1.6, and as far as i know, no other bios will allow you to load maps in halo2 (dont even think x2 cause that one just locks up as well when going past the main menu.)

i've tried various versions of xbdm.dll with ind-bios and they all work flawlessly.
they however do not work so well with the other debug bios'.

easiest solution? buy a used xbox 1.5 or below and toss on ind-bios.

ind-bios is all you should ever need. period.

fyi: i have a 1.0 stock xbox with 64 megs of ram.

[Drilus]

QUOTE(deadparrot @ Mar 27 2006, 08:34 PM)

It's not down to the BIOS.  It's XBDM.DLL which is being over written in memory.  There is a thread in the Development forum dedicated to which versions of XBDM.DLL perform better under 64MB of RAM.

it's the size of the bios.

[noselessmonk]

Pretty much what I said. The bios is taking too much room up in RAM for Halo 2 to fit. If you had 128Mb RAM it would work. But I guess that's out of the question for 1.6 boxes.

The only thing I could say is just wait for/if a new bios is released that is smaller.