So last year, even though I never seem to run into any malware, I renew my subscription to AVG Anti-Spware because of its memory scan returning "leaked" RAM. I didn't realize my MemInfo could do the same thing. I always have over one half of my 1gig but I'm a RAMaholic. So I discover RAM Def XT which does the same thing in about 40 seconds (it's definitely a keeper!). But this little gem you'll really love! Now every 30 seconds sounds a little much but you never even notice it or you can just adjust it yourself in scheduling. I made it every two hours.
Anyone else tried this?
This program runs behind the scenes in Task Manager. How are you able to tweak it?
OMG command run.
Well, that was fun. Bye bye free program.
This program runs behind the scenes in Task Manager. How are you able to tweak it?
Thanks for the link, Slowday. I've only had this running for a short time, but it seems like a great little program -- quite different from any other memory manager I've ever tried.
Actually, Corona, there's not a lot of tweaking to do -- and this is not a memory resident program running all the time in the background. Actually, it's only called for about every 30 minutes (default) by the Windows Task Scheduler -- runs for just a few seconds -- then goes away. If you want to change the frequency it runs, you can do so in Windows Task Scheduler (Advanced).
By the way, I would suggest that anybody interested in trying this program should read the info on the website -- it was written by the app creator. He gives some insight as to how it works.
Now every 30 seconds sounds a little much but you never even notice it or you can just adjust it yourself in scheduling. I made it every two hours.
If I'm not mistaken, I think the default setting is 30 minutes -- not 30 seconds.
If I'm not mistaken, I think the default setting is 30 minutes -- not 30 seconds.
Typo, I did mean minutes. I just installed this on my Vista notebook and it seems to really make a nice difference on it. I left it at 30 minutes and have the XP at every hour now.
Its not a bad little utility but it does make Windows Defender pop up an event when it runs.
I don't use Windows Defender, so I have experienced that problem.
I've only been using it since yesterday when Slowday posted it, but so far, it seems like a slick little memory utility -- very different from other memory managers. It's totally transparent and doesn't use any resources -- just shows up periodically and very quickly does its thing -- then disappears again. Nothing to set -- nothing to fiddle with. Seems like an especially GREAT solution for anyone experiencing memory leak problems.
Windows Defender comes standard with Vista but has to be downloaded and installed for XP and I like it.don't use Windows Defender, so I have experienced that problem.
At my advancing age I can use all the help I can get.Seems like an especially GREAT solution for anyone experiencing memory leak problems.
Its not a bad little utility but it does make Windows Defender pop up an event when it runs.
Strange! I have WD enabled on both the XP and Vista machines and that hasn't occurred.
Okay, will somebody please point me in the direction of the nearest Windows task scheduler. I keep ending up in Windows/System32. I don't see it and no way am I gonna touch anything in there.
Okay, will somebody please point me in the direction of the nearest Windows task scheduler. I keep ending up in Windows/System32. I don't see it and no way am I gonna touch anything in there.
Here goes:
Start / Control Panel / (switch to 'classic view' on the left) / Scheduled Tasks
Okay! Thank you! I knew I've been around there before.
"RAM Optimizers have no effect, and at worst, they seriously degrade performance. Although gaining more available memory might seem beneficial, it isn't. As RAM Optimizers force the available-memory counter up, they force other processes' data and code out of memory. Say that you're running Word, for example. As the optimizer forces the available-memory counter up, the text of open documents and the program code that was part of Word's working set before the optimization (and was therefore present in physical memory) must be reread from disk as you continue to edit your document. The act of allocating, then freeing a large amount of virtual memory might, as a conceivable side effect, lead to blocks of contiguous available memory. However, because virtual memory masks the layout of physical memory from processes, processes can't directly benefit from having virtual memory backed by contiguous physical memory. As processes execute and undergo working-set trimming and growth, their virtual-memory-to-physical-memory mappings will become fragmented despite the availability of contiguous memory."
Mark Russinovich is definitely the best and most reliable source for Windows Internals.
Mark Russinovich is definitely the best and most reliable source for Windows Internals.
Please don't copy from other sources it just junks up the forum.
Please provide your comment and link.
This subject has to be "searched" on the forum first.Then read.
davey
I saw no need to paraphrase, as the information is perfectly accurate and not the first time I've shared that snippit.
I have however updated my wiki Myths page to reflect what Mark says (links only).
I saw no need to paraphrase, as the information is perfectly accurate and not the first time I've shared that snippit.
I have however updated my wiki Myths page to reflect what Mark says (links only).
We enjoy your site also.
davey
CleanMem is gone from my XP Pro system!
I did not notice any system performance improvement as it appeared to slow down in fact.
But cleanmem isnt the same as other memory cleaners. Other memory cleaners are fake as they simply use up all ram there is forcing windows to release ram and move it to the page file.
Cleanmem simply runs 1 api call and lets windows handle the rest.
http://msdn.microsoft.com/en-us/library/ms682606(VS.85).aspx
which if you used cleanmem and watched your page file and virtual memory settings neither grow at all, and in fact the page file drops by a few mb.
The memory that is unused windows simply cleans up, the process can then take it back when it is needed. This is why you actually see a increase in free memory.
Nothing huge but when you have a exe with a memory leak a tool that can tell windows to go clean it up is the trick.
I have been a programmer for many years and know windows memory very well. I also know how much of a pain it is, this program doesnt clean the memory it asks windows to. Since windows is in charge of keeping things clean it makes sence to have windows do the work.
But please before you bash and shoot down a program that you havent even tested and verified please do your homework on why people are even talking about this app in the first place.
http://www.pcwintech.com/tools/CleanMem.html
you can see your not the only one who thought this was a bogus program like majorgeeks did, till they ran it through tests and found it was for real.
Oh forgot to mention, the reason why a lot of the memory cleaners out there dont use this api call is because it wasnt documented till .net, every time you minimize a .net program the memory cleans itself up, this is the api call that is built into .net
Cleanmem simply took that nice little tweak from ms and applies it to the other processes.
Oh forgot to mention, the reason why a lot of the memory cleaners out there dont use this api call is because it wasnt documented till .net, every time you minimize a .net program the memory cleans itself up, this is the api call that is built into .net
Cleanmem simply took that nice little tweak from ms and applies it to the other processes.
Thanks for the informative input.Some users refuse to believe that old problems can be handled in new ways.
They hear a word or phrase and respond with the same old response.
YoKenny is not that kind of user.He investigates and discovers better ways are available.
I don't think he is ever finished checking things out.
davey