Using these so called memory managers actually defeat Windows XP processes which use unused RAM at any given point in time for necessary Windows operating system maintenance processes when it is not being used by legitimate open aps.
If you have aps (usually poorly written freebie code, the same type of code that isn't compliant to Microsoft's established criteria and therefore is for the most part responsible for opening exploits) that leak or retain memory when closed - get rid of them!
From Fred Langa:
"Fred, [name of utility] saves my butt---I get my resources down to 5% and then it kicks in and restores them to 50%..."
Invariably, when I check it out, I discover the reader is talking about his or her pool of system RAM, and not what's usually meant by "System Resources." As is explained in Part One (mentioned above) System Resources in Windows usually means two very specific memory areas: User Resources and GDI (Graphics Device Interface ) Resources. When these memory areas are exhausted, you can get crashes or other weirdness.
General RAM is a whole 'nother thing. Sometimes, some people think that idle, unused RAM is the same thing as available System Resources. It's not; they're very different things. What's more, they're conceptually opposite in use: You want your System Resources to be used as LITTLE as possible, but you want your RAM to be used as MUCH as possible! (I'll explain this in more detail later.)
Thus, some people who use tools to "open up a hole in RAM" are often getting the opposite effect of what they want: They think they're freeing System Resources, but all they're doing is bogging their systems down! Their confusion is understandable because of the way the, um, less polished memory tools toss around the term "System Resources:" The tools *may* be useful for recovering leaked general memory (which usually is a minor problem at worst), but they make it sound like they attack the much more serious problem of User and GDI leaks. Again: They do not.
In fact, the better memory-management tools explicitly state that they do nothing---nada, zip, zero, zilch--- about User and GDI Resources or any memory leaks therein. These apps *may* (and that's a huge qualifier) help with a completely different and less significant kind of memory leak, but that's a separate issue from the very serious issue of User and GDI System Resource leaks.http://www.langa.com/newsletters/2000/2000-06-01.htm
By the way, there is a utility for startup menu management that I use which is easier to use than most others because it tells you intelligeably what you are removing from the startup menu - what programs the dlls are connected with - and doesn't default to safe mode like msconfig does.
It is called Startup Inspector - http://www.windowsstartup.com/
Its companion ap - Startup Monitor will alert you whenever anything tries to add itself to your startup menu and require your approval.
Also on the page is a Startup Programs Knowledge Base in which you can type an ap in question to find out what it is and what it is connected to.
Edited by Enthusiast, 19 March 2006 - 12:47 PM.