Article View: comp.sys.mac.apps
Article #1815Re: Screensnap 2.2 memory problems?
From: Herb Poppe
Date: Tue, 08 May 1990 14:17
Date: Tue, 08 May 1990 14:17
16 lines
1168 bytes
1168 bytes
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
Herb Poppe NCAR
hpoppe@ncar.ucar.edu 1850 Table Mesa Drive
Boulder, CO 80307-3000
(303) 497-1296
Technical Details
Message-ID:
<7258@ncar.ucar.edu>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!asuvax!noao!ncar!ncar.ucar.edu!hpoppeReferences:
<3667@newton.physics.purdue.edu>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!asuvax!noao!ncar!ncar.ucar.edu!hpoppe From: hpoppe@ncar.ucar.edu (Herb Poppe) Newsgroups: comp.sys.mac.apps Subject: Re: Screensnap 2.2 memory problems? Message-ID: <7258@ncar.ucar.edu> Date: 8 May 90 14:17:53 GMT References: <3667@newton.physics.purdue.edu> Sender: news@ncar.ucar.edu Organization: National Center for Atmospheric Research Lines: 16