Feb 17 2010, 05:52 AM
First off, what directory in the F: drive of the xbox do you have to put executables in to get them to show up in the launcher? I already installed the f drive hack. Also I noticed that certain games will launch in the debug bios while other ones cause an error. Halo and Halo 2 don't seem to run but Unreal Championship, Riddick, and GTA San Andreas ran without any problems. What determines if a game will run or not in the XDK bios?
Feb 17 2010, 10:30 AM
The biggest issue when running games under the debug bios is memory.
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.
Feb 17 2010, 09:07 PM
ah ok, makes sense. So you're saying that whether the game will run or not depends on its memory usage? (This is Yoshiro's v1.6 debug bios.) Meaning that games like GTA and Riddick use less RAM than Halo? (I can get the main menu for Halo to launch but it errors as soon as i load up a level. Halo 2 won't load at all.)
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.
Feb 18 2010, 12:30 AM
I have the extra RAM chips for my Xbox, I just don't trust myself to solder them in :-/
Feb 18 2010, 01:10 AM
I wouldn't trust myself with the RAM either. Especially after reading someone's post on here earlier today of them trying to upgrade the RAM and almost wrecking the entire box in the process. They were eventually able to restore the box but the RAM upgrade was a failure.
Feb 18 2010, 08:35 PM
The problem with a ram upgrade is usual that the ram's come from another board. Due to that, the pin's aren't anymore what they are suposed to be. It's also hard to tell how much heat the chip had to take in the desoldering proces. To check your soldering work properly, you almost need a microscope. I also don't know how well a xbox behaves with 128MB ram, if the bios is the normal retail bios like with a softmod.
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.
Feb 19 2010, 07:21 AM
Yeah, I am not really interested in taking the risk with a RAM upgrade. Just seems too tedious. Props to the people who have successfully done it though. Anyways, I wasn't able to spot my F partition in Xbox Neighborhood. And yes, I do believe that F can only handle 137 gb, but that isn't an issue since my HDD is 80 gb. I bought it several years ago when memory was still expensive.
Feb 20 2010, 09:56 AM
I think it's the bios.
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.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here