Error repoted when writing image - unable to get handle on volume (Error 8)

[Simon Gordon]

Ran imagewriter 0.2 against the Ubuntu netbook remix (ubuntu-9.04-netbook-remix-i386.img)

An error occurred when attempting to get a handle on the volume.
Error 8:

The Device was correct, chosen as drive D
Windows is XP, SP2

Note I am not using an admin account (normal XP user)

Anyway I can get more diagnostics out to assist with this bug?

[k20z1 (k20z1)]

I've figured out the problem. All you have to do is rename the file, yes, that's it. I just renamed mine to "Netbook". Hope this helps. :)

[Simon Gordon (linux-sgordon)]

Hm, I think that counts as a workaround and hence this issue is still a bug.

Just to add to this, for my attempt the image was in a folder which had spaces and brackets in the path.

This, with k20z1's comment (his fix meant the filename had no dashes '-' in) implies that the tool does not handle filenames with certain characters?

  Si

[Jens Pranaitis (jens-jenux)]

For me this error only appears when writing without Admin priviledges (which I guess is normal), still it would be nice if the image writer could display a more accurate error message.

[Jeremy Davis (jedmeister)]

I was getting a similar error, but just when I started the app, not when I was trying to write the file. I found that if I disabled my floppy drive I no longer got the error.

[wethedgehog (vsyakvypadok)]

Everything is easy, guys.

You need to save the file with image (*.img, the name of is not important) and Image Writer at the root of disk (C:\ , D:\ etc.)

Image Writer will not work from desktop for example.

[Simon Gordon (linux-sgordon)]

Righto

Not had chance to test this myself, but if it's true that ImageWriter and the image need to be at the root of the disk, that's definately a defect.

  Si

[jeroen.kurvers (jeroen-kurvers)]

Disabling the floppy drive did the thing for me as well.

[Tuxinator (tuxdiving)]

The Image Writer was tested rooted deep within my own "My Documents" folder, the location of it does not matter. However the file extension ".img" needs to be in place, as the open file dialog will only display files ending in ".img" As far as the more user friendly error messages, I apologize for the inconvenience, but Microsoft seems to have failed in providing a "working" means of obtaining an error message from the error code (hence the reason for displaying the error code).

[Tuxinator (tuxdiving)]

I'm still not sure what is causing these sort of problems, but I am working on figuring out how to force windows to return an actual formatted error message, thus allowing more detailed/traceable bugs.

[JS (js1js2)]

Renaming the file, running as admin and copying to the root didn't work for me (and I don't have a floppy drive to disable). Instead, I right-clicked on the drive, hit eject and that seems to work fine.

[Alex Friedberg (blueal22)]

I used to get that error but when i ran image writer as admin it worked fine without a hitch

[Tobin Davis (gruemaster)]

Marking as invalid. No code was uploaded to fix this issue, so "Fix Committed" is inappropriate, and there is a viable workaround.