Just a little project of mine, that I thought I would share.
Basically, I have a scenario sometimes, where two files have the same size, but have somewhat different file names, but I suspect them of being the same file, one renamed.
An example of that, would be something like a pdf file in a zip file, that is a game manual, and the game got updated to v1.1, and that zip file was renamed to suit, and is the same file size, but could possibly be different. I have that happen a lot with downloads from the ZOOM Platform game website.
So rather than relocating a copy to another folder (as I have so often done), and renaming it to match the other file, and then testing with something like TeraCopy, I eventually decided to build my own simple MD5 checker that compares the MD5 value of two files, which it has calculated.
You populate the source fields by drag & drop, preferably to the GREEN and BLUE 'Source' labels.
Version one of the program was a simple affair, but then I decided to play around with progress bars, because I'd had it mind for a while, to develop my own for the Hash Encrypt function, which I use in several of my programs. The speed of incrementation of the progress bar, is tied to the previous calculation (file size & time), so at best is only approximate, so not much more than a guide, but hey, something is better than nothing.
The first thing I needed to do, was create a separate command-line based EXE file (MD5checker.exe) for doing the checksums. It records the file size and time taken and checksum values in a 'Setting.ini' file, shared with the calling program (MD5 Compare.exe). That calling program uses the AdLib commands, to check on the progress of the hashing, while waiting for it to complete for each file being compared.
MD5 Compare v1-2.zip
(29 + 1 previous downloads)
Enjoy!
P.S. If you want to use an algorithm other than the MD5 one, be my guest. I know we can use better ones, but as I sometimes use my program for other scenarios, that involve a recorded MD5 value, I've just stuck to MD5, which is reliable enough.