"Megalomando" <mandolinist@netzero.net> wrote in message
news:63jcd0dpvva0ot9prhgbgl0j72a7f01cge@4ax.com...

I'm feeding about two dozen systems; many are running Windows of
various flavors (NT4 Workstation, 95, 98, and one 2K) and those
have SETI Driver installed, with a local queue of one more WU than
the processors in the system. Those, and my *nix-based systems,
are fed via a pair of Win98 systems running SETI Queue (which are
also running SETI Driver and a client). At the moment, I have
33 accumulated results ready to return, and 207 WU available to
distribute. There are about 40 WU distributed to the various
systems.

Caching is handy, as long as it's not overdone.


Gary

I've been trying to send in wu's & this computer spits out 12 a day I
have 48 to transmit & 62 left to be processed.

I have setidriver set for auto-transmit so I'd say nothing is being
accepted by the server for the last few days & I'm running short on
WUs

I got lucky, when the SETI Server was back up briefly the other day.  I was
just about out of WU's but managed to get another six days worth of WU's
cached.

Thanks to previous outage experiences I've learned the hard way to keep at
least a few days worth of cached WU's available (at least for my main
machine).

I'd definitely recommend Seti Queue or SetiGate to anyone not yet using a
cacheing Add-On, computers issues like the one currently affecting the SETI
Server definitely justify keep a small cache of fresh WU's.

SC