Hacking wwt+wit: Wiimms WBFS+ISO Tools

[Wiimm]

Now it's clear. For character device i must force the fopen() variant. Thanx for all experiments.
The next version is on the way.

btw: --io=2 enables fopen() only for ISO in/out. --io=1 enables it for WBFS in/out and --io=3 for both.

 

[sylver78]

Thanks to you for this great tool and for your fast updates

I'm pretty sure that WiiJManager with wwt could be the ultimate tool for MacOS X users now that speed is the same as WBFS for Mac OS X

 

[Wiimm]

wwt: Wiimms WBFS Tool v0.39a - 2010-03-29
A command line WBFS tool set for various os.

I have updated the tool. The first post with more details is updated too.

Download this EXPERIMENTAL release:

• wwt-v0.39a-r782-i386.tar.gz : linux/i386 version
• wwt-v0.39a-r782-x86_64.tar.gz : linux/x86_64 version
• wwt-v0.39a-r782-cygwin.zip : cygwin (win32) version

Download of the previous stable version:

• wwt-v0.36a-r728-i386.tar.gz : linux/i386 version
• wwt-v0.36a-r728-cygwin.zip : cygwin (win32) version

There is also a GUI available:

• WiiJManager Multiplatform

Last changes:

wwt v0.38a r769 - 2010-03-28

- Some dtime improvements.
- wwt+wit: Option -C is not longer the short version of option --trunc.
- CISO support (EXPERIMENTAL):
ÂÂÂÂ- wdf-dump will also dump the structure and memory map of CISO files.
ÂÂÂÂ- wdf-cat will copy the extended ISO to standard output.
ÂÂÂÂ- On all places where a plain ISO is allowed as source file a CISO is
ÂÂÂÂÂÂallowed too.
ÂÂÂÂ- To force CISO-output use option --ciso or file type ".ciso" or ".wbi".

wwt v0.38b r771 - 2010-03-28

- Bug fix for wwt INIT: Wrong assertion while comparing old and new
ÂÂ calculation for WBFS geometry.

wwt v0.39a r782 - 2010-03-29

- Bug fix: New CISO files > 4 GiB have been truncated (modulo 2^32 error).
- Character devices are allowed for WBFS.
- wwt --auto: If the file /proc/partitions is not found, than all devices
ÂÂ named '/dev/sd*' and '/dev/rdisk*' are scanned for WBFS. If scanning of
ÂÂ '/dev/rdisk*' fails then also files named '/dev/disk*' are scanned.
ÂÂ Using character devices '/dev/rdisk*' will speed up wwt on apple computers.

Sources comes with GPL2. Checkout the sources directly from the SVN repository or browse the source.

 

[Blue-K]

Great work, thanks Wiimm

. It's always amazing how fast and often you update, realy, thanks

.

Now add the SNEEK-Structure for games (Extract, .bin, etc...) and Punes FST Creator/Boot.bin Updater and WWT is finished for me

.

 

[sylver78]

Tested and working perfectly on my Mac with "--auto" and "-p /dev/rdisk" (fast copy) or "/dev/disk" (slow

).
Thanks Wiimm !

 

[drh]

Quick question, am I right in thinking wbfs has a limit of 500 discs?

If so, should I be format a 1tb drive into 2 x 500gb partitions?

Is that possible with wwt format command?

 

[drh]

Great work, thanks Wiimm

. It's always amazing how fast and often you update, realy, thanks

.

Now add the SNEEK-Structure for games (Extract, .bin, etc...) and Punes FST Creator/Boot.bin Updater and WWT is finished for me

.

A few people seem to be excited over this sneek, I searched and read a few threads but still none the wiser to why the excitement!?!??

Does it just allow me to run the system off my SD card instead of the Wii's own memory (but a lot slower because its on SD) or am I missing something?

 

[Wiimm]

Quick question, am I right in thinking wbfs has a limit of 500 discs?

If so, should I be format a 1tb drive into 2 x 500gb partitions?

Is that possible with wwt format command?

