Recovering the unused space on your hard drive for storing other things would be the prime concern.TeenTin said:Any STRONG reason to give up the WBFS HD and use FAT HD instead ?
Dr. Clipper said:Recovering the unused space on your hard drive for storing other things would be the prime concern.TeenTin said:Any STRONG reason to give up the WBFS HD and use FAT HD instead ?
Dr. Clipper said:Either rip it in the loader or use the command line app to convert it. Games need to be split into segments of less than 2GB and that is doen for you by both the loader and wbfs_file.TeenTin said:I have a question :
For a FAT32 HD, how can I put the double layer games (e.g. SSBB) which is about 8GB into it ?
N.B. Biggest file in FAT32 is 4GB.
Thanks !
oggzee said:wbfs_file_1.0_osx.tgz
http://sharebee.com/6f600706
Mac OSX build of the tool.
Untested! (It should work though.)
I just applied the osx patches to the wbfs tool by eddanx and gibbed and rebuilt.
the included binary is for i386 and ppc:
wbfs_file: Mach-O universal binary with 2 architectures
wbfs_file (for architecture i386): Mach-O executable i386
wbfs_file (for architecture ppc): Mach-O executable ppc
however i don't know if this works on ppc correctly. it needs to be tested, maybe run on both windows and osx and compare if the resulting .wbfs file is the same.
remarks for the users : keep in mind that by default the application splits the discs as if it was a FAT16 partion (2gb limit), but most of us will be using FAT32 partitions (4gb limit). both "split size" will work, but using the appropriate size will allow you to keep nearly all your game not splitted..
I think that I am not too far from reality when I estimate that :
around 60% of the games are below 2gbÂÂ---> no split :)
around 30% are between 2gb and 4gb ---> fat16 = split :(ÂÂand fat32 = nosplit :)
around 10% are over 4gb ---> fat16 and fat32 = split.
so if you use "-s 4294900736" you will keep nearly 90% of the games unsplitted...
the 4,294,900,736 is kinda weird value, but I tested as much as I could and it seems that it is the biggest file that fits... maybe you have more knowledge and you can explain why.. because I thought it should be
2^32 - 1 = 4,294,967,295 rounded toÂÂ4,294,966,784 to make it a multiple of 512 as requested by your app
redia said:1. when adding a game are you ripping the whole disc, or only the game partition ? (I like to keep the whole disc for backup purposes, I don't care about the little extra size)
by default all partitions are copied
version 1.1 adds options -a,-g,-1 to control that behaviour
But apparently the copy all partitions does not work for some VC/WiiWare partitions, as reported by wiimm, so using -1 for 1:1 copy should probably solve that issue - but you'll always get the full size file instead of scrubbed. And also note that copy 1:1 is not tested thoroughly yet.
2. would it be possible to extend a little bit the option "-s SIZE"... maybe something like
"-s [SIZE]" for any specific value a user might want
"-fat16" for the 2gb limit
"-fat32" for the 4gb limit
it would be possible, but my testing shows that the libfat that is used by the loader is unsuitable for files larger than 2GB. So, while it's true that FAT can hold up to 4GB files it seems files larger than 2GB will not work properly. On the other hand I tested this very briefly, so if you have time go ahead and try if splits larger than 2GB actually work or not.
the 4,294,900,736 is kinda weird value, but I tested as much as I could and it seems that it is the biggest file that fits... maybe you have more knowledge and you can explain why.. because I thought it should be
2^32 - 1 = 4,294,967,295 rounded to 4,294,966,784 to make it a multiple of 512 as requested by your app
Why the strange value i don't know, but maybe the max size is really 2^32 - cluster size instead of 2^32-1 or something, or you are hitting some other bug in windows (or linux?) implementation...
3. maybe I missed it, but is there a possibility to convert a game from an iso to a specific directory ? (using two different discs should/could make the conversion much faster)
Yes, using the create command:
wbfs_file d:/destination/gameid.wbfs create e:/source/game.iso
4. the function are confusing. for example
extract_iso
extract_wbfs
extract_wbfs_all
shouldn't they be :
extract_iso
extract_wbfs
extract_wbfs_all
for the most common cases yes, but running it on files will work too. in fact converting an wbfs to iso (by just using the .wbfs file as a parameter without commands) is same as running extract_iso with appropriate parameters
5. is import/export to ciso format planned ?
no
6. last but not least, could we use titles.txt for the info file ?
heh, the cfg loader on wii actually does that when installing
but I haven't added titles.txt support to the wbfs_file tool.
it should be easy to add but i have other work to do first.
so to conclude,... info file can be renamed afterwards to whatever you want.
redia said:1. when adding a game are you ripping the whole disc, or only the game partition ? (I like to keep the whole disc for backup purposes, I don't care about the little extra size)
by default all partitions are copied
version 1.1 adds options -a,-g,-1 to control that behaviour
But apparently the copy all partitions does not work for some VC/WiiWare partitions, as reported by wiimm, so using -1 for 1:1 copy should probably solve that issue - but you'll always get the full size file instead of scrubbed. And also note that copy 1:1 is not tested thoroughly yet.
2. would it be possible to extend a little bit the option "-s SIZE"... maybe something like
"-s [SIZE]" for any specific value a user might want
"-fat16" for the 2gb limit
"-fat32" for the 4gb limit
it would be possible, but my testing shows that the libfat that is used by the loader is unsuitable for files larger than 2GB. So, while it's true that FAT can hold up to 4GB files it seems files larger than 2GB will not work properly. On the other hand I tested this very briefly, so if you have time go ahead and try if splits larger than 2GB actually work or not.
the 4,294,900,736 is kinda weird value, but I tested as much as I could and it seems that it is the biggest file that fits... maybe you have more knowledge and you can explain why.. because I thought it should be
2^32 - 1 = 4,294,967,295 rounded to 4,294,966,784 to make it a multiple of 512 as requested by your app
Why the strange value i don't know, but maybe the max size is really 2^32 - cluster size instead of 2^32-1 or something, or you are hitting some other bug in windows (or linux?) implementation...
3. maybe I missed it, but is there a possibility to convert a game from an iso to a specific directory ? (using two different discs should/could make the conversion much faster)
Yes, using the create command:
wbfs_file d:/destination/gameid.wbfs create e:/source/game.iso
4. the function are confusing. for example
extract_iso
extract_wbfs
extract_wbfs_all
shouldn't they be :
extract_iso
extract_wbfs
extract_wbfs_all
for the most common cases yes, but running it on files will work too. in fact converting an wbfs to iso (by just using the .wbfs file as a parameter without commands) is same as running extract_iso with appropriate parameters
5. is import/export to ciso format planned ?
no
6. last but not least, could we use titles.txt for the info file ?
heh, the cfg loader on wii actually does that when installing
but I haven't added titles.txt support to the wbfs_file tool.
it should be easy to add but i have other work to do first.
so to conclude,... info file can be renamed afterwards to whatever you want.
Macintosh:Grigio cambric$ ls -al
total 27539232
drwxr-xr-xÂÂ7 cambricÂÂstaffÂÂÂÂÂÂÂÂ 238 26 Ott 23:21 .
drwxr-xr-xÂÂ5 cambricÂÂstaffÂÂÂÂÂÂÂÂ 170 25 Ott 00:48 ..
-rw-r--r--@ 1 cambricÂÂstaffÂÂÂÂÂÂÂÂ6148 26 Ott 23:06 .DS_Store
-rwxr-xr-xÂÂ1 cambricÂÂstaffÂÂ4699979776ÂÂ9 DicÂÂ2008 family(compress).iso
-rwxr-xr-x@ 1 cambricÂÂstaffÂÂÂÂÂÂ136384 22 NovÂÂ2009 wbfs_file
Macintosh:Grigio cambric$ ./wbfs_file family(compress).iso
-bash: syntax error near unexpected token `('
Macintosh:Grigio cambric$ ls -al
total 27539232
drwxr-xr-xÂÂ7 cambricÂÂstaffÂÂÂÂÂÂÂÂ 238 26 Ott 23:24 .
drwxr-xr-xÂÂ5 cambricÂÂstaffÂÂÂÂÂÂÂÂ 170 25 Ott 00:48 ..
-rw-r--r--@ 1 cambricÂÂstaffÂÂÂÂÂÂÂÂ6148 26 Ott 23:06 .DS_Store
-rwxr-xr-xÂÂ1 cambricÂÂstaffÂÂ4699979776ÂÂ9 DicÂÂ2008 family.iso
-rwxr-xr-x@ 1 cambricÂÂstaffÂÂÂÂÂÂ136384 22 NovÂÂ2009 wbfs_file
Macintosh:Grigio cambric$ ./wbfs_file family.iso
Converting family.iso to WBFS
Writing: RZ9PG9.wbfs
adding RZ9PG9 Family Party: 30 Great Games...
Done inÂÂ0:01:30ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
Info file: ./RZ9PG9_Family_Party__30_Great_Games.txt
Macintosh:Grigio cambric$ ls -al
total 47958824
drwxr-xr-xÂÂ11 cambricÂÂstaffÂÂÂÂÂÂÂÂ 374 26 Ott 23:27 .
drwxr-xr-xÂÂ 5 cambricÂÂstaffÂÂÂÂÂÂÂÂ 170 25 Ott 00:48 ..
-rw-r--r--@ÂÂ1 cambricÂÂstaffÂÂÂÂÂÂÂÂ6148 26 Ott 23:06 .DS_Store
-rw-r--r--ÂÂ 1 cambricÂÂstaffÂÂ1054867456 26 Ott 23:26 RZ9PG9.wbfs
-rw-r--r--ÂÂ 1 cambricÂÂstaffÂÂÂÂÂÂÂÂÂÂ38 26 Ott 23:26 RZ9PG9_Family_Party__30_Great_Games.txt
-rwxr-xr-xÂÂ 1 cambricÂÂstaffÂÂ4699979776ÂÂ9 DicÂÂ2008 family.iso
-rwxr-xr-x@ÂÂ1 cambricÂÂstaffÂÂÂÂÂÂ136384 22 NovÂÂ2009 wbfs_file
Macintosh:Grigio cambric$