Path: utzoo!mnetor!uunet!husc6!bloom-beacon!gatech!udel!rminnich
From: rminnich@udel.EDU (Ron Minnich)
Newsgroups: comp.sys.amiga
Subject: Re: New Virus;deadly
Message-ID: <914@louie.udel.EDU>
Date: 31 Dec 87 21:52:51 GMT
References: <17234@topaz.rutgers.edu> <1425@phoenix.Princeton.EDU>
Reply-To: rminnich@udel.EDU (Ron Minnich)
Distribution: na
Organization: University of Delaware
Lines: 31
Keywords: killer virus on the loose

In article <1425@phoenix.Princeton.EDU> dykimber@phoenix.Princeton.EDU (Daniel Yaron Kimberg) writes:
>In article <17234@topaz.rutgers.edu> mccarrol@topaz.rutgers.edu (<MC>) writes:
>>Well folks, theres yet ANOTHER virus on the loose. This one allows you
>>5 boots of the virus disk, then erases the entire disk, and says 
>>"The Ram Man Was Here". 
>>Anyone else for nuking the asshole who started all this? I just lost
>
>Do you know if the program virustest will detect it?  Someone should write
>a virustest that checks disks.
   and where is a good place to get virustest? I have kind of lost
track of this thread. Also, the first letter indicates that
the virus came in on a fish disk containing microemacs. Do 
i read that right? Do you think it was in the microemacs, or
on the boot track of the disk, ... any ideas?
   Is there a virustest that lets you check lots of disks at once? 
You know, 'put in a disk', it checks it, 'put in a disk' sort
of loop?
   Maybe we need to start a 'kill a rat' program. 
And i mean people, not code.
   How did you lose your backup disk? I am still unclear on the
whole sequence. And how can a company lose a whole product? This 
seems kind of weird; did they only have one backup disk, and not
have a string of backup disks? If so they were being a little 
careless anyway (he says, looking at his piles of unbacked-up
disks. On the other hand, i'm not a company ... around here we
have piles and piles of backups, and at companies i know you
take one backup a month and put it somewhere safe).
   Seems we are going to have to get used to write-locked 
workbench disks, and write-lock everything that can be. Damn. 
-- 
ron (rminnich@udel.edu)