YES, stop using the screen saver version and start using the CLI ot
Command Line Interface version. It lets you use SetiDriver to run it
and the newest version of SetiDriver has a setting called "Force Idel
Only". That will make Seti the lowest priority requesting cpu cycles
and other programs can then happily crunch. The problem is that if
they don't have the same lowest setting Seti will not crunch but the
others will.
The easiset solution will be to go to Boinc when it is up and running
well enough to stay up and then most of the other distributed net
programs will jump on the bandwagon and you can then choose how much
of your processor you want to dedicate to each process. Right now
Boinc is up and down as it goes thru growing pains and I suggest you
stay with Seti Classic until it is fully ready.

On Tue, 03 Aug 2004 01:02:47 GMT, "Blake Young"
<blakeyoung@mail.utexas.edu.NOSPAM> wrote:

I am running WinXP with Seti@Home and I notice that it's using 100% of my
processor.  Normally this wouldn't be a problem, since I only run it during
the idle screensaver, however I also run two other distributed processing
programs.  Therefore, Seti@Home completely takes over the entire computer,
when I would like for some other programs to get some idle processor time.
Is there any way to change this?