home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.sys.mac.misc:21358 comp.sys.mac.system:15781
- Newsgroups: comp.sys.mac.misc,comp.sys.mac.system
- Path: sparky!uunet!spsgate!mogate!newsgate!gpb-mac!gpb
- From: gpb@gpb-mac (greg berryman )
- Subject: Re: disabling extensions: extension manager
- Message-ID: <1993Jan4.173131.19551@newsgate.sps.mot.com>
- Sender: usenet@newsgate.sps.mot.com
- Nntp-Posting-Host: 222.1.248.85
- Organization: SPS
- X-Newsreader: Tin 1.1 PL4
- References: <1992Dec31.213056.2808682256@ultramac.uucp>
- Date: Mon, 4 Jan 1993 17:31:31 GMT
- Lines: 26
-
- Mats.Bredell@udac.uu.se writes:
- :
- : The original question was about finding a way to force an extension to be
- : loaded even if the shift key is being held down. The answer is simple: when
- : the Mac boots, it checks to see if the shift key is down. If so, it doesn't
- : load any extensions or control panels. You can't change this behaviour.
- :
- : Under system 6, the extensions checked for a key combination themselves, but
- : system 7 has made the shift key as an override that will disable everything.
- :
- : One way to force an extension to be loaded is to write a device driver to
- : do all the job. Device drivers are always loaded at startup. The driver colud
- : be very simple, it's enough if it simply loads the extension code and starts
- : executing. As far as I know, no one has done it yet (except for Apple
- : themselves).
- :
-
- MacPassword does it. Change the behaviour, that is.
-
- Greg.
-
- --
- My words, not Motorola's. * ______ *
- gpb@gpb-mac.sps.mot.com * \ BI / * I will NOT ride in the back of the bus.
- Greg Berryman (512)928-6014 * \ / * SILENCE = DEATH
- Motorola Austin, Texas, USA * \/ * First, be true to yourself.
-