As some of you who installed 5.00 have experienced, some code that checked the major version of the client was left in the scheduler. It was supposed to have been removed months ago.

I have fixed the bug. However, the delta from when a server-side bug is fixed to when the various projects update the server-side components is generally a few weeks.

So that we can continue to stabilize the client and give the projects time to update their server-side software we have pulled the 5.00 release and reset our version to 4.70.

I know our previously stated policy was that versions x.50- x.99 were supposed to be development versions, but waiting until all the projects have updated the server-side code at the rate at which we intend to stabilize and release the client would cause a few problems and sleepless nights for a few people. So in the interest of all parties we are breaking our own policy.

On a happier note: It looks like when we start the next release cycle we’ll be using the Linux versioning system. I think that’ll take care of a bunch of issues related to how clients are released and peoples expectations of what has changed between releases.

---

----- Rom
BOINC Development Team, U.C. Berkeley
My Blog

yay! A new client I can use!
(now to wait for projects to switch over so we can get on with using 5.xx.xx)

Also, hooray for the new versioning system, which seems as if it'll allow for more new minor versions.

---

<img border="0" src="http://boinc.mundayweb.com/one/stats.php?userID=567" />
<a href="http://boinc-doc.net/boinc-wiki/index.php?title=Main_Page">BOINC Wiki</a>
<a href="http://www.tamaness.hostrocket.com/BOINC_team.html">Gideontech BOINC team!</a>

First of all, Rom, how dare you listen to the user community! I protest!

Second, is the 4.70 version going to be released across the platforms? We have not had an OS-X version in synch with WIndows for some time ... or, am I going to have to spend a couple weeks figuring out how to compile it?

---

Ok heres my touble, with the 4.45 version of boinc, when I click No new work, the status message "no new work" doesn't appear anymore.

---

Ok heres my touble, with the 4.45 version of boinc, when I click No new work, the status message "no new work" doesn't appear anymore.

It works in 4.70 again.

@Rom - Is there a 4.70 pdb, in case we have to report any problems?

---

4.70 isn't the Windows "Recommended version" yet is it? You're talking about 4.70 being the alpha or beta version, right?

---

Help and BOINC documentation is available here.

First of all, Rom, how dare you listen to the user community! I protest!

Second, is the 4.70 version going to be released across the platforms? We have not had an OS-X version in synch with WIndows for some time ... or, am I going to have to spend a couple weeks figuring out how to compile it?

Paul, I found an OS-X version over at the Berkeley download page, along with the 4.70 pdb. I don't know how recommended it is, though.

http://boinc.berkeley.edu/dl/

---

Boinc 5.00 was intended for Alpha ONLY, and so it follows that 4.70 is for Alpha ONLY.

Here's Roms email to the boinc ALPHA mail list:

Howdy Gang,

Where do I begin....

Okay, so the 5.00 rollout didn't go as planned, the major version
check for the scheduler was supposed to have been removed some time ago.
While I have fixed the bug, it typically takes a month to a month and a half
for the projects to catch-up.

Instead of playing the waiting game, we are going to go ahead and
use the unused development branch version numbers. I fully expect a fair
amount of criticism about this move since I've already told people in the
past that we were not going to do things this way.

This release has a couple more scheduler fixes JM7 did since the
5.00 release, but it is pretty much the same.

I have removed 5.00 from the download server.

On a much brighter note, BOINC will be adopting the Linux versioning
scheme. This will give our version numbers meaning again instead of just an
incremental value of a client release. After we bag this release, we'll
have a '..' version scheme.

I would like to apologize in advance for whatever flak you all might
experience due to the sudden policy change and resulting confusion this will
create with the community.

NOTE: Anybody who installed 5.00 on their machine will need to
uninstall BOINC before installing 4.70. The Microsoft installer technology
does not like to replace files that it deems is older than what is already
on the machine. What generally happens when you attempt to 'upgrade' to an
older version number is the files are removed from the system, but the
'older' files are not placed on the machine and so you'll get an error when
anything attempts to launch BOINC.

----- Rom

hope this helps

tony

---

First of all, Rom, how dare you listen to the user community! I protest!

Second, is the 4.70 version going to be released across the platforms? We have not had an OS-X version in synch with WIndows for some time ... or, am I going to have to spend a couple weeks figuring out how to compile it?

Paul, I found an OS-X version over at the Berkeley download page, along with the 4.70 pdb. I don't know how recommended it is, though.

http://boinc.berkeley.edu/dl/

Yeah, I saw that too ... well, I did the magic here which should force an upgrade out of UCB ... I updated all my machines to 4.45 ... history says that as early as COB today, or within the next week, we will see a new version become the recommended ...

---

Boinc 5.00 was intended for Alpha ONLY, and so it follows that 4.70 is for Alpha ONLY.

I'm not so sure. If he would have wanted the Alpha's only to use it, he'd have posted it to the Alpha email list only. Emailed the Alphians the whole file, if needed.

He then also wouldn't have posted it on here. Nor would he have given this part as an excuse:

I would like to apologize in advance for whatever flak you all might
experience due to the sudden policy change and resulting confusion this will
create with the community.

So maybe it's back to giving it to the people who can find it.

I'm running it since about 3 hours. I do like the "Won't get new work" message being back, I like it that the F1 button really works, my graphics still work, I didn't purge my whole WU list.

But most of all do I like it that in this one, when I update another project, change anything in the way it was (suspended, NNW), that it doesn't change the running project anymore. Only hitting Update would change the running project!

