On Wed, 02 Jun 2004 10:23:32 GMT, "Hurrah" <hurrah@not.here> wrote:

Hi,

I currently run CLI SETI@Home on a number of PC's in a work location where
ADSL/broadband is not available and dial-up is very poor - (31.2k if I'm
lucky).

The networked PC's are supplied with WU's via SETIQueue running on a laptop.

Once the SETIQueue cache is down to zero, the laptop is brought home once a
month (where I do have broadband) and is left switched on uploading the
results and downloading more WU's.

Then the laptop is taken back to work and is left in situ, supplying the
WU's to the PC farm.

This has worked well for approx 3 months and currently churns out about 40
WU's a day.



Of course SETI@Home in it's current guise will be shut-down.

But where will that leave me and the PC's currently running SETI@Home?

Can BOINC be run in the same way?

The answer is probably! Discussions are continuing on how best to do
this. One problem is that ocassionally Boinc will be updated, how will
the computers behind a queue be updated? Manually, then you will be
behind the curve for a while until you realize that you are no longer
getting units and manually update.

Or will a third party have to produce a "BOINC Queue" program to do the same
as SETIQueue?

Probably third party as is done now.