@Whoelse37
The hash is calculated from only the data read from the disc. Any scrubbed parts are ignored. For the hashes to match, it needs to use the same "partitions to keep". If you use "game only" for everything, then there wouldn't be any confusion.
The hashes just now allow you to verify the data is still OK after a few weeks for example. After drive to drive transfers, you can quickly check that the source and destination drives have exactly the same data using the hash.
It also helped me iron out some bugs with CISO. I extracted from WBFS->CISO->WBFS and the 2 hashes are identical which tells me that the CISO is OK.
@digdug3
Yeah, it really shouldn't stop if there's an error. I suppose it was more to help with debugging so that people noticed the errors. Recently, any read errors reported have been due to corrupt discs etc. so (I don't want to speak too soon, but..) I think I've got rid of any read errors caused by the app. Like Cyan mentioned, I'll let it carry on and show an error report at the end.
@Cyan
QUOTE said:
What does it means : "Automatically convert storage convention when drive is mounted" ?
The storage convention selection determines whether you want to store .wbfs files in sub folders or all in the WBFS folder. "Automatically convert" moves all the files to your selected convention when the drive is mounted. Open your drive in explorer.. Select one convention, mount the drive, select the other, mount the drive. You'll see what happens.
I added the new folder naming options last night too for CFG 51b+..
[GameID]_Title
Title_[GameID]
Title[GameID]
The folder names are auto converted too.
@redia
Thanks for that. I was actually just about to do it, but you saved me the trouble.
Edit:
I think I'll have one more release before the covers/info is exposed in the app. There's a few additions etc. that people have requested and it might take a while to finish the covers/info, so I'll finish up the little things first.