Hmm, are you meaning the BOINC-client, or whatever web-browser you're connecting to the download-page with?

If the web-browser, Internet Explorer should correctly show the 64-bit-version, even if you're using the 32-bit IE-version. If it's not, there must be a Vista-specific bug somewhere...

Browsers like Firefox on the other hand incorrectly offers only the 32-bit-version. For these, please use this link instead, and download the client that's correct for you.


To give similar rating systems, both CUDA and Ati now shows the capabilities of the GPU, as defined by nvidia and Ati... so basically as accurate as showing Intel's or Amd's cpu-numbers would be...


Anyway, for the official announcement:

There will be more v6.10.xx-releases, including bug-fixes for any problems that always seems to pop-up, and include updates to translations.

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.
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.
4: If you're upgrading from v6.4.x or earlier, please note that BOINC Manager now shows the run-time and not cpu-time. So especially if you're not running with 100% cpu-usage, the displayed times will be longer than before, and larger than it will show-up as on the WCG web-page after returned. To show the cpu-time of a task, select it (in advanced view), and hit "properties" (one of the buttons down the left side of the Manager).

Also, a customized WCG-version will maybe be made later, if so there'll be one or more beta-versions announced in the WCG-beta-forum.

Since there will be more v6.10.xx-releases, there's in most cases no reason to upgrade now. For anyone that tries it anyway, please post about any problems or anything don't understand, so hopefully it's either possible for someone on the forum to help you, or in case of a real bug the bug can be fixed in a later release.

But of course, questions like "why does it refuse to install on WinMe" likely will be met with RTFM or similar.

RTFM = Read the "fine" manual...


edit - v6.10.17 has now been tested under win2k and it works, so removed the part about v6.6.38 being the last for win2k also.

The previous 6.10.x versions were Beta, so this is the first non-beta 6.10 release.
It includes some interesting changes, and has taken some time to develop. Many WCG people run other non-WCG tasks, including Cuda tasks. So they may appreciate the heads up. I only use the WCG client on one system for that very reason.
By the way, there wont be a new Boinc version every week – hyperbolic speculation is not helpful.
With that exception, I think the useful advice already added justifies this thread.

PS. I was using Firefox on the Vista system, and IE8 did offer up the x64 version!

I ran 6.10.x on several systems prior to the 6.10.17 release. The earlier versions did play about with the GPU task allocation, but by the end (6.10.16) I saw no problems.
I expect I will upgrade to 6.10.17 on my main systems, all systems that have a Boinc useful GPU and all systems that run x64bit platforms.
I will wait for the WCG client for one system that only runs WCG tasks.

Are you running a single project (WCG), or multiple BOINC-projects?

If multi-project, there's a bug in v6.6.36, so upgrading would definitely be a good idea.

If single-project, it's more unclear if upgrading will change your observed behaviour, but it's still possible upgrading will fix things for you...

Also, a couple things to remember:
1: For reporting results, there can be upto a 24-hour-delay, if no other reason to connect. For full list of reasons, see http://www.boinc-wiki.info/Ready_to_Report

2: If asking for work and you don't get anything, example if you've selected only a sub-project with little or no work and not enabled "send me work for another project", you'll get an exponential deferral bounded upwards starting at 1 minute, and doubling for each failure, upto max 24 hours. This info is displayed by selecting a project and hitting "Properties", and will show something like:
CPU work fetch deferred for (time)
CPU work fetch deferral interval (time)

The last shows current upper limit (blank if no problem), and the first shows how long until next time will ask for work (blank if no time).
Manually hitting "update" will reset both counters.

It's unfortunate that WCG calls each sub-project for a "project", since this can lead to mis-understandings. But as far as BOINC goes, WCG is a single project, and it doesn't matter for BOINC if you're running all of WCG's sub-projects or only a single.


"No work available" is normally a server-problem, not a client-problem, if the error-message isn't also accompanied with other messages, like example "won't finish in time".

So, if it's due to a current lack of HFCC and nothing else, changing clients won't change the behaviour. Increasing "additional..." cache-setting to maybe 1 day will probably help in this instance, since less chance of running-out of work before manages to re-fill with work.

If "no work available" is accompanied with something else besides listing the sub-project being out of work, please post the relevant messages showing this.