Weird, isn't it? http://boinc.berkeley.edu/download.php

I did download v. 4.14 when it was available this morning, but haven't upgraded yet, as I have a CPDN model at almost 66% and I'd be sorry to lose it...
that may mean my putting off the upgrade for a few weeks still, unless it becomes compulsory in order to get more WUs or to participate in Predictor (I'm currently running SETI, CPDN, LHC and Predictor). :)

---

WinXP Home, P4 3.2GHz HT, 512Mb RAM. Running SETI, Predictor, Prime Grid, SIMAP, Folding

> Weird, isn't it? http://boinc.berkeley.edu/download.php
>
> I did download v. 4.14 when it was available this morning, but haven't
> upgraded yet, as I have a CPDN model at almost 66% and I'd be sorry to lose
> it...
> that may mean my putting off the upgrade for a few weeks still, unless it
> becomes compulsory in order to get more WUs or to participate in Predictor
> (I'm currently running SETI, CPDN, LHC and Predictor). :)

I'm also in the same position (and in the same projects) ;-)
I think i'll wait a day or two and see if something cames out in the mailing lists or foruns.

---

SETI@home classic workunits: 1,985 CPU time: 24,567 hours



Professor Desty Nova
Researching Karma the Hard Way

> Weird, isn't it? http://boinc.berkeley.edu/download.php
>
> I did download v. 4.14 when it was available this morning, but haven't
> upgraded yet, as I have a CPDN model at almost 66% and I'd be sorry to lose
> it...

Just make sure you exit the BOINC client, then open up Task Manager to see if none of the crunchers are still lingering. If there is one that is still in the list, end its operation (Rightclick, End Process).

Then you can easily either uninstall 4.13 (I did so, it doesn't harm anything) and install 4.14 in its place, or just install 4.14 over 4.13

---

The 4.14 was supposed to only be out for testing, not for general use yet. Since Einstein@Home is in testing, it is available for them.

To be honest I have seen no trouble with 4.13, it seems to be primarily a EAH problem ...

---

...
> To be honest I have seen no trouble with 4.13, it seems to be primarily a EAH
> problem ...

To be honest, there will be always situations, giving the boinc client a suffering environment/situation, anyway what client version/release is used.

To be honest, I feel like a unvolontaired tester since the very first public go. Any kind of project running.

To be honest, bugs are not an option, they are delivered with the applications.

What is working fine for the one person, must not fit for an other person or better say, it's technical setup. How bad everyone is right..

To be honest, Paul, I really like your avatar, even your Angels work of documentation is much more important for community.


Since the beginning of boinc I'm collecting and stocking all client version I can get, and the collections will keep growing in future.

Might we see in your pages, something like a "boinc client" museum?

friendly

ric

Ric,

> To be honest, there will be always situations, giving the boinc client a
> suffering environment/situation, anyway what client version/release is used.

Yes. One of the reasons that Apple and the Macintosh line have fewer problems is that Apple controls not only the software but also the hardware to a great extent. Because the hardware has less "variety" the systems run better.

A victum of its own success, Microsoft has to deal with a huge collection of hardware. More problematic than that is the fact that the drivers for a lot of that hardware are, ahem, weak. Of course, they compounded this with the decision to allow the drivers to run in Ring 0, compromising the stability of the kernal.

> To be honest, I feel like a unvolontaired tester since the very first public
> go. Any kind of project running.

Yes, we all did get drafted didn't we... :)

For all of that, since mid to late third quarter last year I think, for the most part, we have been running a very stable application. At least from where I sit ... we were mostly seeing issues on the server side of the system as we flooded it with results ...

> To be honest, bugs are not an option, they are delivered with the
> applications.

Yes they are. We know how to develop programs better. The trouble is that we are unwilling to pay the cost (time and or money) for high quality software. Again, for all of that, BOINC has been relatively stable. Most of the problems seem to have been with the less stable Win-95 family of OS.

> What is working fine for the one person, must not fit for an other person or
> better say, it's technical setup. How bad everyone is right..

Very true. I never want to seem that I am minimizing someone else's problem, I hope that I come across that way. And if I have been seen as otherwise, well, I am sorry for that.

> To be honest, Paul, I really like your avatar, even your Angels work of
> documentation is much more important for community.

I got my Avatar from the King of Avatars. My artistic abillities range from none to worse than none.

And I thank you for those kind words about the documentation. I do try ... :)

And, as time has gone by I like to think that they have been getting better all of the time. WIth luck, I am going through one of the last iterations of making major changes in the internal structures so I can get back to working only on the content.

> Since the beginning of boinc I'm collecting and stocking all client version I
> can get, and the collections will keep growing in future.
>
> Might we see in your pages, something like a "boinc client" museum?

I don't see why. I might think about a version vs. problem list. But that might be too subjective and hard to make useful.

---