No problem but --auto does'nt work because there are always 2 devices available.

btw: Which usb loader do you use? I know that gx support sector sizes >512, perhaps other loaders too. With sector size 1024 there is space for 1012 discs. try "wwt analyse /dev/sdx" to see calculations with different sector sizes.

 

[Wiimm]

Great work, thanks Wiimm

. It's always amazing how fast and often you update, realy, thanks

.

I have some free days before going to holiday later in this week. And building a release including generating announce message is mostly automatically done by scripts. On the other hand I know my code very well and I know what to do. So changes like enabling character devices are easy.

 

[drh]

Quick question, am I right in thinking wbfs has a limit of 500 discs?

If so, should I be format a 1tb drive into 2 x 500gb partitions?

Is that possible with wwt format command?
No problem but --auto does'nt work because there are always 2 devices available.

btw: Which usb loader do you use? I know that gx support sector sizes >512, perhaps other loaders too. With sector size 1024 there is space for 1012 discs. try "wwt analyse /dev/sdx" to see calculations with different sector sizes.


I use WiiFlow, but I read somewhere about the 500 disc limit some time ago, and wwt always reports a disc count out "x / 500" when doing listings etc, which is confusing if its ok to have more than 500.

I presume I use the regular system tools to partition the disk first before using wwt to format?

Analyse gives the following, but how do I set/change the sector size?

CODE

ANALYZE /dev/disk2s2
------------------------------------------------------------------------------------
ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂHD SECTORSÂÂWBFS SECTORSÂÂ DISCSÂÂÂÂÂÂ (all values in hex)
ÂÂÂÂÂÂÂÂÂÂ WBFSÂÂÂÂ totalÂÂsecÂÂtotalÂÂÂÂsecÂÂmax inode
NAMEÂÂÂÂmagic vrsÂÂÂÂ num sizeÂÂ numÂÂÂÂsizeÂÂnum sizeÂÂADDITIONAL INFORMATION
------------------------------------------------------------------------------------
HEADER:ÂÂÂÂokÂÂ0 741b4a26ÂÂ200ÂÂe836 1000000ÂÂ1f4ÂÂ600ÂÂWBFS header scanning
CALCÂÂ512:ÂÂ-ÂÂ1 741b4a26ÂÂ200ÂÂe836 1000000ÂÂ1f4ÂÂ600ÂÂcalculation of init function
CALC 1024:ÂÂ-ÂÂ1 3a0da513ÂÂ400ÂÂe836 1000000ÂÂ3f4ÂÂ800ÂÂ " but sector-size=1024
CALC 2048:ÂÂ-ÂÂ1 1d06d289ÂÂ800ÂÂe836 1000000ÂÂ7f4ÂÂ800ÂÂ " but sector-size=2048
CALC 4096:ÂÂ-ÂÂ1ÂÂe836944 1000ÂÂe836 1000000ÂÂff4 1000ÂÂ " but sector-size=4096
------------------------------------------------------------------------------------

[08:09:54] [iMac-2] [~/Desktop/wiimms]:

 

[mousex]

123

 

[drh]

Great work, thanks Wiimm

. It's always amazing how fast and often you update, realy, thanks

.

Now add the SNEEK-Structure for games (Extract, .bin, etc...) and Punes FST Creator/Boot.bin Updater and WWT is finished for me

.

A few people seem to be excited over this sneek, I searched and read a few threads but still none the wiser to why the excitement!?!??

Does it just allow me to run the system off my SD card instead of the Wii's own memory (but a lot slower because its on SD) or am I missing something?

It allows you to run the whole Wii from USB. The NAND including Wiiware/vc and even Wii disc games. The sd card is only for booting. It also has higher game compatibility (maybe 100%) as it Has no problems whit ios reloads and such things.
So you can put as many ww/vc and Wii games on a drive as the drive allows and play them all without issues. It is also nearly as fast as the real NAND when running from a good hdd.
@blue-k: you just need to paste punes code into a c file and run gcc over it to get the fst builder.

