Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!decwrl!claris!wombat
From: wombat@claris.com (Scott Lindsey)
Newsgroups: comp.sys.apple
Subject: CDEVs (Mac vs GS) (was Re: APPLE ANNOUNCES ...)
Message-ID: <10152@claris.com>
Date: 15 May 89 09:31:21 GMT
References: <30690@apple.Apple.COM>
Organization: Claris Corporation, Santa Clara CA
Lines: 32

From article <30690@apple.Apple.COM>, by mattd@Apple.COM (Matt Deatherage):
> In article pnet01!pro-sol!pro-nucleus!hzink@nosc.mil writes:
>>
>>For your information, Jason, the CDEVs subdirectory is handled just like on
>>the Mac, where CDEVs (Contro Panel Documents) are dragged into the system
>>folder and become active upon boot.  [...]
>>
> Not quite.  On the IIgs, you don't have to reboot for them to become active;
> you can simple move them in and out of the CDEVs folder.
> 
Not quite.  CDEVs on the Mac are just like those on the GS, except for their
content.  Clarification: Mac CDEVs commonly contain INITs (akin to
SYSTEM.SETUP files).  A Mac CDEV is accessible immediately after being placed
in the system directory... er, folder.  If it depends on prior execution of
an internal INIT, tough.  It either crashes, or, if implemented correctly,
handles the error gracefully & informs the user.

On the GS, the INITs are totally separate from the CDEVs, but there is no less
of a dependancy.  Try using the AppleShare CDEV or the AppleTalk print driver
CDEVs without the AppleTalk SYSTEM.SETUP(s).  Same results.


>>So, I really wish people would do their homework first before generalizing
>>grossly and making assumptions.  Hope this helps.

Well, after a fashion, it does...

-- 
Scott Lindsey     |"Cold and misty morning. I heard a warning borne in the air
Claris Corp.      |    About an age of power when no one had an hour to spare"
ames!claris!wombat| DISCLAIMER: These are not the opinions of Claris, Apple,
wombat@claris.com |    StyleWare, the author, or anyone else living or dead.