So I know what page file is and how it works however, how come when I set a low page file, say 50MB it still says 400MB is being used in Task Manager PF usage?
When I set it to no page file it also shows PF usage.
When I run a game, PF usage goes up even though I want it all running from RAM since I have enough.

Some may reply telling me that I should use a page file because its best practice or w/e, however please stick to the question at hand as I'm more curious why it isn't working the way I thought it would than what is best.

Set the page file to system managed. Unless you have a thorough understanding of how the page files works, and very few people do, you are just going to tie yourself in knots.

Windows XP needs some virtual memory to run efficiently regardless of how much RAM you have.

http://support.microsoft.com/kb/555223

Stuart

Are you sure that your settings are sticking? I've had problems changing the virtual memory settings. I later go back to check and they aren't the way I set them.

One thing for sure, you do have to use the 'Set' button, but that doesn't seem to guarantee that the settings will stick.

The settings should stick, since they are written into the registry.

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Session Manager\Memory Management

Nigel

This is just a sig

Report Offensive Follow Up For Removal

The settings stuck because I checked and it said 0MB virtual memory and 50MB when I set it to that.

In response to #1- Like I said I dont care about best practices I'm trying to understand how it works. As you said, not many people know how it works, I want to know. It's understandable that an OS needs virutal memory to work efficiently, I'm wondering why apps (such as a game) use virtual memory even when I turn it off. (reread first post)

Thank you for the link though, I'll read it and see if I can understand how it works a bit better.

Edit: Found the answer to my question- PF usage is misleading and is the commit charge and not actually how much page file usage. After viewing the %usage for paging file in the Performance Snap-in, I saw that it was not being used.