Toobi-Won Kenobi schreef:
>
>
>
> Switch off compatabilty mode (if you do not use earlier versions)and try
> reducing your number of History states in Preferences.
> Run TaskManager in performance mode in conjuction with PS and see what
> limits are being hit when you are working.
>
In the dialog box for these options I discovered also a slider to set
the use of RAM by PS. In my cas it took 55% of the available 1102 MB.
With TaskManager I already noticed, that loading layered psd-images took
already up to 500 MB of RAM thus nearing the limits of this setting.
This explains my "out of memory-messages" while closing down with a lot
of information on the clip board or while opening plug-ins like Fluid
Mask or Photmatix. These errors don't occur when I run Photomatix in
stand alone mode outside the PS-environment. That would explain a lot....

For a start I moved up the slider to the maximum recommended amount of
798 MB (appr. 70% of the RAM the system leaves free). I could move up to
1102 MB because usually I don't run PS parallel to other applications.

I will report back my experiences.
>
>

"Kees van Surksum" <corne4851@gmail.com> wrote in message
news:47DE58A5.8050900@gmail.com...
> Toobi-Won Kenobi schreef:
>>
>> Switch off compatabilty mode (if you do not use earlier versions)and try
>> reducing your number of History states in Preferences.
>> Run TaskManager in performance mode in conjuction with PS and see what
>> limits are being hit when you are working.
>>
> In the dialog box for these options I discovered also a slider to set the
> use of RAM by PS. In my cas it took 55% of the available 1102 MB. With
> TaskManager I already noticed, that loading layered psd-images took
> already up to 500 MB of RAM thus nearing the limits of this setting. This
> explains my "out of memory-messages" while closing down with a lot of
> information on the clip board or while opening plug-ins like Fluid Mask or
> Photmatix. These errors don't occur when I run Photomatix in stand alone
> mode outside the PS-environment. That would explain a lot....
>
> For a start I moved up the slider to the maximum recommended amount of 798
> MB (appr. 70% of the RAM the system leaves free). I could move up to 1102
> MB because usually I don't run PS parallel to other applications.
>
> I will report back my experiences.
>>

"Toobi-Won Kenobi" <Toobi-won Kenobi@Tatooine.com> wrote in message
news:fro4hd$dqu$1$8300dec7@news.demon.co.uk...
>
> "Kees van Surksum" <corne4851@gmail.com> wrote in message
> news:47DE58A5.8050900@gmail.com...
>> Toobi-Won Kenobi schreef:
>>>
>>> Switch off compatabilty mode (if you do not use earlier versions)and
>>> try reducing your number of History states in Preferences.
>>> Run TaskManager in performance mode in conjuction with PS and see what
>>> limits are being hit when you are working.
>>>
>> In the dialog box for these options I discovered also a slider to set the
>> use of RAM by PS. In my cas it took 55% of the available 1102 MB. With
>> TaskManager I already noticed, that loading layered psd-images took
>> already up to 500 MB of RAM thus nearing the limits of this setting. This
>> explains my "out of memory-messages" while closing down with a lot of
>> information on the clip board or while opening plug-ins like Fluid Mask
>> or Photmatix. These errors don't occur when I run Photomatix in stand
>> alone mode outside the PS-environment. That would explain a lot....
>>
>> For a start I moved up the slider to the maximum recommended amount of
>> 798 MB (appr. 70% of the RAM the system leaves free). I could move up to
>> 1102 MB because usually I don't run PS parallel to other applications.
>>
>> I will report back my experiences.
>>>
>

"Toobi-Won Kenobi" <Toobi-won Kenobi@Tatooine.com> wrote in message
news:fro4hd$dqu$1$8300dec7@news.demon.co.uk...
>
> "Kees van Surksum" <corne4851@gmail.com> wrote in message
> news:47DE58A5.8050900@gmail.com...
>> Toobi-Won Kenobi schreef:
>>>
>>> Switch off compatabilty mode (if you do not use earlier versions)and
>>> try reducing your number of History states in Preferences.
>>> Run TaskManager in performance mode in conjuction with PS and see what
>>> limits are being hit when you are working.
>>>
>> In the dialog box for these options I discovered also a slider to set the
>> use of RAM by PS. In my cas it took 55% of the available 1102 MB. With
>> TaskManager I already noticed, that loading layered psd-images took
>> already up to 500 MB of RAM thus nearing the limits of this setting. This
>> explains my "out of memory-messages" while closing down with a lot of
>> information on the clip board or while opening plug-ins like Fluid Mask
>> or Photmatix. These errors don't occur when I run Photomatix in stand
>> alone mode outside the PS-environment. That would explain a lot....
>>
>> For a start I moved up the slider to the maximum recommended amount of
>> 798 MB (appr. 70% of the RAM the system leaves free). I could move up to
>> 1102 MB because usually I don't run PS parallel to other applications.
>>
>> I will report back my experiences.
Kees,

