WiiJManager Multiplataform (Windows/OS X)

thx! can u post a download link please?

 

+1

 

Thanks for this it looks good, I have been having problems with WBFS manager 3.0.1 recently when extracting ISO to burn on a disc it doesnt do it properly and the result is an unusable ISO with missing info even if i put it back to the HDD its corrupted and wont play, this should be a welcome addition

 

haven't played around with this that much yet (literally 20 seconds so far), but I noticed the link to your blog in the about section actually links to google. Not a huge deal, the app looks very promising, thanks again!

 

wtf is a .wdf file?

 

wdf file description

 

Nice and good for many others. My wish list is very small (http proxy support) because I will stay on powerful command line. I have written some scripts around wwt+wit for maximum automatism, but I will play with the GUI too.

The results of my first tests are hang ups because of the missing http proxy support.

 

Plans to wwt diag checks?

 

@zon7

And remember: I'm able to spent an option (e.g. --gui) for machine readable outputs. Just ask for it.

Example:

Code:

# wwt list --gui
id=abcd12
name=disc name
title=title db
size=1234
itime=2010-03-06 12:34.54
mtime=...
...
END

id=xyyyzz
...

or

Code:

[ID6]
name=...
...

[ID6]
...

 

Schweet! Can't wait for the OSX version... us Mac users need some Apps too

 

Thanks from all the Mac users...

 

download links don't work??

 

I still get the same "The file you are trying to access is temporarily unavailable." message

 

Hint: Perhaps while the loaded PNG has a size of zero. (loading an invalid PNG?)

 

@wiimm:
I think it's time you tackle the file fragmentation issue with wwt on windows. It has been discussed before, but on windows to prevent fragmentation one has to pre-allocate the files. I'm pointing this out again, because with the existence of a gui i guess this will become a popular way to create .wbfs files, but in contrast to wbfs - fat and ntfs do get fragmented so appropriate measures have to be taken to prevent it. wwt in it's current form is not the best choice to create .wbfs file on fat/ntfs that would be played directly by a usb loader. In fact the only reason I kept on developing wbfs_file even though wwt is much more powerful is because it does prevent fragmentation. The code changes required to handle that are minimal, but I guess you would need to switch compiler from cygwin to mingw, which might be problematic.
On the other hand, a quick work-around the problem is to create these files on a local hdd first and then copy them using windows explorer to the external usb hdd, in this way files will not be fragmented.

Oh and another thing I remembered, a while ago i looked at the .wdf format for the possibility of playing it directly from the usb loader, but unfortunately in it's current form it is not suitable because data is not sector aligned. If I recall, the header is about 64 bytes long and then followed immediately by data. I would suggest to increase the header size to either 512 bytes or maybe even to 4096 bytes since this is becoming a popular sector size...