Hacking Wii backup Manager for Windows

[CVonV]

pardon the noobiness but it's hard to find an answer in this 70page thread even with searching.. but what do the letters in the "Partitions" column mean? i've seen "G", "UG", "GO" so far

 

[XFlak]

Game
Update
Game Only???

its in the read me that came with the download

 

[pepxl]

pardon the noobiness but it's hard to find an answer in this 70page thread even with searching.. but what do the letters in the "Partitions" column mean? i've seen "G", "UG", "GO" so far

G = Game
U = Update
O = Other - VC Games and what not like in SSBB

so

G = Game
UG = Update & Game
GO = Game & Other

 

[CVonV]

its in the read me that came with the download

to be fair it was in the changelog.txt

but thanks guys

 

[TeenTin]

Thanks your application. I met a problem when I tried to transfer a game from WBFS partition to an ISO file when I used 0.3.4r4. Actually it transferred nothing. I tested this function in 0.2.4r2, it worked correctly.

I have tested this with Wii Play, it works. However, the ISO generated is different from that generated by wbfs_file.exe.

 

[XFlak]

I know that wii backup manager automatically sparses extracted ISO's to take up less space on disk, does anyone know if wbfs_file.exe does the same thing (if not, that could explain the differences TeenTin found)

 

[redia]

I know that wii backup manager automatically sparses extracted ISO's to take up less space on disk, does anyone know if wbfs_file.exe does the same thing (if not, that could explain the differences TeenTin found)

both application sparse the iso.
two things could explain the difference :
the type of "extract" done by each app (full, game only, ....) but there is also a "full scrub" option.
and the partition layout.
this has already been discussed a few pages ago.
oggzee and fig2k4 found a difference, which is harmless, but could explain a little difference.

teentin, could you give us more information on the difference you are finding ?

R

 

[TeenTin]

I know that wii backup manager automatically sparses extracted ISO's to take up less space on disk, does anyone know if wbfs_file.exe does the same thing (if not, that could explain the differences TeenTin found)

both application sparse the iso.
two things could explain the difference :
the type of "extract" done by each app (full, game only, ....) but there is also a "full scrub" option.
and the partition layout.
this has already been discussed a few pages ago.
oggzee and fig2k4 found a difference, which is harmless, but could explain a little difference.

teentin, could you give us more information on the difference you are finding ?

R

I used beyond compare to do hex compare. They are just different. I chose game only, very carefully.

 

[r3dcat]

Using WiiBackupManager0.3.4r4 ... I have just copied my library of games from one USB drive WBFS partition to another drive WBFS partition and have noticed something painful ... Game Titles have not been copied across as listed on original partition ??? ... Why am I not seeing the same Game Titles listed on both partitions??? and from what I can tell there doesn't seem to be an option to rename ??? Any suggestions please?

OK I have worked out that enabling "Auto rename drive transfers" and "Auto rename WBFS file transfers" enables current Title names to be copied correctly when doing a WBFS -> WBFS partition copy ... I find it a bit strange that this is not a default setting! ... I am guessing most people would want current Titles copied by default ??? ... Also I think the "Auto rename" wording in options->settings->Titles is unclear ... perhaps "Copy current Title on" drive transfers or WFBS file transfers is better layman language ???

... or even better would be to have a tick box for "Copy Original Title on transfers" for those that want original titles otherwise by default copy current Title ???

A feature I find sorely missing from this app is the ability to rename ... I don't like using a Titles.txt and prefer to rename Titles as I add game ISO's to my WBFS partition ... any chance we will see this feature added soon please ???

 

[gaalex]

Thanks your application. I met a problem when I tried to transfer a game from WBFS partition to an ISO file when I used 0.3.4r4. Actually it transferred nothing. I tested this function in 0.2.4r2, it worked correctly.

I have tested this with Wii Play, it works. However, the ISO generated is different from that generated by wbfs_file.exe.

I just noticed my destination folder was a windows compress folder. Then I tested a regular folder, the transferring function worked.

 

[fig2k4]

@TeenTin
If you use the app I suggested (HxD), comparing 2 files is like a text search. When it finds a difference, it'll stop at that address so you can see the difference (Press F6 to find the next difference) . If Beyond Compare can't do it, use HxD to let me know the first addresses that the difference occurs. If it does happen to be only the partition table that's different, it's nothing to worry about. I regret backing up my games with "Game Only" now, since I can't check if Wii Play has any additional partitions. What does the partitions column show for the original ISO when you loaded it in WBM?

