boco Posted February 5, 2011 Posted February 5, 2011 Another possible bug I encountered: I have MD5 file creation for images enabled in the settings. That works great for normal images (one big file). However if that image is split... Example: One has read and stored an split image and created the MD5 digest. DVDImage.i00 DVDImage.i01 DVDImage.i02 DVDImage.mds DVDImage.md5 But when looking inside the .md5 file, there's something like that: # MD5 checksum generated by ImgBurn v2.5.5.0 (http://www.imgburn.com) 0123456789abcdef0123456789abcdef *DVDImage.i00 ImageBurn basically slaps the name of the first part on the MD5 of the whole (unsplit) file. I would have expected multiple MD5 sums of the split parts for easy external verification. (I don't think a log is really needed here).
LIGHTNING UK! Posted February 5, 2011 Posted February 5, 2011 It's just not designed with split files in mind. It generates the MD5 of the image as a whole and is fed its data before the lower level code that decides which file gets written to.
boco Posted February 6, 2011 Author Posted February 6, 2011 Maybe you could state that in the option's tooltip (if there's no intent to change it)? Possibly even disable MD5 generation if a split image is to be created...
Recommended Posts