🚀 go-pugleaf

>From:    microsoft!c-rossgr@uunet.uu.net

>>From:    padgett%tccslr.dnet@mmc.com (A. Padgett Peterson)

>>  6) Must be easy to remove for troubleshooting

>Hey, *my* code never needs to be removed! <grin>

Excuse me, but I use Virex-PC, which is Ross's product.  I do
occasionally need to remove it, not to troubleshoot IT, but because
something is incompatible with it.  One commercial game requires 540K
of FREE memory, not counting MOUSE.SYS, which it uses, and can't fit
if Virex-PC is installed.  A third-party fax board program has TSR
conflicts with Virex-PC.  I don't know what it is doing, but it tries
to take over the same interrupts as Virex-PC and the results are
unpredictable.  (Sometimes it refuses to run.  Sometimes it crashes.)
The need to remove an anti-viral program is not entirely a function of
the anti-viral program's flaws.  I have dealt with the problem by
defining a batch file which creates a dummy file which signifies that
on the next (warm) boot of my PC, Virex-PC is not to be loaded, and
then rebooting.  Anyway, Padgett is right.  A program must be easy to
remove in the event of trouble.  The trouble may not be the fault of
the program.  The game admits it is a hog.  The fax program is written
very sloppily, but it is worth the price I paid for it.  (It came free
with the fax modem board.)

          Robert McClenon
          Neither my employer nor anyone else paid me to say this.