Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!cwjcc!gatech!rutgers!apple!bionet!agate!ucbvax!CORY.BERKELEY.EDU!dillon
From: dillon@CORY.BERKELEY.EDU (Matt Dillon)
Newsgroups: comp.sys.amiga.tech
Subject: Re: problems (probably) with setpatch ... forget that, no problem.
Message-ID: <8810260706.AA15760@cory.Berkeley.EDU>
Date: 26 Oct 88 07:06:49 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 23

I write:
:	With setpatch installed my mouse gets very jerky during compiles and
:the keyboard gets screwed up (like the input device process is hanging for
:long periods of time).  Without setpatch installed everything is O.K.

	Very Very Very interesting.  It turns out that everything works ok
If the *very first thing* I do is 'setpatch' ... i.e., it's the first thing
in my workbench floppy s:startup-sequence now.

	-Before trying that, I had it about in the middle of my boot sequence,
	and this caused the previously indicated problems (but no crash)

	-Before that I had it even later in my boot sequence and it crashed
	 the machine when it tried to mount the remaining partitions on my HD.

	So ... no longer a suggestion ... stick setpatch (this is in 1.3) 
*first* before anything else, period.  If your system (appears to) work
with it where you have it now (if not the very first thing), you could be
installing a time bomb instead of a patch.  The kind of deviant operation
I got not having it first seems to indicate some major stuff being done by
the patch.

					-Matt