Verify after Restore V2

[hajufu]

Hi Alex.

I want to use USBIT in my company to record 4 SD cards simultaneously with the command line tool with an image. The MD5 option is well suited to verify the written image, but there are thereby created 4x 2GB large files that are completely useless for me and a lot of time. If I define as a backup file NUL, no file is written, but I get no MD5 file. I should like to see here a parameter that forces the tool in a kind of test mode, so no image file but written an MD5 file. Can you implement this feature in a later version?

[Alex]

Could you describe the steps a little bit more in detail, f.e. the exact command lines you are using? The verify option /v does already a check of device against image after a backup/restore operation to ensure, that both are identical.

[hajufu]

Hi Alex. Thanks for the reply. You're right, with the option /v everything works as I want it. The problem was, I did not see this option. I have redirected the help of the command line tools into a text file and then open with notepad. I have seen the following:

Code: Select all

USB Image Tool 1.69
COPYRIGHT 2006-2014 Alexander Beug
http://www.alexpage.de

usbitcmd [mode] [device][:volume] [file] [/c] [/g] [/d] [/i] 

                                  [/h] [/t] [/p] [/s] [/n] [/b:xxxx]

mode       defines the operation mode:
           l  list detected USB mass storage devices
           d  show USB mass storage device details
           b  backup a USB mass storage device to an image file
           r  restore an image file to a USB mass storage device

device[:v] USB device number (reported in list mode) or
           Physical drive number (with /p option)
           Use :v to specify volume number in volume mode (optional)

file       image file for backup or restore

/c         compressed image file (imz)
/g         compressed image file (gzip)
/d         use device mode (for bootable devices)
/i         ignore size checks for gzip images
/h         create MD5 checksum in backup mode
/t         truncate oversize image files (only device mode, read FAQ!)
/p         device is the physical drive number instead of the USB device number
/s         scroll percentage output (for piped output in text files)
/n         show non-removable devices
/b:xxxx    read/write buffer size (in 512 byte blocks, 128 = 64kByte, max. 9999)

If I scroll the content, then I would have seen the last line.

Code: Select all

USB Image Tool 1.69
COPYRIGHT 2006-2014 Alexander Beug
http://www.alexpage.de

usbitcmd [mode] [device][:volume] [file] [/c] [/g] [/d] [/i] 

                                  [/h] [/t] [/p] [/s] [/n] [/b:xxxx]

mode       defines the operation mode:
           l  list detected USB mass storage devices
           d  show USB mass storage device details
           b  backup a USB mass storage device to an image file
           r  restore an image file to a USB mass storage device

device[:v] USB device number (reported in list mode) or
           Physical drive number (with /p option)
           Use :v to specify volume number in volume mode (optional)

file       image file for backup or restore

/c         compressed image file (imz)
/g         compressed image file (gzip)
/d         use device mode (for bootable devices)
/i         ignore size checks for gzip images
/h         create MD5 checksum in backup mode
/t         truncate oversize image files (only device mode, read FAQ!)
/p         device is the physical drive number instead of the USB device number
/s         scroll percentage output (for piped output in text files)
/n         show non-removable devices
/b:xxxx    read/write buffer size (in 512 byte blocks, 128 = 64kByte, max. 9999)

/v         verify image/device after backup/restore

BUT ...

The "v /" option is missing in the syntax (the version of the file usbitcmd.exe is still 1.69).

Anyway, thanks for the tool, and I hope that I can convince my employer to a small donation.