Download imageusb 1 5 1000

(drive 1)10-May-2013 - 06:02:20:906 - Drive E:\ - Image completed.10-May-2013 - 06:02:20:906 - Drive E:\ - MD5 Checksum: 46E32625BC7AD46A7FB85A4D48AA6DE210-May-2013 - 06:02:20:906 - Drive E:\ - SHA1 Checksum: 84971417F7AFB7AAC0D47715FDB2B736551133D410-May-2013 - 06:02:20:921 - Verifying Image D:\Transfer\ThumbDrive\ThumbDriveImage.bin created from Drive E:\...10-May-2013 - 06:05:06:468 - Drive E:\ checksum completed.10-May-2013 - 06:05:06:468 - Image D:\Transfer\ThumbDrive\ThumbDriveImage.bin - MD5 Checksum: 46E32625BC7AD46A7FB85A4D48AA6DE210-May-2013 - 06:05:06:468 - Verification passed - MD5 matched. (E:\).10-May-2013 - 06:05:06:468 - Image D:\Transfer\ThumbDrive\ThumbDriveImage.bin - SHA1 Checksum: 84971417F7AFB7AAC0D47715FDB2B736551133D410-May-2013 - 06:05:06:484 - Verification passed - SHA1 matched. (E:\).10-May-2013 - 06:09:13:906 - Getting list of available removable USB drives...10-May-2013 - 06:09:13:906 - Inspecting Drive C:\...10-May-2013 - 06:09:13:906 - Inspecting Drive D:\...10-May-2013 - 06:09:13:906 - Inspecting Drive E:\...10-May-2013 - 06:09:14:687 - Inspecting Drive Z:\...10-May-2013 - 06:09:42:062 - Drive E:\ added to queue.10-May-2013 - 06:09:42:250 - Writing image D:\Transfer\ThumbDrive\ThumbDriveImage.bin to E:\ (drive 1)10-May-2013 - 06:44:26:218 - Drive E:\ write completed.10-May-2013 - 06:55:06:140 - Drive E:\ checksum completed.10-May-2013 - 06:55:06:156 - Drive E:\ - MD5 Checksum: C1534ED10DC46A0385A478F3C20CAD8A10-May-2013 - 06:55:06:171 - VERIFICATION FAILED!!! MD5 Checksum does not match (E:\). Image MD5 Checksum: 46E32625BC7AD46A7FB85A4D48AA6DE210-May-2013 - 06:55:06:171 - Drive E:\ - SHA1 Checksum: 991039FFC0DC49F573C4CE26659F2C632A2823A910-May-2013 - 06:55:06:187 - VERIFICATION FAILED!!! SHA1 Checksum does not match (E:\). Image SHA1 Checksum: 84971417F7AFB7AAC0D47715FDB2B736551133D410-May-2013 - 06:55:16:812 - Exiting... Comment Administrator Join Date: May 2010 Posts: 899 That seems to be the is the normal log that is output. To have imageUSB output debug information you need to start imageUSB with the "-d" command line arguement. It will save the debug information into the logfile, "imageUSB.log". Quick way to do this is create a shortcut to imageUSB.exe. Right click->Properties and then edit the target. (i.e. "C:\Users\Passmark01\Desktop\imageUSB\imageUSB .exe -d") Comment Junior Member Join Date: May 2013 Posts: 4 Sorry, I missed the -d switch when I scanned the help...10-May-2013 - 18:55:48:281 - PassMark Software - imageUSB v1.1.101110-May-2013 - 18:55:48:296 - Getting list of available removable USB drives...10-May-2013 - 18:55:48:296 - Inspecting Drive C:\...10-May-2013 - 18:55:48:312 - Debug: Thread (3204) Drive C:\: Not of USB Type Skipping. DriveType 310-May-2013 - 18:55:48:312 - Inspecting Drive D:\...10-May-2013 - 18:55:48:312 - Debug: Thread (3204) Drive D:\: Not of USB Type Skipping. DriveType 310-May-2013 - 18:55:48:328 - Inspecting Drive E:\...10-May-2013 - 18:55:48:328 - Debug: Thread (3204) Drive E:\ Size: 7797530624 Bytes Volume: LogiQuest APLs Other: NTFS10-May-2013 - 18:55:48:328 - Inspecting Drive Z:\...10-May-2013 - 18:55:48:343 - Debug: Thread (3204) Drive Z:\: Not of USB Type Skipping. DriveType 210-May-2013 - 18:55:48:343 - Ready...10-May-2013 - 18:56:43:312 - Drive E:\ added to queue.10-May-2013 - 18:56:43:312 - Debug: Thread (2840) Successfully opened image file D:\Transfer\ThumbDrive\ThumbDriveImage.bin (7802454528 bytes) for read acess.10-May-2013 - 18:56:43:328 - Debug: Thread (2840) imageUSB image. Actual image size (w/o header) is 7802454016 bytes.10-May-2013 - 18:56:43:343 - Debug: Thread (2840) UFD \\.\PhysicalDrive1 size 7803174912 bytes.10-May-2013 - 18:56:43:343 - Debug: Thread (2840) Unmounting UFD E:\ to prepare for write.10-May-2013 - 18:56:43:500 - Writing image D:\Transfer\ThumbDrive\ThumbDriveImage.bin to E:\ (drive 1)10-May-2013 - 18:56:44:453 - Debug: Thread (2840) Writing...0.1%10-May-2013 - 18:56:44:984 - Debug: Thread (2840) Writing...0.3%10-May-2013 - 18:56:45:484 - Debug: Thread (2840) Writing...0.4%...10-May-2013 - 19:30:34:015 - Debug: Thread (2840) Writing...99.7%10-May-2013 - 19:30:37:187 -

