Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!zaphod.mps.ohio-state.edu!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: <7260@ncar.ucar.edu>
Date: 8 May 90 14:30:39 GMT
Sender: news@ncar.ucar.edu
Organization: National Center for Atmospheric Research
Lines: 25
References:<3667@newton.physics.purdue.edu> <7258@ncar.ucar.edu>

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
> 
Well, foolish me. I should know better than to post a knee-jerk follow-up. 
Bits ain't bytes! Abject apologies and all that...

Harry Chesley, the NetNews reader stack needs a way to cancel a posting 
(if the NNTP protocol will support it). We dummies need one last 
opportunity to save ourselves from stupidom.

Herb Poppe            NCAR
hpoppe@ncar.ucar.edu  1850 Table Mesa Drive
                      Boulder, CO  80307-3000
                      (303) 497-1296