does anyone have an image of the SD card so I can try it?

 

[drh]

By the way, Wiimm, I have just compiled latest version for Mac, should wwt be finding my USB disk as "/dev/rdisk2s1" instead of "/dev/disk2s1".

Thanks
drh

 

[Wiimm]

By the way, Wiimm, I have just compiled latest version for Mac, should wwt be finding my USB disk as "/dev/rdisk2s1" instead of "/dev/disk2s1".

Thanks
drh
Yes it should. sylver78 has found that using the character devices rdisk* is faster. I hope that it true for you too.

You can confirm this if you try:
CODEwwt add -p /dev/disk2s1ÂÂ-vvo any_iso
wwt add -p /dev/rdisk2s1 -vvo any_iso

 

[drh]

Picked a random disc and tried both devices, rdisk is twice as fast, see results:

WBFSv1 #1 opened: /dev/disk2s1
- REMOVE [RT3P54] 
- ADD 1/1 [RT3P54] WDF:Rockstar Games Presents Table Tennis [RT3P54].wdf
ÂÂÂÂ 3745 MiB copied in 10:57,ÂÂ5.7 MiB/secÂÂÂÂÂÂÂÂÂÂ 
* WBFS #1: 1 disc added.

WBFSv1 #1 opened: /dev/rdisk2s1
- REMOVE [RT3P54] 
- ADD 1/1 [RT3P54] WDF:Rockstar Games Presents Table Tennis [RT3P54].wdf
ÂÂÂÂ 3745 MiB copied in 5:09, 12.1 MiB/secÂÂÂÂÂÂÂÂÂÂÂÂ
* WBFS #1: 1 disc added.

Now we just need to figure out how to get the 12.1MiB/sec up to Wiimm's speeds :-)
Although the WDF was coming across a network from another computers shared drive, so perhaps a local copy would be even faster!

 

[sylver78]

@drh : when using an USB disk with iso stored on the computer, I get over 22MiB/s speeds

 

[drh]

Must be because the files are remote then, its still a lot better now than it was before using rdisk.

 

[Bauldrick]

Does iso2wdf have an option to automatically name the file correctly (same as if ADD;EXTRACT had been used) wherever the name is read from?

i.e "EXTRACT RR4PFK -> WDF:Build-A-Bear Workshop [RR4PFK].wdf" , Build-A-Bear Workshop [RR4PFK].wdf is how my files are all 'backed up', but if the iso had been called babw.iso and I ran iso2wdf I'd just got file named "babw.wdf".

 

[Wiimm]

Does iso2wdf have an option to automatically name the file correctly (same as if ADD;EXTRACT had been used) wherever the name is read from?

i.e "EXTRACT RR4PFK -> WDF:Build-A-Bear Workshop [RR4PFK].wdf" , Build-A-Bear Workshop [RR4PFK].wdf is how my files are all 'backed up', but if the iso had been called babw.iso and I ran iso2wdf I'd just got file named "babw.wdf".
No, iso2wdf uses always the source file name for the dest file with different extension.

But you can use the more powerful "wit COPY" instead:

wit COPY source.... dest_dir/%X

%X is one of some escape sequences. See docu of "wit COPY" for more info.

Renaming works also fine:
CODEwit move source... %P/%X --test

# rename all files recurse but don't change the directory
wit move -r source_dir %P/%X --test

# remove --test for real execution

 

[drh]

You know the power of wiimm's tools is amazing but unfortunately I don't think I'm alone in failing to make the best use of them because I simply cannot make sense of the command structure despite reading the help.

I have done many manual and time consuming renames of my library because of this.

I think the only people that understand how to build the commands up from scratch are those that are fluent in unix/linux type command line operations.

I have used a combination of my O/S's standard mv to rename the physical filename and the wit/wwt ST command to rename bad versions of the embedded name to accomplish a complete library named properly with lowercase/capitalised names.

Its all pretty much up-to-date now, but it took me ages and I'm sure there was probably a better way to do it :-(