Originally posted by: Nothinman
Anything running purely in userland can not affect the allocation of physical memory beyond asking to be allocated a chunk of memory for itself. And all that most of the memory "optimizers" do is just request a huge chunk of memory so that the OS has to free memory for it, this causes whatever's currently in memory to be flushed to disk. Then the "optimizer" frees the memory and makes you think it just gained you a ton of free memory when all it ended up doing was clearing out any caching the OS was doing thus making it page all of that data back in as you start running other things again.
As stupid as MS' marketing department may make them look, they really do employ some of the smartest programmers in the world and I would wager that all of them understand memory management better than anyone writing 10K "optimizer" program in VB.
Well spoken.
Back in the days of 95,98 and ME, windows was pretty bad about allowing stuff to clog up your system over time. Running a memory cleaner was actually a decent way to help your system.
BUT NOT EVERY HOUR, like many of them defaulted to.
Only every couple of days, when your background was really clogged up.
And lets be honest, if its only once a week or so, wouldnt it be better to simply restart?