I have been running Win 7 (64 bit) on an AMD X4 processor and using ATI's Cat 10.2 with no problems. I just downloaded ATI's Cat 10.3 and BOINC would no longer establish com with the local host. The client was up an running but no com. I uninstalled Cat 10.3 and reinstalled Cat 10.2 and now everything is back to normal.

The problem is related to an environment where a hybrid HD4200 and a PCIe HD 4850 are active at the same time. Cat 10.2 had no problem with this environment, but Cat 10.3 does.

accidental post.

---

Cheers,

PeterV

.

The problem is related to an environment where a hybrid HD4200 and a PCIe HD 4850 are active at the same time. Cat 10.2 had no problem with this environment, but Cat 10.3 does.

Can we take it that you were running them in Crossfire X?

Just asking because I got my hands on a copy of 7, and I've been toying with the idea of trying it out on my ATI powered Ph II X4 955.

Alinator

I see another odd 10.3 issue with my 5870. WU's used to take ~1:30 to complete prior to 10.3, now with 10.3 the WU's sit at 0% for 1:40 then they jump up to 142% complete and it takes them ~20 seconds to count down to 100% at which time they will upload; there is also a 10 second overlap where the 2nd WU starts before the first has finished the countdown. Boinc 6.10.18 and 10.3 = fubar. Why can't ATI write a driver that works?

That is not a 10.3 issue, but a 0.21 app issue.

You need to update the app you are using to fix that problem.

http://www.arkayn.us/milkyway/

---

That is not a Cat 10.3 problem. It's the new Wu's that MW has put up. Everyone has that problem and the longer Wu's don't pay any better.

@ Arkayn: We posted at the same time. HeHe