Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!mips!atha!aunro!alberta!herald.usask.ca!weyr!f43.n140.z1.FIDONET.ORG!John.Montbriand
From: John.Montbriand@f43.n140.z1.FIDONET.ORG (John Montbriand)
Newsgroups: comp.lang.modula2
Subject: Re: I could use some help right now....
Message-ID: <217.2828E7AF@weyr.FIDONET.ORG>
Date: 8 May 91 06:03:19 GMT
Sender: ufgate@weyr.FIDONET.ORG (newsout1.26)
Organization: FidoNet node 1:140/43 - U of S Computing Se, Saskatoon Sask
Lines: 22

To:  NORVELL@KNOX.BITNET (ozymandias G desiderata)
Hi!
     I've encountered similar problems with binhexed files before.  So far 
the only solution I've been able to work out is to use binhex 4.0--even if 
the file does not completely de-binhex,  this version will leave the 
partially de-binhexed file on the disk--from there you can use stufit to get 
part of the archive.  but this should be done carefully because stuffit will 
crash sometimes when it's working on a corrupt archive.  
     The other possiblilty is that you downloaded the binhex file in three or 
four parts.  In this case you would have to catenate the files together 
before attempting to de-binhex them.
     Another thing you can check is to make sure there aren't any colons in 
the file's header.  Sometimes people put descriptions there and they will 
interfear with binhex if the message contains a colon.
    best of luck,  John......


--  
John Montbriand - via FidoNet node 1:140/22
UUCP: ...!herald!weyr!43!John.Montbriand
Domain: John.Montbriand@f43.n140.z1.FIDONET.ORG
Standard Disclaimers Apply...