Process Explorer V10.11

[nontroppo]

Knowing what exactly is happening to your machine is a pretty fundamental thing when using a computer. Windows has a built-in task manager, but it is primitive.

A wonderful, free alternative is Process Explorer from SysInternals. There isn't information you can't glean from it. It is very customisable, and a great feature are "column sets" - you can save views dedicated to I/O, memory and whatnot and easily switch between them.  My screenshot shows my "general" view of essential resources for each app, this is all customisable.

You can determine working set memory use not only for apps, but dependent DLLs; and you can see which DLLs and handles an app has open.

If a file is locked, it will tell you which app has it opened, it will run google searches on processes you're not sure of. Minimised to the systray it uses few resources and its animated icon keeps you aware of CPU (tooltip tells you the most hungry current app without even opening it!). The new version contains a host of details and more "history" displays to keep track of e.g. I/O operations per-app over time. There are lots of neat touches throughout.

I never leave home without it...

http://www.sysintern...processexplorer.html (which is also a great source of other software)

[Rover]

This is one of my tookit apps.  Thanks for the notice on the new version.

[AbteriX]

If you take care of the file size, visit the sysinternals forum for an howto to reduce it.

...moment...
here>>> Process Explorer size

[f0dder]

Yeah, the EXE is a bit fat... using a resource editor to remove the binary resources isn't too bad, the problem is... which entries to remove?

[AbteriX]

I can't remember totally right, Mr f0dder,
pls take a look into the thraed i have mentioned above,
there is the answer !

[f0dder]

I can't remember totally right, Mr f0dder,
pls take a look into the thraed i have mentioned above,
there is the answer !

-AbteriX (May 15, 2006, 11:05 AM)

DOH!, I hadn't realized the thread was multiple pages

[urlwolf]

hmm, I use it too.
There is something I don't like about it. Even when minimized, it seems to stop all system activity, steal a few CPU cycles for itself (only a few ms), and then update its graphs.

If I'm reading something using opera's middle-click autoscroll, I like it to run smooth. If procExp is running in the background, it becomes jumpy.

Previous versions (9.xx, without multigraphs for each app) didn't have this problem.

[f0dder]

It does steal a few clock cycles, yes. Even the previous versions without multigraphs could cause some problems, but only really in extreme situations - like a test app creating a thousand threads

[nontroppo]

when minimized it uses ~0.54% CPU - when running ~3.2%. that compares to ~0.11% for windows  task manager and ~1.8% running.

Try reducing update frequency to 2 seconds.

I've never noticed it disrupt scrolling in Opera here. What happens if you turn the graphs off?

[Curt]

If you take care of the file size, visit the sysinternals forum for an howto to reduce it.

-AbteriX (May 14, 2006, 02:53 PM)

Handle is only 128 KB and is the command line version of Process Explorer (which is 3½ MB):
http://www.microsoft...dThreads/Handle.mspx

[AbteriX]

Hi Curt, sorry!
Handle  is not the command line version of Process Explorer.
Handle is not an replacement of Process Explorer.
Handle is only to see which files are locked from which application.... smtg like UnLocker

"C:\>handle /?"

Handle v3.2
Copyright (C) 1997-2006 Mark Russinovich
Sysinternals - www.sysinternals.com

usage: handle [[-a] [-u] | [-c <handle> [-y]] | [-s]] [-p <process>|<pid>] [name
]
  -a      Dump all handle information.
  -c      Closes the specified handle (interpreted as a hexadecimal number).
          You must specify the process by its PID.
          WARNING: Closing handles can cause application or system instability.
  -y      Don't prompt for close handle confirmation.
  -s      Print count of each type of handle open.
  -u      Show the owning user name when searching for handles.
  -p      Dump handles belonging to process (partial name accepted).
  name    Search for handles to objects with <name> (fragment accepted).

No arguments will dump all file references.

Ever wondered which program has a particular file or directory open? Now you can find out.
Handle is a utility that displays information about open handles for any process in the system.
You can use it to see the programs that have a file open, or to see the object types and names of all the handles of a program.

Process Explorer on the other hand can show you the 'handles'  too.......but this is only a small part of ProEx.

Light weight alternatives to ProEx are e.g.
"ProcessMate v1.87" from WEIRD173
and "Process Viewer  for Windows" from http://www.teamcti.com/pview/prcview.htm  which have an command line tool pv.exe
and "Process" from http://www.beyondlog...util/processutil.htm
(BTW by searching the homepage URL i found http://www.softpanor...rocess_viewers.shtml)

[Curt]

Hmmm; I didn't bother to read all of the text before posting; I only read the beginnings:




Sorry!