Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!brutus.cs.uiuc.edu!apple!netcom!barry
From: barry@netcom.UUCP (Kenn Barry)
Newsgroups: comp.sys.amiga
Subject: Re: GIF to IFF program available?
Message-ID: <10797@netcom.UUCP>
Date: 11 Apr 90 02:27:50 GMT
References: <9004102003.AA11921@jade.berkeley.edu>
Organization: QQQCLC
Lines: 24

In article <9004102003.AA11921@jade.berkeley.edu> GORRIEDE@UREGINA1.BITNET (Dennis Robert Gorrie) writes:
>People have been suggesting several programs for GIF to IFF conversion.
>I thought I would mention that the original poster wanted programs that
>would convert 640x480 256 color GIFs.  I have used GIF2IFF, and HamSharp,
>and they would both often crash on images of this size, and allways on
>images larger than this.  I had over 700k free fastmem, 350k free chip mem,
>so I am not sure what the problem with these programs was, except I don't
>think I ran out of memory.

	Odd. I've been using HamSharp as my converter of choice for
quite a while, now, and have converted many GIFS that are 640x480
or larger - no crashes. It would die when handed a corrupt GIF file,
but don't forget HamSharp's best feature - it comes with source
code. It can easily be altered to successfuly convert a corrupt
GIF up to the point the corruption occurs, and not to halve the
width of 640-wide GIFs when converting to HAM.

	The amount of memory you mention should be adequate.
Could it be a memory fragmentation or stack size problem?


-  From the Crow's Nest  -                Kenn Barry
----------------------------------------------------------------
ELECTRIC AVENUE:	                  apple!netcom!barry