Hacking Wii backup Manager for Windows

[fig2k4]

@Bladexdsl
From a quick search, your custom titles file should be named "custom_titles.ini" and copied to wherever WiiFlow needs it.

Just a little update...

I noticed yesterday that the title renaming wasn't working the way I remember it did, so I've made some changes and fixed a lot too. For example, pressing enter or escape caused an AV and the title was never renamed.. It may be that the bugs I'm seeing now is because I'm running Windows 7 x64.. Anyone got problems actually renaming the titles in 32-bit Windows? Regardless, the next release will have these fixes so it works.

Another change is when the GameTDB/Custom title matches the original title, it's usually shown in black. But I saw yesterday that it's pretty confusing. I was wondering why a game wasn't using the GameTDB title. It turned out that it was using a custom title, but it matched the original so was shown in black. This would've been much clearer if it was shown in the custom title colour, so now it is. It's the same idea with the GameTDB titles. Even if the GameTDB title matches the original title, it uses the GameTDB title colour.

I need to do some more work on my release packer because Embarcadero, in their wisdom, changed where the version information is stored for XE2 projects and I can't find it. I'm sick of undocumented changes like that, so I'm just gonna inject the version info into the built exe myself and I never need to worry about it again because it's part of my build tool. A lot of work just to increment a number though.

I will pull this thorn out my side soon too. ie. get the database stuff done..

 

[Bladexdsl]

i clicked on where it says game title, renamed but in wiiflow it still says the original name.

 

[JoostinOnline]

i clicked on where it says game title, renamed but in wiiflow it still says the original name.

Use this to edit the title:
http://www.mediafire.com/?ecva1xcdv7c5cp0

 

[Bladexdsl]

thnx

 

[fig2k4]

I've just released build 68.

Changelog

Spoiler

|-Changed: Win32 and Win64 versions are released in the same package. Use whatever one you want..
|-Fixed: The Game info vertical splitter (resizer) wasn't repositioned when setting position if the game info panel. It seemed like it wasn't there, but it was just in the wrong place.
|-Added: Visual styles. Select any of the available styles in the Options->Visual Styles menu.
|-Fixed: Various title edit/display issues. eg. Using enter or escape caused an AV when editing titles. The custom titles now override the WiiTDB ones etc. Loads of little changes to make it work how it should've..
|-Fixed: SNEEK format, main.dol is now identical to wit instead of having trailing junk data like DiscEx.
|-Fixed: OpenGL renderer now works in Win64 and Direct3D was removed.
|-Added: Native Win64 version now available.
|-Fixed: Another little bug in the SHA-1 hash check and SNEEK format. These should be 100% working now.

 

[Burton]

I've just released build 68.
Changelog

Spoiler

|-Changed: Win32 and Win64 versions are released in the same package. Use whatever one you want..
|-Fixed: The Game info vertical splitter (resizer) wasn't repositioned when setting position if the game info panel. It seemed like it wasn't there, but it was just in the wrong place.
|-Added: Visual styles. Select any of the available styles in the Options->Visual Styles menu.
|-Fixed: Various title edit/display issues. eg. Using enter or escape caused an AV when editing titles. The custom titles now override the WiiTDB ones etc. Loads of little changes to make it work how it should've..
|-Fixed: SNEEK format, main.dol is now identical to wit instead of having trailing junk data like DiscEx.
|-Fixed: OpenGL renderer now works in Win64 and Direct3D was removed.
|-Added: Native Win64 version now available.
|-Fixed: Another little bug in the SHA-1 hash check and SNEEK format. These should be 100% working now.

Thanks for this!

 

[nobody_tw]

Hi fig,

Thanks for this.

Is there any new bug fixed about sha-1 hash check between build 67 and 68 ?

It's good for you to have x86 and x64 combined together.

Thanks!!

 

[fig2k4]

There's no changes to the SHA-1 check between 67 and 68. I just combined the change log in the op because build 67 wasn't an official release, it was to test the bug fix.

If you manually edit the game titles, you should update anyway because it wasn't working. I'm not sure how long it was like that for because I never received any bug reports about it. I only noticed because someone asked about why his titles weren't displayed correctly. That problem was because WBFS Manager writes unicode titles as ANSI text (or may have been an old version of WBM), so the special characters were messed up. The only way to allow this is to encode the titles as UTF-8, which WBM has done for a while.

 

[redia]

Fig2k4,

I wanted to start working on the french translation.
but I ended up with a 2000 line file !!

