For those thinking of upgrading apparently 4.19 is on its way. Rom Walton at Berkeley has found another bug.

I'm still on 4.15 working on the 'if it ain't broke don't fix it principle'
Marj

---

_________________________________

Hi Marj999

It seems that 4.19 is the public release.
But I'm going to wait a few hours to be sure, I wouldn't be surprised to see a 4.20 version. :o)

---

Arnaud

let us know how you get on with it....

Marj

---

_________________________________

Running 4.19 here without a problem,

But I hear you on "if it aint broke" theory. Many people in this boat *smile*

Zain
---

---

Teamless? Drop by BOINC Synergy and look around
Also checkout our famous BOINC World Stats

Hi again !!
4.19 is running fine with CP, E@H and Seti for me.
Absolutly no problem on my 2 machines.
Cheers...

---

Arnaud

Heh -

Kinda' makes me wonder if the Berkeley team fully realizes the possible upgrade/maintainence implications if BOINC becomes hugely successful, involving a very large number of projects, and the propensities of the projects to acquire new requirements (or discover heretofore unknown bugs) as they evolve over time.

A large base of actively evolving projects, all requiring changes from time-to-time, along with the required client changes when adding yet new projects, could turn into a fairly constant state of BOINC client upgrades!

As for me, I run CPDN exclusively, so for now, I'm staying with what's tried-and-proven to work well, and satisfies CPDN's current science requirements at this point in time: v4.13.

I've gotten' 'burnt' too often, in this ever wonderful world of computing, by being an 'early adopter'. Now I prefer to wait for feedback from trusted sources, before I jump on the latest 'new thing'.

JMO

Strat

---

Quote from BOINC_projects Mailing list:

This is a bug fix release of the 4.13 source base and contains the following
bug fixes:

<i>1. File upload handling, this affects all projects.
2. File download handling, this affects all projects.
3. CPU and Model Identification code update on Windows, this affects any
projects using homogeneous redundancy, namely Predictor at Home
4. Execute benchmarks before actually attempting to start any applications,
this affects all projects.
5. Increase the buffer for command lines, this affects Einstein at Home.
6. Escape http and socks proxy user information for those who have special
characters in either their username or password, this affects all projects.
7. Fix the special cases where the client was ignoring the server's request
to delay the next RPC to a specific date and time, this affects all
projects.

Rom Walton
</i>

---

Professor Desty Nova
Researching Karma the Hard Way

Professor Desty Nova -

Any sources for the changes in 4.19?

I might have been a bit overly cynical in my last post, and would consider an upgrade if there's other compelling reasons that effect the core BOINC s/w performance besides providing a fix for another project (predicated on the new release proving itself reliable for CPDN, of course).

Strat

--EDIT--

Maybe I misunderstood your post. Did you list the fixes in 4.13, or the problems in 4.13 that are fixed in 4.19?

---

&gt; Maybe I misunderstood your post. Did you list the fixes in 4.13, or the
&gt; problems in 4.13 that are fixed in 4.19?


That is the list of problems in 4.13 that are fixed in 4.19. :-)

I've been running cc4.19 since its release and everything seems to be running fine. E@H, P@H, and S@H are all running without any hitches. I'm still quite a way from fully completing a CPDN WU, but I haven't had any miscellaneous errors since/due to the upgrade. Looks to be fairly stable.

---

www.clintcollins.org - spouting off at the speed of site

From E@H

"I don't know this for sure, but from my own upgrades and user feedback I'm afraid that the "major version" of the state file changed somewhere between 4.14 and 4.17, so an update from 4.17 (and possibly 4.16) to 4.19 should work without problems, but upgrading from prior versions might fail with this error. I didn't look into the the code, though, anyone else to confirm it"

I'm not sure what to do. I'm still on 4.15 with a model about to complete (backed up - or at least it will be before I do anything)

---

_________________________________

&gt; From E@H
&gt;
&gt; "I don't know this for sure, but from my own upgrades and user feedback I'm
&gt; afraid that the "major version" of the state file changed somewhere between
&gt; 4.14 and 4.17, so an update from 4.17 (and possibly 4.16) to 4.19 should work
&gt; without problems, but upgrading from prior versions might fail with this
&gt; error. I didn't look into the the code, though, anyone else to confirm it"
&gt;
&gt; I'm not sure what to do. I'm still on 4.15 with a model about to complete
&gt; (backed up - or at least it will be before I do anything)
&gt;
I saw a couple of posts where the client_state.xml file apparently got corrupted but the major version is still 4.xx in both public and alpha branches.

You can tell the difference in the log file. If it says 0.00 for the previous version the file was corrupted. When a real major version change occurs it will show the previous installed version ie 4.13.

---

BOINC WIKI

BOINCing since 2002/12/8

&gt; &gt; Maybe I misunderstood your post. Did you list the fixes in 4.13, or the
&gt; &gt; problems in 4.13 that are fixed in 4.19?
&gt;
&gt;
&gt; That is the list of problems in 4.13 that are fixed in 4.19. :-)
&gt;

Thank you S@NL - EJG!

I suppose then, an eventual upgrade, should be on my things-to-do-list.

Strat

---

I upgraded from 4.13 to 4.19 yesterday and so far everything is running very smoothly. No problems with "major version change". It just ran a benchmark after upgrading then continued to crunch normally. The only minor hiccup I had was that the install program put a shortcut in the All Users Start Programs, and I'd previously moved it from there to the Owners Start Programs, so when I rebooted the computer it tried to start BOINC twice. But it recovered from that with no problems. I removed one of the shortcuts and now everything is running fine. I'm using Windows XP SP2.
Hope this encourages more people to take the plunge!
Alan

Since v4.19 is now the version of BOINC available from the <a href="http://boinc.berkeley.edu/download.php">SETI@home BOINC download web page</a> for Windows, I'll give it a try here too...

---

<a href="http://www.nmvs.dsl.pipex.com/"><img src="http://boinc.mundayweb.com/cpdn/stats.php?userID=6&amp;team=off&amp;trans=off"></a>

<a href="http://www.nmvs.dsl.pipex.com/">Distributed Mania</a>

Been running 4.19 since it's release. No problems here.

---

"Upgraded" to 4.19 from 4.17 on my win2k box.

20 mintes later:

2005-01-27 19:51:45 [climateprediction.net] Unrecoverable error for result 2xqs_000158426_1 ( - exit code -5 (0xfffffffb))

The CP WU was about 15% done....

---

&gt; "Upgraded" to 4.19 from 4.17 on my win2k box.
&gt;
&gt; 20 mintes later:
&gt;
&gt; 2005-01-27 19:51:45 [climateprediction.net] Unrecoverable error for result
&gt; 2xqs_000158426_1 ( - exit code -5 (0xfffffffb))
&gt;
&gt; The CP WU was about 15% done....

Ouch. :-(

That just motivated me to back up $HOME.

---

I'm running win2K as well with only 60 hrs left on the model so it can wait now till the models finished....

Marj

---

_________________________________

Most of my models are in the middle or their progress. I'm about to make a backup and upgrade to 4.19 during next week.