Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utcs!mnetor!seismo!gatech!cuae2!ihnp4!inuxc!pur-ee!uiucdcs!convex!convexs!allison
From: allison@convexs.UUCP
Newsgroups: net.micro.mac
Subject: Re: downloads
Message-ID: <27000018@convexs>
Date: Thu, 17-Jul-86 10:55:00 EDT
Article-I.D.: convexs.27000018
Posted: Thu Jul 17 10:55:00 1986
Date-Received: Sat, 19-Jul-86 02:06:41 EDT
References: <233@ndsuvax.UUCP>
Lines: 25
Nf-ID: #R:ndsuvax.UUCP:233:convexs:27000018:000:1303
Nf-From: convexs.UUCP!allison    Jul 17 09:55:00 1986


>       I appreciate the several replies I received to my earlier message 
> concerning the crc errors I frequently encounter when binhexing downloaded
> files.  Those replies left two questions still in doubt:
> 
> 1.  Where is the end of the material which should be retained for binhexing?
> That is, some files end with two hyphens and a couple of blanks and a colon.
> How much, if any, of that should be retained?  How does one tell where the
> CRC is?  

The BinHex format uses a colon as "beginning-of-file" and "end-of-file", if 
you will.  Also, the message "This file must be converted...." is required,
I think.  So, strip anything before the "This file..." message and everything
after the "end-of-file" colon (but don't take out the colon!).

Note that xbin (the unix-based binhex) is smart enough to ignore most, if not
all, leading and trailing garbage that BinHex 4.0 barfs on.  So, if you use the
'xbin -> "pack the .data, .info, and .rsrc files together" program (I use
macbin) -> xmodem' scheme (or macget/macput for the MacTerminal die-hards, I
guess), you don't usually have to worry about stripping off the leading and 
trailing garbage.  Xmodem is your friend (usually).

Brian Allison         {allegra, ihnp4, uiucdcs, ctvax}!convex!allison
Convex Computer Corp.
Richardson, TX