Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!gem.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!haven!umd5!jg13
From: jg13@umd5.umd.edu (Allon Stern)
Newsgroups: comp.sys.mac
Subject: Re: Where do I get BinHex 4.0 ???
Message-ID: <5463@umd5.umd.edu>
Date: 15 Oct 89 18:07:12 GMT
References: <851zebolskyd@yvax.byu.edu>
Reply-To: allon@solaax.umd.edu (Allon Stern)
Organization: University of Maryland, College Park
Lines: 21

In article <851zebolskyd@yvax.byu.edu> zebolskyd@yvax.byu.edu writes:
>In <8910102155.AA25150@jade.berkeley.edu>, Greg asks where to get a
>copy of Binhex 4.0. I thought to myself, "Self, why not just EMail the
>chap a copy of it? Of course, you'll have to use StuffIt to compress it
>and convert it to BinHex format, then when he gets it he can....." Rats.

I have found that if you stuff a file with StuffIt (which puts all the info
into the data fork), then FTP the file (I've tried this only with a VMS
machine), then FTP the file back and unStuffIt, it works just fine.
You DO get a warning from StuffIT that the file header (or some such nonsense)
is screwed up, but it still manages to extract the file properly.  I guess this
is not an entirely reliable method to do it, but for sending BINHEX to someone
so you can do things properly.....

                               - -= Allon =- -

-------------------------------------------------------------------------------
   This is a test of the emergency signature system.  Were this an actual
   signature, you would see amusing mottos, disclaimers, a zillion net
   addresses, or edifying philisophical statements.  This is only a test.
-------------------------------------------------------------------------------