Virtual Memory on drive other than C:

[Andrew E.]

Whatever,microsoft,knowlege,TechNet,etc,all say the same
thing,keep the page file off the disk with the operating
system.If you open system properties,advanced,change
virtual memory,(page file)with two disks installed,click
C:,choose custom,leave both windows blank,click set.Then
add to the slave disk,back out,you should be prompted to
restart computer,if not,no changes made.Wishing to do
what now.To verify open DXDIAG for amounts.Why dont you
have xp set to delete page file at shutdown?Its an easy
set-up.
>-----Original Message-----
>We thought it was fixed, but spoke too soon!
>
>However, with the information I got from Nicholas ref to
>http://www.aumha.org/win5/a/xpvm.htm
>the problem is becoming more refined.
>
>With 16M VM on C:, on XP boot the VM on C: stays at 16M
>instead of insisting on creating VM=1024M which is what
>XP does if I specify no VM on C:. I wish I could tell it
>NO PAGEFILE ON C:, because my C: drive is much slower
>than all my other drives. Limiting it to 16M is the best
>XP can do today.
>
>Anyhow, here is the new data getting us closer to the
>root Virtual Memory configuration BUG:
>
>#1 When I run a bunch of memory hungry applications and
>approach using up the RAM, XP says it wants to increase
>my VM.
>
>#2 I check my setting which say 16M on C: and 512M on F:
>
>#3 But at the bottom of the VM settings the total VM
>says only 16M.
>
>#4 So XP only created the 16M on C:!!!!
>
>#5 WORKAROUND: Every time I restart XP, I have to change
>my VM settings for drive F: by increasing the MIN virtual
>memory number to something greater than the one listed in
>the box. So, if I change it from 512M to 640M, a
>pagefile gets created on F: and the total at the bottom
>of the configuration window reflects this.
>
>Again, I wonder if anyone else is using VM on drives
>other than C: and if they are experiencing this BUG.
>
>Steve
>
>>-----Original Message-----
>>Nicholas,
>>
>>Thanks! You did it!
>http://www.aumha.org/win5/a/xpvm.htm
>>is a well written page on the subject of virtual memory.
>>
>>Things work well if I set the min/max Virtual Memory
>size
>>of drive C: to 16MB or greater. 15MB and lower causes
>>the problem I described.
>>
>>Steve
>>
>>>-----Original Message-----
>>>Virtual Memory in Windows XP
>>>http://www.aumha.org/win5/a/xpvm.htm
>>>
>>>(Courtesy of Alex Nichol, MS-MVP)
>>>
>>>
>>>--
>>>Nicholas
>>>
>>>--------------------------------------------------------
>-
>>---------------
>>>
>>>"Steve" > wrote in message:
>>> ...
>>>
>>>| I need your help in resolving my Virtual Memory
>>problem.
>>>|
>>>| If your XP is setup with Virtual Memory on a
>>partition
>>>| other than C: I would like to hear from you. Let me
>>know
>>>| if your partition is on a seperate physical drive.
>>>|
>>>| This will help me figure out if it is just my system
>>or
>>>| an XP issue that needs to be resolved.
>>>|
>>>| Thanks,
>>>| Steve
>>>|
>>>| Following is a revised description (posted on 15th)
>of
>>>| the problem I am experiencing and how I work around
>it:
>>>|
>>>| TO REPRODUCE THE PROBLEM:
>>>| -------------------------
>>>| #1 I change VM on all drives to 0.
>>>|
>>>| #2 Boot the system and erase all pagefile.sys
>>>|
>>>| #3 Change VM on drive F: to either "custom"
>or "system
>>>| managed".
>>>|
>>>| #4 DIR F:\pagefile.sys to verify that it indeed
>exists.
>>>|
>>>| #5 DIR C:\pagefile.sys to verify that it does not
>>exist.
>>>|
>>>| #6 Life is good! The only pagefile being used is on
>>>| drive F: and when I exceed the physical RAM, the VM
>>gets
>>>| used.
>>>|
>>>| #7 Restart or Shutdown XP, then bring back up.
>>>|
>>>|
>>>| PROBLEM:
>>>| #8 A pagefile has been setup on the C: drive and
>>the
>>>| pagefile on F: is no longer being used.
>>>|
>>>| #9 Check the Virtual Memory settings: C: is still
>set
>>>| to "No paging file" with blank MIN MAX fields and F:
>>is
>>>| still set to have paging file. In the MIN field for
>>F:
>>>| is 2048, but the "Currently Allocated" shown at
>bottom
>>is
>>>| 1151MB (all on C:)
>>>|
>>>| #10 Using Windows Explorer, try to erase the pagefile
>>on
>>>| C: and get "Cannot delete pagefile: It is being used
>>by
>>>| another person or program." indicating that XP is
>>using
>>>| it. Using Disk Defragmenter, Analyze C: and you will
>>see
>>>| that the pagefile shows up in RED indicating that it
>>is a
>>>| fragmented file. Pagefiles never show up red, they
>>are
>>>| always green indicating Unmovable file. Intresting.
>>>|
>>>| #11 Using Windows Explorer, try to erase the pagefile
>>on
>>>| F: and it lets me indicating that it was not being
>>used.
>>>|
>>>|
>>>| WORKAROUND:
>>>| #12 Change all drives to "No Paging File" (the F:
>>drive),
>>>| then Restart XP.
>>>|
>>>| #13 This time XP does not try to put a pagefile on
>any
>>of
>>>| the drives.
>>>|
>>>| #13 Set the VM on F:
>>>|
>>>| #14 Erase the old pagefile on C:
>>>|
>>>| Life is good again!
>>>|
>>>|
>>>|
>>>.
>>>
>>.
>>
>..
>
>
>.
>

