Post a Comment
We've had something similar on Windows for years in the form of ProcessExplorer. http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx
It's a shame that the default task manager still sucks even on Vista and you have to rely on third parties to provide a more useful alternative. Reminds me of Finder on OS X ...
Uh ... ProcessExplorer is one of the best tools out there that replaces the task manager. It was originally written by the guys at Sysinternals who are experts at Windows development. Then MS bought them out and ProcessExplorer is now hosted on MSDN.
I just don't understand why MS doesn't just replace the damn task manager with ProcessExplorer that's tons better.
ProcessExplorer, while really useful in its own right, doesn't really offer the same accessibility to the mentioned features as ProcessController does. PE is an extended version of the task manager, while PC is something else.
They both deliver the same functionality, but they deliver it differently.
They both deliver the same functionality, but they deliver it differently.
What's less accessible in PE compared to PC? Judging from the screenshots on the PC page (http://www.k23productions.com/products/process_controller/art/snap....) I'd say PE offers the same information as PC does except most of it is viewable at a glance (http://i.technet.microsoft.com/bb896653.ProcessExplorer(en-us,MSDN....).jpg) rather than having to drill down like in PC. I'd even say that judging from PC's page PE offers more functionality than PC (viewing DLL's mapped into a process' address space for instance, no mention of this on PC's page). Then again, I've not installed PC to see how it stacks up against PE, PE has everything I need anyways, and then some.
And PE is anything but an extended version of the task manager as someone already pointed out (if by extended you mean a wrapper around the native task manager). And even if it was, what difference does it make?
What's funny about the PC screenshot btw is that PC is taking up the most resources together with VLC.
Perhaps the other way around... ProcessController has been around since at least 2000... has the KDE tool you reference been around longer than that? "
Nevermind... I guess you were referring to ProcessExplorer (damn similar names got me all confused)
It is odd to see something ported from an obscure OS to Windows. I tried it and it looks and behaves remarkably like the BeOS version.
I'll have to find some mal-ware and see how it shows up in Process Controller :-)
There SO many odd processes and threads running I will be busy with Google to understand what is not needed.
Maybe some applications found here: http://pcwin.com/software/Network_Process_Monitor/ ?




