On Wed, Aug 12, 2009 at 7:13 PM, Ben Scott<[email protected]> wrote: >> How 'bout using ProcessMonitor to determine what's going on behind the >> scenes while doing the same test? > > EXPLORER.EXE is using a lot of CPU time ...
Oh, you said Process Monitor, not Explorer. The problem there is Windows generates tens of events per second even when it's doing nothing. During a change in network state, it's normal for all sorts of things to happen. There can be (tens of) thousands of events. It's worse than looking for a needle in a hay stack -- at least then I know I'm looking for needle. Did you have something in particular in mind? -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
