🚀 go-pugleaf

In article <1030@thor.stolaf.edu> sobiloff@thor.UUCP (Blake Sobiloff) writes:
>For the past couple of weeks I've been having problems with the downloads from
>the mac binaries and no one has been able to come up with a solution yet.  When
>I download one of the files and try to UnBinHex it I keep on getting CRC$ errors
>and the job fails.  This happens with both BinHex 4.0 and 5.0.  If I use Stuffit
>1.5.x it will UnBinHex them, but with a warning that the file might be damaged.
>When I try to unStuff'em I get the message that the Resource Header is trashed
>and the job aborts.
>
>Thanks...
>Blake "Hey, where's MY fancy footer?" Sobiloff

I find that "cleaning" up the header text with a text editor like MacSink or
Sigma-Edit usually gets rid of the offending chars. If you use rn, and save the
binaries with w ../MacStuff/fname, it automatically appends the saved portion to
to the file fname, however you get header info between the files. Using the find
option, search for "part", and eradicate the unwanted text between parts. Or use
the bhcomb script that was posted a while back.

||<<++>>||<<-->>||<<==>>||<<++>>||<<??>>||<<++>>||<<-->>||<<==>>||<<++>>||
||                                  ||                                  ||
||	   Andrew Stone	            ??		2 + 2 = 5;		|| 
||         stone@hydra.unm.edu	    <> 	    for sufficiently large 2    ||
||	   			    ||					||
||<<++>>||<<-->>||<<==>>||<<++>>||<<??>>||<<++>>||<<-->>||<<==>>||<<++>>||