I've tried this program in win95 and 98 and it works well but IMHO don't think it's really necessary in xp which has fairly good memory management already.
Personal experience, XP has a great RAM manager already built in. When my RAM usuage reaches 80% (used) XP will do a little cleaning and it will go down to ~25% (used). I stay away from such applications for the same reasons dealer mentioned. When XP does it on its own, there is NO slow down, and no hang up.
I agree with everyone, but I must say the _one_ time an application like this can be useful is if you have a computer setup with low RAM (256MB or less) and are trying to play a graphically intensive game like Morrowind at high resolution (starting from 1024 res and above).
I know thats alot of ifs and not many games are as demanding in quite the same way as Morrowind (the game system loads areas into memory and keeps old areas in memory until a certain cache point) but left to its own devices XP can suck itself into a Memory Quagmire and condemn the computer to 10 mins of disk thrashing after the texture memory gets full
A memory program with a "Release memory after it gets X% full" property can help in this situation and stops a Memory Quagmire from occuring
Originally posted by Dublex I agree with everyone, but I must say the _one_ time an application like this can be useful is if you have a computer setup with low RAM (256MB or less) and are trying to play a graphically intensive game like Morrowind at high resolution (starting from 1024 res and above).
I know thats alot of ifs and not many games are as demanding in quite the same way as Morrowind (the game system loads areas into memory and keeps old areas in memory until a certain cache point) but left to its own devices XP can suck itself into a Memory Quagmire and condemn the computer to 10 mins of disk thrashing after the texture memory gets full
A memory program with a "Release memory after it gets X% full" property can help in this situation and stops a Memory Quagmire from occuring