Notes on md5 file format: 

In order to check md5s against the shns, the md5 file must have a 
separate line of info for each shn to be checked. Example:

4144acb1b7a6a9cc7a77ae34d2d494cb *gd74-08-06d2t01.shn
cb067cc0d062754bc20a8fb2ac0095cc *gd74-08-06d2t02.shn
8e9b5383b35b1f19718d2fcb60362e1f *gd74-08-06d2t03.shn

Each 32-character checksum is followed by a space, an asterisk, the shn 
filename (which must exactly match the name of the shn file you have), 
and then some kind of carriage return to make a fresh line for 
the next checksum. Because Unix, DOS and Mac can all differ in 
how they end lines in a file and sometimes in how they create md5s, you 
may occasionally get md5s where a) the lines look "run together" on your 
system, b) the lines have "weird" characters at the ends, or c) the 
asterisk is missing. End of line problems may confuse your md5 checking 
program, and filename mismatches will certainly do so. 

If you think you have one of these problems, open your md5 file(s) in a 
plain text viewer. Add asterisks or carriage returns or delete strange 
end-of-line characters as needed. Change possible typos in filenames to 
match the actual names of the shns you have. Save the changes. 
Linux/Unix users can also use the dos2unix or the flip utility to quickly 
fix ends of lines.

Your md5 should run fine after these changes. 

Further tip: Set your ftp program to transfer md5 files in ascii mode 
(but do still use binary for shn files). This will cut down on format 
problems between platforms.