[JimW±]

Optimally - put a paging file on BOTH disks

How to Configure Paging Files for Optimization and Recovery in Windows =
XP
http://support.microsoft.com/default.aspx?scid=3Dkb;EN-US;314482

The size of the one on the OS drive should be *at least* RAM + about =
12-20 MB

It is also best if the MAX & MIN are the same - then the file will not =
become fragmented & Windows will not need to keep reconfiguring its size
Just make sure the MIN is plenty big enough - if you have a big HD, =
consider making MIN & MAX 2.5 x RAM on the non-OS drive (& then =
defrayment it)

There are advantages to having the pagefile on the outside tracks - =
where more sectors are read in one spin. There are advantages to having =
the paging file in the middle of the drive - less than halfway away from =
any other activity on that drive. There are advantages to having a drive =
JUST for the paging file.
And, there are advantages to having the paging file on the fastest disk

If you dual boot, there are more things to consider -- so you have the =
same size paging files on each drive in each OS


Andrew E. > wrote:
> Whatever,microsoft,knowledge,TechNet,etc,all say the same
> thing,keep the page file off the disk with the operating
> system.If you open system properties,advanced,change
> virtual memory,(page file)with two disks installed,click
> C:,choose custom,leave both windows blank,click set.Then
> add to the slave disk,back out,you should be prompted to
> restart computer,if not,no changes made.Wishing to do
> what now.To verify open DXDIAG for amounts.Why dont you
> have xp set to delete page file at shutdown?Its an easy
> set-up.
>> -----Original Message-----
>> We thought it was fixed, but spoke too soon!
>>=20
>> However, with the information I got from Nicholas ref to
>> http://www.aumha.org/win5/a/xpvm.htm
>> the problem is becoming more refined.
>>=20
>> With 16M VM on C:, on XP boot the VM on C: stays at 16M
>> instead of insisting on creating VM=3D1024M which is what
>> XP does if I specify no VM on C:. I wish I could tell it
>> NO PAGEFILE ON C:, because my C: drive is much slower
>> than all my other drives. Limiting it to 16M is the best
>> XP can do today.
>>=20
>> Anyhow, here is the new data getting us closer to the
>> root Virtual Memory configuration BUG:
>>=20
>> #1 When I run a bunch of memory hungry applications and
>> approach using up the RAM, XP says it wants to increase
>> my VM.
>>=20
>> #2 I check my setting which say 16M on C: and 512M on F:
>>=20
>> #3 But at the bottom of the VM settings the total VM
>> says only 16M.
>>=20
>> #4 So XP only created the 16M on C:!!!!
>>=20
>> #5 WORKAROUND: Every time I restart XP, I have to change
>> my VM settings for drive F: by increasing the MIN virtual
>> memory number to something greater than the one listed in
>> the box. So, if I change it from 512M to 640M, a
>> pagefile gets created on F: and the total at the bottom
>> of the configuration window reflects this.
>>=20
>> Again, I wonder if anyone else is using VM on drives
>> other than C: and if they are experiencing this BUG.
>>=20
>> Steve
>>=20
>>> -----Original Message-----
>>> Nicholas,
>>>=20
>>> Thanks! You did it!
>> http://www.aumha.org/win5/a/xpvm.htm
>>> is a well written page on the subject of virtual memory.
>>>=20
>>> Things work well if I set the min/max Virtual Memory size
>>> of drive C: to 16MB or greater. 15MB and lower causes
>>> the problem I described.
>>>=20
>>> Steve
>>>=20
>>>> -----Original Message-----
>>>> Virtual Memory in Windows XP
>>>> http://www.aumha.org/win5/a/xpvm.htm
>>>>=20
>>>> (Courtesy of Alex Nichol, MS-MVP)
>>>>=20
>>>>=20
>>>> --
>>>> Nicholas
>>>>=20
>>>> -------------------------------------------------------- -
>>>> ---------------=20
>>>>=20
>>>> "Steve" > wrote in message:
>>>> ...
>>>>=20
>>>>> I need your help in resolving my Virtual Memory problem.
>>>>>=20
>>>>> If your XP is setup with Virtual Memory on a partition
>>>>> other than C: I would like to hear from you. Let me know
>>>>> if your partition is on a separate physical drive.
>>>>>=20
>>>>> This will help me figure out if it is just my system or
>>>>> an XP issue that needs to be resolved.
>>>>>=20
>>>>> Thanks,
>>>>> Steve
>>>>>=20
>>>>> Following is a revised description (posted on 15th) of
>>>>> the problem I am experiencing and how I work around it:
>>>>>=20
>>>>> TO REPRODUCE THE PROBLEM:
>>>>> -------------------------
>>>>> #1 I change VM on all drives to 0.
>>>>>=20
>>>>> #2 Boot the system and erase all pagefile.sys
>>>>>=20
>>>>> #3 Change VM on drive F: to either "custom"
>> or "system
>>>>> managed".
>>>>>=20
>>>>> #4 DIR F:\pagefile.sys to verify that it indeed exists.
>>>>>=20
>>>>> #5 DIR C:\pagefile.sys to verify that it does not exist.
>>>>>=20
>>>>> #6 Life is good! The only pagefile being used is on
>>>>> drive F: and when I exceed the physical RAM, the VM gets
>>>>> used.
>>>>>=20
>>>>> #7 Restart or Shutdown XP, then bring back up.
>>>>>=20
>>>>>=20
>>>>> PROBLEM:
>>>>> #8 A pagefile has been setup on the C: drive and the
>>>>> pagefile on F: is no longer being used.
>>>>>=20
>>>>> #9 Check the Virtual Memory settings: C: is still set
>>>>> to "No paging file" with blank MIN MAX fields and F: is
>>>>> still set to have paging file. In the MIN field for F:
>>>>> is 2048, but the "Currently Allocated" shown at bottom is
>>>>> 1151MB (all on C:)
>>>>>=20
>>>>> #10 Using Windows Explorer, try to erase the pagefile on
>>>>> C: and get "Cannot delete pagefile: It is being used by
>>>>> another person or program." indicating that XP is using
>>>>> it. Using Disk Defragmenter, Analyze C: and you will see
>>>>> that the pagefile shows up in RED indicating that it is a
>>>>> fragmented file. Pagefiles never show up red, they are
>>>>> always green indicating Unmovable file. Interesting.
>>>>>=20
>>>>> #11 Using Windows Explorer, try to erase the pagefile on
>>>>> F: and it lets me indicating that it was not being used.
>>>>>=20
>>>>>=20
>>>>> WORKAROUND:
>>>>> #12 Change all drives to "No Paging File" (the F: drive),
>>>>> then Restart XP.
>>>>>=20
>>>>> #13 This time XP does not try to put a pagefile on any of
>>>>> the drives.
>>>>>=20
>>>>> #13 Set the VM on F:
>>>>>=20
>>>>> #14 Erase the old pagefile on C:
>>>>>=20
>>>>> Life is good again!
>>>>>=20
>>>>>=20
>>>>>=20
>>>> .
>>>>=20
>>> .
>>>=20
>> ..
>>=20
>>=20
>> .