Having said that, anyone know what the following means?
07/07/2005 19:44:34|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500

---

Yes, Rom wants your scheduler request and answer files. Make sure you get the one with the error, and not one with a success that happens after ...

---

Yes, Rom wants your scheduler request and answer files. Make sure you get the one with the error, and not one with a success that happens after ...

Did so, thanks Paul.

---

I'm not so sure. If he would have wanted the Alpha's only to use it, he'd have posted it to the Alpha email list only. Emailed the Alphians the whole file, if needed.

Sometimes I believe the Alpha email list is read by more users then this board. ;) But always the development releases are at first for the Alpha test. Because everybody can compile his own release they are not protect as "Alpha only".

But it should always be clear that this are at first really "untested" releases. Alpha project is the testing area or the project. I personal didn't like this open policy. I hate it to read all this postings in the recent past, claiming bad development, producing untested, faulty releases one after the other. So please only donwload Alpha releases if you know what you do.

He then also wouldn't have posted it on here. Nor would he have given this part as an excuse:

I would like to apologize in advance for whatever flak you all might
experience due to the sudden policy change and resulting confusion this will
create with the community.

I believe he posted this for the users who asked him about this and got a wrong answer now, or are building addons and special clients and need a clear release policy. And for my feeling Rom was overruled in this step back and compromized by not optimal information flow. For my feeling it is not by him to apologize. I may be as guilty in this case as other. I am sure, this will not create a problem for Rom's reliabilty. :)

Having said that, anyone know what the following means?
07/07/2005 19:44:34|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500

I didn't saw it before, but as I remember there was a change to display the webserver return value in a message now. If this is correct, it should be the error: "500 Internal Server Error" - "The server encountered an unexpected condition which prevented it from fulfilling the request.". And that can be nearly everything, including scheduler shut down. ;) The messages in the log around this message may show more.

---

Greetings from Bremen/Germany
Jens Seidler (TheBigJens)

Sometimes I believe the Alpha email list is read by more users then this board. ;)

But it should always be clear that this are at first really "untested" releases. Alpha project is the testing area or the project. I personal didn't like this open policy. I hate it to read all this postings in the recent past, claiming bad development, producing untested, faulty releases one after the other. So please only donwload Alpha releases if you know what you do.

I read the alpha email list, Jens. Yet I hardly do anything with it.

But I do agree with you on the openess of the Alpha download list.
I don't mind testing things, I don't mind losing credits. Heck check my total and RAC on the left. ;)

Yet since there isn't an official Beta program anymore for BOINC itself, maybe that the developers want to know what we do with it.

As for Rom apologizing, it would've been about the strange development number, not the actual program, doing right or wrong. 4.50-4.99 are development numbers. Yet since 5.00 was retracted and 4.46 - 4.49 were used by Heffed, Rom and Tony, it left him no other option but to continue in the unused development numbers.

Anything higher than 4.99 would indicate a new development number to any server out there. So all server not optimised for 5.xx would stonewall 5.0x numbers.
So Rom released 4.70 ... we have to 4.99 now to test things. Alpha and those who feel they can be Beta.

The "Failed with a return value 500" error I sent to Rom already. Both my stderrdae.txt and stdoutdae.txt parts.

---

I've had no problems with 4.70 yet; no crashing, no sudden deletion of vital files, no processor hogging, no fatal errors, no BSODs, no memory leaks, nothing. I like this one a lot better than the 4.4x series, in fact, from what I've seen so far.

---

<img border="0" src="http://boinc.mundayweb.com/one/stats.php?userID=567" />
<a href="http://boinc-doc.net/boinc-wiki/index.php?title=Main_Page">BOINC Wiki</a>
<a href="http://www.tamaness.hostrocket.com/BOINC_team.html">Gideontech BOINC team!</a>

I have found a couple of bugs.

The idle check is not working, and non-cpu intensive projects can download too much work.

---

BOINC WIKI

The only thing I have noticed about 4.70 so far is the time has been extended on my prjects. (Einstein increased by 4.5 hours per WU, and LHC by 1 hour.)
Times are still correct on machine running 4.45. No crashes, BSOD, or stopped WU's. Have not tested the switching between projects as of yet.

Respectfully,

Rocky

---

www.boincsynergy.com

The only thing I have noticed about 4.70 so far is the time has been extended on my prjects. (Einstein increased by 4.5 hours per WU, and LHC by 1 hour.)
Times are still correct on machine running 4.45. No crashes, BSOD, or stopped WU's. Have not tested the switching between projects as of yet.

Respectfully,

Rocky

Is this the initial estimate? If so, does the new initial estimate match actual run times (at least approximately?)

---

BOINC WIKI

I have found a couple of bugs.

The idle check is not working, and non-cpu intensive projects can download too much work.

I have sent the fixes for these to Dave A.

---

BOINC WIKI

John, I installed v4.70 on 1 of my P4 HT Computers yesterday & when I started up the Client it showed 1 of the 2 WU's it was working on to have 5:29:30 hours left to run with 2:00:25 hours already computed.

This WU should have been done in about 2 hours total running time on this Computer so I watched it for awhile & the to do time dropped at a normal rate. I reinstalled v4.45 & the same WU was finished almost instantly as soon as I started up the Client and showed a total running time of 1:59:30.

I don't know if thats a bug with the v4.70 or not just thought I'd let you know about it ...