I purposely write to the ISO in block sizes the same as WBFS files so it should be identical to wbfs_file.

Edit: If you have WiiScrubber, load the original ISO and see what partition tables are used too.

@r3dcat

A feature I find sorely missing from this app is the ability to rename ... I don't like using a Titles.txt and prefer to rename Titles as I add game ISO's to my WBFS partition ...

I've got inline editing working, but there's silly behavioural problems with the list view control.

In the demos that came with the code, the editors scroll when the list is scrolled. But I'm having problems with it not scrolling horizontally. It's pretty frustrating since I can see that it works in the demo.

It shouldn't be long before I fix it. It's something to do with the fixed column with the check boxes, I may have to scrap that idea to fix the inline editing if I can't fix the code.

@gaalex
If you can reproduce this and email me the log it'll help me find the problem. I just tried transferring an ISO to a compressed folder but it worked fine. Did it show any errors at all?

 

[TeenTin]

@TeenTin
If you use the app I suggested (HxD), comparing 2 files is like a text search. When it finds a difference, it'll stop at that address so you can see the difference (Press F6 to find the next difference) . If Beyond Compare can't do it, use HxD to let me know the first addresses that the difference occurs. If it does happen to be only the partition table that's different, it's nothing to worry about. I regret backing up my games with "Game Only" now, since I can't check if Wii Play has any additional partitions. What does the partitions column show for the original ISO when you loaded it in WBM?

I purposely write to the ISO in block sizes the same as WBFS files so it should be identical to wbfs_file.

The top one is made by the latest Wii Backup Manager while the bottom one is made by wbfs_file.exe.

The original ISO shows UG in the partitions column.

 

[fig2k4]

ImageShack is quite good for sharing images. I'm seeing an error "No linking from this host" with waffleimages.com. I got it though, by copying and pasting the link. Just checking it..

 

[Hatsu]

Picture in http://gbatemp.net/index.php?s=&showto...&p=2562526:

 

[fig2k4]

To me it looks like extra junk has been copied by wbfs_file for some reason. This is an screenie showing my original PAL scrubbed version with the update partition removed, from before I even started coding WBM..

The sector from 0x200000 to 0x2003FF is empty, but maybe you're not using the PAL version?

I changed a couple of values in the empty sector to "99". The bottom window shows the ISO after converting to WBFS File and back to ISO using wbfs_file. You can see that the sector in question wasn't copied by wbfs_file either.

Did you remember the -g parameter for wbfs_file? Edit: Silly question, obviously you did or the partition table would've shown as the first difference...

 

[TeenTin]

To me it looks like extra junk has been copied by wbfs_file for some reason. This is an screenie showing my original PAL scrubbed version with the update partition removed, from before I even started coding WBM..

The sector from 0x200000 to 0x2003FF is empty, but maybe you're not using the PAL version?

I changed a couple of values in the empty sector to "99". The bottom window shows the ISO after converting to WBFS File and back to ISO using wbfs_file. You can see that the sector in question wasn't copied by wbfs_file either.

Did you remember the -g parameter for wbfs_file? Edit: Silly question, obviously you did or the partition table would've shown as the first difference...

My version is NTSC. I check both the ISOs generated with WBM, and both show only G .

 

[fig2k4]

I'll re-rip 1 or 2 originals later today to see if/why the extra sectors are being used by wbfs_file.

Could you possibly remove the update partition and scrub your NTSC version with WiiScrubber and post a screenie like the previous ones at 0x200000?

 

[leo_bsb]

fig2k4,

all my games are working great, tested with 3 wiis and 4 different drives.

I have one more suggestion: could you export the games list from the drive view? It will use the game name, not the game folder name. It will be usefull to send to friends and control the game database you have.

 

[fig2k4]

Yeah, I plan to keep that simple this time. I already have a text file template and CSV by pontomedon that I'll include with the app. You'll be able to make your own template very easily for other formats too..

 

[fig2k4]

@TeenTin
I just got a chance to test SSBB. The PAL version has a total of 15 partitions. 2 on the first table and 13 on the second.

The reason for the difference is exactly as I thought. With wbfs_file, the second partition table still contains the 13 partitions.

at address 0x40008.. Edit: with WBFS file it's exactly the same, but located at 0x240008..

00 00 00 0D //partition count
00 01 00 10 //offset of the partition info

That's the only part that's different, so it looks like it's OK. I'll get round to the other tests soon with Wii Play..