[Ron Martell]

"Andrew E." > wrote:

> Whatever,microsoft,knowlege,TechNet,etc,all say the same
> thing,keep the page file off the disk with the operating
> system.

That is not correct. Windows XP *requires* the page file to be on the
boot drive for certain specialized functions that use the page file.

Ron Martell Duncan B.C. Canada
--
Microsoft MVP
On-Line Help Computer Service
http://onlinehelp.bc.ca

"The reason computer chips are so small is computers don't eat much."

[Steve Bland]

Your suggestion does not correlate with what I desire. I
really know what I want to do. Help me accomplish this.

I want as small as possible VM on C:

I want a huge one on F:

Are you using VM on a drive other than C:?

Is it causing the problems I describe below?

TIA,
Steve


>-----Original Message-----
>Optimally - put a paging file on BOTH disks
>
>How to Configure Paging Files for Optimization and
Recovery in Windows XP
>http://support.microsoft.com/default.aspx?scid=kb;EN-
US;314482
>
>The size of the one on the OS drive should be *at least*
RAM + about 12-20 MB
>
>It is also best if the MAX & MIN are the same - then the
file will not become fragmented & Windows will not need
to keep reconfiguring its size
>Just make sure the MIN is plenty big enough - if you
have a big HD, consider making MIN & MAX 2.5 x RAM on the
non-OS drive (& then defrayment it)
>
>There are advantages to having the pagefile on the
outside tracks - where more sectors are read in one spin.
There are advantages to having the paging file in the
middle of the drive - less than halfway away from any
other activity on that drive. There are advantages to
having a drive JUST for the paging file.
>And, there are advantages to having the paging file on
the fastest disk
>
>If you dual boot, there are more things to consider --
so you have the same size paging files on each drive in
each OS
>
>
>Andrew E. > wrote:
>> Whatever,microsoft,knowledge,TechNet,etc,all say the
same
>> thing,keep the page file off the disk with the
operating
>> system.If you open system properties,advanced,change
>> virtual memory,(page file)with two disks
installed,click
>> C:,choose custom,leave both windows blank,click
set.Then
>> add to the slave disk,back out,you should be prompted
to
>> restart computer,if not,no changes made.Wishing to do
>> what now.To verify open DXDIAG for amounts.Why dont
you
>> have xp set to delete page file at shutdown?Its an
easy
>> set-up.
>>> -----Original Message-----
>>> We thought it was fixed, but spoke too soon!
>>>
>>> However, with the information I got from Nicholas ref
to
>>> http://www.aumha.org/win5/a/xpvm.htm
>>> the problem is becoming more refined.
>>>
>>> With 16M VM on C:, on XP boot the VM on C: stays at
16M
>>> instead of insisting on creating VM=1024M which is
what
>>> XP does if I specify no VM on C:. I wish I could
tell it
>>> NO PAGEFILE ON C:, because my C: drive is much slower
>>> than all my other drives. Limiting it to 16M is the
best
>>> XP can do today.
>>>
>>> Anyhow, here is the new data getting us closer to the
>>> root Virtual Memory configuration BUG:
>>>
>>> #1 When I run a bunch of memory hungry applications
and
>>> approach using up the RAM, XP says it wants to
increase
>>> my VM.
>>>
>>> #2 I check my setting which say 16M on C: and 512M on
F:
>>>
>>> #3 But at the bottom of the VM settings the total VM
>>> says only 16M.
>>>
>>> #4 So XP only created the 16M on C:!!!!
>>>
>>> #5 WORKAROUND: Every time I restart XP, I have to
change
>>> my VM settings for drive F: by increasing the MIN
virtual
>>> memory number to something greater than the one
listed in
>>> the box. So, if I change it from 512M to 640M, a
>>> pagefile gets created on F: and the total at the
bottom
>>> of the configuration window reflects this.
>>>
>>> Again, I wonder if anyone else is using VM on drives
>>> other than C: and if they are experiencing this BUG.
>>>
>>> Steve
>>>
>>>> -----Original Message-----
>>>> Nicholas,
>>>>
>>>> Thanks! You did it!
>>> http://www.aumha.org/win5/a/xpvm.htm
>>>> is a well written page on the subject of virtual
memory.
>>>>
>>>> Things work well if I set the min/max Virtual Memory
size
>>>> of drive C: to 16MB or greater. 15MB and lower
causes
>>>> the problem I described.
>>>>
>>>> Steve
>>>>
>>>>> -----Original Message-----
>>>>> Virtual Memory in Windows XP
>>>>> http://www.aumha.org/win5/a/xpvm.htm
>>>>>
>>>>> (Courtesy of Alex Nichol, MS-MVP)
>>>>>
>>>>>
>>>>> --
>>>>> Nicholas
>>>>>
>>>>> ----------------------------------------------------
---- -
>>>>> ---------------
>>>>>
>>>>> "Steve" > wrote in message:
>>>>> ...
>>>>>
>>>>>> I need your help in resolving my Virtual Memory
problem.
>>>>>>
>>>>>> If your XP is setup with Virtual Memory on a
partition
>>>>>> other than C: I would like to hear from you. Let
me know
>>>>>> if your partition is on a separate physical drive.
>>>>>>
>>>>>> This will help me figure out if it is just my
system or
>>>>>> an XP issue that needs to be resolved.
>>>>>>
>>>>>> Thanks,
>>>>>> Steve
>>>>>>
>>>>>> Following is a revised description (posted on
15th) of
>>>>>> the problem I am experiencing and how I work
around it:
>>>>>>
>>>>>> TO REPRODUCE THE PROBLEM:
>>>>>> -------------------------
>>>>>> #1 I change VM on all drives to 0.
>>>>>>
>>>>>> #2 Boot the system and erase all pagefile.sys
>>>>>>
>>>>>> #3 Change VM on drive F: to either "custom"
>>> or "system
>>>>>> managed".
>>>>>>
>>>>>> #4 DIR F:\pagefile.sys to verify that it indeed
exists.
>>>>>>
>>>>>> #5 DIR C:\pagefile.sys to verify that it does not
exist.
>>>>>>
>>>>>> #6 Life is good! The only pagefile being used is
on
>>>>>> drive F: and when I exceed the physical RAM, the
VM gets
>>>>>> used.
>>>>>>
>>>>>> #7 Restart or Shutdown XP, then bring back up.
>>>>>>
>>>>>>
>>>>>> PROBLEM:
>>>>>> #8 A pagefile has been setup on the C: drive
and the
>>>>>> pagefile on F: is no longer being used.
>>>>>>
>>>>>> #9 Check the Virtual Memory settings: C: is still
set
>>>>>> to "No paging file" with blank MIN MAX fields and
F: is
>>>>>> still set to have paging file. In the MIN field
for F:
>>>>>> is 2048, but the "Currently Allocated" shown at
bottom is
>>>>>> 1151MB (all on C:)
>>>>>>
>>>>>> #10 Using Windows Explorer, try to erase the
pagefile on
>>>>>> C: and get "Cannot delete pagefile: It is being
used by
>>>>>> another person or program." indicating that XP is
using
>>>>>> it. Using Disk Defragmenter, Analyze C: and you
will see
>>>>>> that the pagefile shows up in RED indicating that
it is a
>>>>>> fragmented file. Pagefiles never show up red,
they are
>>>>>> always green indicating Unmovable file.
Interesting.
>>>>>>
>>>>>> #11 Using Windows Explorer, try to erase the
pagefile on
>>>>>> F: and it lets me indicating that it was not being
used.
>>>>>>
>>>>>>
>>>>>> WORKAROUND:
>>>>>> #12 Change all drives to "No Paging File" (the F:
drive),
>>>>>> then Restart XP.
>>>>>>
>>>>>> #13 This time XP does not try to put a pagefile on
any of
>>>>>> the drives.
>>>>>>
>>>>>> #13 Set the VM on F:
>>>>>>
>>>>>> #14 Erase the old pagefile on C:
>>>>>>
>>>>>> Life is good again!
>>>>>>
>>>>>>
>>>>>>
>>>>> .
>>>>>
>>>> .
>>>>
>>> ..
>>>
>>>
>>> .
>.
>

