If you are referring to SETI Classic's CLI client, the problem is with the
processing priority of the CLI.  It runs at priority 4 instead of 1.  It
should be at priority 1.  There are several parts of Windows that run
between priority 2 and 4 and the SETI Classic CLI interferes with them.  In
this case, you have two choices - use SETI Driver, which has the ability to
force the client to 1, or switch to BOINC.

Mike Ober
http://www.wakeassoc.com/setidriver

"Herman Family" <celcaps@frontiernets.net/without_any_s/> wrote in message
news:DiTWc.3822$N47.506@news02.roc.ny...

I noticed that my xp ran very slowly and didn't download the sp2 update
until I turned seti off for the duration.  Anyone else with the same
problem?

Michael