
Signature
Glen Ventura, MS MVP Shell/User, A+
http://dts-l.org/goodpost.htm
Very good and accurate description of memory limitations and usage.
However, there is no explanation given for the relationship between
FileCache and available memory. I've noticed that applications and large
files open slightly faster the first time around and most definately faster
the second and third time around with my system using 1GB of RAM versus my
old setup of 512MB. Further more, neither setup causes Windows to use the
Virtual SwapFile ( which is to date still at 0KB ).
> Have a look here:
> http://snipurl.com/om0b
>
> Full Link:
http://groups.google.com/group/microsoft.public.win98.gen_discussion/browse_thre
ad/thread/520519be293d9ab7/c61d54aeaa0fffab?lnk=st&q=group%3Amicrosoft.public.wi
n98.gen_discussion+insubject%3AIncreasing+insubject%3Amemory+author%3ARon+author
%3AMartell&rnum=1&hl=en#c61d54aeaa0fffab
> > I'm not sure what "Workarounds" you're talking about...since I only know of
> > one! That is to put an entry in the system.ini file under the vcache
[quoted text clipped - 23 lines]
> > >
> > > Thanks.
Ron Martell - 07 Apr 2006 05:58 GMT
>Very good and accurate description of memory limitations and usage.
>However, there is no explanation given for the relationship between
[quoted text clipped - 3 lines]
>old setup of 512MB. Further more, neither setup causes Windows to use the
>Virtual SwapFile ( which is to date still at 0KB ).
Windows will always attempt to find some use, anything that might
possibly be of benefit, for every bit of the installed RAM. This
includes maintaining a large disk cache of recently accessed files so
that when (and it often is "when" and not "if") those files are needed
again the contents are already in RAM and do not have to be reloaded
from disk.
The reason why it is necessary to limit the size of the disk cache to
not more than 512 mb on systems with huge amounts of RAM is that
Windows will otherwise allocate more than 512 mb of RAM for this if
the RAM is available. However, under the segmented memory model used
in Windows 95/98/Me the 4 gb total x86 32 bit address space is
subdivided into 3 sections:
2 gb for application programs and user data files
1 gb for operating system files
1 gb for "system arena" including support function such as the AGP
video arpeture and the disk cache.
If more than 512 mb of this total 1 gb of address space is committed
to disk cache then it is possible that other users of this address
space will find that there are no available addresses within that
range that are not already in use. Result = crash.
Hope this is the explanation you were looking for.
Good luck
Ron Martell Duncan B.C. Canada

Signature
Microsoft MVP (1997 - 2006)
On-Line Help Computer Service
http://onlinehelp.bc.ca
"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."
Jeff Richards - 09 Apr 2006 07:29 GMT
Just because the system crashes at 512Mb without the workaround doesn't mean
that it will be forced to use less cache when the workaround is installed.
The problem, and the limitation, applies to the address range that is
available to allocate to cache, if needed. Few systems would ever actually
allocate sufficient cache, even with 1Gb of RAM installed, to run up against
the limitation.

Signature
Jeff Richards
MS MVP (Windows - Shell/User)
> Very good and accurate description of memory limitations and usage.
> However, there is no explanation given for the relationship between
[quoted text clipped - 4 lines]
> old setup of 512MB. Further more, neither setup causes Windows to use the
> Virtual SwapFile ( which is to date still at 0KB ).