Okay, let's say I've been using CS2 for a day or so, doing various things.
This morning:

1. I close all the images I've got open and open a scanned JPG image. It's
a 2-1/4" square image at 2400 DPI which, after minor cropping, is ~73 MB.

2.I create an Adjustment Layer for Levels and make the necessary changes.

3. I save it as a .PSD file with the 2 layers

4. I try to save it as a .JPG file. I get the dreaded "Insufficient Memory
to save ..." message.

5. I close Photoshop and reopen it.

6. I load the saved .PSD, flatten it, and successfully save it as a .JPG

Okay, I know that Photoshop caches some stuff, so I've set the Cache Level
in Preferences to 2 instead of the original 6. I've told the program to use
all of the available memory (100%) which it calculates as 907MB (it's really
a 1GB memory but I guess Win2K doesn't allocate all of it to programs).

It's obvious that Photoshop would have had sufficient memory to do the
original save (#4) if the program's caches had really been empty as they
were when I reopened it. Is there anything I can do between images (or
while I'm editing an image) to empty the caches or am I stuck closing and
reopening the program. This is especially important because I've been
screwed being totally unable to save an image in any format after working on
it for a while.


TIA
Norm

"Norm Dresner" <ndrez@att.net> found these unused words:

>Okay, let's say I've been using CS2 for a day or so, doing various things.
>This morning:
>
>1. I close all the images I've got open and open a scanned JPG image. It's
>a 2-1/4" square image at 2400 DPI which, after minor cropping, is ~73 MB.
>
>2.I create an Adjustment Layer for Levels and make the necessary changes.
>
>3. I save it as a .PSD file with the 2 layers
>
>4. I try to save it as a .JPG file. I get the dreaded "Insufficient Memory
>to save ..." message.
>
>5. I close Photoshop and reopen it.
>
>6. I load the saved .PSD, flatten it, and successfully save it as a .JPG
>
>Okay, I know that Photoshop caches some stuff, so I've set the Cache Level
>in Preferences to 2 instead of the original 6. I've told the program to use
>all of the available memory (100%) which it calculates as 907MB (it's really
>a 1GB memory but I guess Win2K doesn't allocate all of it to programs).

You do neet memory for the operating system and other running processes!

Win2K doesn't release 'used' memory in some cases. Not sure if CS2 is as
much a contributing factor, but ... the memory 'pool' shrinks.

You might consider grabbing a copy of XP-Pro before they're gone and you
have to deal with hassle laVista.

>It's obvious that Photoshop would have had sufficient memory to do the
>original save (#4) if the program's caches had really been empty as they
>were when I reopened it. Is there anything I can do between images (or
>while I'm editing an image) to empty the caches or am I stuck closing and
>reopening the program. This is especially important because I've been
>screwed being totally unable to save an image in any format after working on
>it for a while.
>
>
> TIA
> Norm

Norm Dresner wrote:
> Okay, let's say I've been using CS2 for a day or so, doing various
> things. This morning:
>
> 1. I close all the images I've got open and open a scanned JPG image.
> It's a 2-1/4" square image at 2400 DPI which, after minor cropping,
> is ~73 MB.
>
> 2.I create an Adjustment Layer for Levels and make the necessary
> changes.
>
> 3. I save it as a .PSD file with the 2 layers
>
> 4. I try to save it as a .JPG file. I get the dreaded "Insufficient
> Memory to save ..." message.
>
> 5. I close Photoshop and reopen it.
>
> 6. I load the saved .PSD, flatten it, and successfully save it as a
> .JPG
>
> Okay, I know that Photoshop caches some stuff, so I've set the Cache
> Level in Preferences to 2 instead of the original 6. I've told the
> program to use all of the available memory (100%) which it calculates
> as 907MB (it's really a 1GB memory but I guess Win2K doesn't allocate
> all of it to programs).
>
> It's obvious that Photoshop would have had sufficient memory to do the
> original save (#4) if the program's caches had really been empty as
> they were when I reopened it. Is there anything I can do between
> images (or while I'm editing an image) to empty the caches or am I
> stuck closing and reopening the program. This is especially
> important because I've been screwed being totally unable to save an
> image in any format after working on it for a while.

Have you tried the Purge>All in the Edit menu?

--
dvus

"dvus" <dven1@adelphia.invalid> wrote in message
news:63aiq4F250jcjU1@mid.individual.net...
| Norm Dresner wrote:
| > Okay, let's say I've been using CS2 for a day or so, doing various
|> [BIG SNIP OF MY OWN STUFF]
| > Okay, I know that Photoshop caches some stuff, so I've set the Cache
| > Level in Preferences to 2 instead of the original 6. I've told the
| > program to use all of the available memory (100%) which it calculates
| > as 907MB (it's really a 1GB memory but I guess Win2K doesn't allocate
| > all of it to programs).
| >
| > It's obvious that Photoshop would have had sufficient memory to do the
| > original save (#4) if the program's caches had really been empty as
| > they were when I reopened it. Is there anything I can do between
| > images (or while I'm editing an image) to empty the caches or am I
| > stuck closing and reopening the program. This is especially
| > important because I've been screwed being totally unable to save an
| > image in any format after working on it for a while.
|
| Have you tried the Purge>All in the Edit menu?
|
| --

NO! But it looks exactly like what I need. Thanks much.

Norm

In a Windows operating system, 3.x to the horror that is Vista, out of
memory warnings do not necessarily have anything to do with available
physical or virtual memory. In fact they rarely do.
Out of memory warnings usually refer to dwindling system resources, the
pointers that the OS uses to keep track of things. While successive versions
of Windows have improved on this it is still a problem for many reasons.
As someone pointed out many programs do not release their resources, as well
as the memory addresses, they were using after you close them. This used to
be a major issue with MS Word, to name one. Itunes eats up alot even when it
is not running (all praise the great programmers at Apple).
When you purge memory in Photoshop you are forcing the release of both RAM
and system resources that PS was using. Would that other programs allowed
the same. There are shareware programs that say they are able to do this as
well.
If you are getting frequent out of memory messages it would behoove you to
see what background processes and programs are running that are eating
memory and system resources. The one GB of ram in your system, while not
optimal, is sufficient for running files of the sizes you mention in
Photoshop in Win2K.
Not to alarm you but I would run several anti-spyware and an anti root-kit
program to see if that might be an issue.
You also need to check what is loading when you boot your computer--the
WIn2k version of msconfig.
I would also highly recommend you get a copy of WInXP, home or professional,
while you still can. Vista with the current beta service pack is still slow,
incompatible with too many programs and lacking stable drivers for too many
peripherals. However I will admit that CS3 runs reasonably well on Vista,
but time by your stopwatch slower than XP for any disc access operations
(and what does not access the hard drive?).
The MAC OS has comparable memory limits but MAC users tend to single task.
install less programs (there are far fewer programs for them to install),
and, while Leopard is actually more vulnerable to malware attack than XP or
Vista, so far it is not threatened by malware because businesses do not run
on Apple and the overall market share is too small to bother with.

flambe wrote:
> In a Windows operating system, 3.x to the horror that is Vista, out of
> memory warnings do not necessarily have anything to do with available
> physical or virtual memory. In fact they rarely do.
> Out of memory warnings usually refer to dwindling system resources, the
> pointers that the OS uses to keep track of things. While successive versions
> of Windows have improved on this it is still a problem for many reasons.

Usually due to Windows poor implementation of how it re-allocates
resources when programs close. Win2k is Win-NT 4.0 with some bug fixes.

The one bug that didn't get fixed is NT's notorious memory "leaks". The
OS just loses track of pointers after they've been allocated to a
program. When the program releases the pointers, the OS doesn't pick
them back up.

About the only answer when you get one of these out of memory messages
is save what you can and re-boot.

With Win-NT 4.0 and Win2k it's probably a good idea to shut it down and
re-start it every morning before trying to do anything else anyway.

On Thu, 06 Mar 2008 14:53:22 GMT, "Norm Dresner" <ndrez@att.net>
wrote:

>I've told the program to use
>all of the available memory (100%)

Adobe says not to tell Photoshop to use 100%.
http://kb.adobe.com/selfservice/view...0005&sliceId=1
--
Paul Hartman/Dirty Linen
The Magazine of Folk and World Music
www.dirtylinen.com
Remove "SpamBeGone" to reply.

"Pudentame" <no.one@no.were.invalid> a écrit dans le message de
news: 47d1cd86$0$16677$4c368faf@roadrunner.com...
> flambe wrote:
>> In a Windows operating system, 3.x to the horror that is
>> Vista, out of memory warnings do not necessarily have anything
>> to do with available physical or virtual memory. In fact they
>> rarely do.
>> Out of memory warnings usually refer to dwindling system
>> resources, the pointers that the OS uses to keep track of
>> things. While successive versions of Windows have improved on
>> this it is still a problem for many reasons.
>
> Usually due to Windows poor implementation of how it
> re-allocates resources when programs close. Win2k is Win-NT 4.0
> with some bug fixes.
>
> The one bug that didn't get fixed is NT's notorious memory
> "leaks". The OS just loses track of pointers after they've been
> allocated to a program. When the program releases the pointers,
> the OS doesn't pick them back up.
>
> About the only answer when you get one of these out of memory
> messages is save what you can and re-boot.
>
> With Win-NT 4.0 and Win2k it's probably a good idea to shut it
> down and re-start it every morning before trying to do anything
> else anyway.
"
Si stratta a mio avviso di una problema di installazione e
aggiornamento
di un'anomalia mai vista.
Ho trovato ANCHE questa soluzione che ancora devo provare (devo
lavorare
o giocare al tecnico di Scuola Radio Elettra con Adobe?):

http://joemaller.com/2007/08/10/fixi...saving/#update

"