In John John - MVP typed on Thu, 06 Aug 2009 09:07:46 -0300:
Windows 2000 does not run without a pagefile, if you try to disable
the pagefile the system will give you a nag screen and create a 20MB
temporary pagefile (temppf.sys) in the System32 folder, the file will
be deleted the next time the system boots.
That could be John, I wouldn't know. All I know is creating a 20MB
pagefile and throwing into a RAMDisk seems to keep Windows 2000 happy
enough with only one nag screen at boot. Even increasing the swapfile
over 200MB doesn't change this.
You can move the pagefile to any other disk or drive but you will have
to carefully consider the move, moving the pagefile to another
partition on the same disk as Windows or on a disk that is in a slave
relationship to the Windows disk may result in a performance hit and
is usually not a good idea.
Well the believers in defragging help improves performance (I never seen
any noticeable improvements myself since IDE drives came along which
replaced MFM drives) believe keeping the pagefile off on another
partition help keeps fragmentation in better check. Thus improves
performance.
So theoretically keeping the pagefile on another partition or another
drive that shares the same data path (i.e. master and slave), and/or
plus having the head having to move far to another partition should
decrease performance.
Although Microsoft and the hardware manufactures knows about these
bottlenecks and has taken steps to prevent these problems. Thus we have
write delays and caches to solve these problems. So in the real world
with modern hardware and enough RAM, I am not sure you would ever see a
problem.
What kind of applications are you running? Quite possibly the RAM
isn't being used because there is no need for it.
That is almost always a very bad idea! This is an idea that is often
advanced by well meaning individuals who unfortunately don't usually
understand the Windows NT memory management mechanism so they view the
pagefile as an evil presence. Few of them understand how the private
2GB flat address space that each process has available is mapped, they
fail to realize that without a pagefile the processes address space
can actually cause a very large amount of RAM to go completely unused
and wasted.
John
I disagree! Running Windows XP with only 512MB or less and Windows with
256MB or less RAM without a pagefile is almost always a bad idea. And I
have experimented a lot without or with a very small pagefile on both XP
and 2000. There are three big reasons why I'm interested in running
without one.
1) I have a lot of SSD drives and the smallest is only 4GB in size. And
a swapfile eats up a lot of this space. And Asus sets the pagefile at
200MB to tame it down on a stock 4G SSD XP machine.
2) Writing a lot to a SSD decreases the longevity of the drive. So all
unnecessary writing is a bad idea. And a swapfile is one of the biggest
offenders.
3) I also sometimes use Microsoft's EWF. Which buffers all writes to an
OS drive and writes nothing to the actual drive. So write count drops to
zero! The OS doesn't care because it thinks it is all being written to
the drive (so does everything else). This is a neat idea since it is
like having a read-only Windows drive and no virus or malware can live
once the power is turned off.
The write buffer can only hold 512MB worth (I don't know if this can be
changed). Once it gets full, Windows becomes unstable and locks up.
Using it with a swapfile fills this space up very quickly and I am lucky
if I can run 20 minutes or more. Turning off the swapfile I can often
run 20 hours or more and I still haven't used up half of the 512MB.
Now back to what you were saying John. Well the real test is actually
doing it and not just talking about it. And I monitor the memory use and
I find Windows 2000/XP runs well until the free memory drops to under
200MB with a tiny or no swapfile. And I can tell you for me at least
with 2GB of RAM (even with XP), it is virtually impossible for the free
memory to drop this low.