Re: Strange behavior - paging file won't resize.

"nass" <nass@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:42654DCB-98EA-485B-AF37-12E859718A4E@xxxxxxxxxxxxxxxx


"Rock" wrote:

"nass" wrote

> "OldWin32Dog" wrote:
>
>> [Originally posted in windowsxp.configuration_manage]
>>
>> I have recently installed Windows XP Pro on a new laptop. I've >> applied
>> service pack 2 as well as all applicable hotfixes from MS Update.
>>
>> My account is an Administrator on the machine. I go into System
>> Properties
>> and change the paging file settings to a custom size, 3000 initial >> size
>> and
>> 3000 maximum size. I click the Set button, then OK (and so on) until >> I
>> exit
>> System Properties. I get the message telling me to reboot the system. >> I
>> do
>> so. Upon logging back in I notice the paging file is still the same >> size
>> as
>> it had been before I made the change! No messages indicating an error >> in
>> event logs. I go into System Properties and the new settings are >> still
>> set
>> (as noted above).
>>
>> I reboot the box and go into Safe mode. Voila, the paging file size >> has
>> now
>> changed to the size I set. Good. Reboot and go on about business.
>> However, upon logging in I see that the paging file has again gone >> back
>> to
>> its original size!
>>
>> Any ideas as to what is going on here?
>> Thank you!
>
> Hi,
> In setting the page file there are certain rules:
> We all know that the page file minimum is 1.5 the amount of the RAM
> installed on the Operating system and the Maximum is 3 times that > amount.
> Say for example: you have the famous 256 MBs of RAM, the minimum > Paging
> file will be (384 = 1.5X256) and the Maximum amount of the paging file > is
> 1152= 3 X 256.
> So I don't know how much RAM you have installed on your Computer!.
> Read this article:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;308417
> Another if you have a protective softwares that runing and disallowing > the
> changes if all been right?.


I disagree here. There are no rules for setting the page file, nor is there
any maximum. The old rule to have the page file set to 1.5 x the amount of
RAM is not a good one to follow in XP. The amount of page file needed
depends on how much memory is in the system and what apps are run.

The only rule that has any general applicability is that the more memory
there is in the system, the less the page file is needed. Certain apps are
heavy on page file needs so they skew this general rule. I would recommend
you read the article on Virtual Memory and setting the page file by the late
Alex Nichol, MVP. There is a small utility by Bill James, linked to on this
site, with which you can monitor actual page file usage and thus set the
page file accordingly.

Note there is no advantage to setting a minimum and maximum page file
setting to be the same. Set the initial size setting to be above your
normal page file usage as shown by this utility, and then set a maximum
above that to give it some room to grow if some special circumstance needs
it

To the OP, sorry I don't know what is causing your problem. I have not seen
it in practice so it's certainly not universal for SP2 installations, but
that doesn't mean there isn't something unique about your setup with SP2 and
post SP2 updates causing this. On occasion someone posts here with this
problem, but not very often. One culprit indentified in several instances
has been a Norton home product. It's been some time since I saw the last
this tied to a Norton product, so I don't know if it was unique to those
versions, or if it does still occur.

Virtual Memory in Windows XP
http://aumha.org/win5/a/xpvm.htm

Will do Rock...
But if the OP wanted to use Customize Setting these rules can be a guide or
be considered.
If the OP set the page file to lesser than this (Minimum) the system will
produce an Error of a " Virtual memory" kind.
If the OP Increase the Page file size to more than needed, it will n't be a
problem but it will be wasted.
I don't why the OP doesn't like to let windows manage it, instead of custome
settings file?.


Yes, letting windows manage it is ok, though if the system has a lot of memory system managed allocates too much for the page file (assuming you don't have one of those page file hungry apps). And yes the only downside to having too large a page file is that the space is wasted. Normally with hard drive costs the way they are you don't need to worry about this.

--
Rock [MVP - User/Shell]

.

Loading