My problem with BOINC is a bit different:
As a systembuilder, I have about 50 new systems every day. A few run only
for up to 2 hours, some stay on during the night. I use a self-writen
program, a bit like SetiStash (check it out here:
http://home.deds.nl/~th/setipile). The newly build and freshly installed
systems make a network connection to the server, and start my program from
there. My program then lets the client run the Seti-CLI client from the
server. The workunit is on the server. When the cllient is moved to the
stock, the workunit is partly finished. No problem, because another new
machine wil finish it (I see no cheating here...).
I thing I lose this flexibility with BOINC, because, as I read it, it is
only possible to load workunits directly to the client. When the client is
moved to the stock, partly finished workunits are lost. Waste of time. And,
systems that only run for a few hours will probably never finish a
workunit.....

Just my thoughts.

Willy


"Brian" <tramsmash@yahoo.com> wrote in message
news:3f826d65_1@news.iprimus.com.au...

BOINC Announcement
http://setiathome.ssl.berkeley.edu/boinc_transition_plan.html

Brian
3.9 years, 4490 units & wondering if I make it to 5000?