Thanks for the support guys!
Yes you can move it to the SD... they should work just great.
Batch conversion is a given... I'm just trying to get these bugs squashed first.
On that front... I've discovered the cause of all three bugs and I'm in the process of fixing them.
Bug #1, the error 9 bug, is a vista/windows 7 thing. What took me so long to track it down is I thought it was caused by one thing that doesn't work in vista, but it's caused by yet another thing that doesn't work in vista (why dear god why are any of you running vista?
)
Vista changed the variable type in one of my api calls, in 9x and xp you could use one or the other but in vista and window 7 they removed one of them for no apparent reason. I've fixed this issue and now the error is gone!
Start Technical jargon
==================================
For any programmers out there especially those that are writing a wbfs gui.. the problem and solution is this:
"CreateProcess(vbNullString, cmdLine, pra, tra, True, 0, Null, vbNullString, sui, pi)" is used to create a process that you can later use CreatePipe on to grab the command prompt text from wbfs.
In vista it needs to be changed to: ""CreateProcess(vbNullString, cmdLine, pra, tra, True, 0, 0, vbNullString, sui, pi)"
You know what the difference between a null and a 0 is? Pretty much nothing... but that's vista for ya.
===================================
Now the second and third "bug" is vista not being able to see your drive..... this is really a vista "feature" combined with an incompatable version of wbfs.
Bug #2 is on your end and you can fix it right now! Type msconfig, goto the "tools" tab and scroll down to the line that reads "Disable UAP" and click "launch".
Now reboot. Now wbfs has write privelages on your computer because that annoying UAC "do you want to run this?" crap is disabled and this will be necessary for pretty much every version of wbfs.
Bug #3 is unfortunately due to my version of wbfs... it doesn't work well in vista at all and will seldom see your hdd. Fortunately I've found a better version that seems to work (and no, it is NOT delta, and yes it IS a cygwin variant) and I'll be updating the app to use it. Unfortunately, it has trouble extracting isos, which is the whole reason I used the current one in the first place! See I tried to give you guys the best version out there and then you complain for me doing so
Until cygwin builds improve, what I'll do for now is use both exes and allow the user to choose which one to use. My version is better, but if you can't use mine then the other is better than nothing I suppose.
Anyway further testing is required before a release I just wanted to give a status update.