Windows MD5 Sum generator.
Compiled in Delphi 7, so this may be buggy. I'm hoping the Large Fonts issue
some people have been experiencing is fixed by Delphi.
Coments at the top of generated md5 files with date and time of creation.
Semicolon (";") at the start of a line denotes a coment, just as hash ("#") does currently.
Err, some other minor stuff too, but I forget now.
Version 184.108.40.206:Visual changes, mostly affecting Windows XP
Important note: The old md5summer (v220.127.116.11
and older) got its file size information from windows. This filesize is included
as part of the data being checksumed so any change in the reported file size
affects the resulting sum. Unfortunately in some cases windows was reporting
the filesize incorrectly. For this reason the old md5summer gave a checksum
which was always the same (and in a way, correct) but that differed from what
other checksum programs with correct file sizes reported. The new md5summer
no longer relies upon windows to supply the filesize, and hence gets a checksum
that in some cases differs from the old md5summer, but agrees with all other
MD5 checksum programs.
What does this mean? If you have calculated checksums (with an old version of md5summer) on files >200MB and saved the result in a .md5 file for later verification, the new md5summer may report a verification failure when in fact the only difference is that noted above. I will endevaour to release a version of md5summer which detects this.
Version 18.104.22.168:Only 3 changes, all fairly significant though:
Version 22.214.171.124:Again only a few little extras:
Version 126.96.36.199:It's .19 but with a few little extras:
Version 188.8.131.52:Several items of the "To do" list were checked off for 1.1:
MD5summer was originally a tool to help me in my work. I was working on some windows software that was distributed on CD. I didn't have a CD writer in my machine but my colleague down the hall did. This arrangement involved a lot of FTP file transfers from my machine to his. Testing of my CD's was bringing to light a lot of errors that I just couldn't explain, then someone suggested that there may have been errors introduced during the transfer from my machine to his or in the CD burning process. Since my colleagues machine was running debian linux, checking MD5sums of all the files was a snap, but actually generating the sum file was difficult as I only had a command line, non-recursive sum generator. Besides, I'm a GUI freak so I thought I'd make a nice windows version all my own. MD5summer is the resulting product.