Is BOINC 4.43 compatible with CPDN? I just upgraded because my primary project (SETI@HOME) is using that version. I\'ve seen reports that this version is buggy, and we should use a newer version, but this is the latest version available....

IS 4.43 compatible or is there something else???

There is a higher numbered version recommended for Windows, but not Linux.

If you were only running CPDN, you might prefer to stick with 4.19 (available here and from Berkeley) and let others do the debugging. But you should be able to use 4.43 - just take regular backups in case not.

> There is a higher numbered version recommended for Windows, but not Linux.
>
> If you were only running CPDN, you might prefer to stick with 4.19 (available
> here and from Berkeley) and let others do the debugging. But you should be
> able to use 4.43 - just take regular backups in case not.
>
>
Thanks... I shut down BOINC and copied the incomplete 4.19 WUs to the 4.43 version and restarted BOINC. I was getting an error before about no work and I was only allowed one work unit per day... Hopefully this will be cleared up once I finish crunching this WU.

I'm running Boinc 4.43 since few weeks w/o any problem. The only issue I noticed is the wrong value of the progress status. For CPDN, the progress status indicates the progress in the current phase.

Side Effect 1 : The completion time is always over estimated when you are running phase 2 or 3 (especially true a the beginning of a new phase).

Side Effect 2 : The first side effect leads often to a wrong over-committed condition in the scheduler. If you run multiple projects, it's a problem because you would not receive WUs from other projects as is should.

So, if CPDN is your main project you can install and run BOINC 4.43 on your computer elsewhere wait for next release.

I'm running BOINC 4.43 since some days too, no problems :-)
<br><br><br>
-------------------------------------------------
<a href="http://climateapps2.oucs.ox.ac.uk/cpdnboinc/team_display.php?teamid=43">Linux Users Everywhere <i>@ climateprediction.net</i></a>