Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!stanford.edu!msi.umn.edu!cs.umn.edu!mmm.serc.3m.com!pejacoby
From: pejacoby@mmm.serc.3m.com (Paul E. Jacoby)
Newsgroups: comp.sys.mac.apps
Subject: Re: BinHex file format?
Message-ID: <1991Jun19.140602.12873@mmm.serc.3m.com>
Date: 19 Jun 91 14:06:02 GMT
References: <1991Jun19.003241.10372@newsserver.sfu.ca>
Reply-To: pejacoby@mmm.serc.3m.com (Paul E. Jacoby)
Distribution: na
Organization: 3M - St. Paul, MN  55144-1000 US
Lines: 16

In article <1991Jun19.003241.10372@newsserver.sfu.ca> white@newsserver.sfu.ca (Steve White) writes:
>A friend of mine wants info on the BinHex file format, in particular,
>where the resource and data forks start.  His purpose is to port a Mac
>GIFF file (which should be text-only but to which some Mac programs
>pervertedly attach a resource) to his Atari machine.
>Is this information available anywhere?

Don't bother learning Binhex--just strip the first 128 bytes from the
GIF file, or zero (0) them out with a sector editor.  What you most
likely have is a MacBinary header that has been appended to the file by
your communication software.  A very common problem.
-- 
| Paul E. Jacoby, 3M Company, 3M Center, 235-3F-27                   |
| Maplewood, MN   55144-1000     .-----------------------------------|
| => pejacoby@3m.com             |     I'm afraid this is getting    |
|                 (612) 737-3211 |            too silly!             |