Version 6.10.17 Recommended
Posted: Sun Nov 01, 2009 11:04 am
Just a heads up for any one who likes to keep up to date with the BM.
http://boinc.berkeley.edu/download_all.php
Mark
http://boinc.berkeley.edu/download_all.php
Mark
20th June: Website now working again! - and after 21 years UBT is still here and we continue to crunch :-) (PS: I still have no idea where the UBT logo went !)
https://www.ukboincteam.org.uk/newforum/
https://www.ukboincteam.org.uk/newforum/viewtopic.php?t=4395
Just done as suggested, though mine said <ncpus></ncpus> , reloaded 6.10.17 and all good now.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.
I've got a similar problem on one machine, John, although it's an improvement on how it used to be when it wanted to run both MW and Collatz together on one ATI GPUTemujin wrote:I have 1 machine that just wants to run Collatz, the only way I can get it to run MW is to suspend Collatz