On Thu, 22 Jul 2004 20:08:33 GMT, Chefry <dont.have.email@all> wrote:

On Thu, 22 Jul 2004 18:12:47 GMT, f/f george <george@yourplace.com> wrote:

On Wed, 21 Jul 2004 15:52:33 GMT, "Stratcat" <none@no.org> wrote:

I downloaded and installed SETI Driver. Set it up following the instructions on the
website. Set up SETISpy to run with it according to the instructions on that website. But
SETI Driver can't seem to download any units. SETI@Home is still processing the unit it
has though. Any ideas why this is not working? I set it all up on 2 computers and SETI
Driver can't seem to retrieve any WU's on either

Change the "desired cache size" box to a number higher than the number
of units you currently have in your system and it should download them
just fine. It will start with the highest number and work down.
You ARE using the CLI with it right? Just put both in the same
directory and just double click on SetiDriver and it will
automatically run the CLI. I don't believe that you can run the screen
saver version with SetiDriver.

What's the CLI?
I'm using SETI@Home, SETISpy and SETI Driver

The CLI is the "Command Line Interface?", basically it is the same as
the screen saver but without the screen saver, therby increasing the
processing power of your computer available to Seti making the units
process about 10-20% faster. It is available thru the add-ons section
of the main Seti page. If you can find it version 3.03 is faster than
version 3.08 and the only change was for people that use a proxy
server to connect to Berkeley. If you do not use a proxy server to
connect to Berkeley, 3.03 is faster by a few percent. Version 3.03 can
let bad things happen if you use a proxy to connect to Berkeley!!!
I use Seti@Home(CLI version instead of the screen saver version),
SetiSpy and SetiDriver and SetiQueue. SetiQueue is a caching program
that handles all of my machines so I don't have to tweak each one
individually.