Hacking WBFS files verification on FAT32 parition

[mike333]

If You are using FAT32 device with wbfs files on it ... and ... you make md5 checksums before uploading these files on device ... then there is one line script for You.

IFS=$'\n'; for a in $( find . -iname "*.md5" -printf "%h\n"); do echo $a;cd "$a";md5sum --quiet -c *.md5; cd ..; done

Just run it in wbfs directory and go clean house or do something useful.
Script will find all md5 files and run test against them.

 

[Zetta_x]

As interested I am in your post, I have little to no knowledge to why we would be doing this. Can you explain what an md5 checksum is? I'm pretty smart so you don't really have to dumb down an explanation.

 

[ST75]

This is a total guess but I assume that if for some reason you had the md5 checksum for the game BEFORE you added it to the hdd...this script will check the wbfs files AFTER you add them to the hdd and compare the checksum to verify all data.

Like I said...just a guess.

 

[mike333]

As interested I am in your post, I have little to no knowledge to why we would be doing this. Can you explain what an md5 checksum is? I'm pretty smart so you don't really have to dumb down an explanation.
https://secure.wikimedia.org/wikipedia/en/wiki/MD5
MD5 is just a checksum of data stream.
In above scenario one md5 sum is made for one file.
Why?
Lots of homebrew out there. Some of them can speak usb devices and fat32 using libfat.
In perfect world every HB will use libfat only for it and this lib should be updated in all HB and be bug free.
But we are live in different environment.
QUOTE(ST75 @ Sep 5 2010, 04:10 AM) This is a total guess but I assume that if for some reason you had the md5 checksum for the game BEFORE you added it to the hdd...this script will check the wbfs files AFTER you add them to the hdd and compare the checksum to verify all data.
Like I said...just a guess.

Yup.
It is intended to run once a week/month/whatever or after strange things made by homebrew.

No, it won't fix any data corruption. It tells You that particular file was modified.
Backup is still highly advised, especially when You have big game library.

 

[Zetta_x]

I see, thanks for the clarification and the link for more information!

 

[Wiimm]

Wii ISO images have many sha1 check sums on board. The commands wit verify and wwt verify verify these check sums to find out bad dumps.

 

[mike333]

Wii ISO images have many sha1 check sums on board. The commands wit verify and wwt verify verify these check sums to find out bad dumps.

I'm trying hard to find if above tools allows me to check wbfs _files_ on fat32. Help me please.

 

[FIX94]

WIT should be able to verify wbfs files...

 

[mike333]

WIT should be able to verify wbfs files...

Problem is that I cannot find wbfs word on page mentioned earlier.

 

[FIX94]

WIT should be able to verify wbfs files...

Problem is that I cannot find wbfs word on page mentioned earlier.

I tested it now and it works!

I used WIT.

 

[mike333]

Great. Thanks.

 

[Blue-K]

Great. Thanks.
Yeah. Just use
CODEwit -vv verify

And it will work

. But keep in mind that can take a looong time for a game.