barry@primerd.prime.com (02/28/89)
Thanks to all of you who responded to my posting of a few days ago inquiring about BinHex and StuffIt for UNIX. I now have working versions of these, which leads me to my next question ... Normally I use PacerLink to download HQX (BinHex'ed) files to my MAC-II connected to a Prime system (not running UNIX!). Most of these HQX files came from postings to comp.binaries.mac, some were obtained by FTP from SUMEX to either a Sun or a Prime. Most of these files decode correctly on the MAC. In some cases, however, the HQX can't be decoded properly: BinHex gets the name of the Mac file right, but gets a CRC or similar error, while StuffIt (using Decode BinHex option) uses garbage for the file name. The BinHex error occurs after processing for a while, while the StuffIt error happens before any procesisng is done. I tried xbin with one of these HQX files on the Sun and had no problems generating the three forks. I'm pretty sure that PacerLink correctly transmitted the file to the MAC. One of the files that caused this problem was the "logout cdev" recently posted to comp.binaries.mac. I sent a second copy to the MAC, which CompareForks reported as being the same as the first. Yet xbin had no problem with this HQX. Have any of you encountered similar problems? Are the problems due to transmission errors BEFORE the files were sent to the Mac? I'd appreciate any advice is to what might be causing these diffculties. Please reply by mail (although response to comp.sys.mac would be nice if this is a problem of general interest). Thanks, Barry . ------------------------------ Barry Wolman <barry@primerd.prime.com> [129.122.3.1] Principal Technical Consultant Prime Computer, Inc. 492 Old Connecticut Path Framingham, MA 01701 508/626-1700, ext. 4187
md32+@andrew.cmu.edu (Michael Joseph Darweesh) (03/02/89)
make sure that you are stripping the "---end of part # ---" from the end of each
part. This really bugged me until I just tried random stuff and found this
regular text at the
end of the files that had been separated on comp.binaries.mac.
Binhex ignores the last one of these if you are only dealing with
one file because it has it's own flag for the end of the file (":").
So all you have to do is remember to strip all of the headers and those nasty
"--- end of part # ---" that the moderator for the binaries board puts on
the end of those files, then append the files to together in the correct order
and
unbinhex the thing.