Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!apple!ntg!dplatt
From: dplatt@ntg.com (Dave Platt)
Newsgroups: comp.sys.mac.system
Subject: Re: Okay, now I'm really pissed... (CRC errors)
Keywords: System 7, CRC errors, not having a good day
Message-ID: <568@goblin.ntg.com>
Date: 20 May 91 03:50:26 GMT
References: <1991May17.014019.11207@cunixf.cc.columbia.edu> <1991May18.203743.11869@fs7.ece.cmu.edu>
Organization: New Technologies Group, Inc.  Palo Alto CA
Lines: 25

In article <1991May18.203743.11869@fs7.ece.cmu.edu> silvus@vauxhall.ece.cmu.edu (Gregory Lee Silvus) writes:
>I had this problem w/files from sumex. The solution: By chance I tried
>to unbinhex them using the unbinhex option in CompactPro (1.3 ?).
>It worked!!
>
>Perhaps CompactPro and BinHex have some discrepancies, and someone used
>CompactPro instead of BinHex to binhex those files. Let me know if this
>works, please.

There is a known bug, of long standing, in BinHex 4.0.  It is unable to
correctly decode files if the name in the encoded file's header is
longer than about 25 characters (it seems to vary, sometimes).  Binhex
4.0 gets out of sync, somehow, and reports a bogus CRC error.

The bug is in the BinHex 4.0 decoder... the encoded files are actually
valid, and can be decoded by programs that have robust decoders.
StuffIt and Compact Pro seem to have no problem with these files;
mcvert (on Unix) also works.



-- 
Dave Platt                                                VOICE: (415) 813-8917
              Domain: dplatt@ntg.com      UUCP: ...apple!ntg!dplatt
 USNAIL: New Technologies Group Inc. 2468 Embarcardero Way, Palo Alto CA 94303