Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!apple!Apple.COM!lsr
From: lsr@Apple.COM (Larry Rosenstein)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Checking for MF (was Re: Need some MF help)
Message-ID: <1203@internal.Apple.COM>
Date: 6 Apr 89 02:57:05 GMT
Sender: usenet@Apple.COM
Distribution: comp.sys.mac.programmer
Organization: Objects-R-Us,  Apple Computer, Inc.
Lines: 26
References:<1562@neoucom.UUCP> <28689@ucbvax.BERKELEY.EDU> <1179@internal.Apple.COM> <20057@srcsip.UUCP>

In article <20057@srcsip.UUCP> mnkonar@gorby.SRC.Honeywell.COM (Murat N. 
Konar) writes:
> 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

Then I would say that this is probably a bad idea.  You give a simple case 
where this check would fail.  The result of relying on this check will be 
a program that doesn't work when your INIT is installed.

It is also conceivable that a future system would have the system MDEF in 
ROM, or would load the MDEF in the system heap all the time to improve 
program launch time under UniFinder.

People are looking at this from the wrong perspective.  It is natural to 
want to ask "How do I know if MultiFinder is running?" but that is the 
wrong way to look at your program.  You should be looking at the system 
from the point of view of system features, not how those features are 
implemented. 


Larry Rosenstein, Apple Computer, Inc.
Object Specialist

Internet: lsr@Apple.com   UUCP: {nsc, sun}!apple!lsr
AppleLink: Rosenstein1