I wanted to do similar, but how would you go about having a usb drive with ntfs, then fat32 partition load cfg from the fat but then access games on the ntfs?
is it looking for the first partition? i did ntfs then fat32. im thinkin if i did maybe fat32 first, then had an ntfs partition as 2nd, then the forwarder would read the fat first, find the app, run it, then the cfg settings would point it to the ntfs?
The HBC and forwarders will look for Cfg on either the first FAT partition of the SD card or on the drive. Cfg will look for the settings and covers in whatever partition of whatever device you load the .dol from. The device to load the games from is configurable via the "device = usb, sdhc" option and the partition is set by the "partition = WBFS1...4, FAT1...9, NTFS1...9" option. You can also locate the covers in a different device to where the settings are if you like by using the covers_url options (e.g., covers_url = ntfs:/coversgohere). Note that you won't be able to install covers with the loader if you did switch it to an NTFS partition, though.
In summary, here's the locations where things can go:
boot.dol: 1st FAT partition on SD
OR 1st FAT partition on USB
settings (config.txt etc.): same device/partition as boot.dol
covers: 1st FAT partition on SD card
OR 1st FAT partition on USB
OR 1st NTFS partition on USB (read-only)
games: Any WBFS partition, FAT partition or NTFS partition on either SD or USB
QUOTE
Dr. Clipper said:
TheGlow said:
quick question. when I go to boot a game is says loading ios 222 for fat support.
then right under says loading 222...ntfs
am I losing time here or something? whats optimal
It's just oggzee not updating some of the info messages when OMG#50 was added. It probably should say "non-wbfs" instead of "fat".
So if its nonwbfs, would I be better off then using the fat.dol even though its ntfs? any real differences?