Print

[fatbastard911]

I had tried everything since I have booted up my new 4978 bios to get my retail/bought from the store halo cd to work when I turn on my fully working Xecuter 2 Pro modchip.
The Modchip works fine w/ the new bios
I have tested many other authentic and HDD games and they loaded up fine.
My Halo cd boots up fine without the modchip turned on to the 4978 bios, so there isn't anything wrong with the cd.
It does not boot via: boxplorer nor Hddloader, I had tried reinstalling Halo onto my Hard-drive 2 times....
The old bios after flashing the Xbox backs loads up Halo perfectly!!!!
I think Xecuter has a flaw in their new bios.....I wonder what other games will the concur to......Any one else face this?

It just did not boot up with the new 4798 bios in any way, the screen goes black when trying to boot the first screen, + xbox reboots when pressing the eject button.
And remember I said there wasn't any problems booting the game with modchip and bios 4798 turned off...I bought the actual Halo game.......so I shouldn't be facing these problems.....And btw --> In game reset was turned off for the hell of it....

[fatbastard911]

I had tried everything since I have booted up my new 4978 bios to get my retail/bought from the store halo cd to work when I turn on my fully working Xecuter 2 Pro modchip.
The Modchip works fine w/ the new bios
I have tested many other authentic and HDD games and they loaded up fine.
My Halo cd boots up fine without the modchip turned on to the 4978 bios on, so there isn't anything wrong with the cd.
It does not boot via: boxplorer nor Hddloader, I had tried reinstalling Halo onto my Hard-drive 2 times....
The old bios after flashing the Xbox backs loads up Halo perfectly!!!!
I think Xecuter has a flaw in their new bios.....I wonder what other games will the concur to......Any one else face this?

It just did not boot up with the new 4798 bios in any way, the screen goes black when trying to boot the first screen, + xbox reboots when pressing the eject button.
And remember I said there wasn't any problems booting the game with modchip and bios 4798 turned off...I bought the actual Halo game.......so I shouldn't be facing these problems.....And btw --> In game reset was turned off for the hell of it....

[chinmi]

4978 is still in beta stages, wait for a final release version before you do flash it again...

[Al_Ghazi]

Weird.

I just moved to 4977 and have no problems.  If I were you I would just flash back to 4977....

Gaz

[heinrich]

I also cannot load Halo from the retail disc with 4978.  I havent tried it off the hd yet, but I would imagine that the same thing would happen.

[heinrich]

QUOTE (flat235 @ Aug 24 2003, 10:28 AM)

Just a quick question.. ive not downloaded 4978 (yet) - but does the FTP server still operate when you are in a retail game?? (anyone who knows me probably knows what im getting at here ) Cheers TD

http://forums.xbox-s...38&t=93580&st=0

QUOTE

The ftpd DOES NOT RUN ALL THE TIME. XEERO was right in this. You Press A, a nice X^3 FTP SERVER screen pops up, and there you are. So, no, you cant ftp to xbox while playing halo

[Chugalug]

Yeah I had the same thing with 4978, Bought Copy and HD rip don't work, screen just goes black.

[ProstheticHead]

QUOTE

.......you cant ftp to xbox while playing halo.......

sorry that cracked me up as ya cant even PLAY halo!  
also anyone noticed any other games that dont work with new bios? as its pritty odd all they added was the FTP nothing else was changed i have a feeling 1mb bios may not be a good idea becouse the bios is loaded in ram right? so then Halo being a hungrey bugga dosnt have the ram there it needs as its only expecting 256kb taken away.

[Xeero]

QUOTE (ProstheticHead @ Aug 25 2003, 01:36 PM)

QUOTE .......you cant ftp to xbox while playing halo....... sorry that cracked me up as ya cant even PLAY halo!   also anyone noticed any other games that dont work with new bios? as its pritty odd all they added was the FTP nothing else was changed i have a feeling 1mb bios may not be a good idea becouse the bios is loaded in ram right? so then Halo being a hungrey bugga dosnt have the ram there it needs as its only expecting 256kb taken away.

Well, I don't know that Halo "expects 256kb taken away".  I know that the MCPX grabs 256K from the 1.2+ TSOPs, as they are only 256K.  But how much does it grab from the TSOPs in 1.0/1.1, where the onboard chips are 1MB?  I'd assume it doesn't just grab the first 256K unless you had done some extra soldering to define the banks.  I'd say that the 1MB of BIOS in memory will NOT cause a problem with any games (though possibly with emulators).  If it can't run Halo or any other games, I think the problem is something else.

[JayDee]

Tried it with 4978 bfm and Halo is a no go.

If anyone wanted to know that is.....

[lantus]

QUOTE (Xeero @ Aug 25 2003, 05:56 PM)

QUOTE I'd say that the 1MB of BIOS in memory will NOT cause a problem with any games (though possibly with emulators).  If it can't run Halo or any other games, I think the problem is something else.

its not the 1 meg bios in memory that causes problems. Its the amount of memory required by the ftp server to run.

consider this :

lets say i embed an xbe in the bios which does the following

BYTE *foo = malloc(32*1024*1024);

i have just allocated 32 megs of memory, leaving less than 32 left to the xbox.

this means games/apps/homebrew will stop working because they were coded with more memory space in mind.

this is why i think 1 meg bios's will blow

[ProstheticHead]

QUOTE (lantus @ Aug 26 2003, 12:38 AM)

QUOTE (Xeero @ Aug 25 2003, 05:56 PM) QUOTE I'd say that the 1MB of BIOS in memory will NOT cause a problem with any games (though possibly with emulators).  If it can't run Halo or any other games, I think the problem is something else. its not the 1 meg bios in memory that causes problems. Its the amount of memory required by the ftp server to run. consider this : lets say i embed an xbe in the bios which does the following BYTE *foo = malloc(32*1024*1024); i have just allocated 32 megs of memory, leaving less than 32 left to the xbox. this means games/apps/homebrew will stop working because they were coded with more memory space in mind. this is why i think 1 meg bios's will blow

that could be it but isnt the XBE only ran and allocated memory when you hold a when booting?

[unknown_letter]

It does not if you run it using the 4978 BIOS. However, you can try starting the x-box using the original ms BIOS and you will see the original ms dashboard coming up, and it will work fine to play halo. This works at least fine for me...I have the NitroxX chip in my x-box. It does not work if you select "ms dashboard" in your current dashboard (like evoX) since it will load the dashboard but it is still running on the 4978 BIOS. Hope this helped.

[unknown_letter]

It does not if you run it using the 4978 BIOS. However, you can try starting the x-box using the original ms BIOS and you will see the original ms dashboard coming up, and it will work fine to play halo. This works at least fine for me...I have the NitroxX chip in my x-box. It does not work if you select "ms dashboard" in your current dashboard (like evoX) since it will load the dashboard but it is still running on the 4978 BIOS. Hope this helped.

[heinrich]

Halo runs fine for me with 4978.03 now.