"John Clark" <fredclark@consltec.demon.co.uk> wrote in message
news:+CwBSLBRuzV$Ewal@consltec.demon.co.uk...

<big-time snippage>

Following these suggestions is the way I play it. However, I have
changed the situation slightly. My small network consists of -

1.      A single proc P3 750, o/c to 840. This has no cash over the WU
        being processed. This runs a single instance of the CLI, with
SETI Driver and SETI Spy.
2.      I have a dual proc P3 933@933, and 2 instances of the CLI and
SETI Driver/Spy.
3.      Finally, I have a dual proc Xeon @ 2.8 Ghz with HT enabled. This
        runs 4 instances of the CLI, with Driver and Spy.

The whole system is tied together with SETI Queue, as my proxy server
and stats generator.

NOTE: SETI Watch would also do the job OK.

In each of the versions of SETI Driver I have the Proxy server box
ticked, and the TCP/IP address: port 5517 enabled.

The system works fine, collecting all the WUs as these are finished and
dishing out the new WUs. None of the SETI Driver cashes are above the
number needed to process the appropriate number of units for each of the
network PCs.

In the evening SETI Queue sends the day's collection of completed WU
results off and automatically collects the replacements.

Hmmm....this looks like a configuration which would work as a solution
for another poster who goes by the nick ~Misfit~. I currently am only
running a single machine, but will be building another soon. This is a
solution I'm going to toss in an archival folder, and re-examine when the
time to reconfigure comes about, but will keep in mind the possible
'simultaneous start' situation f/fgeorge and I discussed in a previous
post.

Thanx
--
Strat�








---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.515 / Virus Database: 313 - Release Date: 9/1/2003