Check this out:
A computer belonging to user named enrgeeman. Like lots of other users this one is either too ignorant or too stupid, to upgrade the CC to > 4.13. Can/could project managers do something about that (like deny WU request for CCs below v. 4.19)?

[edit](silly html tags)[/edit]

---

There's no solution calling people names, that's for sure. Take a look at the text to the left of the reply field next time...

But some of us thinks that it might be a good idea to have BoincMgr display an upgrade message when a new version is available for download. That would take care of those situations where crunchers are unaware of any new version. It's not a perfect solution, but one of many that could be done in parallell. Your suggestion of denying WU requests are another. Something similar has been done several times before, I beleive. At least I had to upgrade more than once to get new WU's (in the classic project).

---

> There's no solution calling people names, that's for sure. Take a look at the
> text to the left of the reply field next time...
>
> But some of us thinks that it might be a good idea to have BoincMgr display an
> upgrade message when a new version is available for download. That would take
> care of those situations where crunchers are unaware of any new version. It's
> not a perfect solution, but one of many that could be done in parallell. Your
> suggestion of denying WU requests are another. Something similar has been
> done several times before, I beleive. At least I had to upgrade more than
> once to get new WU's (in the classic project).
>
>

I think that both solutions are absolutely feasible. Didn't einstein deny to send new wus to clients below 4.19? the problem is I think that not all (or even a small part) of users take a regular look on all the homepages. Most parts of the userbase want to install a program without caring afterwards. this was possible with the old seti, but not with boinc. Before the final switch happens, one of the 2 solutions should be implemented, because once people have switched many of them will not come back to the message boards.

---

BOINC automatically updates the project software, so why can't BOINC be made capable of updating itself? A lot of BOINC software is running on machines that are inconvenient to update each time there's a new version of BOINC. This could be an option that the user could enable or disable, according to whether or not they wanted to allow automatic installation. But it should be an available capability. As long as updates to BOINC have to be done manually, there will be many machines running old, old versions.

---

--Bill

Hi

This was discused a few month ago.
It is impossible to auto upgrade the core client.
What the devs can do, is an info message from the sheduler that informs to update the client to a x.xx version.

greetz from Germany
Mike

---

With each crime and every kindness we birth our future.

Hi

> This was discused a few month ago.

for example in this thread.

Cheers
Femue

---