Hacking WBFS Manager 2.0

  • Thread starter Thread starter AlexDP
  • Start date Start date
  • Views Views 35,259
  • Replies Replies 99
Mirror anyone ?

WiiNewz doesnt like me
biggrin.gif
 
You can also lose the List button. The list command should be executed automatically when a WBFS partition is in focus.
 
Knocks said:
You can also lose the List button. The list command should be executed automatically when a WBFS partition is in focus.
That is a good suggestion but again, this goes back to my previous comment. If I do that, then everytime the user selects a drive letter, it would be "touched" by the application, and thats not something I'd like for any app to do to my drives, and as such I won't be doing that myself. When an app is gonna be missing with someones drives, it should require the user to explicitly initiate the action.
 
2.2 version works perfectly for me. However, 2.2.1 even can't open. Showed "fatal error occured".
Here is the message showed:
Code:
---------------------------
Fatal Error
---------------------------
Fatal error occured. Please send the following information to the application developer at [email protected] (You can copy this text by pressing Ctrl+C or use the log file in the installation directory (must Run as Administrator in Vista+)): Message: ????????? 'zh'?

????: name 
Stack trace:ÂÂÂÂ? System.Globalization.CultureTableRecord..ctor(String cultureName, Boolean useUserOverride)

ÂÂ ? System.Globalization.CultureTableRecord.GetCultureTableRecord(String name, Boolean useUserOverride)

ÂÂ ? System.Globalization.CultureInfo..ctor(String name, Boolean useUserOverride)

ÂÂ ? WBFSManager.MainWindow.Window_Loaded(Object sender, RoutedEventArgs e)

ÂÂ ? System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)

ÂÂ ? System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)

ÂÂ ? System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)

ÂÂ ? System.Windows.UIElement.RaiseEvent(RoutedEventArgs e)

ÂÂ ? System.Windows.BroadcastEventHelper.BroadcastEvent(DependencyObject root, RoutedEvent routedEvent)

ÂÂ ? System.Windows.BroadcastEventHelper.BroadcastLoadedEvent(Object root)

ÂÂ ? MS.Internal.LoadedOrUnloadedOperation.DoWork()

ÂÂ ? System.Windows.Media.MediaContext.FireLoadedPendingCallbacks()

ÂÂ ? System.Windows.Media.MediaContext.FireInvokeOnRenderCallbacks()

ÂÂ ? System.Windows.Media.MediaContext.RenderMessageHandlerCore(Object resizedCompositionTarget)

ÂÂ ? System.Windows.Media.MediaContext.RenderMessageHandler(Object resizedCompositionTarget)

ÂÂ ? System.Windows.Media.MediaContext.Resize(ICompositionTarget resizedCompositionTarget)

ÂÂ ? System.Windows.Interop.HwndTarget.OnResize()

ÂÂ ? System.Windows.Interop.HwndTarget.HandleMessage(Int32 msg, IntPtr wparam, IntPtr lparam)

ÂÂ ? System.Windows.Interop.HwndSource.HwndTargetFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)

ÂÂ ? MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)

ÂÂ ? MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)

ÂÂ ? System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Boolean isSingleParameter)

ÂÂ ? System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)

ÂÂ ? System.Windows.Threading.Dispatcher.WrappedInvoke(Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)

ÂÂ ? System.Windows.Threading.Dispatcher.InvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Boolean isSingleParameter)

ÂÂ ? System.Windows.Threading.Dispatcher.Invoke(DispatcherPriority priority, Delegate method, Object arg)

ÂÂ ? MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)

ÂÂ ? MS.Win32.UnsafeNativeMethods.ShowWindow(HandleRef hWnd, Int32 nCmdShow)

ÂÂ ? System.Windows.Window.ShowHelper(Object booleanBox)

ÂÂ ? System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Boolean isSingleParameter)

ÂÂ ? System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)

ÂÂ ? System.Windows.Threading.Dispatcher.WrappedInvoke(Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)

ÂÂ ? System.Windows.Threading.DispatcherOperation.InvokeImpl()

ÂÂ ? System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state)

ÂÂ ? System.Threading.ExecutionContext.runTryCode(Object userData)

ÂÂ ? System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)

ÂÂ ? System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)

ÂÂ ? System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

ÂÂ ? System.Windows.Threading.DispatcherOperation.Invoke()

ÂÂ ? System.Windows.Threading.Dispatcher.ProcessQueue()

ÂÂ ? System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)

ÂÂ ? MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)

ÂÂ ? MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)

ÂÂ ? System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Boolean isSingleParameter)

ÂÂ ? System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)

ÂÂ ? System.Windows.Threading.Dispatcher.WrappedInvoke(Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)

ÂÂ ? System.Windows.Threading.Dispatcher.InvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Boolean isSingleParameter)

ÂÂ ? System.Windows.Threading.Dispatcher.Invoke(DispatcherPriority priority, Delegate method, Object arg)

ÂÂ ? MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)

ÂÂ ? MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)

ÂÂ ? System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)

ÂÂ ? System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame)

ÂÂ ? System.Windows.Threading.Dispatcher.Run()

ÂÂ ? System.Windows.Application.RunDispatcher(Object ignore)

ÂÂ ? System.Windows.Application.RunInternal(Window window)

ÂÂ ? System.Windows.Application.Run(Window window)

ÂÂ ? System.Windows.Application.Run()

ÂÂ ? WBFSManager.AppMain.Main()
---------------------------
??ÂÂ 
---------------------------
 
