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.
The event log is another much appreciated addition, recording *every* process, window and module that is loaded and unloaded - and the time when it occured - whilst WinTasks has been running. Fortunately, the window also provides a filter so that you aren't presented with an entirely unmanageable list. One downside of all this logging, is its relatively high processor usage - WinTasks consistently used 10% of my processor whilst running. As a result, its not something I would want running continuously, but those of you with something a little beefier than my 3 year old 500Mhz processor probably won't notice a thing!
all that, just from starting notepad.exe....
The final feature that needs mentioning - especially on a developers site - is the inclusion of a scripting language. The manual includes a reasonable overview of this, and the website has plenty of examples, but essentially it allows you to run something like
if process_file = "notepad.exe" then
stop
alert "notepad is not allowed to run on this computer"
endif
LIUtilities have strongly promoted the security benefits of running a program such as WinTasks; with that script being once such example. However, it does seem strange that if they envisage scripts being programmed to prevent certain applications from running, that they provide no way of locking WinTasks so that it cannot be halted; otherwise, such 'protection' is pretty pointless.
Comments