On 8 Mar 2014, at 13:24:25 PM PST, Koralatov wrote:
On Sat, Mar 08, 2014 at 20:33, Ken Daggett wrote:
Somewhere in that chain, probably in passing through an OS X machine,
the file lost the resource fork. Thus the file is most likely not
going to be useful on an older Mac and, since it is not a text or
graphic file, will not be of much use on any newer Mac.
Just to sate my curiosity (and please forgive me if I've misunderstood
something), but if the resource fork contains the actual data of the
file, why is the remaining file so large? What data does it contain?
---------------
Well, back in the "olden days" Mac files consisted of a "data fork"
and a "resource fork." The "resource fork" contained such things as
icons (usually a bunch in different sizes), creator codes and other
things that either the OS or the application used in conjunction with
the data fork to execute the program. I think the "data fork"
contained the executable code and maybe data associated with what we
might think of as "stored data" or information. (Thinking of a
picture, drawing or text file.)
Ken
--
--
-----
You received this message because you are a member of the Vintage Macs group.
The list FAQ is at http://lowendmac.com/lists/vintagemacs.shtml and our
netiquette guide is at http://www.lowendmac.com/lists/netiquette.shtml
To post to this group, send email to [email protected]
To leave this group, send email to [email protected]
For more options, visit this group at
http://groups.google.com/group/vintage-macs
Support for older Macs: http://lowendmac.com/services/
---
You received this message because you are subscribed to the Google Groups "Vintage Macs" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
