Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!purdue!i.cc.purdue.edu!h.cc.purdue.edu!s.cc.purdue.edu!ain From: ain@s.cc.purdue.edu (Patrick White) Newsgroups: comp.sys.amiga Subject: Re: The ultimate fix!!! Message-ID: <3568@s.cc.purdue.edu> Date: 18 Sep 88 17:15:13 GMT References: <681@zehntel.UUCP> <3084@hermes.ai.mit.edu> <4197@thorin.cs.unc.edu> <599@accelerator.eng.ohio-state.edu> <378@uwslh.UUCP> Organization: PUCC Land, USA Lines: 14 To: unc!bell@ecn In-Reply-To: <4241@thorin.cs.unc.edu> Cc: Bcc: In article <4241@thorin.cs.unc.edu> you write: >It might be possible for virii to move the nifty code out of the boot block >and execute it after it's done its dirty work, but a virus that can do all Why bother.. the virus can keep part of iteslf on the disk so it can be larger.. then it has all the room to emulate anything it wants to... But, the best solution (and only real one?) is to hack a version of kickstart so the bootblock never gets executed -- and have a normal one around for use with games and such with custom bootblocks.. presto, no more spreading of infections.. of course all you poor people with 500 and 2000s who traded boot-up time for flexibility loose, but then that was your decision, not mine. Pat White (ain@s.cc.purdue.edu)