I downloaded BOINC, installed it and created an account. What has to happen now to get a SETI work unit? Do I need to do something?

I don't see anywhere I have an option?

---

Hello Harry,

have you attached Boinc to Seti (or any othre project)?

The (very good) manual for Boinc is the BOINC Powered Projects Documentation by Paul D. Buck and the FAQ therein.

A quick installation guide in this is here and for windows go here afterwards.

---

Gruesse vom Saenger

For questions about Boinc look in the BOINC-Wiki

You're not missing anything. BOINC is simply unable to download SETI workunits. This BOINC mess seems to be a typical techie project implemented without any adult supervision (i.e., management). Go back to SETI classic; it is downloading workunits and running just fine. If these bozos drop classic before they get BOINC working, well, just blow it off and go on to something else. There are lots of these projects available that don't need this BOINC disaster.

---

> You're not missing anything. BOINC is simply unable to download SETI
> workunits. This BOINC mess seems to be a typical techie project implemented
> without any adult supervision (i.e., management). Go back to SETI classic; it
> is downloading workunits and running just fine. If these bozos drop classic
> before they get BOINC working, well, just blow it off and go on to something
> else. There are lots of these projects available that don't need this BOINC
> disaster.
>
How come that you have such a complete different experience as I have with boinc?

It's beeen absolutly fine with me for the last 5 month, no real problems.

Only exception are the ones not caused by the project team, but some unrelated third party.

First several power outages for the whole building, that came of course as a total suprise, and had them put some extendet UPS to their servers.

Then their ISP cut them off the internet, again nowhere near their area of influence.

Unfortunately these things happened just as lots of classic folk appeared on the scene, that had absolute and total loss of memory of all the outages from classic.

---

Gruesse vom Saenger

For questions about Boinc look in the BOINC-Wiki

> You're not missing anything. BOINC is simply unable to download SETI
> workunits. This BOINC mess seems to be a typical techie project implemented
> without any adult supervision (i.e., management). Go back to SETI classic; it
> is downloading workunits and running just fine. If these bozos drop classic
> before they get BOINC working, well, just blow it off and go on to something
> else. There are lots of these projects available that don't need this BOINC
> disaster.

From the S@H/Classic website:

March 22, 2005
We're now fully back on-line. More information about recent outages can be found in Technical news (on the new SETI@home page).

March 21, 2005
Our Internet link through Cogent went down at around midnight UTC on March 18/19. It is still being looked at by Cogent. In the meantime, data service (upload/download) is unavailable. We do not yet have a projected time to fix - it could be a couple of days.

IMHO, they use the same power and the same internet link. If there is a problem here, the same problem occurs at S@H/Classic also.

>
> From the S@H/Classic website:
>
> March 22, 2005
> We're now fully back on-line. More information about recent outages can be
> found in Technical news (on the new SETI@home page).
>
> March 21, 2005
> Our Internet link through Cogent went down at around midnight UTC on March
> 18/19. It is still being looked at by Cogent. In the meantime, data service
> (upload/download) is unavailable. We do not yet have a projected time to fix -
> it could be a couple of days.
>
> IMHO, they use the same power and the same internet link. If there is a
> problem here, the same problem occurs at S@H/Classic also.
>
Except with a lot fewer people on S@H Classic, upload/download is much easier and takes place in the background much better so you don't notice the problem as much. The problem with BOINC is that everyone is trying to upload and download WUs at the same time. IIRC, SETI Classic doesn't use the same servers, just the same internet/power. BOINC probably has some sort of limit on the maximum number of connections to the server to prevent an inadvertant Denial of Service attack on the BOINC servers. If you've got tens of thousands of people all trying to connect at once, you're <B>going</B> to have problems.

---

> > You're not missing anything. BOINC is simply unable to download SETI
> > workunits. This BOINC mess seems to be a typical techie project
> implemented
> > without any adult supervision (i.e., management). Go back to SETI
> classic; it
> > is downloading workunits and running just fine. If these bozos drop
> classic
> > before they get BOINC working, well, just blow it off and go on to
> something
> > else. There are lots of these projects available that don't need this
> BOINC
> > disaster.
> >
> How come that you have such a complete different experience as I have with
> boinc?
>
> It's beeen absolutly fine with me for the last 5 month, no real problems.
>
> Only exception are the ones not caused by the project team, but some unrelated
> third party.
>
> First several power outages for the whole building, that came of course as a
> total suprise, and had them put some extendet UPS to their servers.
>
> Then their ISP cut them off the internet, again nowhere near their area of
> influence.
>
> Unfortunately these things happened just as lots of classic folk appeared on
> the scene, that had absolute and total loss of memory of all the outages from
> classic.

BOINC simply will not download workunits. SETI@home classic is running perfectly, but I have attached to both SETI and Einstein through BOINC and BOINC is unable to attach to a scheduler for either project. I'm going to uninstall BOINC and move on. When SETI@home classic goes down, that's the end of SETI for my three computers.

---