Well I'm not trying to start an argument in here, but in my experiences this has been the best optimization procedure for the pagefile. My MCSE teacher at Heald College also suggested this same procedure, and there are many links all over the net with the same info, here's one for starters.
I guess everyone else is wrong too
If everyone is stating and restating a fallacy, then yes...everyone is wrong.
FWIW, I can find lots of links that suggest that rule of thumb is bunk.
If you want to set an initial, fine...though this number is almost always set too high based on the old 1.5 to 2.5 times ram that made sense when computer had 8mb of ram. In todays 512mb or 1gb ram computers such rules are silly
The point I was trying to get across was that NO MAX should be set
If I read your post correctly, and perhaps I did not, it seems like you are advocating a static sized page file, which contradicts your link. If your MCSE instructor advocates a static page file then he needs to rethink that.
Anyway, since this problem we are working on has yielded "out of memory messages"
I suspected a page file ceiling. As it turns out, there was a ceiling of 360mb (who set that?). I want to eliminate that ceiling as an issue
Whether liloltiredblood wishes to do that later is irrelevent....for now, we want a max size page file.
Here is the current rule of thumb for page files....LET WINDOWS HANDLE IT unless you have a good reason not to.