Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!lavaca.uh.edu!uhnix1!sugar!ssd
From: ssd@sugar.hackercorp.com (Scott Denham)
Newsgroups: comp.sys.amiga
Subject: VirusX 4.0
Keywords: VirusX 4.0, task held, ouch
Message-ID: <4957@sugar.hackercorp.com>
Date: 18 Jan 90 19:49:42 GMT
Organization: Sugar Land Unix - Houston
Lines: 22

I hate to risk bringing up another round of VirusX 4.0 flames & claims,
but after running it quite happily on a BBS system since the day after
it was posted on Plink it's suddenly gone south on me, and I'm a bit
concerned that it could signal the presence of some unwanted guest
in the system somewhere.  Starting about a week ago, VirusX 4.0 dies
with a task held requestor immediately upon being started, whether from
startup-sequence or from a shell later. The subject system is a 1 meg
1.3 ROM, A500 with a Supra SCSI controller (not the new one) and a
ST277N.  To the best of my recollection, I didn't change anything on
the system around the time it started dying, and I almost *NEVER* test
uploaded software on the BBS system. VirusX 3.2 still runs fine, and
KV detects nothing amiss in the c: or other binary directories. Don't
see any odd named files lurking about, either, nor is anything happening
that might suggest there's a virus like unexplaied disk access, writes
to floppies, slow validation, etc.  I know there is a problem with stuff
that tries to use reserved locations, but I saw nothing for the first
month I ran the program.  Anybody have any comments, ideas, or 
suggestions???  
  
         Scott Denham 
           Houston, TX 
            ssd@sugar.hackercorp.com