This is what I have figured out when it comes to all these version numbers.

My current core client is V4.05. (BOINC itself)
My current SETI client is v4.03. (Science, 'worker', application)

This is the notice from the dev team:

September 30, 2004
UPDATED: A new version (4.05) of the windows SETI@home client is available (and will be automatically picked up by your core clients next time you contact our servers).

When my current WUs get finished, my v4.05 core client will automatically download the v4.05 SETI client. I will then have v4.05 core and SETI clients.

I figured that this would help eliviate some of the confusion with all these version numbers. If I happen to be wrong, someone chime in and set me straight. But, I do not believe that I am wrong with this logic.

NOW:
I am now receiving this message from the scheduler:

SETI@home - 2004-10-01 17:38:30 - Message from server: A new version (4.09) of the BOINC core client is available from this project's web site.

I need to know that v4.09 has indeed addressed and fixed the dial-up problem of the v4.05 core client. Can someone please confirm this for me before I download and install v4.09?

L8R....

---

Rick A. - BOINCing right along now.... It can only get better! </p>
<img><img>

Consider this on my system

Boinc 4.09
Seti 4.05
LHC 4.46
Climate 4.04

It's generally better to have the latest version to get rid of small bugs. (I usually wait a day or two to make sure the file is good e.g. Seti 4.04 was corrupted when posted.)


I'm on dial up. I have no problem in that area.

> Consider this on my system
>
> Boinc 4.09
> Seti 4.05
> LHC 4.46
> Climate 4.04
>
> It's generally better to have the latest version to get rid of small bugs. (I
> usually wait a day or two to make sure the file is good e.g. Seti 4.04 was
> corrupted when posted.)
>
>
> I'm on dial up. I have no problem in that area.
>
>

When up/downloading WUs, the currently running WUs continue to run, or are paused and then re-started when up/downloading is finished? The problem was that the WUs would not re-start even though a message to the contrary was posted in the message tab. Thanks....

L8R....

---

Rick A. - BOINCing right along now.... It can only get better! </p>

> I need to know that v4.09 has indeed addressed and fixed the dial-up problem
> of the v4.05 core client. Can someone please confirm this for me before I
> download and install v4.09?

No it hasn't fixed the problem. But you really don't have much choice because you will not be able to get any more work using CC 4.05.

> > I need to know that v4.09 has indeed addressed and fixed the dial-up
> problem
> > of the v4.05 core client. Can someone please confirm this for me before
> I
> > download and install v4.09?
>
> No it hasn't fixed the problem. But you really don't have much choice because
> you will not be able to get any more work using CC 4.05.
>
>

You're saying that the v4.05 SETI core won't work with the v4.05 client core? Bummer.... I guess I will have to get v4.09 and continue to leave the network connection disabled until I'm ready to take care of things. :-(

L8R....

---




Rick A. - BOINCing right along now.... It can only get better!

"There is no fate except that which we create for ourselves."

Live Long and Prosper....

Yhere should not be a problem using Boinc CC 4.05. The original plan was when one was using CC 3.XX AND the new 4.xx was out, the scheduler would send a message to the CC stating that you need to upgrade to Ver 4.xx.
It should not matter untill Boinc CC 5.xx is out.
The reason was they had fix the bugs in one major version but was still getting the error from the old Version. so they came up with the major Version change.
Try with what you have Boinc message tab will tell you if you need to upgrade when it ask for more work from the schedule server.

Fred BOINC Alpha & BOINC Beta Tester

> Yhere should not be a problem using Boinc CC 4.05. The original plan was when
> one was using CC 3.XX AND the new 4.xx was out, the scheduler would send a
> message to the CC stating that you need to upgrade to Ver 4.xx.
> It should not matter untill Boinc CC 5.xx is out.
> The reason was they had fix the bugs in one major version but was still
> getting the error from the old Version. so they came up with the major Version
> change.
> Try with what you have Boinc message tab will tell you if you need to upgrade
> when it ask for more work from the schedule server.

There have been posts from people saying they are using 4.05 and get the message from the server saying they need 4.09.

Hi

