Path: utzoo!attcan!uunet!samsung!olivea!orc!bu.edu!dartvax!carr!kurash From: kurash@carr.dartmouth.edu (Mark Valence) Newsgroups: comp.sys.mac.programmer Subject: Re: doing real work at interrupt // Notification Manager Summary: What choices are left? Keywords: NMInstall SystemTask jGNEFilter (yuck) Message-ID: <25578@dartvax.Dartmouth.EDU> Date: 5 Nov 90 16:48:49 GMT References: <2038@exodus.Eng.Sun.COM> Sender: news@dartvax.Dartmouth.EDU Reply-To: kurash@carr (Mark Valence) Organization: Dartmouth College Lines: 25 In article <2038@exodus.Eng.Sun.COM> zellers@prisoner.Eng.Sun.COM (If they build it) writes: >In article kurash@quimby (Mark Valence) writes: >>So what is a well meaning programmer to do without NMINstall at interrupt >>time. The only thing I can think off it to patch System Task and >>have my interrupt code set flags to tell the patch to do a NMInstall... No, in fact I didn't write that. It was written by Michael Pierce, who pointed out that NMInstall is unstable. I must say, that changes things. I have always been hesitant about patching important traps (recall the discussion concerning patching ExitToShell and similar traps 'globally'), due to MultiFinder's intrusiveness. I might first write a driver that mimicked the Notification manager, install it at INIT time when my interrupt code is installed, and service these 'notification requests' at SystemTask (dNeedTime). >I like to set flags which I read from a 'jGNEFilter' daisy chain - it's >a nice place to patch, since it's called at a very stable time. >-- >-------------------------------------------------------------------------- >Steve Zellers zellers@prisoner.sun.com >"And that's why we have to have computers, because man, nobody's perfect." You said it, not me :) Mark.