While I was hacking the TrilogicV3.2 loader to make a Turbo Tape 250 loader to be used with my prg2tap tool I noticed that TAPClean was unaware of the Trilogic loader signature (i.e. the CRC value of the CBM DATA part of genuine Trilogic tapes). This resulted in the scan not being limited to using just the Trilogic scanner for Trilogic tapes when the option to only scan for formats whose signature is found in the CBM boot is enabled, which significantly increased scan times.
I’ve now added the signature in TAPClean v0.33-pre5 and I am reviewing the mechanism used to enable scanners when the option to only scan for those formats whose signature is found in the CBM boot is disabled. Off the top of my head I know that Trilogic tapes are usually single on tape, but if they weren’t, the current scan mechanism would not look for Trilogic files once the signature of a different format is found in the CBM boot. That’s probably not what should happen, or maybe it doesn’t matter because Trilogic files are really occurring without other formats upfront but a CBM boot🙂