MD5summer (v1.2.0.5) appears that it did not generate the correct hash value for a large file checked. It generated the correct code and verified its own executable (md5summer.exe) but when used on two large private ISO images downloaded from the 'net (630MB and 530MB respectively), it reported a "Checksum did not match" error. After doing much checking, I finally tried a command line utility (md5 - http://www.fourmilab.ch/md5/\) and was able to verify that the provided md5 did match the downloaded file. Since I could not see the actual generated code, I could not tell if it was generating an improper code, or it was not able to match the code that it generated with what was provided.
I've provided only the md5 supplied for the download, not the image itself (since it is both not permitted and large).
md5 file used that did not match the hash code
What is the status of this bug? I want to use md5summer to verify transfer of a number of files (both small and large), but it's not going to be much help if it generates the wrong checksums in some cases.