[softwarelist] Re: Odd DPlngScan error
- From: Chris Johnson <chris@xxxxxxxxxxxxxxxxxxxxx>
- To: davidpilling@xxxxxxxxxxxxx
- Date: Wed, 07 Dec 2016 17:25:43 +0000 (GMT)
In article <afccccea55.Alan.Adams@xxxxxxxxxxxxxxxxxxxxxx>,
Alan Adams <alan@xxxxxxxxxxxxxxxx> wrote:
I get this on every image from my camera. The images are 4928 x
3264. Increasing the WimpSlot in both places in !Run to 20000K
doesn't fix it.
It is not the wimp slot that is important here. You need to go in to
iconbar menu -> Choices -> Memory
You will see an entry 'Max RAM'. It is this that should be increased
to deal with large images in 24/32 bbp colour entirely in RAM. You
could raise it to 64000K or more depending how much memory your
machine is fitted with.
While you are in that dbox, check that 'Temporary file' is pointing
to a valid location. It should default to <Wimp$ScrapDir>. However,
the line in the !Run file that sets this has been commented out if
you are using 1.27.
The line is
|Set DPlngScan$Scrap <Wimp$ScrapDir>
If it has that leading pipe character remove it, resave !Run, and
rerun DPScan.
This location is where DPScan will place its temporary files when
using virtual memory, for when image memory requirements exceed the
set RAM size.
I am not sure when the line in !Run became commented out. I was
assuming it was recent, but checking the old version 1.25 in my
backup it is commented there, and the file is time stamped 2011.
It has now become important because the new version is not supplied
with a config file, which was setting it before.
The latest version (1.27b) on my web site has had this corrected.
Sorry for the cockup.
--
Chris Johnson
To unsubscribe or subscribe goto:
//www.freelists.org/list/davidpilling
Other related posts:
