Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!decwrl!labrea!agate!eris!bryce
From: bryce@eris (Bryce Nesbitt)
Newsgroups: comp.sys.amiga
Subject: Re: ** Read this message!! ** Bugs in Kickstart you should know about!!
Message-ID: <7238@agate.BERKELEY.EDU>
Date: 27 Feb 88 21:59:00 GMT
References: <7231@agate.BERKELEY.EDU> <21290@bbn.COM>
Sender: usenet@agate.BERKELEY.EDU
Organization: University of California, Berkeley
Lines: 37

In article <21290@bbn.COM> cosell@BBN.COM (Bernie Cosell) writes:
>In article <> bryce@eris.berkeley.edu (Bryce Nesbitt) writes:
|>
|>You must reboot to get rid of the protection.
|
|Huh? Did you mean this last sentence... why would you *want* to get rid of
|the protection?

You would not.  But let's say I implemented this like the SCA virus... then
you would need to do more than just reboot :-).  Wow!  What a neat way to
do automatic software updates :-).


|I notice that you mention the A2000 explictily.  I guess this means
|that this isn't actually a patch for kickstart (since I think we'ed
|need new ROMs to really do that, no?) .

Who needs to change ROMs to patch Kickstart?  The OS has this magic 
"SetFunction()" call all set up for the purpose.


>Perhaps I'm (as usual) missing the obvious, but I'm
>not sure what I'm supposed to do with this guy -- put it in my
>startup-sequence?

Yes.  Just put "patch_1" in the startup-sequence.  No need to run it.


|If so, does its placement have any bearing on other
|things in s-s (e.g., Andy's previous alert() patch).?

This fixes the Alert() bug, so Andy's "setalert" patch is not needed.

|\_/|  . ACK!, NAK!, EOT!, SOH!
{O_o} .     Bryce Nesbitt
 (")        BIX: mleeds (temporarily)
  U	    USENET: bryce@eris.berkeley.EDU -or- ucbvax!eris!bryce