X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 13c228,ec0c87d4aa30c522
X-Google-Attributes: gid13c228,public
X-Google-Thread: fd588,ec0c87d4aa30c522
X-Google-Attributes: gidfd588,public
X-Google-Thread: f996b,ec0c87d4aa30c522
X-Google-Attributes: gidf996b,public
X-Google-Thread: 124e6c,ec0c87d4aa30c522
X-Google-Attributes: gid124e6c,public
X-Google-Thread: 110f55,ec0c87d4aa30c522
X-Google-Attributes: gid110f55,public
X-Google-ArrivalTime: 1994-02-21 23:58:11 PST
Newsgroups: 
 alt.binaries.pictures.utilities,alt.ascii-art,alt.ascii-art.animation,alt.binaries.pictures.ascii,alt.binaries.pictures.misc
Path: 
 gmd.de!newsserver.jvnc.net!howland.reston.ans.net!agate!ames!koriel!sh.wide!wnoc-kyo-news!omrongw!lsa.ncl.omron.co.jp!tnishi
From: tnishi@lsa.ncl.omron.co.jp (Nishiyama Tetsuto)
Subject: Re: a problem with ASCGIF.EXE conversion program
Message-ID: <1994Feb22.075811.29669@omrongw.wg.omron.co.jp>
Sender: news@omrongw.wg.omron.co.jp (News Manager)
Nntp-Posting-Host: kansas.lsa.ncl.omron.co.jp
Reply-To: tnishi@lsa.ncl.omron.co.jp
Organization: Omron Corporate R&D H.Q.- R&D Support Dept.
References: <CKpJBw.Eu5@walter.bellcore.com>,<CLL9u5.LKz@news.ci.ua.pt>
 <2kc8c0$73o@golem.wcc.govt.nz>
Date: Tue, 22 Feb 1994 07:58:11 GMT
Lines: 24


In article <2kc8c0$73o@golem.wcc.govt.nz>, wells_s@ix.wcc.govt.nz (Steve
Wells) writes:
|> ]        ... and since then any GIF give the same error.
|> ] 
|> ]        There's a special format the GIF image have to respect?
|> 
|> Not having used the program I'm not sure, but it could be due to the
|> GIF being in 89a format instead of the older 87a format.  (The difference
|> seems to produce absolutely no difference in file-size or image-quality
|> so I'm not sure why it exists).
|> 
|> There's bound to be a convertor for the PC somewhere....
|> 

I got my hands on the source for a GIF->ASCII convertor from another news-
group that someone had written but after compilation, had the same problems
and when I looked at the code, it WAS for GIF87a where I was using GIF89a.
I think it's the same program and same problem.

...didn't know how to fix it though...so I threw it out.
=========================================================================
Teddy Nishiyama  (tnishi@lsa.ncl.omron.co.jp)  OMRON Corporation  (^_^;
R&D Support Dept(LSA), Shimokaiinji, Nagaokakyo-shi, Kyoto-fu 617  JAPAN