Does not effect the results DM, just inflates buffering and if small without impact, but if you run 2-3 or more days buffer and see the DCF rapidly go down to 0.3 or lower, you suddenly have more cache than the deadline of 10 days, this going into a high priority processing state and never coming out, for the moment it does you're backfilled with too much work. Also you're knocked out the 'reliable' range if that matters. Those that run a mix of projects some having shorter deadlines including 3 days might discover other undesirable side effects and I've experienced a few, soliciting words I could not print here.

Was that a trick question ;? Well, there was recently a recommended 6.6.36 recommended, then a 6.6.38, which had 'special behavior' that made people go back to 6.6.36 and we had 6.6.40 in the coming and in no time 6.6.41 now 'recommended'. Who's going to take 'recommended' seriously here? (Not a trick question).

Forums still down, Trac down, official BOINC wiki down, the BTS translation service down... somehow a frequent weekend event, I think, when people who work Monday-Friday, not on BOINC, have time so read up and maybe download... oops that's down too, which means not even the WCG version can be obtained...hmmm, now that has suction.

edit: The download direct link does work now, but very very slowly, to the point of timing out.

All versions is tested before release, but it's impossible to test for all combination of software users can be using, so ocassionally something unexpected happens.

The "end-of-line" in a serie like v6.6.41 is, mostly only has a single or a couple changes from previous version, so testing in these clients is normally concentrated on these changes and not everything else.

But, the changes will also be included in the next alpha-release, if it's not already present, and gets tested as part of alpha-testing.


So, looking specifically on v6.6.41, there's 4 changes since v6.6.38 (not counting the linux/mac-specific changes). All of the changes has been tested in v6.10.xx without AFAIK any problems popping-up. So, why these changes gives any problems in v6.6.41 I've got no idea about...


But anyway, v6.10.17 is now released for all platforms:


As always at the start of a new client-serie, there will be more releases, to fix some known bugs (if a bug is also present in previous release-serie, it won't normally hold-up release of a new serie), or a known bug only affecting a small minority of users. Also, there is always some unexpected problems popping-up when more users starts to use a client, that needs to be fixed.

Appart for mentioned in the announcement, a couple facts:
1: Win9x and WinMe won't work, last supported build for these OS is v6.6.38. Not explisitely mentioned, but it's possible this is also true for win2k.
2: Supports Win7 and Snow Leopard.
3: Known bug, if running AQUA@home, there's some problems with SMP-scheduling, should be fixed in next release.

I have an Intel server motherboard with 2 - E5520 Intel Xeon quad core processors. When first built it was running W7-64bit RC with BOINC 6.2.19. At the time it was running 16 jobs at a time and cranking out ~38,000 points per day.

I just upgraded to W7-64bit RTM Home Premium and BOINC 6.10.18. Now it only runs 8 jobs at a time and the point total is off about 75%.

Any ideas what I need to do to get it running at full speed again? Should I go back to 6.2.19?

I'm not aware of any problems! According to BOINC's website, 6.10.18 is now the recommended version. I've been running that on a few computers now for a few days and have not encountered any problems.