Imageusb

Author: e | 2025-04-25

★★★★☆ (4.4 / 3406 reviews)

chrome os pc

- ImageUSB portable; - ImageUSB portable; - ImageUSB portable; - ImageUSB 1.3 Build 1001 portable; - ImageUSB portable; - ImageUSB portable; - ImageUSB portable; - ImageUSB portable; - ImageUSB portable; - ImageUSB portable; - ImageUSB portable; - ImageUSB portable; - ImageUSB 1.3 Build 1001 portable; - ImageUSB portable; - ImageUSB portable; - ImageUSB portable;

Download Website Block Software

ImageUSB PassMark ImageUSB( U ) v

(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

ImageUSB - скачать бесплатно ImageUSB - SoftPortal

Junior Member Join Date: May 2013 Posts: 4 ImageUSB does not seem to have a problem creating/verifying image files created from NTFS drives. However, when attempting to verify after writing from an NTFS image file, it always gets a checksum error. I notice that the USB drive is remounted as soon as the writing is complete (before verification starts). I suspect that Windows is writing to the drive when the mount occurs and that is causing the verification error. Is it possible to add an option to not remount the USB drive after writing? Administrator Join Date: May 2010 Posts: 899 I tried to replicate this on my local machine and was unable to get the verification problem you are seeing.1. Format USB Stick NTFS2. Create Image with Verification On (PASSED)3. Write Image to USB Stick with Verification On (PASSED)If you run the software in debug mode (see help file) when it does verification, in additional to the checksums checks, it will also do actual byte comparison and output the offset where the contents differ in the logfile.Other things:Did you create the image on a different machines? What was the OS used? Different user accounts with different permissions? Comment Junior Member Join Date: May 2013 Posts: 4 Tried XP and Windows 7 Originally posted by Richard (PassMark) View Post I tried to replicate this on my local machine and was unable to get the verification problem you are seeing.1. Format USB Stick NTFS2. Create Image with Verification On (PASSED)3. Write Image to USB Stick with Verification On (PASSED)If you run the software in debug mode (see help file) when it does verification, in additional to the checksums checks, it will also do actual byte comparison and output the offset where the contents differ in the logfile.Other things:Did you create the image on a different machines? What was the OS used? Different user accounts with different permissions? I'll try the logging. I tried creating the image and writing to the USB drive on two different machines and two different operating systems (XP and Windows 7), they both reacted the same way. The USB drives are: Kingston Digital DataTraveler SE9 8GB USB 2.0 (DTSE9H/8GBZ). Comment Junior Member Join Date: May 2013 Posts: 4 WinDiff and Log FilesI repeated the whole process (creating/restoring the image) on a Windows XP machine. I also ran WinDiff against the original directory structure that the source USB drive was created from. Even though it fails verification, the contents are identical which is why I think it may be an NTFS log issue.Here's the ImageUSB log you requested:10-May-2013 - 05:43:52:281 - PassMark Software - imageUSB v1.1.101110-May-2013 - 05:43:52:281 - Getting list of available removable USB drives...10-May-2013 - 05:43:52:296 - Inspecting Drive C:\...10-May-2013 - 05:43:52:296 - Inspecting Drive D:\...10-May-2013 - 05:43:52:296 - Inspecting Drive E:\...10-May-2013 - 05:43:52:312 - Inspecting Drive Z:\...10-May-2013 - 05:43:52:312 - Ready...10-May-2013 - 05:45:07:062 - Drive E:\ added to queue.10-May-2013 - 05:45:07:062 - Creating image from Drive [E:\]...10-May-2013 - 05:45:07:078 - Creating image D:\Transfer\ThumbDrive\ThumbDriveImage.bin from E:\. - ImageUSB portable; - ImageUSB portable; - ImageUSB portable; - ImageUSB 1.3 Build 1001 portable; - ImageUSB portable; - ImageUSB portable; - ImageUSB portable; - ImageUSB portable;

Free imageusb Download - imageusb 1.4. - UpdateStar

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, Tried using Clonezilla but found it difficult to use, and we did not have any success with it. Then we came across HDDGURU HDD Raw Copy Tool. It has a very user friendly GUI and was simple to use. It took 3.5 hours to clone the drive (USB to serial adapters USB 1.1), but in the end we had a cloned drive. We plugged the new drive into our spare Posix box and everything worked fine.I found HDD raw copy tool to be the best solution for our situation. I would mention that we done this on an XP machine. We do have a Windows 7 machine but have not tried it on there yet, but I thought this experience with HDDGURU HDD Raw Copy Tool may be informative and useful for others . New 14 Aug 2012 #6 Welcome to SevenForums and you start your journey here with a rep.:) Thanks ka0jdn for sharing your valuable experience and bringing back to life this almost 9 months old thread. This almost immediately set my mind rolling. We have been discussing ways and means of cloning a bootable flash drive which brought to the fore two programs ImageUSB and USB Image Tool. Why not use this HDD RAW Copy Tool? And so here it is. Plug in the Source UFD (here my 1 GB Imation bootable Lucid Puppy drive) and the Target UFD ( my 8GB HP v220w UFD) and run HDDRawCopy1.02Portable.exe . ( I downloaded the Windows executable requiring no

Free imageusb 汉化 Download - imageusb

Restart سيبدأ حاسوبك بعملية اعادة التشغيل ولكن قبل الاقلاع للويندوز سوف يخضع لإجراء الاختبار علي الرامات وستظهر لك شاشة تماماً مثلما هو موضح في الصورة أعلاه، شاشة زرقاء يُعرض بها شريط لمعرفة حالة الاختبار والوقت المستغرق للانتهاء لذلك تحلي بالصبر لحين ينتهي الاختبار وسيتم إعادة تشغيل حاسوبك تلقائياً بمجرد انتهاء الاختبار. ثم عند الانتقال لسطح المكتب بعد تشغيل الحاسوب مجدداً ستظهر لك نافذة علي الشاشة توضح لك نتيجة الاختبار وما إذا كان هناك مشاكل بالفعل ام لا وما هي المشكلة بالتحديد ومن ثم عليك اما البحث عن حلها او شراء رامات جديدة.- الطريقة الثانية بإستخدام برنامج MemTest86في حالة اذا كانت الاداة الخاصة بالويندوز اخبرتك ان لا وجود لمشاكل في الرامات لكنك لازلت مقتنع أن هناك مشكلة هنا يجب عليك استخدام أداة MemTest86 الاحترافية والمتقدمة لاختبار الرامات وعرض المشاكل الخاصة بها. فهي أداة حجمها صغير لكنها تعمل بشكل ذاتي اي ستحتاج إلي حرق الاداة علي CD او DVD او فلاشة USB حتي يتم إجراء الاختبار بعيداً عن الويندوز.ولحرقها علي فلاشة او اي قرص تخزين آخر ستقوم بالتوجه لصفحة تحميل الاداة ثم قم بالتمرير للاسفل لتضغط علي رابط "Image for creating bootable USB Drive" وسيتم تحميل ملف مضغوط ستقوم بفك الضغط عنه لاستخراج مجموعة من الملفات تضغط منها علي ملف imageUSB ليتم فتح نافذة خاصة بحرق الاداة علي فلاشة كما هو موضح في الصورة اعلاه.فتقوم اولاً بوضع "علامة صح" بجانب الحرف الخاص بالفلاشة التي تريد استخدامها لحرق الاداة عليها (يجب أن تكون خالية من اي ملفات) ثم بمجرد تحديد الفلاشة اضغط علي زر Write to UFD وانتظر لحين ينتهي من حرق الاداة

Free imageusb download Download - imageusb download for

Digital investigation for a new era Extract forensic data from computers, quicker and easier than ever. Uncover everything hidden inside a PC. Discover data Discover relevant data faster through high performance file searching and indexing. Extract passwords, decrypt files and recover deleted files quickly from Windows, Mac, Linux file systems and Android phones. Learn More Identify evidence Identify evidence and suspicious activity through our hash matching and drive signature analysis features. Identify and analyze all files and even automatically create a timeline of all user activity. Learn More Manage your case 360° Case Management Solution. Manage your entire digital investigation with OSF’s new reporting features. Build custom reports, add narratives and even attach your other tools’ reports to the OSF report. Learn More Collection of Tools OSForensics Discover relevant data and evidence faster through high performance file searching. Learn More OSFMount Mount local disk image files in Windows as a physical disk or a logical drive letter. Learn More OSFClone A self-booting solution which enables you to create or clone exact raw disk images. Learn More Training OSForensics courses offered to suit a diverse range of users and skill sets. Learn More Volatility Workbench Volatility Workbench is a graphical user interface (GUI) for the Volatility tool. Learn More ImageUSB Write an image concurrently to multiple USB Flash Drives. Learn More Latest Events Dallas Crimes Against Children (CACC) August 11 - 15, 2024 Dallas, TX Learn More Northwest ICAC Conference October 6 - 11, 2024 Seattle, WA Learn More See our full schedule of conferences and events for the year. See all Events. - ImageUSB portable; - ImageUSB portable; - ImageUSB portable; - ImageUSB 1.3 Build 1001 portable; - ImageUSB portable; - ImageUSB portable; - ImageUSB portable; - ImageUSB portable; - ImageUSB portable; - ImageUSB portable; - ImageUSB portable; - ImageUSB portable; - ImageUSB 1.3 Build 1001 portable; - ImageUSB portable; - ImageUSB portable; - ImageUSB portable;

PassMark ImageUSB -PassMark ImageUSB( U ) V

I bought a Surface Pro 3 and I moved the recovery partition to a USB flash drive, using the built-in Windows 8 tool. I would like to free up that USB drive and install the recovery partition on another USB drive. Is that possible? The "create a recovery drive" tool in Windows 8 will not work, because I cannot copy the recovery partition to that drive anymore (which is understandable, it was removed from the Surface). asked Sep 29, 2014 at 1:58 2 Since copying the files won't work, you can try to clone the USB drive to the other:Let the USB drive with the recovery partition be A, the blank one be B.Download ImageUSB and extract it (Winrar etc).Connect A and B to your computer and start ImageUSB.First we want to make a complete image of your pen drive and save them on the system. Now select your pen drive from the list and then click on Create from UFD option.Save it anywhere convenient (eg Desktop) and it will be saved it as .bin file on the system. Finally, click on Create image. Once it's done, select B and click Write to UFD.Now that it's done, remember to check if B is working!Read more here.Other methods to clone a USB here. answered Sep 29, 2014 at 6:13 Rsya StudiosRsya Studios3,6962 gold badges19 silver badges25 bronze badges You must log in to answer this question. Start asking to get answers Find the answer to your question by asking. Ask question Explore related questions See similar questions with these tags.

Comments

User5925

(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 -

2025-04-11
User5349

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

2025-03-29
User8128

Junior Member Join Date: May 2013 Posts: 4 ImageUSB does not seem to have a problem creating/verifying image files created from NTFS drives. However, when attempting to verify after writing from an NTFS image file, it always gets a checksum error. I notice that the USB drive is remounted as soon as the writing is complete (before verification starts). I suspect that Windows is writing to the drive when the mount occurs and that is causing the verification error. Is it possible to add an option to not remount the USB drive after writing? Administrator Join Date: May 2010 Posts: 899 I tried to replicate this on my local machine and was unable to get the verification problem you are seeing.1. Format USB Stick NTFS2. Create Image with Verification On (PASSED)3. Write Image to USB Stick with Verification On (PASSED)If you run the software in debug mode (see help file) when it does verification, in additional to the checksums checks, it will also do actual byte comparison and output the offset where the contents differ in the logfile.Other things:Did you create the image on a different machines? What was the OS used? Different user accounts with different permissions? Comment Junior Member Join Date: May 2013 Posts: 4 Tried XP and Windows 7 Originally posted by Richard (PassMark) View Post I tried to replicate this on my local machine and was unable to get the verification problem you are seeing.1. Format USB Stick NTFS2. Create Image with Verification On (PASSED)3. Write Image to USB Stick with Verification On (PASSED)If you run the software in debug mode (see help file) when it does verification, in additional to the checksums checks, it will also do actual byte comparison and output the offset where the contents differ in the logfile.Other things:Did you create the image on a different machines? What was the OS used? Different user accounts with different permissions? I'll try the logging. I tried creating the image and writing to the USB drive on two different machines and two different operating systems (XP and Windows 7), they both reacted the same way. The USB drives are: Kingston Digital DataTraveler SE9 8GB USB 2.0 (DTSE9H/8GBZ). Comment Junior Member Join Date: May 2013 Posts: 4 WinDiff and Log FilesI repeated the whole process (creating/restoring the image) on a Windows XP machine. I also ran WinDiff against the original directory structure that the source USB drive was created from. Even though it fails verification, the contents are identical which is why I think it may be an NTFS log issue.Here's the ImageUSB log you requested:10-May-2013 - 05:43:52:281 - PassMark Software - imageUSB v1.1.101110-May-2013 - 05:43:52:281 - Getting list of available removable USB drives...10-May-2013 - 05:43:52:296 - Inspecting Drive C:\...10-May-2013 - 05:43:52:296 - Inspecting Drive D:\...10-May-2013 - 05:43:52:296 - Inspecting Drive E:\...10-May-2013 - 05:43:52:312 - Inspecting Drive Z:\...10-May-2013 - 05:43:52:312 - Ready...10-May-2013 - 05:45:07:062 - Drive E:\ added to queue.10-May-2013 - 05:45:07:062 - Creating image from Drive [E:\]...10-May-2013 - 05:45:07:078 - Creating image D:\Transfer\ThumbDrive\ThumbDriveImage.bin from E:\

2025-04-08
User6214

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,

2025-04-11
User4863

Tried using Clonezilla but found it difficult to use, and we did not have any success with it. Then we came across HDDGURU HDD Raw Copy Tool. It has a very user friendly GUI and was simple to use. It took 3.5 hours to clone the drive (USB to serial adapters USB 1.1), but in the end we had a cloned drive. We plugged the new drive into our spare Posix box and everything worked fine.I found HDD raw copy tool to be the best solution for our situation. I would mention that we done this on an XP machine. We do have a Windows 7 machine but have not tried it on there yet, but I thought this experience with HDDGURU HDD Raw Copy Tool may be informative and useful for others . New 14 Aug 2012 #6 Welcome to SevenForums and you start your journey here with a rep.:) Thanks ka0jdn for sharing your valuable experience and bringing back to life this almost 9 months old thread. This almost immediately set my mind rolling. We have been discussing ways and means of cloning a bootable flash drive which brought to the fore two programs ImageUSB and USB Image Tool. Why not use this HDD RAW Copy Tool? And so here it is. Plug in the Source UFD (here my 1 GB Imation bootable Lucid Puppy drive) and the Target UFD ( my 8GB HP v220w UFD) and run HDDRawCopy1.02Portable.exe . ( I downloaded the Windows executable requiring no

2025-04-22

Add Comment