On Wed, Dec 03, 1997 at 06:09:50PM -0800, Bill Studenmund wrote:
> Your problem is not that the mac keeps a seperate resource fork, but that
> you used a file transfer method which was not very savvy. That's not the
> OS's fault. :-)

How should I have known that.. using mac (the world's 'easiest' computer)
for the first time :-)
> 
> For ftp, I typically use fetch, and the "Raw Data" mode will do exactly
> what you expect. Only the data fork, not the resource fork, goes along
> for the ride. "Binary" mode actually uses the MacBinary format, which
> does add extra data to the front of a file. Note: that data's not the
> resource fork, but a combination of the finder info, and some sort of
> length info so that the data and resource forks can get split apart later.
> If you only get 128 extra bytes, I doubt you actually got a resource fork.

Okay, I stand (sit) corrected.

But I still like the AmigaOS idea - using simple plain files to store the
extra information (like application name, options, etc.) instead of a
special filesystem level thing which would make backups difficult and
force you to use that single filesystem type..

  -jm