Usb. Also, I have the latest version Does anyone have any other pointers. Ive tried different OS but that does not work. Ive run imageusb in compatibility mode and as admin always still not working. I ran debug mode.The funny thing is, imageusb worked a few times for me and verified 5 drives at one time success a few times and then it started failing. I cant figure out why. Comment Administrator Join Date: Jan 2003 Posts: 10625 What was the output from debug mode?What file(s) had different sizes?Maybe there is some other process running on the machine that is making changes on the USB drive (in parallel between the write and verify stages).This might be malware replicating itself on to the USB drive, it might be some background file backup task that flags files on the USB drive as backed up, it might be some anti-virus program scanning the drive then making changes in NTFS to indicate which files have been scanned. Comment Junior Member Join Date: Jan 2015 Posts: 2 I guess I just wont use Verify any more!I was also hoping maybe passmark could add in a write speed status on each usb for imgusb software during imaging Comment

A while ago I had some hardware issues with my desktop and used a USB stick to put a bootable memtest on it to do some diagnosis (at the time it was that one of the memory sticks was bad). Fast forward several weeks later however and now I'd like to find a way to get rid of memtest on my USB so that I may use it again for storing small documents and things of that nature. Would anyone know how to restore a USB stick to its original state? asked Feb 6, 2013 at 21:27 1 Insert USB Disk.Launch the imageUSB program that you used to create the MemTest86 USB and select the appropriate USB Disk. (Be careful and select the correct drive!).Choose the Zero USB Disk option & Run.Drive MBR (Master Boot Record) is now Zeroed. You will need to reinsert the drive for Windows to recognize it and prompt for formatting before you can use it again. A normal format will now recover the full capacity of the USB drive. answered May 2, 2015 at 3:33 3 Just format the drive, which will make it unbootable and empty. answered Feb 6, 2013 at 22:09 TFMTFM4,2732 gold badges32 silver badges37 bronze badges 1 No need to format your device!If you can't remove or change anything, then probably your USB Stick is in "Read-Only" state.Otherwise, smtg is wrong with your driver or there is a stupid virus. But if all is OK, just make your Windows show all System and Hidden files,or start CMD.exe and write there: attrib -s -h -r \*.* /s /dNow all files are visible and are not Read-Only, including memtest. Now you can remove all odd files! answered Feb 6, 2013 at 23:16 JetJet2,56628 silver badges35 bronze badges You can do it without imageUSB. From the memtest86 7.4 USB package readme file: WARNING: THIS PROCESS WILL COMPLETELY DELETE THE DATA ON THE DRIVE For Linux/Mac: 1) Insert the USB drive into a USB slot. 2) Determine which device the USB drive is assigned as (eg. /dev/sdc on Linux, /dev/disk1 on Mac). 3) As root,