Steve
December 11th 03, 09:30 PM
Another clue . . . maybe . . .
When I bring up defrag for C: where the unwanted pagefile
exists, I can see the pagefile is a fragmented chunck
denoted by red. I know this is the pagefile because that
chunck disappears when I delete the pagefile.
In contrast, when I get VM on drive F: then use defrag to
analyze the F: drive, the pagefile shows up green
indicating unmoveable.
This may or may not be related, but I thought it would be
worth mentioning.
Steve
>-----Original Message-----
>First, I can't believe it. Microsoft gives me two free
>service calls which I use finding real software short
>falls. Now I have found another, but can't speak
>directly to them! They should be paying us to
>find/report these errors! Not Cool!
>
>I have been waiting for a fix to roll out, but have not
>seen one yet.
>I have not seen this problem described in the knowledge
>base.
>
>
>Problem Description:
>#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:
>
>#7 Perform a system shutdown and power 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" and F: is still set to have paging
>file.
>
>#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.
>
>#11 Using Windows Explorer, try to erase the pagefile on
>F: and it lets me.
>
>WORKAROUND:
>#12 Change all drives to "No Paging File" (the F: drive)
>Restart the system.
>
>#13 Set the VM on F:
>
>#14 Erase the pagefile on C:
>
>Life is good again!
>
>I hate doing this every time I get a power glitch.
>What is broke here?
>
>Steve
>.
>
When I bring up defrag for C: where the unwanted pagefile
exists, I can see the pagefile is a fragmented chunck
denoted by red. I know this is the pagefile because that
chunck disappears when I delete the pagefile.
In contrast, when I get VM on drive F: then use defrag to
analyze the F: drive, the pagefile shows up green
indicating unmoveable.
This may or may not be related, but I thought it would be
worth mentioning.
Steve
>-----Original Message-----
>First, I can't believe it. Microsoft gives me two free
>service calls which I use finding real software short
>falls. Now I have found another, but can't speak
>directly to them! They should be paying us to
>find/report these errors! Not Cool!
>
>I have been waiting for a fix to roll out, but have not
>seen one yet.
>I have not seen this problem described in the knowledge
>base.
>
>
>Problem Description:
>#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:
>
>#7 Perform a system shutdown and power 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" and F: is still set to have paging
>file.
>
>#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.
>
>#11 Using Windows Explorer, try to erase the pagefile on
>F: and it lets me.
>
>WORKAROUND:
>#12 Change all drives to "No Paging File" (the F: drive)
>Restart the system.
>
>#13 Set the VM on F:
>
>#14 Erase the pagefile on C:
>
>Life is good again!
>
>I hate doing this every time I get a power glitch.
>What is broke here?
>
>Steve
>.
>