[JimW±]

Perhaps you are having a permission problem
You should NOT need to keep resetting the pagefile size
http://support.microsoft.com/default.aspx?scid=3Dkb;en-us;140472

Steve Bland > wrote:
> Your suggestion does not correlate with what I desire. I
> really know what I want to do. Help me accomplish this.
>=20
> I want as small as possible VM on C:
>=20
> I want a huge one on F:
>=20
> Are you using VM on a drive other than C:?
>=20
> Is it causing the problems I describe below?
>=20
> TIA,
> Steve
>=20
>=20
>> -----Original Message-----
>> Optimally - put a paging file on BOTH disks
>>=20
>> How to Configure Paging Files for Optimization and Recovery in
>> Windows XP http://support.microsoft.com/default.aspx?scid=3Dkb;EN-
>> US;314482=20
>>=20
>> The size of the one on the OS drive should be *at least* RAM + about
>> 12-20 MB=20
>>=20
>> It is also best if the MAX & MIN are the same - then the
> file will not become fragmented & Windows will not need
> to keep reconfiguring its size
>> Just make sure the MIN is plenty big enough - if you
> have a big HD, consider making MIN & MAX 2.5 x RAM on the
> non-OS drive (& then defrayment it)
>>=20
>> There are advantages to having the pagefile on the
> outside tracks - where more sectors are read in one spin.
> There are advantages to having the paging file in the
> middle of the drive - less than halfway away from any
> other activity on that drive. There are advantages to
> having a drive JUST for the paging file.
>> And, there are advantages to having the paging file on the fastest
>> disk=20
>>=20
>> If you dual boot, there are more things to consider --
> so you have the same size paging files on each drive in
> each OS
>>=20
>>=20
>> Andrew E. > wrote:
>>> Whatever,microsoft,knowledge,TechNet,etc,all say the same
>>> thing,keep the page file off the disk with the operating
>>> system.If you open system properties,advanced,change
>>> virtual memory,(page file)with two disks installed,click
>>> C:,choose custom,leave both windows blank,click set.Then
>>> add to the slave disk,back out,you should be prompted to
>>> restart computer,if not,no changes made.Wishing to do
>>> what now.To verify open DXDIAG for amounts.Why dont you
>>> have xp set to delete page file at shutdown?Its an easy
>>> set-up.
>>>> -----Original Message-----
>>>> We thought it was fixed, but spoke too soon!
>>>>=20
>>>> However, with the information I got from Nicholas ref to
>>>> http://www.aumha.org/win5/a/xpvm.htm
>>>> the problem is becoming more refined.
>>>>=20
>>>> With 16M VM on C:, on XP boot the VM on C: stays at 16M
>>>> instead of insisting on creating VM=3D1024M which is what
>>>> XP does if I specify no VM on C:. I wish I could tell it
>>>> NO PAGEFILE ON C:, because my C: drive is much slower
>>>> than all my other drives. Limiting it to 16M is the best
>>>> XP can do today.
>>>>=20
>>>> Anyhow, here is the new data getting us closer to the
>>>> root Virtual Memory configuration BUG:
>>>>=20
>>>> #1 When I run a bunch of memory hungry applications and
>>>> approach using up the RAM, XP says it wants to increase
>>>> my VM.
>>>>=20
>>>> #2 I check my setting which say 16M on C: and 512M on F:
>>>>=20
>>>> #3 But at the bottom of the VM settings the total VM
>>>> says only 16M.
>>>>=20
>>>> #4 So XP only created the 16M on C:!!!!
>>>>=20
>>>> #5 WORKAROUND: Every time I restart XP, I have to change
>>>> my VM settings for drive F: by increasing the MIN virtual
>>>> memory number to something greater than the one listed in
>>>> the box. So, if I change it from 512M to 640M, a
>>>> pagefile gets created on F: and the total at the bottom
>>>> of the configuration window reflects this.
>>>>=20
>>>> Again, I wonder if anyone else is using VM on drives
>>>> other than C: and if they are experiencing this BUG.
>>>>=20
>>>> Steve
>>>>=20
>>>>> -----Original Message-----
>>>>> Nicholas,
>>>>>=20
>>>>> Thanks! You did it! http://www.aumha.org/win5/a/xpvm.htm
>>>>> is a well written page on the subject of virtual memory.
>>>>>=20
>>>>> Things work well if I set the min/max Virtual Memory size
>>>>> of drive C: to 16MB or greater. 15MB and lower causes
>>>>> the problem I described.
>>>>>=20
>>>>> Steve
>>>>>=20
>>>>>> -----Original Message-----
>>>>>> Virtual Memory in Windows XP
>>>>>> http://www.aumha.org/win5/a/xpvm.htm
>>>>>>=20
>>>>>> (Courtesy of Alex Nichol, MS-MVP)
>>>>>>=20
>>>>>>=20
>>>>>> --
>>>>>> Nicholas
>>>>>>=20
>>>>>> ---------------------------------------------------- ---- -
>>>>>> ---------------
>>>>>>=20
>>>>>> "Steve" > wrote in message:
>>>>>> ...
>>>>>>=20
>>>>>>> I need your help in resolving my Virtual Memory problem.
>>>>>>>=20
>>>>>>> If your XP is setup with Virtual Memory on a partition
>>>>>>> other than C: I would like to hear from you. Let me know
>>>>>>> if your partition is on a separate physical drive.
>>>>>>>=20
>>>>>>> This will help me figure out if it is just my system or
>>>>>>> an XP issue that needs to be resolved.
>>>>>>>=20
>>>>>>> Thanks,
>>>>>>> Steve
>>>>>>>=20
>>>>>>> Following is a revised description (posted on 15th) of
>>>>>>> the problem I am experiencing and how I work around it:
>>>>>>>=20
>>>>>>> TO REPRODUCE THE PROBLEM:
>>>>>>> -------------------------
>>>>>>> #1 I change VM on all drives to 0.
>>>>>>>=20
>>>>>>> #2 Boot the system and erase all pagefile.sys
>>>>>>>=20
>>>>>>> #3 Change VM on drive F: to either "custom"
>>>> or "system
>>>>>>> managed".
>>>>>>>=20
>>>>>>> #4 DIR F:\pagefile.sys to verify that it indeed exists.
>>>>>>>=20
>>>>>>> #5 DIR C:\pagefile.sys to verify that it does not exist.
>>>>>>>=20
>>>>>>> #6 Life is good! The only pagefile being used is on
>>>>>>> drive F: and when I exceed the physical RAM, the VM gets
>>>>>>> used.
>>>>>>>=20
>>>>>>> #7 Restart or Shutdown XP, then bring back up.
>>>>>>>=20
>>>>>>>=20
>>>>>>> PROBLEM:
>>>>>>> #8 A pagefile has been setup on the C: drive
> and the
>>>>>>> pagefile on F: is no longer being used.
>>>>>>>=20
>>>>>>> #9 Check the Virtual Memory settings: C: is still set
>>>>>>> to "No paging file" with blank MIN MAX fields and F: is
>>>>>>> still set to have paging file. In the MIN field for F:
>>>>>>> is 2048, but the "Currently Allocated" shown at bottom is
>>>>>>> 1151MB (all on C:)
>>>>>>>=20
>>>>>>> #10 Using Windows Explorer, try to erase the pagefile on
>>>>>>> C: and get "Cannot delete pagefile: It is being used by
>>>>>>> another person or program." indicating that XP is using
>>>>>>> it. Using Disk Defragmenter, Analyze C: and you will see
>>>>>>> that the pagefile shows up in RED indicating that it is a
>>>>>>> fragmented file. Pagefiles never show up red, they are
>>>>>>> always green indicating Unmovable file. Interesting.
>>>>>>>=20
>>>>>>> #11 Using Windows Explorer, try to erase the pagefile on
>>>>>>> F: and it lets me indicating that it was not being used.
>>>>>>>=20
>>>>>>>=20
>>>>>>> WORKAROUND:
>>>>>>> #12 Change all drives to "No Paging File" (the F: drive),
>>>>>>> then Restart XP.
>>>>>>>=20
>>>>>>> #13 This time XP does not try to put a pagefile on any of
>>>>>>> the drives.
>>>>>>>=20
>>>>>>> #13 Set the VM on F:
>>>>>>>=20
>>>>>>> #14 Erase the old pagefile on C:
>>>>>>>=20
>>>>>>> Life is good again!
>>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>> .
>>>>>>=20
>>>>> .
>>>>>=20
>>>> ..
>>>>=20
>>>>=20
>>>> .
>> .

