Hacking And another WBFS GUI

[Master Mo]

Can you see a drive letter for your wbfs partition ?

Yes, put both partitions are not recognized by the tool. It is not the fault of the guis or something.

I found a guide to solve this problem here at gbatemp. Still need to try it out:

http://gbatemp.net/index.php?showtopic=145...p;#entry1869380

 

[manias]

Nice work,

I just wish someone would now work on fixing WBFS so it has better support with drives with multiple partitions.

Just use the cygwin version compiled by_JL_.
It works well with multiple partitions because you specify the drive and partition number instead of a drive letter.

Can you show me, where I can find this? I searched for it but with no success...

I already tried several of these wbfs-tools for Windows but all with the same error: "could not open drive: no error". So I assumed, that the error had something to do with the formation on the Wii and I`ve decided to reformat it to ntsf and use the wbfs_win to formate it on Windows but I still get the same error. So it has to be a problem with the recognition of the partition.

Would be really great. if you could direct me to that tool, so I could try it

you have to run cmd in admin mode or u get that error

 

[Scarfish]

Hmm looks like there something wrong with an array.
Strange is that it works for me and some other peoples.
Have you installed the latest .Net Framework ?

Anyway i changed the program a bit the download link is in the first post.

Just look closely at the show_list() method and look for places where it could possibly go wrong. Build some nice checks around these places.

 

[nIxx]

In the newer Version i put everywhere a try and catch
i mean this should do it at least it should "catch" the errors

 

[shtonkalot]

Missed version 6 but have tried 7, First time I ran it I got the usual error message, then continued and this time the GUI not just ran but worked! Before the buttons for add, delete, extract and read resulted in another error message.
Now when I run it I get no error message on startup...!? That is weird, isn't it?

Also I just noticed there is a difference in the included wbfs_win.exe compared to the original one I got from the "wbfs_win_delta" package. The difference being that when I run the included one from command prompt I get a pause after every command I run, including just running the app with no flags after it.

nIxx, have you made any changes to the wbfs_win executable? If not where did that version come from.

Breaking news, the older versions of the app now load without problem. I wonder what the problem was? perhaps my antivirus?

 

[nIxx]

Hmm really weird and i´m asking me the same.
Debugging is so annyoing especially if you get no errors but some others.
Possibly a .Net Framework Version blocks the other but i really don´t know for me everything was working fine

.

Ah and i doesn´t made changes to the wbfs_win.exe but i know what you mean but why the wbfs_win acts like this i don´t know or i´m not sure. I thought possibly it´s still running as a process in the background but in the Task manager there is no wbfs_win.exe anymore.

 

[qbert]

I think there is an error concerning the file name format, but not a GUI fault. But the GUI could advise for that

 

[kingofsnake]

Gave up on vista, this GUI works great on my XP machine.

 

[qbert]

In Vista, try to run the program as Administrator

 

[julen163]

I found the problem from Array.
This is because the program read the list of .iso in the directory.
If there is nothing in the ISO directory, then error occurs....

=;.-)




[/indent]

Doesn't work for me, giving me an error:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.IndexOutOfRangeException: Index was outside the bounds of the array.
at WindowsFormsApplication1.Form1.show_list()
at WindowsFormsApplication1.Form1.Form1_Load(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
WBFSTool
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Documents%20and%20Settings/Administrator/Desktop/wbfsTOOL4/WBFSTool.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:





When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

​

 

[nIxx]

Stupid me thankyou for the hint i will fix this

 

[Maximillion]

Hey tried your tool its pretty nifty =P was wondering what you wrote it in
and how you managed to take the the data from wbfs_win.exe its really been bugging me

 

[Prisoner]

I wonder why it keeps giving me error on MS .NET Framework...

 

[shanefromoz]

I also get the same error and have windows upto date.
Anyone got any ideas?

Cheers

 

[nIxx]

So i hopefully fixed all errors now.
Edit: Made a little stupid mistake in v9 delete wasn´t working.
WBFS-GUI v11

 

[Prisoner]

now it works

 

[nIxx]

Nice to here this

 

[nIxx]

So now it´s really fixed (packed the wrong file

)
WBFS-GUI v12

 

[Chemodile]

I like this one, but a couple problems:
- Whenever I add an ISO, after it finishes I'm unable to add another one until I close the program and re-open it. It says "ERROR #12" when I try this.
- Is there a way to queue up multiple ISOs? I'm unable to select more than one ISO from the list at a time. It would be nice to either be able to select multiple ISOs at once to be added, or have an "add all from current directory" button. As it stands I'm going to have to close and re-open the program 25 more times to finish adding all my ISOs.

 

[nIxx]

This should work now again

:
WBFS-GUI v13