USB Image Tool 1.51 released

Version 1.51 is a minor update and just fixes two interface flaws.

Tags:

28 Responses to “USB Image Tool 1.51 released”

  1. Friedl Says:

    OK best tool

  2. aakash Says:

    gud software

  3. Peter (from AU) Says:

    Hi Alex,

    I managed to recreate a code 87 error: I bought a few USB keys and had to image them from saved images on my HD (all my boot USB keys are saved on my HD with your great tool). I have re-imaged them all but one. This one came up with error code 87. I retried few times and same again. Then I realised this one image was not really made by your tool but with Power ISO when I was trying unsuccessfully to make a bootable USB key from Paragon recovery CD. I saw in one of previous comments you came across with this error. To check this I tested few more bootable CDs: I would create an ISO from the CD and try to image the USB with it. Every time I got a code 87 error on the end of the writing to the USB key. It seams to me the direct image of bootable CD can not be used for a USB key… which is a shame coz I still can not get bootable USB of Paragon Manager 9. But you tool is a life saver: when you loose your USB drive, or it gets broken, or just dead you buy a new one and in few seconds you get it back and alive instead of hours of creating a new one! BTW you Pay Pal on German account for donations IS working just fine, I tested it 😉

  4. Alex Says:

    Thx, I just tested it with a CD image, and it came up with error 87 as well. I’m not exactly sure why, because the data itself shouldn’t matter, when you write it to a flash dive. It just won’t work, when you try to access it. I guess I will do some debugging there. For putting an ISO CD image on a flash drive I would have to do an on-the-fly file system conversion. Maybe I should take a deeper look into this, as so many people are asking for it. I did some FAT file system programming, when I wrote DiskXS. also, thanks for donating, it’s really appreciated.

  5. Mrmagic Says:

    I promess a donation if you do this, this tool WILL become famous if this is done, it’s already spreading in fame…Like nero or ultraiso at their beginning! 😉

  6. hyperx Says:

    Schade, leider .NET. Werde wohl doch weiterhin ein kleines Linux bemühen müssen …

  7. Alex Says:

    Das Kommandozeilentool benötigt kein .net. Dennoch werde ich diese Abneigung gegen .net nie verstehen. Wer Windows nutzt, kann auch .net nutzen, das macht dann auch keinen Unterschied mehr. Es beschwert sich ja auch keiner über die VC-Runtimes, die Windows sogar schon teilweise beeinhaltet, die Windows-API (jedenfalls über deren Vorhandensein) oder die JavaVM. Frameworks machen halt viele Dinge einfacher. Man muss das Rad (vor allem für GUI-Programmierung) nicht jedes mal neu erfinden.

  8. Ronald Müller Says:

    Zum Zeitpunkt bin ich am evaluieren des Tools. Das Backup läuft gut. Wenn jedoch das Image als Restore auf einen anderen Stick ausgeführt wird, so wird der Fehlercode 32 angezeigt. Schade, dass keine Hilfe mit den Fehlercode integriert ist.

    Mit der Befehlszeile komme ich auch nicht weiter:
    D:\>usbitcmd.exe r ATV te.img.gz

    Gibt Windows Seven die Fehlermeldung Das Programm wir nicht richtig ausgeführt. Das Programm wird geschlossen.

    Schade, wir möchten das Tool gerne als Zertifizierer in der Schweiz einsetzen. Könnten wir uns nicht direkt in Verbindung kommen!

  9. Alex Says:

    Die Fehlercodes sind die Standard-Windowsfehlercodes. Mit der nächsten Version kann ich auch einen detaillierteren Text dazu einbauen. Code 32 ist eine sharing violation. Vermutlich ist während des Restore noch ein Ordner auf dem USB-Stick geöffnet oder eine andere Operation greift noch darauf zu. Das Restore braucht exklusive Schreibrechte, da es auf niedriger Systemebene arbeitet.
    Der Aufruf des Kommandozeilentools ist nicht ganz richtig. Anstelle von ATV muss die device number eingetragen werden, die zu diesem Gerät mit “usbitcmd l” (kleines l für list) angezeigt wird. Das Image muss bei der Angabe auch im gleichen Verzeichnis oder im Suchpfad liegen.
    Mailkontakt geht auch über software(at)alexpage.de

  10. Dennis Says:

    Hello. I created an image file from a 32megabyte Memorex flash drive. The image file was created successfully. However, when I try to restore from the image file to the Memorex flash drive, I get a code 32: Could not access the image file! Am I doing something wrong?

    thx,
    d

  11. Dennis Says:

    Just tried a restore using command line mode with the command:

    usbitcmd r 2204 Memorex32.img /d

    And it worked!

    May be a privilege thing, but I tried running Image Tool as admin (but I am always logged in as admin).

    d

  12. jorge simoes Says:

    what is error 112?

  13. Alex Says:

    112 means not enough space on target drive. This could aslo be a result of writing an image of > 4GiB to a FAT32 hard drive. FAT32 only allows file sizes upto 4GiB.

  14. TeenTin Says:

    If restored a 2G image (bootable) to a 4G USB Thumbdrive in device mode, successfully. But how can I make use of the 2G unallocated space ? I have tried windows’ disk manager and partition magic, but failed.

    Thanks a lot !

  15. Alex Says:

    You can try it with the Gparted live CD.

  16. David Says:

    Hi-

    I have an image file I created on Linux. It dd’s to a usb stick on Linux fine – the image contains the whole device, including partition table and boot sector, and a FAT32 partition. I can then plug it into a Windows PC and Windows reads it ok.

    However, if I instead use USB Image Tool, on Windows, to write the image to the usb stick, then Windows can’t see the partition on the stick.

    Any ideas?

    Thanks

    David

  17. David Says:

    Actually this is wierd. I can read the partition in a command prompt, but not in Windows Explorer – even if I remove and unplug the stick.

  18. Alex Says:

    Did you use device mode? What partition type is it? Windows doesn’t recognize anything but FAT/FAT32 and NTFS. It also doesn’t really work well with multiple partitions on a removable flash drive.

  19. David Says:

    Yes, device mode. Partition type is FAT32. There is one partition on the image.

  20. Alex Says:

    This still sounds strange. Does it appear as an icon in Windows Explorer? has it the flash drive icon? Does Windows try to format it, when you click on it? Can you browse the directory in the command shell?

  21. David Says:

    Sorry for the delay, I’ll take a look soon.

    I have another question: USB Image Tool supports compressed images.

    I’m creating my image on Linux, could you give me details of which compression scheme you’re using please so I can compress them on Linux?

    Thanks

    David

  22. Alex Says:

    Compression is either zip or gzip.

  23. KC Says:

    I got “Could not access the usb device (Code: 3)!” when I tried to restore the empty bootsector. What does code 3 mean?
    Thanks

  24. Alex Says:

    This error code says “The system cannot find the path specified.”

  25. David Says:

    Worked fine this time. I’ll let you know if it happens again.
    Thanks for the .img.gz support – I wrote one out on Linux and USB Image Tool wrote it fine to a stick.

    It’d be great if a future version was able to generate self contained executables which included the img file and restored themselves to the user’s choice of stick. 🙂

    Thanks
    David

  26. Ejal Says:

    If you have a bootable ISO and want to make a bootable USB stick from it, 9 out of 10 times unetbootin (unetbootin.sourceforge.com) will do the trick.

    Since this is open source maybe you can find some info on how they did that, Alex.

  27. tahuma Says:

    Hallo Alex,

    ein Hinweis noch: es gibt Probleme mit langen Filenamen bzw. Leerzeichen im Filenamen (z.B. \Images und Backups\).
    Dies erzeugt beim Zurückspielen des Images folgende Fehlermeldung:
    “Could not convert internal zip file name to MBCS. Code 3”
    Aber ansonsten ein tolles Tool!

    long filenames or spaces produce error message:
    “Could not convert internal zip file name to MBCS. Code 3”

  28. Alex Says:

    Ich habe versucht, dies mal nachzustellen. Allerdings klappte es bei mir sowohl mit Leerzeichen als auch Umlauten im Pfad. Ich bräuchte etwas mehr Informationen. Wie war der vollständige Pfad inlusive Dateiname bzw. wie lang war er insgesamt? Compressed image file (imz)? Welches Betriebssystem (XP/Vista/7)?

Leave a Reply