From: "Rich Gauszka" 

http://www.microsoft.com/technet/sysinternals/ProcessesAndThreads/processmonito
r.mspx

Process Monitor's user interface and options are similar to those of
Filemon and Regmon, but it was written from the ground up and includes
numerous significant enhancements, such as:

      . Monitoring of process and thread startup and exit, including exit
status codes

      . Monitoring of image (DLL and kernel-mode device driver) loads

      . More data captured for operation input and output parameters

      . Non-destructive filters allow you to set filters without losing data

      . Capture of thread stacks for each operation make it possible in many
cases to identify the root cause of an operation

      . Reliable capture of process details, including image path, command
line, user and session ID

      . Configurable and moveable columns for any event property

      . Filters can be set for any data field, including fields not
configured as columns

      . Advanced logging architecture scales to tens of millions of captured
events and gigabytes of log data

      . Process tree tool shows relationship of all processes referenced in
a trace

      . Native log format preserves all data for loading in a different
Process Monitor instance

      . Process tooltip for easy viewing of process image information

      . Detail tooltip allows convenient access to formatted data that
doesn't fit in the columna

      . Cancellable search

      . Boot time logging of all operations






"Gary Britt"  wrote in
message news:4602cb11$1{at}w3.nls.net...
> Actually there is a new tool from sysinternals that came out at the end of
> 2006.  Its called Process Monitor (procmon) and combines the features of
> regmon and filemon.  Output might be much improved over regmon, but I
> haven't tried it so don't know for sure.
>
> Gary
>
> Frank Haber wrote:
>>> Sysinternals
>>
>> It's regmon.exe.  Its output is voluminous, and I remember the filtering
>> is sketchy.  Hard to use, unlike filemon or procexplorer.  I guess if you
>> had plenty of disk space and built some tools to parse the logfile......

--- BBBS/NT v4.01 Flag-5