[toaster4]

Hello,

I am a noob to TLH, but have been using various trading software for about 10 years. I had been using windows xp until recently, but upgraded to windows 7 (64-bit) and now my older tools no longer work, so I gave TLH a try.

I'm in the process of reorganizing my collection and pulling files off old discs and moving them to an external hard drive.

My problem is with verification of md5 files. Files that verify as OK using md5sum cause errors in TLH with a "does not exist or cannot be opened" error.

Same fileset, same locations, etc.

With TLH:
----------
Checksum file 'D:\shnflac\badhat1994-09-10\badhat94-09-10d2.md5'

Line 1: file ' badhat94-09-10d2t01.shn' does not exist or cannot be opened.
Line 2: file ' badhat94-09-10d2t02.shn' does not exist or cannot be opened.
Line 3: file ' badhat94-09-10d2t03.shn' does not exist or cannot be opened.
Line 4: file ' badhat94-09-10d2t04.shn' does not exist or cannot be opened.
Line 5: file ' badhat94-09-10d2t05.shn' does not exist or cannot be opened.
Line 6: file ' badhat94-09-10d2t06.shn' does not exist or cannot be opened.
Line 7: file ' badhat94-09-10d2t07.shn' does not exist or cannot be opened.

There were errors.
----------

With md5sum:
----------
D:\shnflac\badhat1994-09-10>md5sum -c badhat94-09-10d2.md5
badhat94-09-10d2t01.shn: OK
badhat94-09-10d2t02.shn: OK
badhat94-09-10d2t03.shn: OK
badhat94-09-10d2t04.shn: OK
badhat94-09-10d2t05.shn: OK
badhat94-09-10d2t06.shn: OK
badhat94-09-10d2t07.shn: OK
----------

I created checksums for the files and they match what is in the md5's.

After playing with it and looking at everything, the errors that I see can be isolated to 1 thing, an asterisk (1 per line) in the md5 file. The filesets that I have that work ok under both follow a format of 'checksum *filename' whereas the ones that TLH doesnt work on are just 'checksum filename'. I read the guide posted earlier in this thread on checksums, but the asterisk was not always present. tons of md5's on db.etree.org do not have them (like this ones for the show in this example at http://db.etree.org/md5view.php?md5key=88419).

I guess my real question is whether this is a bug or an intentional choice. I don't think I'd like to edit hundreds of older .md5 files just to have them work with TLH, but if it's an error on my part or something, please let me know so I can continue to use this program, its awesome.

Thanks guys,
toaster