P
Paul Mars
4/24/06
unreal. Well I now have a pagefile.
Everytime I set it to custom or sys managed, a pagefile.sys file would be
created in the root and it would work fine, until a re-boot. Then it would
be gone and "no pagefile" was set.
Someone suggested putting the pagefile on another partition, so I did. Again
it was created and used. Again after a re-boot "no pagefile" was set, but
the file remained on the partition. At this point, I made the pagefile again
on the root, and it stayed after a re-boot. After the re-boot, it is still
set to the root in system properties~virtual memory and when I look at the
other partition, it says "no pagefile", BUT the file on the other partition
is being accessed, and the one on the root is not.
I am totally lost.
4/29/06
Now I see that the I drive pagefile was last accessed on 4/29(right now),
last modified on 4/22, and created on 4/22. The pagefile on root was created
4/22, last modified and last accessed on 4/27.
Paul
unreal. Well I now have a pagefile.
Everytime I set it to custom or sys managed, a pagefile.sys file would be
created in the root and it would work fine, until a re-boot. Then it would
be gone and "no pagefile" was set.
Someone suggested putting the pagefile on another partition, so I did. Again
it was created and used. Again after a re-boot "no pagefile" was set, but
the file remained on the partition. At this point, I made the pagefile again
on the root, and it stayed after a re-boot. After the re-boot, it is still
set to the root in system properties~virtual memory and when I look at the
other partition, it says "no pagefile", BUT the file on the other partition
is being accessed, and the one on the root is not.
I am totally lost.
4/29/06
Now I see that the I drive pagefile was last accessed on 4/29(right now),
last modified on 4/22, and created on 4/22. The pagefile on root was created
4/22, last modified and last accessed on 4/27.
Paul