X-no-Archive:yes
I do use SetiDriver (and like it), and have it set to low priority, and see
exactly the behavior Mark Bixby described, on my NT workstation. If I exit
SetiDriver (which also takes down the seti@home task(s) it's managing), the
UD Agent CPU hits 90+%. Now, I can see CPU activity in Task Manager for UD
Agent while Seti@home is running, but it is a crawl. Perhaps it is simply
not a good idea to run two such processes on the same PC, or at least on
certain PCs where one process can consume all available CPU.

Greg Stigers
http://www.cgiusa.com

-----Original Message-----
From: Jeff Kell [mailto:[log in to unmask]]
Sent: Monday, April 16, 2001 3:19 PM
To: [log in to unmask]
Subject: Re: OT: SETI as opposed to Cancer Research


Mark Bixby wrote:

> I've been running both Seti@Home and UD on Win98 for the past several
days.  It
> seems that Seti@Home doesn't leave much (if any) CPU left over for UD.  I
was
> unable to see any change in the UD progress indicator until I terminated
> [log in to unmask]

If you use SetiDriver you can set the client priority to high/med/low.

Jeff

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *