http://boinc.berkeley.edu/download.php

BOINC 6.10.17 is now recommended for all platforms. Windows 98/ME support has stopped, you need Windows 2000 or above to be able to install it.

The major change is ATI detection. Besides being able to run CUDA coprocessors, you can now also run work on ATI GPUs. Only a handful of projects that use it though.

Version History
Change Log for 6.10.0 to 6.10.17

---

Rom Walton wrote:

We are pleased to announce that 6.10 is now ready for public use.

This release of BOINC contains the following enhancements:

1. Support for ATI GPUs

2. Support for detecting proxy configurations within companies

3. Improvements to the CPU/GPU scheduler

4. A new default screen saver

I would like to thanks everybody who has used a pre-release version of 6.10 over the last couple of months, for providing feedback and helping us make the BOINC system even better.

Release Notes: http://boinc.berkeley.edu/wiki/Release_Notes

System Requirements: http://boinc.berkeley.edu/wiki/System_requirements


----- Rom

BOINC Development Team

[/quote]

---

Tried to open on my G5 Dual Processor running Mac OS 10.5.8. No joy. Doesn't recognize me as Admin and wants me to add myself as a User via a Terminal Application Tool. Need help to do that, but why do I have to if I'm Admin? Why doesn't it open immediately? (Been running SETI/BOINC for 12 years with ease, till now).

---

I have Snow Leopard, 10.6. Very professional installation this time around. I selected all users, to admin Boinc. It works as expected.

For those out there, with an Administrator account and limited user accounts, who do not want to execute Boinc as Administrator do the very simple steps below, logged on as Administrator:
1) Open System Preferences->Screen Saver. Deselect BOINC and reselect the screen saver you used to use as Administrator.
2) System Preferences->Accounts, Select 'Login Items' tab. Select Boinc manager. Check '-' below.

As each user, you will find the same account settings. Leave them as is, for users you want to run Boinc.

---

Two quirks i have with recommended BOINC 6.10.17 on 32bit windows xp sp3 :

1) After network connection was going unwantedly down a "slowly blinking" (2 seconds) popup from system tray icon was going on my nerves ("Network status"). To resolve restarting the client helped. The hint from the popup to do "Advanced->Do network communication" did not work.

2) The option "Advanced->shutdown connected client" repeatable does restart the client on first try. A immediately following second attempt really shuts the client down. No idea why.

These are no way showstoppers, but don't work as wanted i guess.

---

_\|/_
Urs

Tried to open on my G5 Dual Processor running Mac OS 10.5.8. No joy. Doesn't recognize me as Admin and wants me to add myself as a User via a Terminal Application Tool. Need help to do that, but why do I have to if I'm Admin? Why doesn't it open immediately? (Been running SETI/BOINC for 12 years with ease, till now).

If I am not mistaken, the Mac version comes with a Readme.rtf, from which it reads:

Due to new restrictions imposed by OS 10.6 Snow Leopard, there has been a change in BOINC's security implementation. Non-administrative users can no longer run BOINC Manager unless they are added to group boinc_master. As of BOINC 6.10.5, the BOINC installer asks whether or not you wish to allow this.

Although this change was made for compatibility with OS 10.6 Snow Leopard, the change in BOINC affects all users, not just those running OS 10.6.

The 6.10.17 Mac installer displays a dialog asking "Do you want non-administrative users to be able to run and control BOINC?". You should run the installer again and answer YES.

---

Jord, The Installer doesn't ask! I've tried 3 times to install and never get the dialog. I've had to use Time Machine twice to Restore 6.6.36. Any guesses on how to fix? (I'm also running OS 10.6.1 on my MacBook Pro, but I'm afraid to try to install 6.10.17 on it.)
Jruss

I'll report that back to the developer. Thanks for that.

Apropos, since I do not have a Mac, I don't know how to solve it either.
Just stay on 6.6.36 until we get a definitive answer on this.

---

Thanks....standing by while continuing to number crunch on 2 machines.

---

Just installed on Vista Ultimate x64 with no problems. One thing I did notice was that the CPU benchmarking gave higher results that previous Boinc versions? No big deal, just an observation.

Also installed 6.10.147 on a fresh install of Ubuntu 9.10. It works, but only after I installed 6.4.5 from the Ubuntu Software Manager, then uninstalled 6.4.5, and then installed 6.10.17. Strange. It still isn't quite right though. The "Tasks" tab only seems to update times and percentages when you move the mouse? And Boinc Manager doesn't stop all the tasks when I exit, and it still won't stop all the tasks even after I've selected to "Enable Manager exit dialog?" from the "Options" page.

Jord, The Installer doesn't ask! I've tried 3 times to install and never get the dialog. I've had to use Time Machine twice to Restore 6.6.36. Any guesses on how to fix? (I'm also running OS 10.6.1 on my MacBook Pro, but I'm afraid to try to install 6.10.17 on it.)
Jruss

