Hacking Wii backup Manager for Windows

[redia]

thanks for keeping us updated on the progress.

Cheers,
R

 

[Buster777]

check again the preferences/drives/ and be sure the "see only mounted drives" is not checked.
As windows can't mount WBFS, with this option checked by default, they are hidden.

Many thanx Cyan. That fixed the problem for me.

'Buster'

 

[fig2k4]

Can you tell me if your WBFS drive had a letter assigned in Windows?

I curious if it's WBFS drives in general that don't show up without using volumes names or just because there's no letter assigned, which would be normal..

 

[XFlak]

I can confirm that a wbfs drive WITH a drive letter does show up unless i untick "see only mounted drives"

so even with a drive letter, wii backup manager see's it as an un-mounted drive

 

[fig2k4]

Damn, that explains all the confusion.

WBFS drives with a letter assigned show up OK here with Windows 7.. I'll think of some workaround because it's not really acceptable for WBFS drive not to show at all by default..

Edit:
I could be just a bug that's fixable though because the very first versions used drive detection via the assigned letters without problems.

 

[redia]

I can confirm that a wbfs drive WITH a drive letter does show up unless i untick "see only mounted drives"

so even with a drive letter, wii backup manager see's it as an un-mounted drive

+1...
same test.
same result.
even if my drive has a letter.. it does not show until I untick the box.

R

 

[XFlak]

Damn, that explains all the confusion.

WBFS drives with a letter assigned show up OK here with Windows 7.. I'll think of some workaround because it's not really acceptable for WBFS drive not to show at all by default..

Edit:
I could be just a bug that's fixable though because the very first versions used drive detection via the assigned letters without problems.

that's odd, because I had the "problem" using windows 7 ultimate 64-bit (and on my friends Windows 7 Ultimate 32-bit)

 

[Cyan]

ah, I always thought it was because windows didn't mounted the drive as readable (FAT32 or NTFS), and would ask to format it if selected.
I didn't try the first version, I'll try and report here

edit :
0.3.0 final : no option to show or hide mounted drives (all the drives are available)
0.3.1beta2 : no option for mounted drives
0.3.1beta3 : no option for mounted drives
0.3.1 final : 1st time this option is available : Has the bug
0.3.2 : same
0.3.3 : same

ok, test ended.
It seems the bug is here from the start.
I'm using Win XP pro SP2.

 

[DGenerateKane]

Damn, that explains all the confusion.

WBFS drives with a letter assigned show up OK here with Windows 7.. I'll think of some workaround because it's not really acceptable for WBFS drive not to show at all by default..

Edit:
I could be just a bug that's fixable though because the very first versions used drive detection via the assigned letters without problems.

that's odd, because I had the "problem" using windows 7 ultimate 64-bit (and on my friends Windows 7 Ultimate 32-bit)

Pretty sure I had the same problem with the same version of windows.

 

[sniperz]

I'll allow force mode in the next release. But you'll need to resave those wbfs files since they won't (or shouldn't) work on the Wii either.

The read error could also be caused by a bad burn, or just a dirty disc. I've never had problems with single layer discs, but dual layered discs are terrible for burning. I've had a few burns that look good until I've checked them with DVDInfoPro. You can run a read test on the disc to see if there's any bad sectors. Games will play fine until those bad sectors are encountered.

I put the backup disc which got a error at the finishing in my PC drive into Wii and tried to reinstall it with CFGv51,after it's done,i could see it in the game list and then i started the game, everything was ok,amazing!
So i guess the Wii drive has a better compatibiliy with the backup discs.i have wiikey 1 and cIOS249 v14,222,223mload v4 installed,dose this help with it ?

 

[Spidy1000]

The wiikey makes the wii more compatible with backups, so that is not really a good comparison. My wiikey 2 plays everything i throw at it if i run from disc, even rewritables (as long as it is good quality). I always burn on Verbatim +R bitset to -ROM

 

[fig2k4]

It does sound like Windows is a little pickier when it comes to scratched discs etc. when using the CreateFile() API maybe because it relies on the CDFS driver. leo_bsb had 1 disc that got an error too, then ripped it with ImgBurn OK, so probably using SPTI would work better, or it could be just that raw ripping the whole disc to ISO works better in that situation. I'm not sure yet.

I'll look at using SPTI later because it would be cool to directly burn discs with the app too.

@Cyan
Sorry man, I meant a little older than that.

Anything prior to 0.2.4 used the letters for drive detection. I'm confident that I'll get this working correctly before the next release..

