Xref: utzoo comp.sys.apple:11622 comp.sys.mac:29288
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!lll-winken!uunet!iscuva!johng
From: johng@iscuva.ISCS.COM (John Gardner)
Newsgroups: comp.sys.apple,comp.sys.mac
Subject: Re: GIF from Mac to II
Summary: Don't use MacBinary
Message-ID: <2433@iscuva.ISCS.COM>
Date: 30 Mar 89 21:02:27 GMT
References: <8903251013.aa03744@SMOKE.BRL.MIL> <19388@srcsip.UUCP> <22098@agate.BERKELEY.EDU> <16331@cup.portal.com>
Followup-To: comp.sys.apple
Distribution: usa
Organization: ISC Systems Corporation, Spokane WA
Lines: 18

In article <16331@cup.portal.com> -Rich-@cup.portal.com (Richard Sherman Payne) writes:
>
>I have had problems viewing GIF files transferred with (I think) Red Ryder in  
>the past. The problem is a 128 byte header file that some MAC software 
>appends to the beginning of the GIF file, ignororing COMPUSERVE's 

You may be seeing the 128 byte MacBinary header that Red Ryder appended to the
file. It has nothing to do with the GIF protocol at all. If you downloaded the
file then Red Ryder would strip the MacBinary header and all would look well.
 
You need to send the image of the file if your destination machine is unable
to strip MacBinary. Send the file in Xmodem text mode which should just send
the Macintosh's data fork without manipulation. I'm not extremely familiar
with Red Ryder's Xmodem upload facility but it should have that kind of 
functionality.

John Gardner
{backbone}!uunet!iscuva!johng