OvenMaster
VIP Member
I searched for info on this and came up dry, so I thought I'd ask.
When I had a PC with Win95, I would launch Windows, and then apps, and only after my RAM was full did Windows start allocating data to the swapfile. Apps that stayed in RAM worked really fast and reliably.
I've noticed with XP that even with only Windows and startup programs launched, there's hundreds of megs of stuff already in my swapfile, and lots of empty RAM. Opening up lots of apps never seems to fill up my RAM like I thought it "should".
So. My question is, is there any way to force XP to fill up RAM first before adding anything to the swapfile? It's fixed at 2GB on my slave drive.
Tom
When I had a PC with Win95, I would launch Windows, and then apps, and only after my RAM was full did Windows start allocating data to the swapfile. Apps that stayed in RAM worked really fast and reliably.
I've noticed with XP that even with only Windows and startup programs launched, there's hundreds of megs of stuff already in my swapfile, and lots of empty RAM. Opening up lots of apps never seems to fill up my RAM like I thought it "should".
So. My question is, is there any way to force XP to fill up RAM first before adding anything to the swapfile? It's fixed at 2GB on my slave drive.
Tom
Last edited: