🚀 go-pugleaf

In article <8810260706.AA15760@cory.Berkeley.EDU> dillon@CORY.BERKELEY.EDU (Matt Dillon) writes:
>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)

Even more interesting.  You can find out what SetPatch is doing by
running it without the redirection to NIL:. The current version of
SetPatch does the Alert patch, the Layers patch,fills in the
68020/68881 exception table, and patches AllocEntry.

I can't figure out which of these would cause your problem.

We recommend that it be first because there was no way of explaining 
to all users and having them actually understand the effects.  So in the
standard Startup-Sequence we do an Addbuffers first, which is perfectly safe.
But try explaining which commands are fine, and which need the patches,
and you'll soon end up like I did; and just say "Put it First"

			andy
-- 
andy finkel		{uunet|rutgers|amiga}!cbmvax!andy
Commodore-Amiga, Inc.

"I first began to lose faith in software engineering when I found out
 that no two printers were compatible."

Any expressed opinions are mine; but feel free to share.
I disclaim all responsibilities, all shapes, all sizes, all colors.