Post by: obcd on July 20, 2010, 02:40:00 AM
If you have a debug recovery disk image, you can extract that iso with the Qwix program. It will show everything that is installed on the C and E partition of a debug xbox. Most of the stuff is the same on a retail xbox. You just need to ftp the missing parts to your xbox C and E partitions. They can coexist perfectly with the retail dash files.
With everything set up as expected, you can launch the pbl. It will load the debug bios, and that one will launch the debug dash. Mission completed.
A retail xbox only has 64 meg of memory while a debug one had 128 meg of memory.
I don't think that 64 meg is enough to run your game under the debug dash.
regards.
Post by: gruntlord6 on July 20, 2010, 08:18:00 AM
QUOTE(obcd @ Jul 20 2010, 02:40 AM) 
The Kingroach ndure Toolset creates a ndts folder on the E partition. It contains a version of the Unleashx dashboard used to tune your softmod. (I am unsure if the krazy ndure does the same thing.) The default.xbe in that folder is a version of the Phoenix Bios Loader. It loads a new BFM bios in your xbox ram. Before we had the nkpatcher, it was used in softmods to launch another (patched) bios. It can also launch a debug bios version.
If you have a debug recovery disk image, you can extract that iso with the Qwix program. It will show everything that is installed on the C and E partition of a debug xbox. Most of the stuff is the same on a retail xbox. You just need to ftp the missing parts to your xbox C and E partitions. They can coexist perfectly with the retail dash files.
With everything set up as expected, you can launch the pbl. It will load the debug bios, and that one will launch the debug dash. Mission completed.
A retail xbox only has 64 meg of memory while a debug one had 128 meg of memory.
I don't think that 64 meg is enough to run your game under the debug dash.
regards.
it is, its a requirement to run real time halo for halo 2, which is the reason im doing this.