In order to be easily testable, a scanner must conform to the set of
conditions listed below. We believe that those conditions are fairly
reasonable, are not too restrictive, and are useful to both the end
users and the developpers of the product, because they allow them to
test it more easily.

Several of the scanners tested for this release of the test results do
*not* conform to those conditions. This makes the task to test those
scanners very difficult, annoying, and time-consuming. Therefore,
products that do not conform to those conditions will be discontinued
in the next releases of the test results. We label them as "not good
enough even to be worth testing". The users are strongly advised to
avoid those products.

Here is the list of conditions.

1) The scanner must be able to create a report file.

2) In the *beginning* (not at the end!) of this report file, the
scanner must list the directory path that has been scanned.

3) The scanner must be able to list in the report file all objects
that are scanned - not only those that it thinks are infected.

4) The full path of the scanned files must be present in the report
file. Long paths MUST NOT be abbreviated, e.g. by using "..." instead
of several intermediate directory names. Shortening the file paths is
acceptable when displaying them on the screen, but *not* in the
report file.

5) The scanner must be able to scan files with extensions defined by
the user, or if it is not so, it must at least scan the files with
extensions COM, EXE, SYS, and BAT.

6) The scanner must be able to run in "scan-only" mode. If its default
mode is to automatically disinfect all viruses found, there should be
an option to run it in "scan-only" (i.e., no disinfection) mode.

7) The scanner must be able to run unattended - and not to stop on
each infected object and request user input. When the program is ready
with the scan, it must be able to exit automatically and not wait for
additional user intervention.

8) The scanner must be able to run from the command line, scan a
subdirectory tree (not just whole drives) and create a report file
with a name and location supplied by the user.

9) If the scanner issues an audible alarm each time it detects a
virus, there should be a way to turn the sound off. This is not
necessary if the alarm is issued only once - at the end of the
scanning, but the alarm should be able to go away by itself, i.e.
without requiring user intervention.

10) The scanner must be able to run without problems on a huge
directory tree - i.e., something like 7,000 directories containing
20,000 files shouldn't be a problem for it.

11) The only limit of the size of the report file that the scanner
creates must be the amount of free disk space.

12) It should be possible to scan multiple diskettes without leaving
the scanner. The scanner should prompt the user to change the
diskettes. It must request ONE AND THE SAME input from the user
between two diskettes, regardless of whether a virus is found or not.

13) The report file generated when scanning multiple diskettes must
contain information about all the scanned diskettes - not only about
the infected ones, or only about the last one.