PsyBlade said:are you sure the files are the same?
maybe riped with different settings?
QUOTE(9th_Sage @ May 5 2010, 12:12 PM) I don't understand this either. WBFS files, which you'd probably get if you'd been ripping games to FAT32, should take up about the same amount of space as the games on NTFS would (be they WBFS files or sparse files).
apoptygma said:smf said:Once you have games in .wbfs files, then storing them split every 4gb is irrelevant (as long as you store the games in directories, which isn't hard).
I've got my split files *not* in directories and it works fine - Is this expected? I mean by that all my .wbfs files are in a wbfs folder, including the split ones... I've read before they are supposed to have their own sub-folders but when I did it I just threw them right in with the rest and it was fine. I'm guessing if the game tries to read data in the second 'chunk' i'm going to get a crash? I should probarbly fix this. What's the naming convention for the folders? just the disc ID?
ciris said:(since discovering CFG usb loader boots .iso's, my next project will be to convert all the wbfs titles to sparse .iso's. for easy burning to disks)
Wever said:Honestly...I don't get this concern. Ever played a PC game? Back there, it's as normal as can be that games are "split" in multiple files, and it's never an issue. Serious: I have used split files for MONTHS now, and I have yet to see a first error because of it*, either in the loader or the game itself. And considering you're using it as well...what kind of errors did you have?apoptygma said:I guess I'm more concerned about other issues like the >4gb files not being split causing issues, or for some reason a loader not working.
*I'm not counting uloader here. The .ciso files it uses apparently can't be split on a FAT32 partition.
OrGoN3 said:The question is, has anyone had problems by NOT splitting wbfs files and on an NTFS partition?
smf said:OrGoN3 said:The question is, has anyone had problems by NOT splitting wbfs files and on an NTFS partition?
It's supposed to work. You could get problems if there is a bug in the loader, but that could happen no matter what format you use.
usb loader gx definately is more stable if you use WBFS files on FAT32 (stick to rev 921 + hermes v4).
dwmyke said:My reason for having NTFS was the fact that formatting FAT32 in windows only lets you use 32 gig partitions. I'm sure there's some way around that though...
dwmyke said:My reason for having NTFS was the fact that formatting FAT32 in windows only lets you use 32 gig partitions. I'm sure there's some way around that though...
smf said:dwmyke said:My reason for having NTFS was the fact that formatting FAT32 in windows only lets you use 32 gig partitions. I'm sure there's some way around that though...
http://www.ridgecrop.demon.co.uk/index.htm?guiformat.htm
smf said:ciris said:(since discovering CFG usb loader boots .iso's, my next project will be to convert all the wbfs titles to sparse .iso's. for easy burning to disks)
I'm intrigued, how much time do you actually spend burning iso's to disc?
Edhel said:I like being able store other files on my external drive, some would be over 4GB. Also the fact NTFS will allow me to defragment my drive properly (folders included) without doing anything special.