Edit:
I've fixed the drive detection issue. Obviously I didn't test WBFS drives with the new code.

Drives were only showing up if there was a disk inserted. WBFS drives were classed as not having a disk inserted because Windows doesn't recognise the filesystem. I just changed it to simply check if the "drive" exists, so SD card slots etc. will still show up even if there's no card in it too. Anyway, it works like it should now..

About the drive menu delays, I noticed it's a hell of a lot worse when you have a DVD inserted in a drive. Caching of the drive lists is definitely needed..

 

[Spidy1000]

if not already possible, could you make it possible to (when adding a folder with iso's) add a folder with subfolders that have iso's in them? So search all folders in the selected folder for iso's. I tried this in the newest version, but it does not seem to work. I think this would be nice and usefull if it can be done

 

[fig2k4]

Make sure you selected "Add files from folder recursively" in settings. All file types should already be added from sub folders. I just tested with .wbfs and .iso from a WBFS folder and earlier today I added some .rar files from a folder recursively. If you pick the actual drive letter it should search your whole drive too.

Another reason that the ISO might not show up is because it could be deemed to be invalid. Check the log for that.

Let me know if none of that is relevant, it could still be a bug..

 

[DGenerateKane]

Make sure you selected "Add files from folder recursively" in settings. All file types should already be added from sub folders. I just tested with .wbfs and .iso from a WBFS folder and earlier today I added some .rar files from a folder recursively. If you pick the actual drive letter it should search your whole drive too.

Another reason that the ISO might not show up is because it could be deemed to be invalid. Check the log for that.

Let me know if none of that is relevant, it could still be a bug..

That option is already selected, I just chose a folder with multiple folders with isos and rars in them and it added nothing. The Log says: CODE14:56:06 Found files. 200
14:56:07 (SearchFoldersThread) Thread terminated.
14:56:07 (SearchFoldersThread) Time taken. 00:00:06
14:56:07 (AddFilesThread) Thread started
14:56:07 (AddFilesThread) File count 200
14:56:07 (AddFilesThread) Thread terminated.

 

[fig2k4]

Can you email me the log? I've tried this over and over. For me it finds all rar, iso etc. and loads anything that's valid.

 

[DGenerateKane]

I found the problem after rearranging some files. When it goes to add a valid iso/rar it stops the whole operation if said iso/rar is corrupt/incomplete. After removing some files and trying again it found two games. After checking what came next alphabetically I found another game that was incomplete. After removing all of the incomplete ones it was able to find and add all the games in the folder including the ones in sub folders.

 

[Spidy1000]

I found the problem after rearranging some files. When it goes to add a valid iso/rar it stops the whole operation if said iso/rar is corrupt/incomplete. After removing some files and trying again it found two games. After checking what came next alphabetically I found another game that was incomplete. After removing all of the incomplete ones it was able to find and add all the games in the folder including the ones in sub folders.

So i guess the program should be modified to add only valid iso's and skip the ones that are corrupt/incomplete. So it won't stop when it finds something it doesn't like.
I Hope this feature will be implemented in the next version

EDIT: I just tested my own situation again, and it turned out i had the recursive folder option disabled. Now it works. So i guess all my iso's are valid

 

[fig2k4]

Usually, the thread carries on adding the next files the current one is invalid. The only thing I can think of is that reading the files is causing an error, maybe with memory allocation, and raises an exception. That would probably cause the thread to terminate prematurely. I'll need to try and recreate the problem here to track it down.

I could also wrap up the critical operations in try..except statements to catch the exceptions and allow the thread to ignore them.

For example..

try
Load the ISO
except
Error, carry on with the next file..
end;

BTW, does the log show any mention of the word "exception"?

 

[icebrg5]

Tried using the latest version of this app again today on a vista 64 bit machine today and once again it would not see the hard drive at all.I even unchecked the mounted volumes only box from the settings and it made no difference at all.

Wbfs manager worked just fine on it though and even after formatting the drive to wbfs with it and then trying this app to load the hard drive it would load the hard drive but wouldnt show any of the games that were on it and also told me it the drive was unusable.

I've only tried it on a 64 bit operating system twice now and both times i could never get this app to show the drive properly.The first time i was told it was the drive unmounted/mounted volume issue since when i tried it the first time the option to look for mounted/unmounted volumes was not there.


So whats the issue im having?

Is this app not compatible with 64 bit systems?
*People have posted in this thread it works for them on 64 bit systems
so i don't think that's the reason*

Is it the 64 bit operating system?

Is it Vista?