If you are that concerned about swap file usage you can remove it altogether. I think Windows even then still manages to do some disk swap work, somehow, but that is something I would have to check with a monitor. Windows allots RAM according to program design/inbuilt memory demands, the commit charge, but then actively manages memory for the immediate demand. Doing things that way, it has to keep a fair chunk up its sleeve for unexpected memory demands. Some interrupts cannot be ignored/postponed. With only TM running mine keeps about 50MB in reserve [apart from Available mem], but that jumps to 100MB as soon as I open an app. I also use a separate disk for the swap file. It is on timed shutdown if no activity... I hear it wind up again occasionally, but if I have high mem demand stuff running it stays full on. Windows will run happily on 1/2GB, but some apps may cause it to give you a Running low on Virtual Memory warning. [Btw, you will often see on the web that VM is the swap file. No it aint. With memory management VM is considered to be ALL memory - it is called virtual because running processes are not actually getting the memory they asked for. Roughly speaking].