[comp.sys.amiga] PBM difficulties

stevem@hal.CSS.GOV (Steve Masters) (12/09/90)

I recently downloaded the PBM (Extended Portable Bitmap Toolkit) and have been
attempting to use it on my A2500/30 with 3M of memory.  I am trying to use
the package to convert a GIF file I downloaded to an IFF file.

While running the giftoppm program, I get a 'out of memory allocating array'
message.  I have about 1.2 Mbytes of free fast memory available at the time
of the program call (and about 500 K chip memory free).  I have tried
enlarging the stack (from 50K to 1000K) with no luck.  Does anyone know how much
memory this program will need?

I have tried the FBM package as well, but after conversion from GIF->FBM->IFF,
the resulting IFF file either shows blank on my screen (if I'm lucky) or
crashes the machine (if I'm not :(  ).  I have seen the IFF->GIF thread
over the last few days and will try some of the programs listed.

It is really important that I find a method to decode GIF files into IFF
files (in a "batch" mode, without having to interactively save each IFF file
as in "Snap) on my Amiga.  If anyone can give me any pointers and tips, it would
be much appreciated.  E-Mail or postings to c.s.a. are OK.

Steve Masters    stevem@hal.CSS.GOV
ENCSO, Inc.
Melbourne, FL  USA  32940
(407) 254 4122

lar@pc.usl.edu (Robert, Lane A.) (12/11/90)

In article <493@hal.CSS.GOV> stevem@hal.CSS.GOV (Steve Masters) writes:
   I recently downloaded the PBM (Extended Portable Bitmap Toolkit)
   and have been attempting to use it on my A2500/30 with 3M of
   memory.  I am trying to use the package to convert a GIF file I
   downloaded to an IFF file.

   While running the giftoppm program, I get a 'out of memory
   allocating array' message.  I have about 1.2 Mbytes of free fast
   memory available at the time of the program call (and about 500 K
   chip memory free).  I have tried enlarging the stack (from 50K to
   1000K) with no luck.  Does anyone know how much memory this
   program will need?

Giftoppm doesn't need much stack space (8K is plenty), but it needs to
be able to dynamically allocate enough _contiguous_ memory to hold the
image it is working on.  1.2 MB should be enough to convert a moderate
sized image, but if it's badly fragmented then you're out of luck.
Try rebooting, and if that doesn't work then try killing off some of
the other things you have using up memory.  If none of this helps, you
may need to invest in more RAM.

Lane
lar@usl.edu