it was my understanding that half of the reason to switching to BOINC was so users would automatically recieve updates to their client software. somehow this is not happening for me. i end up not having any work credits for days thinking you're just out of work again... i have to manually muck around on your website trying to figure out if i have the latest version and if not, download and hope that fixes my problem. when will this be addressed?

i am currently running version 4.05 but am manually downloading the latest (4.1x). running on windows xp pro, PIII toshiba laptop with 256mb RAM.

---

The SETI client does automatically update. When a new version comes out it is automatically downloaded and all workunits downloaded after that will use the new client. Workunits downloaded with the old client will be processed with the old client and returned.

The BOINC client is not automatically updated. However, you will see a message under the message tab when a new version of it is available.

Uh, under the messages tab. This isn't too useful. In addition to being a stream of system upload, download messages, it appears to reset whenever the machine reboots. So how is it that you're supposed to find out that a new version is available? Thanks

---

When wu's are created they are assign to a application version.
You may not get the new app version untill all of the old app wu's are completed. Even after receiving the new app wu, you may receive the old one again if the wu is resent for some reason.
You can check the page http://setiweb.ssl.berkeley.edu/apps.php for the current version.

---

Fred
BOINC Alpha, BOINC Beta, LHC Alpha, Einstein Alpha

> The BOINC client is not automatically updated. However, you will see a message
> under the message tab when a new version of it is available.
>

But it would be better to do also a automatic update also for the boinc client?

---

<img src="http://www.boincstats.com/stats/banner.php?cpid=eb8430bdcd1ac999e6fdea2ba9da7454">

>
> > The BOINC client is not automatically updated. However, you will see a
> message
> > under the message tab when a new version of it is available.
> >
>
> But it would be better to do also a automatic update also for the boinc
> client?
>
Too may people screamed about this being a security hole, so it was not done.

---

BOINC WIKI

> >
> > > The BOINC client is not automatically updated. However, you will see
> a
> > message
> > > under the message tab when a new version of it is available.
> > >
> >
> > But it would be better to do also a automatic update also for the boinc
> > client?
> >
> Too may people screamed about this being a security hole, so it was not done.
>

maybe the problem is about running indipendent project and a boinc client update could be incompatible with a project if they don't update the application.

---

<img src="http://www.boincstats.com/stats/banner.php?cpid=eb8430bdcd1ac999e6fdea2ba9da7454">

IIRC, this has happened to SETI@Home once already: The BOINC project came out with an update, but the existing SETI@Home science clients had problems with it. SAH eventually caught up. So yes, this is a limitation of running independent projects on top of a common infrastructure.