I have 58 WUs left, but i noticed on my brothers machine XP 2800+ Win XP home running Boinc 4.06.
He was´nt getting work, but after installing Boinc 4.09 het got work smoothly with seti 4.05.

greetz Mike

Ok, I bit the bullet. I just downloaded and installed v4.09 core client. So far, the changes I've seen have been with benchmarks:

Whetstone: was 1437.87 - is now 1178
Dhrystone: was 2077.13 - is now 2088

I've also noticed that preempted WUs no longer say Preempted , they now say Paused .

Other than the above, everything seems to be running just fine. I'll have to give it a few days to be sure. I just wish they would have fixed the dial-up problem. v3.20 had no problem with it. v4.05 sucked when it came to dial-up and from what I understand, v4.09 isn't any better. Since it's the weekend, I may just enable the network connection and let v4.09 go at it to see for myself.

L8R....

---




Rick A. - BOINCing right along now.... It can only get better!

"There is no fate except that which we create for ourselves."

Live Long and Prosper....

> Consider this on my system
>
> Boinc 4.09
> Seti 4.05
> LHC 4.46
> Climate 4.04
>
> It's generally better to have the latest version to get rid of small bugs. (I
> usually wait a day or two to make sure the file is good e.g. Seti 4.04 was
> corrupted when posted.)
>
>
> I'm on dial up. I have no problem in that area.
>
>

You're running BOINC v4.09 and have no problems with dial-up? I read in a different post here that the problem hadn't been fixed in v4.09.

I'm still running v4.03 SETI client (many WUs in cache to finish) and v4.03 CPDN client (maybe no v4.04 for the same reason as SETI). I just started running v4.09 BOINC core client today, I waited about 2 weeks before moving to it.

L8R....

---




Rick A. - BOINCing right along now.... It can only get better!

"There is no fate except that which we create for ourselves."

Live Long and Prosper....

Mystery solved....! The following is a message I left in a different thread:

TEST COMPLETE

RESULTS OF TEST:
Well, the dial-up problem does indeed seem to be fixed. I shut down my dial-up connection, shut down BOINC and then restarted BOINC. BOINC made it's connection via dial-up, uploading here and to LHC, and when done my running WUs re-started as they are supposed to. YEAH!!!! I will now leave my network connection enabled in BOINC.

L8R....

---




Rick A. - BOINCing right along now.... It can only get better!

"There is no fate except that which we create for ourselves."

Live Long and Prosper....

> Mystery solved....! The following is a message I left in a different thread:
>
> TEST COMPLETE
>
> RESULTS OF TEST:
> Well, the dial-up problem does indeed seem to be fixed. I shut down my dial-up
> connection, shut down BOINC and then restarted BOINC. BOINC made it's
> connection via dial-up, uploading here and to LHC, and when done my running
> WUs re-started as they are supposed to. YEAH!!!! I will now leave my network
> connection enabled in BOINC.

It doesn't happen every time. It's better, but not fixed.

> > Mystery solved....! The following is a message I left in a different
> thread:
> >
> > TEST COMPLETE
> >
> > RESULTS OF TEST:
> > Well, the dial-up problem does indeed seem to be fixed. I shut down my
> dial-up
> > connection, shut down BOINC and then restarted BOINC. BOINC made it's
> > connection via dial-up, uploading here and to LHC, and when done my
> running
> > WUs re-started as they are supposed to. YEAH!!!! I will now leave my
> network
> > connection enabled in BOINC.
>
> It doesn't happen every time. It's better, but not fixed.
>
>

Well, I've been using v4.09 CC for about 36 hours now, leaving the network connection enabled, and everything has worked just fine. As a matter of fact, now get this, at certain times I will have 3, yes three, WUs being processed at the same time, but I believe this may have just been a weird anomoly. For quite a while now I have only seen 2 running with 4 preempted (paused).

When WUs get finished, BOINC dials up the network connection and uploads the WU. The currently running WUs resume after the upload is complete. The dial-up connection is shut down when there is no activity detected after 5 minutes. The real test will come tomorrow when I'm at work all day.

L8R....

---




Rick A. - BOINCing right along now.... It can only get better!

"There is no fate except that which we create for ourselves."

Live Long and Prosper....