Go ahead and install the CLI on your HP.  Put the file "stop_after_send.txt"
in the folder with the GUI client and let it finish it's current WU.  Then
you don't have to worry about lost CPU cycles.

Mike.

"jason symes" <jsymes@nospam.netins.net> wrote in message
news:buim37$ba2$1@news.netins.net...

Thanks for all the helpful suggestions! My Gateway's crunching numbers

even

faster tahn before, and once the HP gets done with the work unit that it's
almost finished with, I'll get rid of the gui there too!
"~misfit~" <~misfit~@his_desk.com> wrote in message
news:4k1Pb.17734$9k7.314078@news.xtra.co.nz...

MPBroida wrote:

"Michael D. Ober" wrote:

Download SETI Driver from http://www.wakeassoc.com/setidriver and
copy it and your command line client into a folder.  On the Win98
box, you should also download _default.zip from the SETI Driver
web-site and unzip it into the c:\windows folder and reboot.  Start
SETI Driver and set your cache size.  Don't touch the maximum
processes on either system.  If you need to use a proxy setting on
the GUI, put these settings into SETI Driver and it will use them.
Click Transmit.  When the SETI client asks for a log-in (it will
only do this once per machine), enter the same userid you are
currently using.  On a permanent connection, select "Auto Transmit".
Minimize SETI Driver, right click it's icon and select "Save
Configuration".  You're done.

To go with Mr. Ober's excellent SETI Driver, grab
SETI Spy from "http://cox-internet.com/setispy/".
They work well together, with SETI Driver providing
caching services (and more) while SETI Spy gives you
a log and display of your stats.  Neither uses much
CPU time, so the S@H commandline client gets it all.

URL for SETI Spy:
http://cox-internet.com/setispy/

Or just grab the integrated package from Marcel's site and it will do
everything for you, installing SETISpy, SETIDriver and remove the GUI
version.

http://members.home.nl/marcel.zuiderveld/
--
~misfit~