Weird PSCS2 Problem

Archived from groups: rec.photo.digital (More info?)

Steven Wandy wrote:

> I am having a strange problem with PSCS2.
> I use a Epson Perfection 1660 scanner using the latest Twain driver
> (Version 5.something).
> I was trying to scan a picture and anytime I set the resolution above 300
> DPI in the Twain settings PSCS2 would lock up after the scan was done. (It
> looks like in addition to starting the scanning process with the Twain
> driver, WIA - the windows software to acquire images - is also running. I
> can see the window showing scanning progress from WIA in back of the Epson
> one.)
> When I use PS Elements 2 or PS Image Ready CS2 the problem does not occur.
> I have already tried removing the Twain driver and reinstalling it. I am
> not sure when this
> problem started occuring because I rarely scan above 300 DPI and
> definitely did not try since upgrading from CS to CS2.
> Any suggestions? Thanks, Steve
>

Not enough RAM (or defective RAM?)or you need a larger scratch disk? Just a
thought since if only affects larger images. I'd run one of those ram
testing programs and see if anything turns up.
--

Stacey

Archived from groups: rec.photo.digital (More info?)

Stacey wrote:
> Steven Wandy wrote:
>
>
>>I am having a strange problem with PSCS2.
>>I use a Epson Perfection 1660 scanner using the latest Twain driver
>>(Version 5.something).
>>I was trying to scan a picture and anytime I set the resolution above 300
>>DPI in the Twain settings PSCS2 would lock up after the scan was done. (It
>>looks like in addition to starting the scanning process with the Twain
>>driver, WIA - the windows software to acquire images - is also running. I
>>can see the window showing scanning progress from WIA in back of the Epson
>>one.)
>>When I use PS Elements 2 or PS Image Ready CS2 the problem does not occur.
>>I have already tried removing the Twain driver and reinstalling it. I am
>>not sure when this
>>problem started occuring because I rarely scan above 300 DPI and
>>definitely did not try since upgrading from CS to CS2.
>>Any suggestions? Thanks, Steve
>>
>
>
> Not enough RAM (or defective RAM?)or you need a larger scratch disk? Just a
> thought since if only affects larger images. I'd run one of those ram
> testing programs and see if anything turns up.

Maybe allocating 40% RAM to Photoshop will allow Epson scan enough
memory to complete the task. Seeing as CS2 only runs on XP I'd guess you
haven't (yet) modified the default Window swap file. Do it now maybe?
Set the swap file to a fixed size of 4092 (maximum permissible) and if
possible move it to a drive Photoshop is not using as a scratch drive.

Otherwise maybe follow Stacey's suggestion and buy more RAM. Although
what you are trying can be done with 512 meg.

--
Douglas

Archived from groups: rec.photo.digital (More info?)

>
> Maybe allocating 40% RAM to Photoshop will allow Epson scan enough memory
> to complete the task. Seeing as CS2 only runs on XP I'd guess you haven't
> (yet) modified the default Window swap file. Do it now maybe? Set the swap
> file to a fixed size of 4092 (maximum permissible) and if possible move it
> to a drive Photoshop is not using as a scratch drive.
>
> Otherwise maybe follow Stacey's suggestion and buy more RAM. Although what
> you are trying can be done with 512 meg.
>
> --
> Douglas

Have 2 Gig of RAM so I doubt if that is the problem (and as I stated
Elements and Image Ready don't exhibit the same problem. Will try the
suggestion of increasing the size of the swap file.

Archived from groups: rec.photo.digital (More info?)

>
> Have 2 Gig of RAM so I doubt if that is the problem (and as I stated
> Elements and Image Ready don't exhibit the same problem. Will try the
> suggestion of increasing the size of the swap file.
Followup. Adjusted the Virtual Memory, reset the computer and same problems
with CS2.

Archived from groups: rec.photo.digital (More info?)

Steven Wandy wrote:
>>Have 2 Gig of RAM so I doubt if that is the problem (and as I stated
>>Elements and Image Ready don't exhibit the same problem. Will try the
>>suggestion of increasing the size of the swap file.
>
> Followup. Adjusted the Virtual Memory, reset the computer and same problems
> with CS2.
>
>
Yes, but did you alter the allocation of RAM in Photoshop? I'm not
familiar with your specific scanner but I have had that problem on my
workstations with 5 gig of RAM and Epson 4870 scanners. I fixed the
problem by allocating *less* memory to Photoshop.

Windows doesn't care if you have 256 meg of RAM or 5 Gig. It will still
start to swap out to virtual memory at about 125 meg of memory
saturation. If you put the swap file on a separate (high speed) drive
and fix the size of it, Windows runs better and faster.

The real speed increase from installing more RAM is only realized when
you create a "ramdrive" in that RAM and use it for the Windows swap
file. Not something I can explain here as the subject moves off topic.

Photoshop does care about memory allocation but it is also controlled by
windows in how it uses it's allocation. Have you ever had an error
"cannot allocate memory block ###. Close some programs and try again"?

This is what Windows does when Photoshop is running but a program like
Epson scan requiring more of 'base' RAM (that part under the first 1024
megabytes where programs store their critical info in) than is
available, tries to start.

The error message may be suppressed in some versions of XP but it never
the less still happens. You can fix it by allocating *less* memory to
Photoshop. All PS does then is start to swap out to it's own swap file
at an early point and run a little slower.

And here is the tip of the day:
Never presume Information you cannot see as being the cause, is flawed.
You have to address the whole issue, not just a part of it or asking for
advise is a wasted effort.

--
Douglas