Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!amdcad!ames!ucsd!orion!bonnie.ics.uci.edu!nagel
From: nagel@bonnie.ics.uci.edu (Mark Nagel)
Newsgroups: comp.sys.mac
Subject: Re: MacMan and double-clicking
Message-ID: <385@orion.cf.uci.edu>
Date: 16 Apr 88 22:59:23 GMT
References: <23499@bbn.COM>
Sender: news@orion.cf.uci.edu
Reply-To: nagel@bonnie.ics.uci.edu (Mark Nagel)
Organization: University of California, Irvine - Dept. of ICS
Lines: 23
Summary: a *shaky* method of fixing the problem

In article <23499@bbn.COM> mesard@BBN.COM () writes:
>A couple of people have posted saying that after running the MacMan
>application, double clicking in the Finder no longer opens things (until
>the machine is rebooted).
>
>Is there anyone that this _doesn't_ happen to?  It sure is bugging the
>heck out of me and my Mac+ running Finder 6.0/System 4.2.

It's already been mentioned that this happens because MacMan alters
the global SysEvtMask at location $0144.  I modified MacMan to prevent this,
although my method may be incorrect or whatever.  What I did was search for
the string 0144 using Fedit or any disk editor in the MacMan program and 
changed it to 0000.  This forces MacMan to store the new event mask in 
location 0 which is unused.  I would've chosen another place, like AppScratch
or similar, but I wasn't sure whether MacMan was using it.  The string 0144
only occurs one time, so you should be able to change it easily.  It cures the
problem, but I feel strange about the way I did it.  It would have probably
been better to change the entire store instruction to NOP's, but I didn't do
this.  REMEMBER to do this on a copy...

Mark D. Nagel    Department of Information and Computer Science, UC Irvine
                 nagel@ics.uci.edu             (ARPA)
                 {sdcsvax|ucbvax}!ucivax!nagel (UUCP)