Path: utzoo!attcan!uunet!lll-winken!ames!killer!davidg
From: davidg@killer.DALLAS.TX.US (David Guntner)
Newsgroups: comp.sys.amiga
Subject: Re: Virusx 3.1 bug (was Re: Virusx bug)
Message-ID: <6754@killer.DALLAS.TX.US>
Date: 12 Jan 89 03:59:49 GMT
References: <2786@ihlpm.ATT.COM>
Organization: The Unix(R) Connection, Dallas, Texas
Lines: 30

From article <2786@ihlpm.ATT.COM>, by jmdavis@ihlpm.ATT.COM (Davis):
> I got my copy of VirusX3.1 from the Lattice BB, I noticed something strange.
> The .zoo file contains the executable, the zoo-ed source, a .doc file and
> a readme file as well as the kv stuff mentioned above.
  
> I read the .doc file, it was all about version 3.0 I installed virusx3.1
> and then read the readme file. THE README FILE SAYS VIRUSX SHOULD BE
> 11374 BYTES (or something close to that). I SIZED MINE AND IT WAS
> 11589 (or something close)!!!!!! ARRRRRRRRGH. I ran kv on it and it said there
> was no virus here. Furthermore, I always write protect my system disk,
> I downloaded, unzoo-ed, and executed it all from VD0: and I didn't get
> any of the normal IRQ virus symptoms.
  
> Does anybody know what gives?


It was simply a mistake on Steve's part.  I had the v3.0 version, and this 
number actually DID match the byte count of VirusX.  That message was in the
v3.0 notes, as you will recall.... :-)  As long as you run kv on the file and
it doesn't report the virus being in it, you're ok.  Steve just forgot to
update that byte count in the v3.1 notes (I know how you feel, my heart skipped
a couple of beats when I saw that they didn't match, until I realized what
the problem was... -- ran kv on it just to be sure, and it came out fine).
                  --Dave

-- 
        David Guntner  UUCP: {ames, mit-eddie}!killer!davidg
                       INET: davidg@killer.DALLAS.TX.US
"...Different ship, but she's got the right name. Treat   --Admiral L. McCoy
 her like a lady, and she'll always bring you home."    "Encounter at Farpoint"