Looks like some of the latest downloads having a weird effect on my
OpenCL ATI crunching.
(WIN 7; 64bit, 8 GByte DDR3 1600; BOINC 7.0.25; 64bit)
BOINC's log shows only 1 ATI 5870 GPU, but also use all coprocessors?
Maybe a cc_config.xml in BOINCs map will do?
Or has it something todo with some updates?
Anyone with similar issues?

---

From the posts I have seen over the years using <use_all_gpus>1</use_all_gpus> to get all GPU's to work is often required.

Did you change from 6.x to 7.x or just an upgrade from and older 7.x to 7.0.25 when you noticed this?

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

From the posts I have seen over the years using <use_all_gpus>1</use_all_gpus> to get all GPU's to work is often required.

Did you change from 6.x to 7.x or just an upgrade from and older 7.x to 7.0.25 when you noticed this?

I'm running BOINC 7.0.25 for a month and work OK, also without a cc_config.xml file.

But, I received some WIN 7;(64bit) updates and the trouble started.
I just tried a cc_config, using all coprocs, but no joy?!
BOINC 7 states seeing all coprocs?!
Gonna check all recent updates.
This
host.

---

From the posts I have seen over the years using <use_all_gpus>1</use_all_gpus> to get all GPU's to work is often required.

Did you change from 6.x to 7.x or just an upgrade from and older 7.x to 7.0.25 when you noticed this?

I'm running BOINC 7.0.25 for a month and work OK, also without a cc_config.xml file.

But, I received some WIN 7;(64bit) updates and the trouble started.
I just tried a cc_config, using all coprocs, but no joy?!
BOINC 7 states seeing all coprocs?!
Gonna check all recent updates.
This
host.

It appeared, a update has disabled the AMD-APP 2.4, installed it again and problem solved ;-)

---