No Teemu I have not reported anything to them. Until this discussion, I thought it was a Moo problem.

---

Running 7.0.28 in Vista with 1 HD4850 (i7 920 host) and it's going just fine.

I do too, but not on ALL of my machines, and that is the problem. If you switch away from Moo and then come back it doesn't always work. I have one machine that is Win7 64 bit ultimate with an AMD 5870 in it and it runs Albert just fine but won't even download a Moo unit! BOTH projects are set to 30% and are the ONLY two gpu projects on the machine yet all the machine crunches is Albert units!! On another machine I have both an AMD 5870 and an AMD 5770 and it crunches ONLY for Moo and works just fine, it is also a Win7 64 bit Ultimate machine. I do not know what the problem is but it could be the new scheduler, I HEARD that it was based on credits, trying to even out credits between projects before it shares, if that is true than for me that is a no go, as NO Other PROJECT will get to the level of my Moo credits ever again!

Indeed, but I could still add an advanced scheduler option that makes the scheduler to only ask for one resource even though the tasks will use all GPUs in the end. You just can't blame me then if you systems overheat or crawl to a stop due to overcommitting GPU resources. ;)

This would probably be easier than to make the full support for running one task per GPU but this would be first step anyway. (Such scheduler modification is needed anyway eventually.)

That would be a very useful addition. As far as overheating, they can't run any faster than 99% anyway, and TThrottle eliminates overheating worries altogether. Crawling to a stop? Haven't had that problem. The machines running the 1 ATI WUs on multiple GPUs along with POEM as outlined above are doing fine and using all the GPU finally too. This app_info trick (and hopefully soon a scheduler option) allows me to run Moo to a far greater extent than I could previously.

Indeed, but I could still add an advanced scheduler option that makes the scheduler to only ask for one resource even though the tasks will use all GPUs in the end.

Again, a very nice addition. Another useful addition for the advanced preferences would be to allow us to change the priority without having to edit the ini files.