Something strange happened to me. I was adding a game from an ISO when it stopped midway through with an error. I think another process tried to get access to the ISO. Anyway, the game didn't appear on the list, but when I tried to redo the transfer, it would give me an error as if it was already on the hard drive. I had to manually delete it with the updated command line utility.

Also, if you change the name of the game on the ISO, your program won't accept it anymore. Perhaps you should disable that "feature" or put a warning.
 
AlexDP said:
Knocks said:
You can also lose the List button. The list command should be executed automatically when a WBFS partition is in focus.
That is a good suggestion but again, this goes back to my previous comment. If I do that, then everytime the user selects a drive letter, it would be "touched" by the application, and thats not something I'd like for any app to do to my drives, and as such I won't be doing that myself. When an app is gonna be missing with someones drives, it should require the user to explicitly initiate the action.

If a user is running a WBFS manager, he wants his WBFS partition "touched." You can't perform any operations without listing first, so the list command is really redundant.
 
One other possible feature: Is there a way to verify the image on the disk? Someone mentioned in another thread that Wii games have a SHA1 checksum built-in. If so, that could be used to ensure the game hasn't been corrupted.

BTW, a tip for everyone: I had accidentally deleted a game with the old wbfs tool, then re-added it from an ISO. This damaged the game that was originally next to it. If this happens, delete BOTH games and re-add them both using the latest wbfs tool.
 
hdhacker said:
One other possible feature: Is there a way to verify the image on the disk? Someone mentioned in another thread that Wii games have a SHA1 checksum built-in. If so, that could be used to ensure the game hasn't been corrupted.
This is a great idea! Seconded!
 
hdhacker said:
Something strange happened to me. I was adding a game from an ISO when it stopped midway through with an error. I think another process tried to get access to the ISO. Anyway, the game didn't appear on the list, but when I tried to redo the transfer, it would give me an error as if it was already on the hard drive. I had to manually delete it with the updated command line utility.

Also, if you change the name of the game on the ISO, your program won't accept it anymore. Perhaps you should disable that "feature" or put a warning.
I'm not sure what your referring to about the renaming. Renaming works fine, whether you do it on the Games To Add side, or on the WBFS Drive....


Knocks said:
AlexDP said:
QUOTE(Knocks @ Apr 13 2009, 04:35 AM) You can also lose the List button. The list command should be executed automatically when a WBFS partition is in focus.
That is a good suggestion but again, this goes back to my previous comment. If I do that, then everytime the user selects a drive letter, it would be "touched" by the application, and thats not something I'd like for any app to do to my drives, and as such I won't be doing that myself. When an app is gonna be missing with someones drives, it should require the user to explicitly initiate the action.

If a user is running a WBFS manager, he wants his WBFS partition "touched." You can't perform any operations without listing first, so the list command is really redundant.

I understand that the user obviosuly wants his WBFS partition touchd
smile.gif
the problem is, in order to check if the partition is indeed WBFS, I would need to access said partition.
 
FenrirWolf said:
Does the SHA-1 Checksum thing care that the update partition is missing? If so it would report every game as corrupt...
why would it. scrubbing doesn't remove the update partition. update partitions should be included in every valid iso. the loaders just circumvent the update partition. if you had removed the update partition it would be a image that needs trucha to be present.

or did i get something wrong.
 
AlexDP said:
hdhacker said:
Something strange happened to me. I was adding a game from an ISO when it stopped midway through with an error. I think another process tried to get access to the ISO. Anyway, the game didn't appear on the list, but when I tried to redo the transfer, it would give me an error as if it was already on the hard drive. I had to manually delete it with the updated command line utility.

Also, if you change the name of the game on the ISO, your program won't accept it anymore. Perhaps you should disable that "feature" or put a warning.
I'm not sure what your referring to about the renaming. Renaming works fine, whether you do it on the Games To Add side, or on the WBFS Drive....

I renamed the game title of an ISO. I then tried to add it to the drive and I got an error message saying something about the ISO not being recognizable.
 
AlexDP said:
I understand that the user obviosuly wants his WBFS partition touchd
smile.gif
the problem is, in order to check if the partition is indeed WBFS, I would need to access said partition.

You wouldn't be touching any random partition though. If the user has used the Manager before, the program will open the last used partition, right? That partition will be used WBFS, so no problem. And if this is his first time using WBFS Manager, then he would have to select the correct WBFS partition from the list manually. The program shouldn't perform the list command on non-WBFS partitions obviously, which is just a simple check.

I'm just a fan of clean interfaces.
smile.gif
 
I just wanted to comment on this great tool. It is what I use daily now for my WBFS management...

I did however want to request a feature. Multiple ISO extraction. It would be nice to be able to select multiple games to extract and have them save with their respective HD filenames in ISO format to the PC drive. I couldn't imagine this feature would be difficult to add (I was actually surprised that is wasn't there initially!) and would make the manager a little more complete
smile.gif
 
Screemer said:
FenrirWolf said:
Does the SHA-1 Checksum thing care that the update partition is missing? If so it would report every game as corrupt...
why would it. scrubbing doesn't remove the update partition. update partitions should be included in every valid iso. the loaders just circumvent the update partition. if you had removed the update partition it would be a image that needs trucha to be present.

or did i get something wrong.
I understood that single partitions are signed and not the whole disc. And did you ever inspected a ISO which is extracted from WBFS? At the moment I just have Wii SPorts Resort here extracted, but it just has Partiton: 0 - PART INFO and Partition: 1 - Data (Game), no Update partition.
 

Site & Scene News

Popular threads in this forum