A couple of questions:
[1] Just to make sure I understand your problem, what is the exact wording of the alert you see with BOINC 6.10.17?

[2] Does the user under which you are trying to run BOINC have administrative privileges? (If you open the Accounts System Preferences, is the box "Allow user to administer this computer" checked?)

---

Charlie Fenton
BOINC / SETI@home Macintosh & Windows Programmer

The "Tasks" tab only seems to update times and percentages when you move the mouse?.

I'm having this issue under CentOS 5.4 with latest Nvidia drivers, too.

Using ATI Catalyst drivers 9.10 with 6.10.17, I found out that the clocks of my 4870x2 go to 3D mode and stay there all the time BOINC Manager is running.
This is happening without SETI having work to crunch on the GPU.
Is this normal?

The "Tasks" tab only seems to update times and percentages when you move the mouse?.

I'm having this issue under CentOS 5.4 with latest Nvidia drivers, too.

Also updated another box from 6.4.5 and same thing. This time Fedora, non-cuda Nvidia card, fedora-supplied video drivers.

Another box, CentOS 5.4 with ATI integrated video, OS-supplied drivers appears to be ok.

I've had trouble with both this version and 6.10.16. On a AMD64 - no probs. On the Q6600 quad though, for some reason it sets the 'Use CPU cores' to 0. All 4 cores just sit there with 'waiting to run' showing. GPU still runs fine. Tried all sorts to get them started but the manager just over-rides anything I put in. So I've had to revert back to 6.6.38.
Windows 7, stock speeds, 4 gig RAM

Using ATI Catalyst drivers 9.10 with 6.10.17, I found out that the clocks of my 4870x2 go to 3D mode and stay there all the time BOINC Manager is running.

I'm not sure how you deduct that they "go to 3D mode". What program do you use for that?

This is happening without SETI having work to crunch on the GPU.
Is this normal?

As you've been told on Seti already, that project doesn't even have work for your GPU. When it has work (at this moment very little), it's for CPU and CUDA (or Nvidia) GPUs only. Not for ATI GPUs. And for the foreseeable future there won't be an ATI compatible app available from Seti either.

So if you only do Seti, or at least do no work for the projects that actually support ATI GPUs, there's no real use for you to allow BOINC to detect the GPU at this point. And really, simply said, that's all BOINC does: detect if a certain DLL file is present on your system and from that deduct that your ATI card is capable or not to do Brook+/CAL calculations on those projects that support it (Collatz and Milkyway). (If you want to see what it does in detail, read through Coproc.cpp)

And so, you can easily disable the GPU detection. To do so, make a file called cc_config.xml in your BOINC Data directory, or edit an existing one. The file doesn't come with BOINC, you will always have to make it yourself.

Add into it the following lines:

<cc_config>
    <options>
        <no_gpus>1</no_gpus>
    </options>
</cc_config> 

Save file, exit BOINC & restart it. A simple Advanced->Read config file won't do in this situation.

---

On the Q6600 quad though, for some reason it sets the 'Use CPU cores' to 0. All 4 cores just sit there with 'waiting to run' showing.

Please check in your BOINC Data directory if you have a file called cc_config.xml
If you do, open it and look for the line <ncpus>0</ncpus>.
If that one is in there, either remove it, or change it to <ncpus>-1</ncpus> (that's minus one). Then exit BOINC & restart it.

The ncpus line is really only for debugging, it can be used to run more tasks per CPU than you actually have CPUs. In BOINC 6.4.5 to 6.5.0 it was used to add 1 so you could run work on the CPUs and GPUs at the same time.

In BOINC 6.6 the separate CPU and GPU schedulers were added, so you wouldn't need this line. You probably changed it at the time to <ncpus>0</ncpus>.

This later changed as the possibility was added to not run work on the CPUs, but only on the GPU. So to disable all CPUs, a value of zero for ncpus was no CPUs, To disable the ncpus option, the line either had to be removed or it had to get the value of minus one.

This change of how it worked was never back-ported properly to release versions of BOINC 6.6.

---

For all, I have updated my CUDA & CAL FAQ.

---

Installed on 2 hosts (WinXP SP3 32bit) and I've noticed that when hovering over the BOINC icon in the taskbar it shows the state of the workunits when the BM was last exited and not the current status.

---

Please check in your BOINC Data directory if you have a file called cc_config.xml
If you do, open it and look for the line <ncpus>0</ncpus>.
If that one is in there, either remove it, or change it to <ncpus>-1</ncpus> (that's minus one). Then exit BOINC & restart it.

Thank you - that cured it! The line was "<ncpus></ncpus>" - now <ncpus>-1</ncpus> and all tickity boo!