imageUSB and the 512-byte header
Is there a reason that imageUSB doesn't include the 512-byte header when calculating the MD5sum? I need to image USB devices and archive them with an MD5 sum, but all of our current MD5 validation utilities include the 512-byte header, so I can't use the MD5sum returned from imageUSB.
Is there a way to optionally have imageUSB include the 512-byte header when calculating the MD5sum? Or failing that, are there MD5 utilities available for windows that would let me ignore the 512-byte header? I'm really just trying to save myself some time, by avoiding having a second process calculate the MD5 again.
Thanks for any input you can provide!
Tags for this Thread