Print

[JbOnE]

has anyone else had a problem playing Halo on a devkit xbox ?
here's the setup - complex 4627 debug bios and the complex 4627 debug dash. all other games seem to work except for Halo i did a few searches for patches etc.. in a few forums and havem't seen anything on it yet. tried it from the original disk and form the hard drive - looks like it's gonna launch but then hangs at a black screen b4 the "MS" intro.bik. any help would be appreciated seeing as how i am dying to use the vid capture tools to make some really sweet Halo vids - thx in advance for any help

pEAcE
JbOnE

[EvilWays]

There's something called nodebug that i think you use for halo on a debug box

[JbOnE]

 that bites if it can't run in debug  
anyone know if someone has yet (or what to look for in the xbe to change) altered Halo to run with debug ? thx again

pEAcE
JbOnE

[BCfosheezy]

I'm having the same problem. I got nodebug and ran halo but I lost all debugging functioanlity... which did not suprise me because if you read the readme provided it states that it gets Halo to run by turning debugging off. It goes from the debug console to the msdash after running nodebug. Then you have to use a retail cd. Then you cannot take screen capture or anything. I think we're going to have to resort to stripping the xbe down. I don't know how or what to take out to make the xbox think Halo's in developement. That is really what we need here.

[JbOnE]

I was thinking along the same lines. I tried playing around with the xbe in dexbe - patched it for debug and turned on the debug flags - same deal - black screen hang right b4 MS intro.bik. So now I'm thinkin it's not a prob with a debug flag, especially since any other retail copy of a game I try works fine. I'm leaning more towards a memory issue now. Figure the debug client running is resident in the ram, and if Halo is setup to use either all of that ram or an adress being used by the debug client, then it would stop loading when it reaches that point, which is what it appears to be doing. Again - just a theory - but I'm hopin it will spark other theories so we can finally run Halo with the debug on (cuz we all know it's not about playing it lol it's what we want to be able to do with it   ) I look to the masters for help here

pEAcE
JbOnE

[JbOnE]

BCfosheezy - I was workin on that output from xbwatson too still haven't found a refence to the

EX: ExAllocatePool (0005D000) returning NULL

yet. But still tryin heheheh. There are a ton more cheats in there to unlock as well as being able to get the video feed dumped striaght to the pc (which is really my goal). So I'll be goin on this till I eventually pass out tonight lol. So if you find anything else - post
My latest attempt at xbe tinkering was to disable the preload for most of the functions - still no luck So back to that NULL thing ....

pEAcE
JbOnE

[knepley]

tatx dual debug bios playing halo fine here

[BCfosheezy]

well after your post I started thinking along these lines... bear with me. If you use the latest evox dash and you have your ethernet plugged it, it will hang like this too. It does it while loading halo for me all the time. I will boot it from evox dash and it hangs at this exact same spot. I am thinking that maybe it has something to do with system link games or some type of networking issue.

EDIT: I figured since it is a debug xbox I might as well view the debug info right?
Here it is:

Xbox image loaded: DeviceHarddisk0Partition1gameshalodefault.xbe
This XBE was linked with  XAPILIB.LIB version 1.00.3911.01
This XBE was linked with     D3D8.LIB version 1.00.3925.01
This XBE was linked with    D3DX8.LIB version 1.00.3911.01
This XBE was linked with   DSOUND.LIB version 1.00.3936.01
This XBE was linked with  DSOUNDH.LIB version 1.00.3937.01
This XBE was linked with    XNETS.LIB version 1.00.3911.01
This XBE was linked with XBOXKRNL.LIB version 1.00.3911.01
This XBE was linked with     LIBC.LIB version 1.00.3911.01
EX: ExAllocatePool (0005D000) returning NULL

NOTE: JbOnE for your theory: The debugger uses 1288 kb of memory (322 pages).

INFO on Xswitch: Turns off debug mode so complex 1.02 will even run certain retail games like halo (they don't work on complex1.02 due minor bug). It releases and renews the ip adress incase a network card has problems and the connection dies.

[JbOnE]

QUOTE (knepley @ Jun 2 2003, 08:22 PM)

tatx dual debug bios playing halo fine here

with debug ?? if so what version of tatx are u using ??

pEAcE
JbOnE

[BCfosheezy]

QUOTE

tatx dual debug bios playing halo fine here

Please state your setup. Are you booting the dev dash or just booting evox?
Are you able to take in game screenshots of halo?

[JbOnE]

BCfosheezy - never mind mr.tatx-dual-debug-workin-with-halo. what's the saying lol - blowing smoke up our asses hehehe - just popped the tatx dual debug on the dev system - works the same - no halo - and now it won't let me reflash it least i still have debug functions - back to the drawing board...

[BCfosheezy]

Well if Halo will not load with debugging turned on... this may be a good time to try the stealth feature of my chameleon.

[JbOnE]

k- after trying for all the quick fixes so far i dug into our nice little error...

EX: ExAllocatePool (0005D000) returning NULL

from what i've been able to dig up so far i was kinda right with my 1st theory about the memory issue. ExAllocatePool is trying to allocate memory to initialize and since the dbug is resident in it - it's freezing up (returning the NULL value) if the value you posted of debug memory usage is correct (1288) then i'm thinking if we can reset the base value for pool allocation to let's say 1289 - we might be in business. now all i gotta do is learn how to do that heheheh......

[BCfosheezy]

the answer to all of our problems lies in the hands of undead. He is the head of team-assembly who made the tatx dual debug bios and he is active in these forums. Let's both pm him and see if he will help us.

[JbOnE]