Yep, "--read_cc_config" does not bring the desired results.

P.S. If anyone needs the script working with ATI cards, lemme know. I don't own any of these red stallions, but it won't be hard to modify it.

---

... set clocks and fan, modify XML, restart BOINC.

I think - better first close BOINC, then change GPU clocks - it's not good to change clocks while SETI is running (may crash/hang ?)

Your observation that game need lower clocks and SETI works with higher clocks is strange - usually it is opposite.

script does not handle situations where BOINC core runs as service. If someone needs such functionality, let me know, I'll add it.

As you know Service install of BOINC can't use GPUs on Vista & 7 so it's highly improbable someone will need to enable/disable GPUs on Service install.

If anyone needs the script working with ATI cards, lemme know.

It's somehow stupid that BOINC have options

<ignore_cuda_dev>0</ignore_cuda_dev>
<ignore_ati_dev>0</ignore_ati_dev>

and not just

<ignore_GPU_dev>0</ignore_GPU_dev>
or
<ignore_Coprocessor_dev>0</ignore_Coprocessor_dev>

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

I think - better first close BOINC, then change GPU clocks - it's not good to change clocks while SETI is running (may crash/hang ?)

It works in this way - setting clocks before start, after exit of BOINC. The scheduler, part of this new version, has options allowing to manipulate when to run external programs, per instance - before or after BOINC, and, more important, to wait, or not to wait one to exit and then run next program in queue. This is important for programs which not allow more than one instance running at a time, like case with nvidiaInspector.

Anyway, its good precaution, although I have never experienced BOINC crash or whatever malfunction of BOINC/SETI software while changing clocks. Of course, the values used are safe, pretested before any actual SETI calculations, which may reach the server.

Your observation that game need lower clocks and SETI works with higher clocks is strange - usually it is opposite.

Some parts of GPU are not used or at least not heavily used by CUDA, like ROPs, TMUs, AFAIK. So they can fail during game, while not causing trouble with CUDA app.

---