Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!mcsun!ukc!icdoc!tsun3.doc.ic.ac.uk!zmacv14
From: zmacv14@tsun3.doc.ic.ac.uk.doc.ic.ac.uk (C P Brown)
Newsgroups: comp.sys.amiga
Subject: Re: VirusX
Message-ID: <1410@gould.doc.ic.ac.uk>
Date: 12 Dec 89 14:25:00 GMT
Sender: news@doc.ic.ac.uk
Reply-To: zmacv14@doc.ic.ac.uk (Phil Brown)
Organization: Imperial College Department of Computing
Lines: 15


Recently, I got attacked (again) by the Lamer Exterminator. Now it was
immediately found and killed (in memory) by VirusHunter. Then I tried running
VirusX3.2 (GREAT prog, BTW) on the affected disk to zap it. The boot block
was not recognised as the LE, just as a non-standard one. So I replaced it
anyway (all well and good). But VirusX, when I deliberately gave it the LE to
kill in memory, it discovered it and killed it and ... software error, CRASH!
Given that VirusX3.2 mentions the LE in its kill-list, I was surprised that
a) it did not recognise the boot block and
b) crashed when it found it in memory
I will of course upgrade to 4.0 ASAP, meanwhile, any ideas?

Cheers,

Phil