-=> Mocking Mack Barss to All <=-
   
 MB> I have run across the WAZZU.A virus on one of the Win95 systems that
 MB> I look after.  The problem I am running it to is that if I boot from a
 MB> clean write protected diskette and run the latest version of McAfee's 
 MB> SCAN or any other virus detector, they all come back 
 MB> indicating that no virus was found.
possibly you're not scanning the right objects on the drive... wazzu
will reside in doc or dot files...
 MB> Now comes the really annoying part... even if I boot with a Win95
 MB> system diskette that is write protect and run the various virus
 MB> scanning programs they will all indicate that no virus was found. 
 MB> However, as soon as the system boots normally from the hard drive and
 MB> VShield kicks in, it indicates that it has found traces of the WAZZU.A
 MB> virus in memory and always at the same location (448k).  
wait, it's popping up as soon as you boot? as in before ms word ever
gets loaded?
if thats the case then you have a false alarm... for a macro virus
scanner that doesn't false alarm i'd suggest f-macrow... it's also one
of the best macro virus detection programs out there...
 MB> Now, how is it that booting from a clean boot disk and scaning the
 MB> harddrive indicates no virus, yet booting from the hard drive indicates
 MB> traces of the virus.  Better yet, how do I get rid of this virus with
 MB> out formatting when all virus scanning programs says there is no virus?
wazzu is a macro virus, not a memory resident virus... it shouldn't be
present right after booting up so i really suspect that you're
experiencing a false alarm problem... mcafee is well known for it's
bugs (it's still a good product but the bugs make it hard to make
effective use out of it) so i suspect that if it is the only product
giving you warnings and if it's giving you warnings of a virus in an
environment where the virus cannot be then i'd say you don't really
have a virus...
which is not to say you don't have any problem at all, when did this
whole thing start? did it coincide with an upgrade of the vshield
program? if so it could be just a bug... otherwise it sounds like
something that gets loaded automatically during bootup has been
corrupted is a very particular way.. (possibly a system file got
grunged by an actual instance of a wazzu infection that has since been
cleaned up - which isn't supposed to happen, but...)
try telling your scanner to scan all files next time you use it...
... wash, rinse, repeat...
--- Maximus 2.02
---------------