Separate names with a comma.
Discussion in 'Wii - Backup Loaders' started by fig2k4, Oct 30, 2009.
Why is that funny? Do these work on Wii U formatted HD's also?
LOL still does not get it sad
No. And to forewarn anyone about to use this on their Wii drive....
0.4.5 build 76
|-Fixed: A serious issue with title renaming that caused corrupt WBFS files.
Was NOT fixed. I was left with 100+ corrupted games after using this to rename.
latest is 0.4.5 build 78 and has been out for ages.
Don't know if I ever used build 76 but I never have any problem with it including rename a whole 500G hdd full of Wii games
Umm there are two ways right now to play backups on a Wii U:
Installing to home menu (WUP Installer)
For Loadiine: Yes there are 1 or 2 tools I've seen to manage the games on your SD card. I guess this is as close as something's getting to Wii Backup Manager for Wii U.
As for installing games just use Wii U USB Helper to download games and move them to SD in the right folders to install them there with the homebrew WUP Installer (y mod).
Grab the tool here:
Thanks but I was referring to the title of the thread. A Windows program to manage Wii U games.
I know but please read what I wrote:
Wii Backup Manager moves wbfs files (which are ISOs of Wii Discs in fact) between internal and/or external drives.
For Wii U there is no "put an ISO (which would be WUD) on an external drive and directly launch it from the console". The method closest to this is Loadiine where you put "Loadiine ready folders" (containg at least code and content folders) instead of ISOs on an SD card (since USB is still not supported by Loadiine).
So to manage these "Loadiine ready folders" which are similiar to Wii's WBFS files which are handled by Wii Backup Manager you could use one of these two tools:
To manage NUS packages you could use
Wii U USB Helper
as stated before but you would have to install these packages first to your console with WUP Installer (or System Config Tool).
So to come back to what you've been referring to -> A "Wii U Backup Manager for Windows" can't exist as there is no way to directly play Wii U ISOs (which are WUDs) on the console.
To be fair it can exist but why would anyone code a program to handle WUD files on USB drives if it's nothing but pointless/useless?
Yes, I was full aware of build 78. I was just saying that the bug was NOT fixed in 76, therefore it is still present in build 78. If you didn't experience the renaming bug it's because you probably haven't ever had "Allow permanent changes to Wii disc header" enabled. Try it for yourself, lol.
Here's where another member had it happen and supposedly how to fix the corrupt images, but I was never able to figure out the instructions.
ahh, you mean the title stored INSIDE the ISO?
I thought you meant the filename used for the wbfs and its folder.
That's really not a good idea to edit an ISO's internal data, it was used when folders didn't exist in "wbfs formated partition" and there were no "wiitdb.xml" from gametdb to rename the game's titles displayed in the loaders.
Why not just use the game's title read from Gametdb, or the the sub-folder's name?
having the internal title changed in the game's header might not even be noticeable on USB Loaders, as they are not reading titles from the header (unless specifically asked in the settings), and you won't see that title either on your computer.
Sorry for all your corrupted games
The explanation to fix it is maybe correct, but it requires manual edition of each game file one by one.
Maybe WIT can fix wbfs files automatically?
I don't know if it has a header fixing function.
Let's call @Wiimm here, he is best placed to know what his tool is capable
Uwizard can manage SD card? I didn't follow its development, I could add it to the wiki.
There is also these game managers:
Some are just utilities to make a list of games you have, not all of the listed apps are copying games to SD. Maybe you'll find some useful tools you forgot.
Why change a known good iso? You are asking for trouble yourself.
If there is something wrong with the iso to begin with, I would simply ditch it not to say mass editing all isos.
This. You can't fix a corrupt disc image. Some of the data doesn't exist.
"wwt verify" and "wwt verify" can analyse images and help to find bad (not usable) images.
"wwt analyse" helps to analyse the data structure of WBFS partitons even if the partition header is destroyed.
http://wit.wiimm.de/ explains the commands. Use the right navigation bar to select a tool and in a second step the command.
thank you for your reply.
I didn't look at all the commands on your site to see if it could fix wbfs with a bad header.
So, instead of using an hex editor and doing all the math manually, just use WIT with a batch to fix all your corrupted header at once.
Now you know it's possible, so you should take a look, take your time and read all the commands to see what's possible.
I recommend using the test mode for learning all the command, see what happens, compare the results, etc.
when you are sure and ready to do it, remove the test mode.
If you really don't understand, I might take the time too help you, but I don't have a bad header game to try, and I would prefer you to search and learn.
To begin with it effects wbfs files, not isos. Secondly, my personal reasoning for using it makes no difference. The author stated it was fixed & it was not. It's as simple as that. If a person has no use for the bugged feature that's fine, but acting like it's insignificant because it doesn't effect you personally is absurd. Also, see the below answer.
You can fix the corrupt header caused by the bug with the built in repair options. The only problem is that it reverts the renaming done by using the bugged feature that was supposed to be fixed.
I tried reading all of that stuff and I couldn't find how to run wit or wwt commands on a single wbfs file. What would be the proper entry for example let's say "wwt verify" on a file named test.wbfs & located in D:\Wii\ ?
I have renamed an filled 500GB HDD of .wbfs without problems
Doesn't matter, be it iso, wbfs partition or wbfs files for FAT32 partition, you should always start from a known good iso/wbfs or rip direct from retail disk.
If you think this is a significant bug, will you stop using Wiibackupmanager all together?
If you explicitly use a feature that is off by default, you should know what you are doing.
Again, mass editing a whole drive of games to correct potentially a small number of games is not a good idea. If a large number of your games had header problems then god bless you.
I know, you would argue a bug is a bug, but you are the only one I have ever heard being hurt by this feature.
Well, you can revert, so maybe its time you begin learning hex editing?
"wit verify filename.wbfs" should be all you need.
Fixing the structure of the header doesn't replace the data that was there originally. If the signing key of a partition is corrupted then there's know way to know what to fix it with, for example. You could copy it from a known good image but then why not just use the good one.
I don't know of any header-related bugs in WBM other than it not understanding the WiiWare demo container for Smash Bros.
1) It does matter, lmfao. If it ONLY effects wbfs then it only effects wbfs. It CAN'T matter for iso. Period.
2) All of my images were good to begin with. I used the feature because I simply don't like seeing things like "SPYRO08", "FFCC EOT" or "PIKMIN1 for Wii", etc. The renaming feature was there for a reason & the author them self said renaming should not be re-writing the header & thus the bug was fixed. However, it still re-writes the header and causes the wbfs image to be unuseable.
3) The feature is off by default because most people don't rename their images/headers & like things to look ugly and unorganized??? You know - a personal choice? Ever heard of such a thing?
4) I knew 100% perfectly fine what I was doing, it's the feature that's broken. Not me or because I didn't know what I was doing. That was one of your more stupid comments about it all.
5) There is another person who had to fix tons of games due to the bug. I even pointed directly to their post in this very same thread. The author themselves listed it as "serious", so what's there to argue with? Why are you even trying to argue the facts of the matter? Sounds like you just want to argue for arguments sake. You didn't use the feature? Well good for you! Congrats! YAY! Yippie Skippy!
6) Ummm. I already know how to hex edit.
Your attitude about me not knowing what I'm doing & that I don't understand hex editing just proves that you want to be argumentative just to be a dick about it. "Doesn't matter... You should... If you think... You should know what you are doing... You are the only one... Maybe it's about time you..." See what I mean? You're just being a prick for absolutely zero reason other than try to prove to me that the bug is of zero importance. I'd also like you to know that this incident happened years ago. I have no further use for Wii Backup Manager as I have all the titles I would ever want or need for the Wii. I'd also like to mention AGAIN that I was pointing out the bug for those who may want to use the feature & that it wasn't fixed as stated by the author. Just because YOU never used it doesn't mean no one else ever will. Might be nice for them to know, you know? Evidently not by your line of thinking of just forget it and not let ANYone know.
But it is fixable and DOES replace the data that was originally there. Either by hex editing or by using the built in WBM repair option. The header contains the text wbfs & the size of the image in hex, the original/good info is not needed because those two things are all we need to fix it. After repairing the file hashes match 100% with the original images so there is no loss of data. The header renaming bug is obviously there, if it was mentioned by the author as "serious" and was supposedly fixed. How can one not know of the bug if the author specifically mentioned it in release notes?
Say the header shows there were two partitions on the optical disc: the game data and the update partition.
Now say something overwrote the size of the game data partition with zeros. How do you determine how big the game partition was? There are still two in the disc image but that image is now unrecoverable.
There is no need at all to alter the system area of a cleanly ripped disc. If you want to change the display name of a game you can do that with any of the loaders either by changing the wiitdb.xml file data or with title name override files.