I have a retail 1.0 with a 250GB HDD and PCBioXX Chip. My dashboard boots from F:, while my apps and games reside on F: as well.

I installed Phoenix Bios Loader in C: with the debug dash (cpx-debug-dashboard4627). PBL boots 4627_Debug_BFM-1MB.bin and TATX_Debug_BFM.bin (each 1mb) just fine. My debug dash appears and all is good.

My problem is that I cannot boot any apps or games from the F: drive. It's as if the debug system doesn't recognize F:. I've edited the evoX.ini in the E:/devkit/samples/evox to search F:, but no luck. It recognizes stuff on E: just fine. I've also installed fdrive.dxt in E:/devkit/dxt, but that seems to only affect the PC side of the system.

When I use the Xbox Neighborhood on my PC, I see an F: labled "Memory Unit 1A (F:)", but when I dive into it, it's empty. I can make folders here, but when I search for them on my Xbox (using boxplorer), what I just made on the PC is not there.

Is there a way I can launch games from my F: (E: just won't cut it)? Does the problem have to do with my beyond 137GB HDD? Is it BIOS related? Any help or sugestions would be MUCH appreciated! Thanks!!!

I haven't had any success with PBL recognizing drive F with any of the debug BIOSes. Using the non-BFM BIOS on a chip or TSOP, however, works perfectly.

Thanks for the reply. Looks like i'll be switching BIOSs until I get a new chip...

In order to launch files from the F drive, you have to double click them from your computer. You can't actually browse them from the xbox, just the comp. I would say that it's probably the pbl causing nothing to show up. why not use the debug bios all the time and put your dashboard in the tools folder. Only problem you might find is Halo. (Won't play unless you turn debug off) and one other game, can't remember which one. Use PBL to load a different bios that way. You could even use the dashboard.xbx file to run evox, or maybe edit it to run a different dash. That would be cool.

Thanks for your help P. Just ordered a SmartXX chip to be able to boot different BIOSs just for this reason.

You mentioned running the debug dash as an app. How would I do this? I have cpx-debug-dashboard4627 and it gives me a new C and E to copy over. Would I still need to copy over the existing MS dash?

I want to play Live (once in a while) so my ultimate setup would be:

Boot different BIOS when wanted (chip has this function)
Have Ava, evoX, etc boot as my dash (I know how to boot retail dash/modchip dash)
Have the debug dash as an app to start up to take screenshots/vid capture

I'm just stuck on how to make the debug dash and app due to the new partitions it wants me to copy over and overwrite. Any help/suggestions would be GREAT!