gonaads, i'm very surprised at your post...there is no user that can safely lower the pagefile to that small setting, what will happen with a setting that small, is the os will find areas that you did not allocate, and it will page there, creating more hardrive activity, and creating a more fragmented envirnment, not a less fragmented enfinment.
sometimes, we will suffer performance hits that we don't even realize, and with a pagefile this small, the os is definately slower, though some people might not notice, the slow down is there regardless.
you cannot stop xp from expanding the pagefile, even though you try... by setting a static max and min, as soon as the commit charge reaches the commit limit, which is the only time the pagefile even wants to expand, and of course, is the very time YOU NEED the pagefile to be bigger, (AND which by the way, and oviously, THE COMMIT CHARGE REACHES THE COMMIT LIMIT SOONER WITH A SMALL PAGEFILE THEN WITH A BIG PAGEFILE), the os will therefore find other areas on the hardfrive, and page to those other areas, it will do it more, and it will do it sooner, and it will do it less efficiently, then if you allow the os and the pagefile to do the job it was well designed to do
you can easily prove this to yourself, by lowering your pagefile to the setting you suggest, and take a look at permon...you will see more pagefile activity, not less with this setting.
all of this is allready documented by microsoft, way back when nt was first released...here's the paragraph, and referance;
"...A pagefile that's set too small can lead to overactive disk swapping, or "disk thrashing." The only real drawback with a relatively large swapfile is that you might not have as much disk space available for other uses as you would if you'd followed the pagefile setup recommendations."...
for your referance, document number; Q102020:
i'm amazed there are people tha tstill believe there can possibly be a benefit to a small pagefile
now, since that document, microsoft has severely increased the minimum recomendation, but the facts of that document remain, there is no slowdown whatsoever with a big pagefile, and quite a performance hit if the pagefile is too small
and now, about cahcheman...no, cahcheman will make this problem worse, it will release ram that is in use, and if it's not in use, then it's allready released by xp.
cacheman is for millenium and 9x......hardly fotr nt...that's exactly what the pagefile is for in the first place