Path: utzoo!attcan!uunet!cs.utexas.edu!sun-barr!decwrl!ucbvax!pro-carolina.UUCP!delton
From: delton@pro-carolina.UUCP (Don Elton)
Newsgroups: comp.sys.apple
Subject: Re: resource forks, encore une fois
Message-ID: <8905190505.AA19064@obsolete.UUCP>
Date: 19 May 89 04:25:44 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 20

Network Comment: to #2714 by obsolete!TMPLee%DOCKMASTER.NCSC.MIL

From a CATalog, forked files look just like any other file.  The change I was
discussing with ECP16 was to make forked files look different in catalog
listings since they normally don't.  This is required because you have to
specify which fork you plan to open when you open a file under GS/OS 5.0. 
This means that a COPY from the current ECP16 (or most any other program that
wasn't written with forked files in mind) will only copy the data fork and not
the resource fork.  Right now there aren't many files that are forked on the
system disk (don't remember exactly how many) but expect to see more and more
applications with resource forks.  There's an external command for APW called
DUPLICATE that's designed to copy these files until the programs get updated
and ECP16 will be updated to handle them transparently as the Finder now does.

UUCP: [ sdcsvax nosc ] !crash!pro-carolina!delton
ARPA: crash!pro-carolina!delton@nosc.mil
INET: delton@pro-carolina.cts.com

Pro-Carolina: 803-776-3936 (300-2400 baud, login as 'register')
     US Mail: 3207 Berkeley Forest Drive, Columbia, SC  29209-4111