James first started this website when learning Visual Basic back in 1999 whilst studying his GCSEs. The site grew steadily over the years while being run as a hobby - to a regular monthly audience of over half a million unique developers. In July '08 James left his job as Head of Development at a digital agency in London to focus his energies on developerFusion full-time.
Along the toolbar, you can access the rest of WinTasks features. One interesting feature is the 'presets' option. This allows you to save up to 4 'configurations' of currently running processes. Essentially, when you load a preset, WinTasks will automatically terminate (= use with care!), and start the processes to match those that were running when you saved it.
The AutoStart window gives you direct access to programs configured to automatically start up; and remove/temporarily disable them. WinTasks also provides a print command from every window - something frequently overlooked by other applications. The 'Windows' feature is especially interesting, displaying a list of windows for any selected process.
Bet you didn't know Outlook had that many windows...!
Next up is the Modules window - displaying a list of all the DLLs - and most importantly, their full file path - in use by a particular process, which is especially useful for us developers trying to escape from DLL hell.
The statistics window
Finally, we come to the statistics window - which is undoubtedly one of the most useful. In comparison to the standard windows task manager, it provides graphs for CPU and *physical* memory usage; and not just the total usage, but the usage for the selected process too. This is clearly a life-saver when trying to identify memory leaks - or simply when resources come under most demand. Graphs can be displayed over a number of different periods - 24 hours, 2 hours, 10 mins and 1 minute. Unfortunately, if there are a large number of small peaks, the 24 hour view isn't much use, as you just get one block of colour.
Comments