it looks like you added the developer/editor names (from the filter) in the list...
I doubt these should ever be translated...

R

 

[Etheboss]

Fig2k4,

I wanted to start working on the french translation.
but I ended up with a 2000 line file !!

it looks like you added the developer/editor names (from the filter) in the list...
I doubt these should ever be translated...

R

Exactly, i posted a remark like this earlier, but with no response...2000 lines are not easy to go trough...i am still reluctant...i like to do it but i have limited time...
My question was: does the translation file really have that many lines? or are there obsolete lines too?
I remember fig2k4 telling me that new lines are added when you use the update translation option, but what about lines that are not used anymore?
I only want to translate what is neccesary..

 

[redia]

Exactly, i posted a remark like this earlier, but with no response...2000 lines are not easy to go trough...i am still reluctant...i like to do it but i have limited time...
My question was: does the translation file really have that many lines? or are there obsolete lines too?
I remember fig2k4 telling me that new lines are added when you use the update translation option, but what about lines that are not used anymore?
I only want to translate what is neccesary..

Etheboss,

if you look at the way the file is build it is pretty easy to "clean" it.

the file is formatted it this way

Spoiler

WBM Language file

Display name = xxxxxx
Author = xxxxxx
Strings version = 0.4.3 build 68

 

[Etheboss]

Thanx for the indepth explanation...now i know exactly what to look for (i was not only planning to translate the new lines, but also check the already translated lines for mistakes) it will save a lot of time.

 

[fig2k4]

Cheers, I see the problem.

When you use the "New language file" menu item, the strings are built from scratch using the text/captions of every control in the app, along with the langstrings.txt (Which is the strings from my source, as I explained before). When I rebuilt the lang files before the release, the filter combo boxes were empty, so I didn't notice this happening. All the existing language files are rebuilt automatically and you can see that the extra strings aren't there.

All I have to do is set the tag property of the controls that means "Do not translate" and it'll be fixed. In the mean time, you can safely ignore anything that you don't want/need to translate. When I rebuild the files for the next version, all of those strings will be automatically removed because they don't exist in the app, so you don't even need to manually check what's needed.

Without the automation, imagine having to sync all those language files manually? Adding and removing strings for every language by hand.. Simply, there wouldn't be any language files because nobody, including me, would want to do that..

Once you've translated some of the strings, you can use the "Update language strings" as often as you want to reformat the file like redia showed. All untranslated strings are moved to the bottom of the file, so you can easily see which ones have been translated already. If you're using a language file from an old version of WBM as a starting point, this function also updates it to contain all the strings for the current version.

I did notice 1 or 2 other strings there that aren't needed, like "Panel 4", which is a default caption on a panel control that I forgot to change because it's just a container for other controls. If you see anything like this, just don't translate it, it won't do any harm either way. Things like 1x and 2x and some other strings might not need translated, but I don't know every language so everything's there just to be safe.

 

[fig2k4]

I quickly fixed a couple of bugs. Here's build 69 (Win32 only) with the fixes..

http://www.4shared.com/file/GeyiY2EF/WiiBackupManager_Win32_Build69.html

|-Fixed: Database filter dialog wasn't translated correctly when setting the language.
|-Fixed: "New language file" function was adding all the database filters to the new file. ie. all the developer/publisher names etc.

Hopefully I didn't miss anything, I was trying to get the fix out before I get the kids ready for Halloween.

 

[roubagalinhas]

"full scrubbing mode" does the same as "keep game partition only"?
or is is it different in any way? better? worse?

 

[fig2k4]

Full scrubbing will free up an extra few meg, but it actually fragments the files more than normal. It's probably better not using it. It was more of an experiment to see if I could optimise the scrubbing, but it doesn't make it small enough to warrant the extra fragmentation IMO. A few pages back, you'd see that I was actually considering removing the option.

 

[Lucif3r]

Full scrubbing will free up an extra few meg, but it actually fragments the files more than normal. It's probably better not using it. It was more of an experiment to see if I could optimise the scrubbing, but it doesn't make it small enough to warrant the extra fragmentation IMO. A few pages back, you'd see that I was actually considering removing the option.

A few extra megs is definitely not worth extra unnecessary fragmentation.
Or well, what do you mean by "a few meg" btw? 100? If its over 100 it might be worth it if you have a lot of games ...

 

[fig2k4]

I mean around 5-10 MB per disc. :/

 

[Lucif3r]

I mean around 5-10 MB per disc. :/

Definitely not worth it then

 

[roubagalinhas]

i agree

and thanks for the explanation