"Working in Background"

Justin Thyme wrote:
"Justin Thyme" wrote in message
...


The Process Explorer by Sysinternals shows many processes but only Idle

and

Process Explorer itself indicate any measurable numbers. It may well be
that there is something going on, but below the threshold of Process
Explorer's ability to measure it, like 0.5%.


It may in poor taste to reply to one's own post but I have something that
news to me and maybe to someone else he

Sysinternals's Process Explorer, which has been updated almost daily
recently and now at release 9.25, is capable of displaying CPU run times
fractionally to two decimal places. (Maybe it's been there all along and I
have neglected it!)

I still haven't used the new-to-me feature but I may be able to use it to
see just what is running in the background, even at very low levels.

Ken Bland



My first thoughts were that the mouse setting or Process Explorer were
the ones gumming up the works. Second was it could be a hard-drive
having to power up or something. Last but not least is something's
giving shutdown a hard time and winmgmt has to tell everybody about it.


Rick

Winmgmt is our old friend the Data catcher for PCHealth....

Ken - here's my standard spiel for winmgmt problems.....

Disable PCHealth Data Collection Service (which is of no use
to man or beast!) - in two places.

1) Task Scheduler - disable PCHealth Data Collection
2) in MSCONFIG | Startup , uncheck PCHealth (PCHSchd.EXE) - click Apply,
OK - Windows will reboot.

See if that helps.


--
Noel Paton (MS-MVP 2002-2005, Windows)

Nil Carborundum Illegitemi
http://www.btinternet.com/~winnoel/millsrpch.htm

http://tinyurl.com/6oztj

Please read http://dts-l.org/goodpost.htm on how to post messages to NG's

"Rick T" wrote in message
...
Justin Thyme wrote:
"Justin Thyme" wrote in message
...


The Process Explorer by Sysinternals shows many processes but only Idle

and

Process Explorer itself indicate any measurable numbers. It may well be
that there is something going on, but below the threshold of Process
Explorer's ability to measure it, like 0.5%.


It may in poor taste to reply to one's own post but I have something that
news to me and maybe to someone else he

Sysinternals's Process Explorer, which has been updated almost daily
recently and now at release 9.25, is capable of displaying CPU run times
fractionally to two decimal places. (Maybe it's been there all along and
I
have neglected it!)

I still haven't used the new-to-me feature but I may be able to use it to
see just what is running in the background, even at very low levels.

Ken Bland



My first thoughts were that the mouse setting or Process Explorer were the
ones gumming up the works. Second was it could be a hard-drive having to
power up or something. Last but not least is something's giving shutdown
a hard time and winmgmt has to tell everybody about it.


Rick

Rick,
As I recall, my pointer went through the 'hourglass flickering'
during shut down, even though it was shutting down properly. My current XP
machine does the same thing. Did you go through all the TS ideas at the
aumha site??
Heirloom, old and fixin' to burn some

"Rick T" wrote in message
...
Justin Thyme wrote:
"Justin Thyme" wrote in message
...


The Process Explorer by Sysinternals shows many processes but only Idle

and

Process Explorer itself indicate any measurable numbers. It may well be
that there is something going on, but below the threshold of Process
Explorer's ability to measure it, like 0.5%.


It may in poor taste to reply to one's own post but I have something that
news to me and maybe to someone else he

Sysinternals's Process Explorer, which has been updated almost daily
recently and now at release 9.25, is capable of displaying CPU run times
fractionally to two decimal places. (Maybe it's been there all along and
I
have neglected it!)

I still haven't used the new-to-me feature but I may be able to use it to
see just what is running in the background, even at very low levels.

Ken Bland



My first thoughts were that the mouse setting or Process Explorer were the
ones gumming up the works. Second was it could be a hard-drive having to
power up or something. Last but not least is something's giving shutdown
a hard time and winmgmt has to tell everybody about it.


Rick