--- On Mon, 3/9/09, lrbarrios <[email protected]> wrote:
> I'm familiar with the concept of converting executable
> code to text
> for transmission (e.g. uuencode). I just didn't think
> I would have to
> deal with this when downloading files. So I guess the
> servers that
> hold these Mac resource fork bearing files can handle this.
If the serve is a Mac running Mac OS or OS X, or some server version of Windows
with Services For Macintosh, and you're downloading with a Mac, then there's
generally not a problem downloading files that aren't .bin or .hqx encoded.
There's also Mac support for Linux so that files may be stored and retrieved
un-encoded. The 'ultimate problem' is with the user end- you just can't
download un-encoded Mac files that must keep their resource forks to anything
but a Mac. (Or a PC with hacked-on Intel OS X, or a Mac emulator.)
OS X supports the split fork file format, but doesn't require it. .dmg is the
OS X disk image format, no resource fork. If you're working exclusively with OS
X then file forks shouldn't be a problem.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to 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 unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/vintage-macs?hl=en
Low End Mac RSS feed at feed://lowendmac.com/feed.xml
-~----------~----~----~----~------~----~------~--~---
