Jump to content

Verification Question


gleemonex

Recommended Posts

i just burned an iso with the latest imgburn and got some weird results from the verification process afterwards.

 

I 19:19:30 Verifying Sectors...

I 19:26:05 Device MD5: f677811101d818cc65b0e441a2a05aa1

I 19:26:05 Device (Padded) MD5: d37d25306bad80ea61ed9b97843a9172

I 19:26:05 Image MD5: f677811101d818cc65b0e441a2a05aa1

I 19:26:06 Operation Successfully Completed! - Duration: 00:06:36

I 19:26:06 Average Verify Rate: 11,574 KB/s (8.4x) - Maximum Verify Rate: 16,765 KB/s (12.1x)

 

if the md5s didn't match, why didn't the program tell me there was a problem? i just got the "Operation Successfully Completed!" box.

 

btw, what does the "padded" mean?

Link to comment
Share on other sites

The MD5s did match (device vs image). If you look at the version history, it explains the padded MD5.

 

Added: An alternative 'Padded' MD5 calculation for when burning + verifying an image on DVD+R media where the drive automatically pads the image so the last sector is divisible by 16.

Regards

Link to comment
Share on other sites

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.