On Wed, 28 Oct 2009 17:01:45 -0700, DaveT wrote:

Well. Either I screwed it up or I fixed it. I put a cc_config.xml file in 
C:\Documents and Settings\All Users\Application Data\BOINC 
containing the lines:
<cc_config> 
    <options> 
       <ncpus>4</ncpus> 
    </options> 
</cc_config> 
Then I did a "Read Config File". Boinc freaked out for a bit and couldn't connect to the client.
Then all the tasks dissappeared. I stopped and started Boinc a couple of times. Then I renamed the
cc_config.xml to X cc_config.xml and stopped and started Boinc. Now it seems to be working with four
CPU tasks and one CUDA as expected. I guess it's fixed, I dunno. Thanks. 

The cc_config file was needed when cuda workunits first came out
because the Boinc manager didn't know anything about gpus. It only
allowed as many jobs as cpus to run so if a cuda job was running on the
gpu there was a cpu doing nothing. For 4 cpus and one gpu you would set
the ncpus to 5.

The current version know about the gpu so you don't need the ncpus
option and it upsets things if there. I can't remember if it causes
workunits to fail but since things are now working I'd delete it and
just keep my fingers crossed :-)

-- 
Regards - Rodney Pont
The from address exists but is mostly dumped,
please send any emails to the address below
e-mail	ngpsm4 (at) infohitsystems (dot) ltd (dot) uk