Xref: utzoo comp.sys.mac.programmer:5391 comp.sys.mac:29600
Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!ucbvax!pasteur!ames!xanth!nic.MR.NET!srcsip!gorby!mnkonar
From: mnkonar@gorby.SRC.Honeywell.COM (Murat N. Konar)
Newsgroups: comp.sys.mac.programmer,comp.sys.mac
Subject: Re: Checking for MF (was Re: Need some MF help)
Message-ID: <20057@srcsip.UUCP>
Date: 6 Apr 89 00:14:37 GMT
References: <1562@neoucom.UUCP> <28689@ucbvax.BERKELEY.EDU> <1179@internal.Apple.COM>
Sender: news@src.honeywell.COM
Reply-To: mnkonar@gorby.UUCP (Murat N. Konar)
Distribution: comp.sys.mac.programmer,comp.sys.mac
Organization: Honeywell Systems & Research Center, Camden, MN
Lines: 33

In article <1179@internal.Apple.COM> goldman@apple.com (Phil Goldman) writes:

>This is a very bad thing to do, and, as was mentioned in a previous 
>posting, the one known legitimate reason for doing so will soon be fixed 
>in SysEnvirons.

But for now you can check if the standard MDEF (id=0) is in the system
heap or the application heap.  If it's in the system heap then MF is 
probably running.  I say probably because an init I'm working on loads
the MDEF into the system heap and there may be other inits that do this
too.   


>Doing such checks makes it very much harder to move MultiFinder 
>functionality to the System or ROM.  Worse, it makes it dirtier to add new 
>Mac OS functionality.
>
>-Phil Goldman
>Apple Computer




What he said.  Use my method only at your own risk.





____________________________________________________________________
Have a day. :^|
Murat N. Konar        Honeywell Systems & Research Center, Camden, MN
mnkonar@SRC.honeywell.com (internet) {umn-cs,ems,bthpyd}!srcsip!mnkonar(UUCP)