go to the virtual memory
configuration window and
set it to custom with a
initial size=2 and max=1.5
times the size of your
ram.
example: if you have 1 gig
of ram, then set the max
to 1.5 gigs. however, there
is also a recommended size
provided by your operating
system and can be found
on that same window where
you set the size.
be sure to have only
1 pagefile as some
people set 2 or more.
then reboot.
in addition to the pagefile
system, you might also
benefit by a freeware
called pagedefrag.
it can be downloaded
from microsoft.com
here are some helpful
links:
http://search.microsoft.com/results.aspx?mkt=en-US&setlang=en-US&q=virtual+memory+too+low
to run windows only.
and 512 is perfect to
run windows with regular
third party software.
further, the error message
the o.p. is receiving is the
result of the vm being in
automatic mode.
therefore, the suggestion
to leave it as is, is simply
telling the o.p. to put up
with the nagging problem
as posted.
"In fact, the correct setting for virtual memory is "system managed
size".
Argumentative, although many hold that view.
If the minimum and maximum pagefile sizes are not the same, the
pagefile will initially be allocated to the minimum size, then
expanded as more space is needed, up to the maximum. On most
systems, this will mean that the pagefile will be fragmented,
possibly in widely separated parts of the disk. If there is a
significant amount of paging activity, this can lead to unnecessary
performance degradation. Setting the minimum and maximum the same
size may still result in a fragmented pagefile, but does reduce the
likelihood of serious fragmentation. If the system is paging heavily
and the pagefile is heavily fragmented, consider moving the pagefile
to a newly formatted partition on a separate disk Source:
http://members.shaw.ca/bsanders/WindowsGeneralWeb/RAMVirtualMemoryPageFileEtc.htm
nagging problem is a
reasonable solution for
idiots.
lastly the manipulative
arguments that suggest the
vm "has" to be set to auto
mode are faulty ones.
if they were not then the
microsoft software engineers
would have omitted the custom
and no pagefile options from
the operating system.
therefore i stand by my suggestion
and successful experience by
setting the vm to a fixed/custom
size that alleviates problems
like that of the op's.
obviously there are chicken
littles that cannot ween
themselves off the "idiot"
proof options.
of convenience.
it is not wrong to suggest
it or faulty to recommend
it.
however if you or anyone
really wants an exact number
for the amount of pagefile/vm
the system uses, then simply
get it.
it is not hard to analyze it
nor faulty to ascertain some
elightenment.
you will likely find and
also prove to yourself that
your system will never
use more that a couple
hundred megs of pagefile
regardless if it is set to .5
or 1.5 or 10.5 the actual
size of your ram.
if you prove to yourself
that none of your software
demands more pagefile than
say half the size of your ram,
then setting your vm to half
the size won't cause any
problems. thus the argument
for the 1.5 formula will prove
to be more vm than necessary.
the only exception is for
specialty software that is
"engineered" to demand lots
of pagefile, like video or
graphics editors.
but in these cases, you will likely
need additional ram anyways as
per the software requirements,
thus the vm will also be
larger as well.
but for the most part, off
the shelf software is engineered
for the average user and the
average pc configuration.
lastly, your argument that
custom/fixed sizing of the
vm are for a certain class
of computer users is faulty.
the custom/fixed sizing of
the vm is for a certain class
of configuration where the
automatic resizing is not
managiable by windows
on some pc's.
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.