🚀 go-pugleaf

> 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.
> -- 

This brings me to a question:  what about desk accesories with more than just
DRVR resources.  I think the DAM used to take care of it.  I think I remember
seeing STR and DLOG(s) showing up in my system that were obviously DA material.

But now with the MV ( Moving Van ), I'm not so sure that integrity is
maintained.  ( Larry, if I'm wrong, give a holler )  I sat down not too
many nights ago and converted all my DA's over to Resource format.
What fun :-).  I was tempted to fire up switcher with a small Ramdisk
containing the current system and one window running DAM and the other
running MV.  Just tempted, not crazy.  I was afraid of one too many things
updating the system at once.  If someone wants to try it, let me know how
it all works out :-).  Well now I've got some old DA's bombing on me.
( Here I insert appropriate praise for the Resume resource, THANK YOU!!! )
So my question stands, what does MV move?
-- 
Time for a new catchy phrase in my                           Howard C. Simonson
 .signature, now if I could only     ...{dragon,hplabs,ihnp4,nsc}!amdahl!howard
  think of one...

[ Opinion? What opinion.  I think you have the wrong guy... ]