I definitely recommend setting the swap file (disk space used for virtual 
memory) to a fixed size, rather than letting windows grow and shrink and 
grow and shrink and fragment and reallocate it, and generally make it a slow 
sticky mess.

On 28 Jan 2006 at 0:53, Don Penlington wrote:

> The usual rule of thumb is to set virtual memory at twice RAM as a starting 
> point.

  Various rules of thumb for this have been handed around.  The amount of 
virtual memory needed depends on the task load, and not directly on the 
amount of physical RAM installed.  Any rule of thumb which is based on the 
physical RAM is *assuming* that you already have adequate physical RAM for 
the mix of applications you want to tun.
 
> It's one of those error messages that doesn't really mean what it 
> says.  Although you may have plenty of RAM, some programs seem to want to 
> write to virtual memory regardless. If this is limited or constrained by 
> Windows management or lack of disk space, you could get that error message.

  Part of allocating memory to a process is allocating swap space to 
virtualize that memory.  So if a program asks the OS for memory, and there 
isn't swap space available, the program's request is denied, and this is 
generally reported as "insufficient memory" without any knowledge of *why* 
the request failed -- the code issuing the error message simply doesn't know 
such details.

David Gillett

                         PCSOFT's List Owner's:
                      Bob Wright<[log in to unmask]>
                       Drew Dunn<[log in to unmask]>