55% memory is considered to be the optimum memory allocation for PS,
increasing the ammount past this can cause problems with the OS.
Rather than increase the allocation it is better to increase the ammount of
RAM.
Added memory idealy needs to be in matched pairs, 2 x 512, 2 x 1GB etc.,
Did you try reducing the history states in preferences?

TWK

>>> I will report back my experiences.
> Kees,
>
> 55% memory is considered to be the optimum memory allocation for PS,
> increasing the ammount past this can cause problems with the OS.
> Rather than increase the allocation it is better to increase the ammount of
> RAM.
> Added memory idealy needs to be in matched pairs, 2 x 512, 2 x 1GB etc.,
> Did you try reducing the history states in preferences?
>
> TWK
>
>
Hi Toobi-Won,

Took a while to get back to this issue because I was on the road once
again. So far I have noticed a slight improvement after I allocated more
RAM to PS. Now I suffer hardly any memory problems. You were right about
the immense amount of RAM neccesary to perform tasks in multiple layers
on for instance RAW files.

What the unequal memory bits concernes, the problems I reported started
way before I changed the second 512 MB for a 1 Gig, so you may be right
about that, but in my opinion it has nothing to do with the problem
reported. Nevertheless I will consider bying another 1 Gig bit to put
into the main slot.

And yes, I reduced the historie states also, maybe that did the rest...

Thanks for your .

Kees

"Kees van Surksum" <corne4851@gmail.com> wrote in message
news:47ED3BBB.7040700@gmail.com...
>
>>>> I will report back my experiences.
>> Kees,
>>
>> 55% memory is considered to be the optimum memory allocation for PS,
>> increasing the ammount past this can cause problems with the OS.
>> Rather than increase the allocation it is better to increase the ammount
>> of RAM.
>> Added memory idealy needs to be in matched pairs, 2 x 512, 2 x 1GB etc.,
>> Did you try reducing the history states in preferences?
>>
>> TWK
> Hi Toobi-Won,
>
> Took a while to get back to this issue because I was on the road once
> again. So far I have noticed a slight improvement after I allocated more
> RAM to PS. Now I suffer hardly any memory problems. You were right about
> the immense amount of RAM neccesary to perform tasks in multiple layers on
> for instance RAW files.
>
> What the unequal memory bits concernes, the problems I reported started
> way before I changed the second 512 MB for a 1 Gig, so you may be right
> about that, but in my opinion it has nothing to do with the problem
> reported. Nevertheless I will consider bying another 1 Gig bit to put into
> the main slot.
>
> And yes, I reduced the historie states also, maybe that did the rest...
>
> Thanks for your .
>
Hello Kees,

Glad to , you should see a little improvement when ypu match your RAM
sticke, possibly more if you MB has dual controllers.
http://www.hardwaresecrets.com/article/133

Regards
TWK

> Hello Kees,
>
> Glad to , you should see a little improvement when ypu match your RAM
> sticke, possibly more if you MB has dual controllers.
> http://www.hardwaresecrets.com/article/133
>
> Regards
> TWK
>
>

Hi,

After I experienced some shutdowns again. I decided to do the final
test. I went to the website you advised me, but there they did not say
anything against unequal memory sticks.

But I thought I understood it matters which stick is in which slot. So I
opened up my laptop and exchanged the memory sticks, so that the biggest
one is in the primary slot and the original 512 MB in the secondary
slot. And guess what...??? No problems whatsoever anymore......!!

Even with 1,2 Gigs RAM in use PS keeps running like hell.

I'm glad and hope I can somebody else with this information.

Best regards
Kees

"ac4851" <corne4851@gmail.com> wrote in message
news:47f68cdf$0$2943$ba620e4c@news.skynet.be...
>
>> Hello Kees,
>>
>> Glad to , you should see a little improvement when ypu match your RAM
>> sticke, possibly more if you MB has dual controllers.
>> http://www.hardwaresecrets.com/article/133
>>
>> Regards
>> TWK
>>
>>
>
> Hi,
>
> After I experienced some shutdowns again. I decided to do the final test.
> I went to the website you advised me, but there they did not say anything
> against unequal memory sticks.
>
> But I thought I understood it matters which stick is in which slot. So I
> opened up my laptop and exchanged the memory sticks, so that the biggest
> one is in the primary slot and the original 512 MB in the secondary slot.
> And guess what...??? No problems whatsoever anymore......!!
>
> Even with 1,2 Gigs RAM in use PS keeps running like hell.
>
> I'm glad and hope I can somebody else with this information.
>
> Best regards
> Kees
Hello Kees,
Thanks for the update

Regards
TWK