HaloMods "Classic" Read-only Archive

I can't seem to get it working. I know about the tutorial, and everything seems to work fine up until I launch the program from my apps. It says Loading BIOS, flashes to a black screen with lines, and then back to a black screen and freezes.

I'm using UnleashX, and it's located in my E: drive. It seems to freeze as it's loading my dashboard, so maybe I have it placed in the wrong spot?

What version xbox do you have? I have a v1.6 and have always had a little trouble trying to do debug stuff. Also, make sure you have your autoupdate disabled before you try to launch Halo 2.

You find your Xbox version in the MS Dashboard Settings, right? Or is it here?

If it's in the dashboard, I have v1.5. To be precise:

K: 1.005838.01
C: 1.005960.01

According to this site though, I'm using v1.6b.

Follow my advice and connect with RTH during the loading screen. That will fix a few problems once you are able to get halo loaded.

Okay, thanks.

But first I need to get my dashboard loaded.

Sorry to bump this, but I've gotten it working. I copied my dashboard along with the dashboard.xbx file to the C: drive, so it would appear in the dashboard list. (maybe this is what's screwing up Halo 2 loading? EDIT: Nope, as I can load other games just fine)

For anyone that has the problem of the app loading to a black screen and then freezing, just choose a different Xbox version in the debug installer. 1.5 didn't work for me, so I tried 1.6, and it worked perfectly!



Now I just need to get Halo 2 to run.

I boot into the debug dashboard, connect with Entity (successful) and then run Halo 2. Black screen.

I'm guessing this has something to do with the AU, because other games load fine under the debug dash. Could someone please tell me where the AU is? It's not in /E/Games/Halo 2/, is it? Because I've tried disabling that before.

It says in the readme "Some games, however (Halo 2, for example), are problematic in that when they start up, they actually overwrite the memory space used by the xbdm.dll file. This causes your Xbox to freeze or sit at a black screen."

Which seems to be my problem. But in that same file, it says "The latest xbdm.dll file write protects it's memory. So when launching games like Halo/Halo2, which used to overwrite the xbdm.dll memory, it should now run fine."

Which ruins any hope of that being the problem.

I haven't ever gotten RTH to work before... on either xbox, with or without the AU, on nearly every other xdk version, with different BIOSs.

On my 1.6 chipped xbox, I've tried starting Halo 2 with no AU on Yoshiro's xdk BIOS. RTH says it connected but can't change anything. Tried it with H2 AU1.1. Same thing. Both on the XGI bios. Same thing.

On my debug xbox (the green thing with 128mb ram), I've tried Halo 2 with and without the AU, same thing. (Can't use XGI - be pointless too - this IS the real thing)

I try but when I do it I can't load any maps.

At least you get the menu loaded.

To get debug working on a v1.6 xbox (with Halo 2 at least), you're going to need an older version of the xbdm.dll. I really can't help you with this and I would prefer if no one discussed it as xdk files are illegal to have... If you use the latest xbdm.dll on a 1.6, the maps will fail to load due to memory allocation issues.

Don't worry, I won't ask about it here. I'm sure I'll find it on my own.

Thank you for the information!