Nanaki Posted July 9, 2005 Share Posted July 9, 2005 (edited) Well, in one of my latest uA discs I noticed that the use of my virtual memory was going thro the roof. My VMware couldn't even handle it anymore so it started complaining about 'not enough virtual memory, press OK to expand it'. Not very unattended-like.Anyway, I noticed that most setups "leave" processes running in the background. After about 20 setups (this includes Office and OpenOffice, two big boys) processes of over 80meg were just "left behind". Detecting and pskilling them manually is not my thing, so I introduce VMcleaner 0.2.Here's how it works, when you use the parameter "/w":vmcleaner /wit wil create a list of the currently running tasks and save in a file in the TEMP-directory. If you're a bit clever, you know that you need to run this at the beginning of your install method (RunOnceEx/XPlode/...), preferably the first entry.Afterwards, run VMcleaner without any parametersvmcleaneronce in a while (after every setup, after five setups, whatever, your choice). It will detect all the tasks again and kill any new ones that were created. This makes the virtual memory less occupied and faster again.You can run the first command again anytime to rewrite the tasks that shouldn't be killed.*wanders off*edit: and it can be used in a normal Windows-environment too! *shuts down 100 notepads*VMcleaner02.zipv0.2 (10/07/2005):- Can now detect and kill a similar-named task Edited January 6, 2007 by Nanaki Link to comment Share on other sites More sharing options...
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!Register a new account
Already have an account? Sign in here.Sign In Now