Notes:

TbScan(X) does not mean TurBo-SCAN as some users assume, but stands for
Thunderbyte Scan. TbScan and TbScanX are supplied on the Thunderbyte
disk.

TbScan and TbScanX both need a signature file TBSCAN.DAT or
VIRUSSIG.DAT. Because these files are updated a lot, they are not
supplied with this package. Both of these files are available at
Thunderbyte support BBS +31-85-212395 or at many other BBSs.

Some users think that scanning for all viruses in all files is the best
scanning method (by using "TBSCAN *.* -a +n"). This is not true: It only
increases the possibility of false alarms. It is not usefull to scan for
bootsector viruses in .COM files or to scan for COM viruses in .EXE
files. Use this option only when you already encountered a virus and
want to make sure that you really destroyed all infected files.

If you run TbScan AFTER running another scanner, it is possible tyhat
TbScan finds signatures of viruses in memory. This does not mean that
you have a virus, but is caused by the fact that TbScan detects the
signatures left in memory by the other virusscanner.

If you loaded TbScanX in video-memory it is possible that TbScan detects
signatures in high memory if you are using the -e switch.

Due to safety routines in the TbScan program, it can not be compressed
with programs like PkLite, LzExe, or Diet. This is not very painfull
after all because the file isn't that big!

TbScanX is Windows 3.0 aware. It is possible to load TbScanX BEFORE
starting a Windows 386-enhanced-mode session. TbScanX will not interfere
with copies of it running in other DOS windows.