Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!dino!ux1.cso.uiuc.edu!tank!mimsy!mojo!russotto
From: russotto@eng.umd.edu (Matthew T. Russotto)
Newsgroups: comp.sys.mac.apps
Subject: Re: Screensnap 2.2 memory problems?
Message-ID: <1990May8.164336.14731@eng.umd.edu>
Date: 8 May 90 16:43:36 GMT
References: <3667@newton.physics.purdue.edu> <7258@ncar.ucar.edu>
Sender: news@eng.umd.edu (The News System)
Organization: College of Engineering, Maryversity of Uniland, College Park
Lines: 17

In article <7258@ncar.ucar.edu> hpoppe@ncar.ucar.edu (Herb Poppe) writes:
>In article <3667@newton.physics.purdue.edu> cca@newton.physics.purdue.edu 
>(Charles C. Allen) writes:
>> Then Screensnap 2.2 appeared on the net.  It seems to do all we need,
>> and works fine with images that are small enough.  Unfortunately,
>> there is a size beyond which it simply will not capture an image, even
>> when it's application size is bumped up to over 3M.  Now, since a
>> full-screen image should take less than 1M (1024x768x8), I'm a little
>> confused about why it continues to complain about insufficient memory.
>> Any ideas?
>
>1024x768x8 = 6,291,456
BITS.  Which is 6,291,456/8 = 786,432 BYTES

--
Matthew T. Russotto	russotto@eng.umd.edu	russotto@wam.umd.edu
][, ][+, ///, ///+, //e, //c, IIGS, //c+ --- Any questions?