Path: utzoo!mnetor!uunet!cbmvax!rutgers!ukma!sean
From: sean@ms.uky.edu (Sean Casey)
Newsgroups: comp.sys.amiga
Subject: Re: The REAL virus problem
Message-ID: <8007@g.ms.uky.edu>
Date: 8 Jan 88 06:03:25 GMT
References: <7967@g.ms.uky.edu> <265@coplex.UUCP> <7977@g.ms.uky.edu> <1401@uoregon.UUCP> <3091@cbmvax.UUCP> <7993@g.ms.uky.edu> <3104@cbmvax.UUCP>
Reply-To: sean@ms.uky.edu (Sean Casey)
Organization: The Leaning Tower of Patterson Office @ The Univ. of KY
Lines: 25

In article <3104@cbmvax.UUCP> andy@cbmvax.UUCP (Andy Finkel) writes:

[regarding the "auto-boot vector" or whatever it is called...]

>Who said anything about a memory location ?  That has nothing to
>do with it.  Read the first 4 words of the second paragraph
>carefully.  (In my copy, its "The code is called")

Ah, but from what has been told to me, it has everything to do with it.

If I have the virus in my machine, and I warm boot with a clean, write
enabled workbench disk, the clean boot sector gets loaded and I have
no problems.  Right?  Wrong.  The way it was explained to me is that
the virus gets hold of the machine before the boot sector can be read in,
and in fact corrupts the good boot sector.

If what was described in "THE BOOT PROCESS" was all there was to it, then
warm booting with a secure disk would be safe.

Sean
-- 
--  Sean Casey               sean@ms.uky.edu,  sean@UKMA.BITNET
--  (the Empire guy)         {rutgers,uunet,cbosgd}!ukma!sean
--  University of Kentucky in Lexington Kentucky, USA
--  "My feet are wet."