Article View: comp.sys.mac
Article #29163Re: System 6.0 breaks my CDEVS!
From: Ken Mcleod
Date: Tue, 14 Jun 1988 11:17
Date: Tue, 14 Jun 1988 11:17
21 lines
1453 bytes
1453 bytes
Well, after looking more closely, I discovered the reason why various
cdev's were breaking under System 6.0: they check for the presence of
certain packages in the System file (usually PACK 7 or PACK 4) that
no longer exist! (except in the ROM). Even Apple's Sample cdev in IM V
does this (although there's a brief disclaimer that you "really should"
check for the packages in ROM). Ouch.
Then there's the MultiFinder test. Most sample source code I've seen
(actually, ALL) checks for MultiFinder's presence by testing to see
whether the WaitNextEvent trap is implemented. Now, in System 6.0,
it's implemented ALL THE TIME, whether you're in MF or not. So if
application X assumes it's running under MultiFinder when it isn't,
well, look out.
Question: how do you detect MultiFinder's presence or absence under 6.0?
Ken McLeod ========================= ....... ======================
UUCP: {crash uunet}!pnet06!thecloud :. .: Chief Weapons of UNIX:
ARPA: crash!pnet06!thecloud@nosc.mil :::.. ..::: "Fear, surprise, and
INET: thecloud@pnet06.cts.com //// ruthless efficiency."
Technical Details
Message-ID:
<226@hodge.UUCP>Path:
arc1-ca.pugleaf.net!utzoo!attcan!uunet!hodge!pnet06!thecloudShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!hodge!pnet06!thecloud From: thecloud@pnet06.cts.com (Ken Mcleod) Newsgroups: comp.sys.mac Subject: Re: System 6.0 breaks my CDEVS! Message-ID: <226@hodge.UUCP> Date: 14 Jun 88 11:17:09 GMT Sender: rusty@hodge.UUCP Organization: People-Net [pnet06], Orange, CA Lines: 21