Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!snorkelwacker!mit-eddie!bu.edu!bu-cs!dartvax!eleazar.dartmouth.edu!erics
From: erics@eleazar.dartmouth.edu (Eric Schlegel)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Patching ExitToShell under MultiFinder
Keywords: ExitToShell Multifinder
Message-ID: <19266@dartvax.Dartmouth.EDU>
Date: 9 Feb 90 17:02:01 GMT
References: <204@brain.UUCP>
Sender: news@dartvax.Dartmouth.EDU
Distribution: comp
Organization: Dartmouth College, Hanover, NH
Lines: 19

In article <204@brain.UUCP> root@brain.UUCP (Chuck Shotton) writes:
>Multifinder has an interesting quirk in that it patches ExitToShell, and doesn't
>give a damn about any patches that may already be in place. Does anyone have
>a suggestion as to how an INIT can patch ExitToShell at boot time (prior to
>knowing if Multifinder is going to be active) and make sure that the patch is
>in place AFTER Multifinder is done munging the trap?


MultiFinder patches a number of traps in this fashion - it's quite annoying.
I haven't tried this yet, but I think installing a Notification Manager 
callback in your INIT, and having the callback routine patch the trap, would
work. The Notification Manager certainly won't start notifying until after
MF is installed, so you should be able to safely patch over MF's patches.

-eric

--
Eric Schlegel '90             |   "Never underestimate the bandwidth of a
eric.schlegel@dartmouth.edu   |    station wagon full of tapes."