Posted 17 February 2010 - 05:52 AM
Posted 17 February 2010 - 10:30 AM
If you have a retail converted xbox, it only has 64MB of memory. Debug unit's had 128MB.
The debug bios takes more memory and the debug dash is bigger as well.
I remember people using very old debug dashes to take screenshots from the Halo programs.
The newer ones simply used 2 much memory.
Another issue is that original debug biosses don't run retail games. The game needs to be debug signed. Most modchip debug biosses don't have those limitation.
I know that the F patch makes the f partition visible to the xbox neiborhood.
I don't know if you can launch xbe's from there in the debug dash.
Posted 17 February 2010 - 09:07 PM
And I have the fpatch installed in the dxt directory on the E drive but the F drive won't show up in Xbox Neighborhood.
Edited by chocolatecheese, 17 February 2010 - 09:09 PM.
Posted 18 February 2010 - 12:30 AM
Posted 18 February 2010 - 01:10 AM
Posted 18 February 2010 - 08:35 PM
Are you sure that the F drive doesn't come up with another drive letter in the neighborhood?
I remember using the tatx bfm debug bios. I am not sure if it can handle a F partition bigger than 137 GB.
Posted 19 February 2010 - 07:21 AM
Posted 20 February 2010 - 09:56 AM
If I remember well, when I used an original debug bios, the f drive didn't show up as well.
If you use the phoenix bios loader, you can quickly test other debug biosses.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users