

In order to do this, we can use a library for retrieving information from the machine. The status can include but is not limited to CPU usage, network latency, memory usage, and disk usage. I wasn't able to find something about this in the help file.A monitoring tool allows users to see the status of a machine at a specific point in time. It is a graphical representation of the overall process activity based on the number of events or the elapsed time. I must admit, I don't really understand the purpose of this feature. In the tools menu, there is new the new point " Activity Summary".

I found a third new feature which the SearchWinIT article doesn't mention. I suppose, I won't need this feature either. So this feature only gives you some limited information about the process' activity during a certain time span. It only displays the activity span for each process (see screenshot) in the Process Activity Summary window (formerly called Process Summary). Unfortunately, Procmon 1.2 doesn't really allow you to "see how each process is running" (whatever that is supposed to mean).

There is another new feature that sounds interesting in the SearchWinIT article:Īlso included in the latest version is a feature that lets users better see how each process is running during an activity trace by showing a graph for each one. Well, that's not really exciting either, is it? Process Monitor has the new switch "/run32" for this purpose which does nothing else than run the 32 bit version of the tool.

You can now open log files on a 64 bit machine that were generated on a 32 bit system. Process Monitor 1.2 has some new features, though. It just means that Process Monitor's filters only affect the display of events, but not the event data itself. The real name of the feature is non-destructive filtering and it's not new because the predecessors of version 1.2 already supported it. So, it seems like my desktop is just screwed up and MS didn't add "destructive" filtering. I tried the tool on two other Vista machines, and it worked there without problems.
