"Terry Pratchett" <tpratchett@unseen.demon.co.uk> wrote in message
news:8oE+Y1OJZXAAFAfo@unseen.demon.co.uk...

In message <egm200djkp86aaemf1h4r0metg30akjgc3@4ax.com>, f/fgeorge
<f/fgeorge@yourplace.com> writes

As long as you are going to relaod anyway, switch to the Command Line
Interface(CLI)! Download the setiathome-3.03.i386-winnt-cmdline.exe
file and of course SetiDriver and SetiSpy too.

Er...I don't think so.  We're running the CLI on most of the network and
it's fine, but while looking at various add-ons I saw it mentioned that
CLI causes problems if run with WordPerfect.  That's the word-processor
of choice here, and is on the 'problem' machine  There's a program
called run'hide that automatically shuts down the CLI while WP is
running, but since it's running throughout the working day on that
machine there would be no gain for me:-(
--
Terry Pratchett

Terry the new version of Seti driver shold take care of the conflict issue
in Win XP AFAIK.  It was rewritten to change the priority level of seti so
that it can use idle instead of low setting.

Larry