Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site topaz.ARPA
Path: utzoo!watmath!clyde!cbosgd!cbdkc1!desoto!packard!topaz!shulman
From: shulman@topaz.ARPA (Jeff Shulman)
Newsgroups: net.micro.mac
Subject: Re: Font/Da Mover
Message-ID: <1958@topaz.ARPA>
Date: Sat, 11-May-85 10:26:00 EDT
Article-I.D.: topaz.1958
Posted: Sat May 11 10:26:00 1985
Date-Received: Sun, 12-May-85 06:01:17 EDT
References: <525@water.UUCP>
Reply-To: shulman@topaz.UUCP (Jeff shulman)
Distribution: net
Organization: Rutgers Univ., New Brunswick, N.J.
Lines: 33

In article <525@water.UUCP> phcalamai@water.UUCP (Paul H. Calamai) writes:
>Perhaps I'm doing something wrong but it appears to me that
>desk accessories in DAM v1.3 or v1.4 format cannot be loaded
>using the new Font/DA mover. The new mover does however recognize
>these DA's if they are already loaded (using the DAMover)
>and can then be used to create the equivalent DA in the format
>readable by the new mover.
>
>Is this truly the case or am I missing something (in which
>case I apologize to those in-the-know).
> 
>	Thanks in advance, Paul (calamai@anl-mcs.arpa or
>	phcalamai%water%waterloo.csnet)


DA's are implemented as device drivers.  These drivers are kept in DRVR
resources in the resource fork of the SYSTEM file.  The Apple DA/Font
mover deals directly with these resources in the resource fork.  DAM,
on the other had, moved these resoures to (from) the data fork of the
saved DA file from (to) the resource fork of the SYSTEM file.

Since the DA/Font mover is not looking in the data fork of a file (and DAM
probably has its own way of storing things) the two DA movers are totally
incompatible.

Of course, once in the SYSTEM file, either mover will be happy to save a
DA in its own format.
-- 

							Jeff

uucp:   ...{harvard, seismo, ut-sally, sri-iu, ihnp4!packard}!topaz!shulman
arpa:   SHULMAN@RUTGERS