Have you ever created a bunch of CDs to give out to friends and family only to receive some back because they didn't work? Of course they worked since the other ones you sent out were fine. It must be them! But you wouldn't want to start a family feud over a burnt CD so you graciously make another copy. The next time you decide to burn stuff you should double check your work with FileCheckMD5.
So how will FileCheckMD5 help you out? Well part of this is understanding what MD5 is. In the most basic of terms MD5 insures that the copy you made is the same as the source. Often MD5 are used to double check software downloads on the Internet.
Brandon Staggs, creator of FileCheckMD5, developed an application that can recursively scan all the files and folders in your project and create a MD5 file that you can burn onto your CDs. That way, before you start sending out those disc you can double check if all the data made it intact. You can even burn the application along with your files to have the receiver check the integrity of the disc on their end.
Sure you could always just verify that your CDs were burned correctly using the built in checker that came with your burning software but asking your friends to check to make sure the MD5 hash matches sounds much more technical.
Reader Comments (Page 1 of 1)
7-16-2008 @ 10:24AM
Tom said...
When I put super important information onto a CD, I use (on windows) QuickPar and make as much par files as I can. You can make up to 150% recoveribility. Theoretically, if you drilled a hole through the cd and could somehow get the files unaffected by that hole to copy off, using all the parts of the .par files still there you could recover all data. I should do tests sometime. Would Download Squad blog about it if I did?
Reply
7-16-2008 @ 2:24PM
mrjason said...
bash users looking for something similar can use my md5tool.sh bash script that wraps around the md5sum gnu utils program:
http://www.worldsworstsoftware.com/md5tool.html
I personally use the script to verify backed up and archived data integrity on a regular basis. The script creates a checksum.md5 file in the directory you specify, that checksum.md5 file has the md5 checksums for every file found below the directory you specified. Then later you can run the script with the "CHECKALL" argument to make the script find and verify every checksum.md5 file it finds.
Reply