On Tue, 2 Nov 2004 18:06:15 +0000, John
<fredclark@consltec.demon.co.uk> wrote:

You could also try SETI Queue as a proxy to feed SETI Driver on each PC
on you network. In each case SETI Driver can be set to use a proxy (SETI
Queue) at a private IP address (say 192.168.0.1). Queue will cache the
WUs (CLI only) as well as Driver, and send off the WU results when these
are received via your always on broadband.

John, this could solve a prob on one of my machines if I'm right: it
downloaded 3 WU's but it fails to send em once they got finished. The
first try was the same: it received the WU, but never sent the result.
So I deleted the whole bunch and tried again, with the result
mentioned above. If Seti Queue works from only 1 puter I might put it
onto that one and direct the unwilling one to the proxy. 

SETI Queue can be set to seek sweet units (high AR), which will download
quickly. I see from my Queue WU cache I downloaded 23 HAR WUs at one
shot before it stopped.

HAR WUs will crunch more quickly.

Yes I know.... few years back there were those VLAR's IIRC, which took
a lot more time. Oh well, they gotta be crunched too, and I don't
mind. I'm not into this for record-breaking :-) Funny thing compared
to 2 yrs back is that my 2200 XP now crunches in roughly 3 hrs 50
mins, while I never seen lower than 6 or 7 before.... then again, it
doesn't run a server with 4-500 users onto it any longer too.

Louis