Awww, man... I don't mean to sound ungrateful, because it's got to be hard to even imagine all the time and "TLC" that have gone into TLH (and thank you
very much!), but I think someone should wake me up if and when TLH looks a little less like rocket science, really.
Last time I tried TLH was back around the Windows Security bug announcement here, and all I could get it to deal with .WAVs,
but back then I was thinking I wanted to do whatever it took to get the shntool fingerprints for .SHNs for TTD posts, so at the same time I installed shntool not realizing there were issues between TLH and the particular version, that were stated here
but were not stated on the download page for TLH where I got it. I tried everything I could think of (or read about here) to get rid of shntool but still could not get TLH to deal correctly with anything but .WAVs, and just gave up. After that, I still have not caught up with changes to TLH.
So, as always, mkwACT is where I end up back at, because that, I can get to actually work in the here and now when I need it. In fact, other than its distaste for those ubiquitous lines that begin with ye olde octothorpe #, I have never had a single difficulty with it nor needed to force my tiny brain to try to contend with many pages of complicated support for it.
Being the case that mwkACT chokes on info inside the .md5 file that it considers to be spurious, like the lines that identify the file as having been created by TLH or the MD5 Summer, I've copied and renamed and edited hundreds and hundreds of md5 files for torrents that were created by TLH, everything with the "spurious text" gets an extra edited .md5 file that will plainly state "all files verified correctly" with mkwACT - that is on top of the extra md5s that get generated to monitor corruption in text files and artwork images, since a lot of the md5s I get with torrents address only the audio files and not other contents. And then I pass them onto people who probably don't get why there are sometimes 3 or 4 checksum files with a single show, or the protocols I use to try make sure that they too can get a straight answer out of mkwACT, just by clicking on a single md5 file.
And I realize that this is splitting hairs somewhat, because I think mkwACT should announce file corruption in addition to announcing that it found characters it doesn't like, but this stuff can be pretty disconcerting for the novice user - it took quite a long time for me to fully trust that mkwACT wasn't one of those programs that stops on the first few errors it finds and then fails to announce additional ones.
And this is technically mkwACT's problem rather than TLH's of course, but if I've understood correctly, I probably shouldn't expect a fix from MKW?
So on behalf of myself and anyone else who may still be in this same boat, I'm wondering if it would be possible / adequate if TLH put an identifier for md5s that it created, into the
md5 file name or elsewhere, instead of into the md5 files themselves, so that these files will give a straight readout with mkwACT. Windows displays a date of creation for the md5 file anyway, so I'm guessing the date of creation doesn't actually need to be stated
in the md5 file itself at least?
And I know, this would be applicable to MD5 Summer as well, but 95% of the files in question came from TLH.
Or is all this just lazy and completely ignorant of me? (Likely so, and apologies if it is).