Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!mailrus!cornell!uw-beaver!uw-june!yeung
From: yeung@june.cs.washington.edu (Ricky Yeung)
Newsgroups: comp.sys.mac
Subject: Re: BinHex/ResEdit availability
Summary: xbin
Message-ID: <5609@june.cs.washington.edu>
Date: 31 Aug 88 21:09:19 GMT
References: <8483@cup.portal.com> <870221@hpcilzb.HP.COM>
Organization: U of Washington, Computer Science, Seattle
Lines: 25

In article <870221@hpcilzb.HP.COM>, tedj@hpcilzb.HP.COM (Ted Johnson) writes:
> There are only 2 ways to get BinHex:
> 	(1)from a human (e.g, a friend, a user group, etc.)
> 	(2)from a BBS
> 
> It wouldn't make sense to send it via e-mail, because then it would
> already be encoded in BinHex format (chick and egg problem).
> 
> -Ted
There is a program called 'xbin' (developed at Brown Unvi., I think) that 
decodes BinHex files on the UNIX side. The decoded files (.info, .data,
.rsrc) can then be downloaded via 'macput'.  Actually that would save you
20-30% of time than downloading the original BinHex file.
So one alternative to get BinHex if you're on a UNIX system:
1. Ask someone to send you 'xbin' and 'macput' if they are not in your system.
2. Ask someone to send you BinHex in BinHex format vie e-mail.
3. 'xbin' the BinHex file.
4. 'macput' the decoded files.

If you have 'macput' only, you can ask someone to send you the decoded files.
(binary files can be sent via e-mail by the uuencode/uudecode programs)

Hope that helps.

-Ricky
yeung@june.cs.washington.edu