Firstly, great work on UnleashX!

I think i've finally found a replacement for Evox after mucking around with Avalaunch and MxM, but never really finding that they suited my needs...


Ok, after installing UnleashX, doing a bit of tinkering and getting the menu the way i wanted, i noticed that whenever i'd ftp in (using SmartFTP), F: Drive wouldn't show up.

However, It shows up in the File Explorer (ie. EnableDriveF = True). And all my progs etc on F: work from the menu.


Any ideas?

tri refreshing your ftp client

are the other drives showing?

if so (meaning only F: won't show up) go to settings in unleash. At the very bottom where it says Enable Drive F, make sure that it says YES.

Then reboot, you should be golden.

rake

For the record, yeh, the other drives were showing...

I think it might have been a bug in the Config.xml file. Cause when i uploaded the original with only sligh network mods, it was showing again. Also I did go into settings and make sure it said YES next to Enable F. ALthough it was already set in my Config.xml file so i dunno...

It's smartFTP caching the folders. By default, most FTP clients does this, just turn this off, you don't need it anyway in a LAN/Direct connection scenario.

One thing that I've found is retail bioses can't access the f drive. It will appear empty even after ftp refresh if booted with an exploit without PBL, or PBL loading a retail bfm bios.

That's a known fact. The F partition doesn't exist on retail Xboxes so we would expect that a retail BIOS wouldn't recognize it. You need some sort of hacked BIOS in order to use F or G.

Qwix has no problem upping games to F: on the box i just TSOP'd (4907.67, 200gb) but flashFXP can't get F at all either ... stock config.xml, F enabled ...

Unless its a type-o, thats a very old bios. Its up to 4983 now.

my bad, went from memory without looking ... i flashed his with my custom 4979.06_stfu_1mb.bin, same one as on my box ... my F works, his doesn't show up ... wtf?