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.

Mike Ober.

"jason symes" <jsymes@nospam.netins.net> wrote in message
news:buhb80$3pe$1@news.netins.net...

Exactly, so hopefully I grabbed the right command line client. Now, what

are

the available switches for the commandline client? I couldn't find a doc
describing any.
"Michael D. Ober" <obermd-.@.-alum-mit-edu-nospam> wrote in message
news:x9WOb.1062$Mu.24531@news.uswest.net...

In that case I go back to my original thought - you're running the GUI
client.  Switching to the CLI client will dramatically improve your
throughput.

Mike.

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

At the time I checked the usage stats the client was disabled, so

nothing

was using 93% or 95% of my resources. When I run it, then all 100% of

my

resources are used, as I would imagine is normal.
"Michael D. Ober" <obermd-.@.-alum-mit-edu-nospam> wrote in message
news:xOVOb.1056$Mu.23088@news.uswest.net...

What's using the 93-95% of your CPU?  The client should be getting

98-99%

when nothing else is running.