Virtual Memory

Besides defragmenting the paging file and increasing the size , how else can I fix my virtual memory to run game software faster?

 

"Virtual memory" and "fast" is a paradox.

There are a few ways to supposedly optimize your page file. First, don't make it too big. That just gives Windows more things to keep track of. The general rule is no bigger than 500 MB should be necessary (or 1.5 times your RAM, whichever is lesser). Fixing the size is, as you've gathered, already a good idea, since Windows doesn't have to manage it anymore.

Second, you can do some partitioning tricks. Optimally, you want to place your swap file on a HDD on a different channel than the system. That is, if your OS is on a HDD on IDE 1, you want your page file on IDE 2. Since we don't want anything to bother the swap file, create a partition just for the swap file. I usually make it 1 GB, since you can't change this later without some difficulty. You want this partition to be the first one on the drive, since the first partitions are on the outer tracks and have the highest read/write transfer rates. In Windows XP/2k, you should format the drive with NTFS and use the largest cluster size possible (since there's only one file on it, there's no need to waste all that addressing). I usually call it drive P: so that it never interferes with my other drives -- that is, it's always on the bottom so I never accidentally click on it.

 

in addition to Chickens post
http://www.majorgeeks.com/vb/showpost.php?p=175783&postcount=2

or if you want to get REALLY REALLY GEEKY
http://www.cenatek.com/product_rocketdrive.cfm

 

ROFL

I've always wanted to set up a 4 GB system and make a 1 GB RAM drive just for the page file. Although I don't think you can actually ever do that.

 

why not?