Error message encoding is messed up

Thanks for the tip. I'll add this to my immediate todo for the next release update.

I've made the required modifications and pushed them to sourceforge. Please test this version to see if it works (if you can reproduce the error).

Also, this is the first build from this build environment (Windows 7, QT 4.84). I'm not sure if it still supports 32bit or not (should).

MD5sum:
4e3c1f4349aa47f5502630b1de901616 *win32imagewriter-0.6+fixes.zip

I didn't try it yet, but the code seems wrong. Did you test it? You'll get utf16 text in errormessage, so it shouldn't be declared char* as char is supposed to be used for encodings compatible with ASCII, i.e. zero byte means end of string. In utf16 is 2-byte encoding and you can get zero byte very often, e.g. for all ASCII characters. So you'll probably get only the first byte from the message as the second byte will be zero if Qt doesn' doesn't detect utf-16 heuristically, but I wouldn't rely on heuristics. I suggest to declare WCHAR *errormessage. Qt should understans it.
Like this:

WCHAR *errormessage=NULL;
FormatMessageW(FORMAT_MESSAGE_FROM_SYSTEM | FORMAT_MESSAGE_ALLOCATE_BUFFER, NULL, GetLastError(), 0, (LPWSTR)&errormessage, 0, NULL);
QMessageBox::critical(NULL, "File Error", QString("An error occurred when attempting to get a handle on the file.\nError %1: %2").arg(GetLastError()).arg(errormessage));

I am working on redoing these completely. I am also working on implementing translatable text strings. Should have another release very soon.