well in all fairness, the BOINC developers couldn't have accounted for all the various nVidia and ATI GPU applications that would eventually pop up as faster, more efficient alternatives to classic project apps. though with the advent of the multi-GPU crunching machine, you'd think that all these recent revisions of the BOINC client would allow it to play nice with all the anonymous GPU apps out there...

Well, I'm willing to cut them a lot of slack, but when you try to start a task that has ZERO probability of success to complete, and you knew that in advance, one has to draw the line somewhere! ;-)

<edit> This is BOINC. I set some log parameters, and it's tryiing to start stuff it shouldn't. There is just no way it can run at the time split selected.

well in all fairness, the BOINC developers couldn't have accounted for all the various nVidia and ATI GPU applications that would eventually pop up as faster, more efficient alternatives to classic project apps. though with the advent of the multi-GPU crunching machine, you'd think that all these recent revisions of the BOINC client would allow it to play nice with all the anonymous GPU apps out there...

Also, Sunny's computer has one project that uses CAL(MW) and one that uses OpenCL(SETI).

Cal recognizes both GPU's as available resources, while OpenCL only recognizes the 4850.

To Cal:
Device 0: HD3300
Device 1: HD4850

To OpenCL:
Device 0: HD4850

Maybe when they start the betas for 6.14.x, they will have OpenCL detection implemented.

---

well in all fairness, the BOINC developers couldn't have accounted for all the various nVidia and ATI GPU applications that would eventually pop up as faster, more efficient alternatives to classic project apps. though with the advent of the multi-GPU crunching machine, you'd think that all these recent revisions of the BOINC client would allow it to play nice with all the anonymous GPU apps out there...

Well, I'm willing to cut them a lot of slack, but when you try to start a task that has ZERO probability of success to complete, and you knew that in advance, one has to draw the line somewhere! ;-)

<edit> This is BOINC. I set some log parameters, and it's tryiing to start stuff it shouldn't. There is just no way it can run at the time split selected.

My point was the CC tried to restart on a core it knew wasn't possible to run on, and that lead to a dump of every WU for every project on the host.


That's a pretty severe penalty, regardless of who's at fault! ;-)

Is there any use in compiling a 64bit version?

@ Sunny129

Hmmmm,

I have an M4A78T-E which has the HD 3300 (RS780D), along with an HD 4850.

I'm running straight stock for MW but also crunch Collatz and I'm not having problems with trying to start MW tasks on the integrated since the update to 59.

On the earlier versions it would try and start one on the 3300 if I snoozed the GPUs and then re-enabled them though.

you bring up a good point. i should see if its even necessary to edit the cc_config and restart BOINC in order to switch from S@H to MW@H (or back again) now that i'm dealing with the new MW@H v0.59. i'll experiment with it over the next day or two and report back.

well i've confimed it - i do not need a cc_config that ignores the integrated GPU in order get MW@H to run correctly on the 5870. one particular problem i had before was that a 2nd task would try to start running on the integrated GPU while another task was already running on the 5870, causing it to error out. that doesn't happen anymore w/ MW@H v0.59. however its just as much manual labor to remove the cc_config file from the BOINC data directory every time i watn to switch over to the MW@H project than it was to simply edit the cc_config file to ignore another device. and i still have to restart BOINC between switching GPU projects/apps.

honestly i didn't expect that to change though, especially when you consider what Arkayn said about my rig a few posts up - MW@H is a CAL app that recognizes both of my GPUs, while S@H is OpenCL and only recognizes the 5870.

---

Is there any use in compiling a 64bit version?

Not until this one is fixed.

My MW is still using 100% CPU.
I have 8 CPU cores and 2 GPUs. Normally I run E@H on all 8 CPU cores but have had to use only 6 since MW now needs 2 cores to run 2 GPUs at full speed.
Win7 64 with HD5970
http://img84.imageshack.us/i/milkywayi.jpg/

My MW is still using 100% CPU.
I have 8 CPU cores and 2 GPUs. Normally I run E@H on all 8 CPU cores but have had to use only 6 since MW now needs 2 cores to run 2 GPUs at full speed.
Win7 64 with HD5970
http://img84.imageshack.us/i/milkywayi.jpg/

Think I figured out what's happening (but why?). You're running 2 GPUs. See my post here:

http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=2338&nowrap=true#47700

...Catalyst 11.3 drivers might still be worth a shot, as Windows XP 32-bit users have generally been having luck with these drivers.

I can confirm that 11.3 has mostly solved the UI responsiveness problem but it's still on the order of 0.5sec sometimes to echo a character to the screen. It also looks like it's dropped the % activity on the GPU when MW is running. Will have to monitor for awhile.

...Catalyst 11.3 drivers might still be worth a shot, as Windows XP 32-bit users have generally been having luck with these drivers.

I can confirm that 11.3 has mostly solved the UI responsiveness problem but it's still on the order of 0.5sec sometimes to echo a character to the screen. It also looks like it's dropped the % activity on the GPU when MW is running. Will have to monitor for awhile.

are you concurrently running any CPU tasks?

---

are you concurrently running any CPU tasks?

Yes. BOINC is running the CPU WU's at Low priority and the MW 0.59 ATI client at BelowNormal.

oops...accidental post...

---