[JimW±]

http://www.jsiinc.com/subf/tip2700/rh2733.htm


JimW=B1 > wrote:
> Perhaps you are having a permission problem
> You should NOT need to keep resetting the pagefile size
> http://support.microsoft.com/default.aspx?scid=3Dkb;en-us;140472
>=20
> Steve Bland > wrote:
>> Your suggestion does not correlate with what I desire. I
>> really know what I want to do. Help me accomplish this.
>>=20
>> I want as small as possible VM on C:
>>=20
>> I want a huge one on F:
>>=20
>> Are you using VM on a drive other than C:?
>>=20
>> Is it causing the problems I describe below?
>>=20
>> TIA,
>> Steve
>>=20
>>=20
>>> -----Original Message-----
>>> Optimally - put a paging file on BOTH disks
>>>=20
>>> How to Configure Paging Files for Optimization and Recovery in
>>> Windows XP http://support.microsoft.com/default.aspx?scid=3Dkb;EN-
>>> US;314482
>>>=20
>>> The size of the one on the OS drive should be *at least* RAM + about
>>> 12-20 MB
>>>=20
>>> It is also best if the MAX & MIN are the same - then the
>> file will not become fragmented & Windows will not need
>> to keep reconfiguring its size
>>> Just make sure the MIN is plenty big enough - if you
>> have a big HD, consider making MIN & MAX 2.5 x RAM on the
>> non-OS drive (& then defrayment it)
>>>=20
>>> There are advantages to having the pagefile on the
>> outside tracks - where more sectors are read in one spin.
>> There are advantages to having the paging file in the
>> middle of the drive - less than halfway away from any
>> other activity on that drive. There are advantages to
>> having a drive JUST for the paging file.
>>> And, there are advantages to having the paging file on the fastest
>>> disk
>>>=20
>>> If you dual boot, there are more things to consider --
>> so you have the same size paging files on each drive in
>> each OS
>>>=20
>>>=20
>>> Andrew E. > wrote:
>>>> Whatever,microsoft,knowledge,TechNet,etc,all say the same
>>>> thing,keep the page file off the disk with the operating
>>>> system.If you open system properties,advanced,change
>>>> virtual memory,(page file)with two disks installed,click
>>>> C:,choose custom,leave both windows blank,click set.Then
>>>> add to the slave disk,back out,you should be prompted to
>>>> restart computer,if not,no changes made.Wishing to do
>>>> what now.To verify open DXDIAG for amounts.Why dont you
>>>> have xp set to delete page file at shutdown?Its an easy
>>>> set-up.
>>>>> -----Original Message-----
>>>>> We thought it was fixed, but spoke too soon!
>>>>>=20
>>>>> However, with the information I got from Nicholas ref to
>>>>> http://www.aumha.org/win5/a/xpvm.htm
>>>>> the problem is becoming more refined.
>>>>>=20
>>>>> With 16M VM on C:, on XP boot the VM on C: stays at 16M
>>>>> instead of insisting on creating VM=3D1024M which is what
>>>>> XP does if I specify no VM on C:. I wish I could tell it
>>>>> NO PAGEFILE ON C:, because my C: drive is much slower
>>>>> than all my other drives. Limiting it to 16M is the best
>>>>> XP can do today.
>>>>>=20
>>>>> Anyhow, here is the new data getting us closer to the
>>>>> root Virtual Memory configuration BUG:
>>>>>=20
>>>>> #1 When I run a bunch of memory hungry applications and
>>>>> approach using up the RAM, XP says it wants to increase
>>>>> my VM.
>>>>>=20
>>>>> #2 I check my setting which say 16M on C: and 512M on F:
>>>>>=20
>>>>> #3 But at the bottom of the VM settings the total VM
>>>>> says only 16M.
>>>>>=20
>>>>> #4 So XP only created the 16M on C:!!!!
>>>>>=20
>>>>> #5 WORKAROUND: Every time I restart XP, I have to change
>>>>> my VM settings for drive F: by increasing the MIN virtual
>>>>> memory number to something greater than the one listed in
>>>>> the box. So, if I change it from 512M to 640M, a
>>>>> pagefile gets created on F: and the total at the bottom
>>>>> of the configuration window reflects this.
>>>>>=20
>>>>> Again, I wonder if anyone else is using VM on drives
>>>>> other than C: and if they are experiencing this BUG.
>>>>>=20
>>>>> Steve
>>>>>=20
>>>>>> -----Original Message-----
>>>>>> Nicholas,
>>>>>>=20
>>>>>> Thanks! You did it! http://www.aumha.org/win5/a/xpvm.htm
>>>>>> is a well written page on the subject of virtual memory.
>>>>>>=20
>>>>>> Things work well if I set the min/max Virtual Memory size
>>>>>> of drive C: to 16MB or greater. 15MB and lower causes
>>>>>> the problem I described.
>>>>>>=20
>>>>>> Steve
>>>>>>=20
>>>>>>> -----Original Message-----
>>>>>>> Virtual Memory in Windows XP
>>>>>>> http://www.aumha.org/win5/a/xpvm.htm
>>>>>>>=20
>>>>>>> (Courtesy of Alex Nichol, MS-MVP)
>>>>>>>=20
>>>>>>>=20
>>>>>>> --
>>>>>>> Nicholas
>>>>>>>=20
>>>>>>> ---------------------------------------------------- ---- -
>>>>>>> ---------------
>>>>>>>=20
>>>>>>> "Steve" > wrote in message:
>>>>>>> ...
>>>>>>>=20
>>>>>>>> I need your help in resolving my Virtual Memory problem.
>>>>>>>>=20
>>>>>>>> If your XP is setup with Virtual Memory on a partition
>>>>>>>> other than C: I would like to hear from you. Let me know
>>>>>>>> if your partition is on a separate physical drive.
>>>>>>>>=20
>>>>>>>> This will help me figure out if it is just my system or
>>>>>>>> an XP issue that needs to be resolved.
>>>>>>>>=20
>>>>>>>> Thanks,
>>>>>>>> Steve
>>>>>>>>=20
>>>>>>>> Following is a revised description (posted on 15th) of
>>>>>>>> the problem I am experiencing and how I work around it:
>>>>>>>>=20
>>>>>>>> TO REPRODUCE THE PROBLEM:
>>>>>>>> -------------------------
>>>>>>>> #1 I change VM on all drives to 0.
>>>>>>>>=20
>>>>>>>> #2 Boot the system and erase all pagefile.sys
>>>>>>>>=20
>>>>>>>> #3 Change VM on drive F: to either "custom"
>>>>> or "system
>>>>>>>> managed".
>>>>>>>>=20
>>>>>>>> #4 DIR F:\pagefile.sys to verify that it indeed exists.
>>>>>>>>=20
>>>>>>>> #5 DIR C:\pagefile.sys to verify that it does not exist.
>>>>>>>>=20
>>>>>>>> #6 Life is good! The only pagefile being used is on
>>>>>>>> drive F: and when I exceed the physical RAM, the VM gets
>>>>>>>> used.
>>>>>>>>=20
>>>>>>>> #7 Restart or Shutdown XP, then bring back up.
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>> PROBLEM:
>>>>>>>> #8 A pagefile has been setup on the C: drive
>> and the
>>>>>>>> pagefile on F: is no longer being used.
>>>>>>>>=20
>>>>>>>> #9 Check the Virtual Memory settings: C: is still set
>>>>>>>> to "No paging file" with blank MIN MAX fields and F: is
>>>>>>>> still set to have paging file. In the MIN field for F:
>>>>>>>> is 2048, but the "Currently Allocated" shown at bottom is
>>>>>>>> 1151MB (all on C:)
>>>>>>>>=20
>>>>>>>> #10 Using Windows Explorer, try to erase the pagefile on
>>>>>>>> C: and get "Cannot delete pagefile: It is being used by
>>>>>>>> another person or program." indicating that XP is using
>>>>>>>> it. Using Disk Defragmenter, Analyze C: and you will see
>>>>>>>> that the pagefile shows up in RED indicating that it is a
>>>>>>>> fragmented file. Pagefiles never show up red, they are
>>>>>>>> always green indicating Unmovable file. Interesting.
>>>>>>>>=20
>>>>>>>> #11 Using Windows Explorer, try to erase the pagefile on
>>>>>>>> F: and it lets me indicating that it was not being used.
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>> WORKAROUND:
>>>>>>>> #12 Change all drives to "No Paging File" (the F: drive),
>>>>>>>> then Restart XP.
>>>>>>>>=20
>>>>>>>> #13 This time XP does not try to put a pagefile on any of
>>>>>>>> the drives.
>>>>>>>>=20
>>>>>>>> #13 Set the VM on F:
>>>>>>>>=20
>>>>>>>> #14 Erase the old pagefile on C:
>>>>>>>>=20
>>>>>>>> Life is good again!
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>>=20
>>>>>>> .
>>>>>>>=20
>>>>>> .
>>>>>>=20
>>>>> ..
>>>>>=20
>>>>>=20
>>>>> .
>>> .