Steve wrote:
> "Far Canal" <me@privacy.net> wrote in message
> news:MPG.1fd3afd4299f9be7989ed6@news.readfreenews. net...
>> Rick wrote
>>
>>
>>> One way to approach it is to look and see who they are talking to. You
>>> might try grabbing a copy of TCPView from Sysinternals (which has since
>>> been absorbed by Microsoft at http://************/y82msb ) and have it set
>>> to autostart. Then watch for your svchost connections and use whois to
>>> find
>>> out who it is talking to.
>>>
>>> Off the top of my head, I suspect you will find that it is Microsoft's
>>> WGA
>>> program module that phones home shortly after booting up a Windows XP
>>> system. Try going here:
>>>
>>> http://en.wikipedia.org/wiki/Windows_Genuine_Advantage
>>>
>>> for more info.
>>>
>>>
>>>
>> XP-AntiSpy is very useful for turning off unwanted M$ crap
>> http://www.xp-antispy.org/
>> Makes it easy to turn parts of it back on for M$ Update. Allegedly.
>> Version 3.96-4 has recently appeared and stops automatic install of IE7
>> which is causing problems for many.
>>
>
> Thank you Kurt, Rick and Far Canal.
>
> WGA certainly took it's toll on my resources. Decided to stick with it
> rather than wind back the system to ease the pain of update.
>
> The IE7 install seems to have slowed down the PC as well but IE7 itself
> seems to run OK.
>
> Time to start working our what is driving SVCHOST sessions. Thanks again,
>
> --
> Steve
>
>
I'm sorry to report that I have tried everything I can think
of - particularly everything that is different about my
portable than my desktop (where SAS doesn't drain resources).

Windows update is, and has been, disabled.
I turned off Windows firewall - seemed to have no effect.

I just spent the last hour using Process Explorer and
suspending each process to see if it reduced CPU use by SAS
and the excessive fluctuations. I could not find a process
that stopped the cpu jumping to 40+ usage, then to 12% and
right back to 40 something % - sometimes into the 50s.

Whatever this process is, it is happening literally every
one or two seconds - back and forth.

And, as noted before, it doesn't happen on my desktop.

If anyone has any other suggestions, I'll be happy to try
them as I'm really very disappointed to find SAS unusable on
my portable - the machine that is, in fact, much more
vulnerable because of the traveling it does and the various
wireless connections I make while traveling.

Is there a more thorough way to track this down?

Thanks.

Louise