Path: utzoo!attcan!uunet!lll-winken!lll-lcc!ames!nrl-cmf!ukma!rutgers!att!mtuxo!mtgzy!felixc
From: felixc@mtgzy.att.com (Felix Cabral)
Newsgroups: comp.sys.amiga
Subject: Virusx bug
Keywords: Found possible bug in virusx
Message-ID: <4575@mtgzy.att.com>
Date: 4 Jan 89 14:24:00 GMT
Organization: AT&T, Middletown NJ
Lines: 46

I recently purchased a Fred Fish diskette with Virusx on it. I needed it
since I got a visit from the SCA virus. I came across a problem I encountered
using Virusx. I decided to post it in order to get some info on the problem.
If this problem has already been talked about, please excuse me since I'm a
less than six months subscriber to this newsgroup.

Let me first ask if I do have the SCA virus. I got a bar across my screen
saying "The virus was strong but I am stronger". Other things were printed
including "servo and storeroom boy". After looking at the code I also saw
"LSD!LSD!LSD!LSD!LSD!...". Is this really the SCA virus. Needless to say
it wiped out my disk after all this appeared on the screen.

Now for the problem. Virusx determined that indeed it was the SCA virus
by giving me a requester asking me if I want to ignore or remove it. I
decided to search my other diskettes. Virusx came up with the requester
if I switched diskettes back to back but only if the first diskette
had the virus and the second had a "nonstandard" boot code. Now, even if
the virus was not on the second diskette Virusx put up the SCA virus
warning. This would not happen if I placed a good diskette in any of the
drives prior to placing the diskette without a standard boot code in any
drive. If instead of finding the SCA virus on the first diskette (as mentioned
above) it found a nonstandard boot code, Virusx would inform me of a
nonstandard boot code on the second diskette. Apparently, a flag somewhere
is not being cleared. In essence, Virusx warns of a nonstandard boot code
or an SCA virus for a diskette which does not have a standard boot if
prior to checking it either situations were found in a prior diskette. But
again only if the second diskette is entered in a drive immediately after
a bad one.

I have version 1.21 of Virusx. Another point is this happens only with
version 1.2 workbench even with kickstart versions 1.1 or 1.2. It
does not happen with 1.3 workbench.

For a day or so I believed I got the virus from a brand new box of diskettes.
Because these diskettes had no standard boot block (uninitialized) Virusx
gave me the SCA virus warning since I first checked a diskette that really
did have the virus. Now I still don't know where I got it from.

Can someone shed some light on this problem with Virusx or is it a workbench
problem? ALso considering the ascii code (messages) mentioned above is this
virus the SCA virus?
-- 
Felix Cabral		{felixc@mtgzy.att.com}      "Just give me a rad 
AT&T Bell Labs		{	  or         }       wave, a rad board 
Middletown,NJ		{  att!mtgzy!felixc  }       and a sick day"
4B-402 (201) 957-5081