Two of the suggestions amount to not installing your new memory - pretty
dumb suggestions.
So I'd definitely use:
"Use the MaxFileCache setting in the System.ini file to reduce the maximum
amount of memory that Vcache uses to 512 megabytes (524,288 KB) or less."
Further I would suggest the bigger the file cache becomes the less efficient
it becomes and in single user workstation environment it is likely to just
hog lots of memory for little benefit. In your position I'd set it to about
2x your largest scan size (about 60Mb LS-30) + about 20Mb extra = 140MB.
This will leave a minimum 600Mb for your applications.
So convert to Kb 140 x 1024 = 143360 and add immediately under the line
"[vcache]" in system.ini
MaxFileCache=143360
You may like to try a little smaller or larger cache size to see if it is
any better. The thing to consider is how you work. If you regularly re-open
multiple files you have just closed then you may do better with a larger
setting. Conversely if you never close files and immediately reopen them
then smaller may be better but I wouldn't go below one big scan of cache as
you always benefit from having enough file cache for the file output. This
allows you to continue working in the shortest possible time when you save a
file. If you save from Vuescan and then open in PSP then this will also come
straight from the memory cache provided you have not done anything else in
between and PSP is already open.
You may also wish to consider setting "MinFileCache" to try to ensure that
the last big file is always available from cache. After all PSP should be
happy with 600Mb. Some people set MinFileCache to the same value they set
for MaxFileCache so their machine does not waste it's time memory managing
the cache. This is a dangerous policy on a low memory machine but with
600Mb to spare it is unlikely to cause you a problem.
Steve
----- Original Message -----
From: "Rob Geraghty" <harper@wordweb.com>
To: <filmscanners@halftone.co.uk>
Sent: Thursday, July 26, 2001 6:11 AM
Subject: filmscanners: Scanning and memory limits in Windows
> I'm just about to plug another 256MB of RAM into my computer and I thought
> I'd better check up on a bug I'd heard mentioned in relation to Windows
> 98. In fact the bug applies to all versions of Windows other than those
> in the NT class (NT 4.0 and Win2K), not just 98. I think Microsoft's
suggested
> workarounds on MSDN are hilarious. I wish I could move to Win2K, but I
> am reasonably certain that the combination of hardware and software I have
> will not work in that environment. So here's the warning in case you plan
> to have more than 512MB RAM in your Windows 95, 98, 98SE or ME computer:
>
> >The Windows 32-bit protected-mode cache driver (Vcache) determines the
> maximum
> >cache size based on the amount of RAM that is present when Windows
starts.
> >Vcache then reserves enough memory addresses to permit it to access a
cache
> >of the maximum size so that it can increase the cache to that size if
needed.
> >These addresses are allocated in a range of virtual addresses from
0xC0000000
> >through 0xFFFFFFFF (3 to 4 gigabytes) known as the system arena.
> >
> >On computers with large amounts of RAM, the maximum cache size can be
large
> >enough that Vcache consumes all of the addresses in the system arena,
leaving
> >no virtual memory addresses available for other functions such as opening
> >an MS-DOS prompt (creating a new virtual machine).
> >
> >WORKAROUND
> >To work around this problem, use one of the following methods:
> >
> >Use the MaxFileCache setting in the System.ini file to reduce the maximum
> >amount of memory that Vcache uses to 512 megabytes (524,288 KB) or less.
> >
> >For additional information about how to use the MaxFileCache setting,
click
> >the article number below to view the article in the Microsoft Knowledge
> Base:
> >
> >Q108079 32-Bit File Access Maximum Cache Size
> >Use the System Configuration utility to limit the amount of memory that
> Windows
> >uses to 512 megabytes (MB) or less.
> >
> >For additional information about how to use the System Configuration
utility,
> >click the article number below to view the article in the Microsoft
Knowledge
> >Base:
> >Q181966 System Configuration Utility Advanced Troubleshooting Settings
>
> >
> >Reduce the amount of memory that is installed in your computer to 512 MB
> >or less.
>
>
> Rob Geraghty harper@wordweb.com
>
>
>
>
>
