I really don't understand why an installed client can't read the user controlled settings on the local system regarding GPU or CPU for each project as part of the fetch. The user can change those settings at the project site and can control for differing workstation settings by using different groups for different workstation configurations.

Barry,

Check out the BOINC message board again. We have progress: it'll need server updates as well as a new client build, and I can already see some fine tuning needed during testing, but the direction of movement is positive. Berkeley is not deaf, merely hard of hearing!

I really don't understand why an installed client can't read the user controlled settings on the local system regarding GPU or CPU for each project as part of the fetch. The user can change those settings at the project site and can control for differing workstation settings by using different groups for different workstation configurations.

Barry,

Check out the BOINC message board again. We have progress: it'll need server updates as well as a new client build, and I can already see some fine tuning needed during testing, but the direction of movement is positive. Berkeley is not deaf, merely hard of hearing!

And it begs the question what made them change their minds ... in famous pigeon expiriments they rewarded randomly and the pigeons developed elaborate "dances" to get the food pellet ... because it is what works ... just as one of my dogs knows that if she scratches on the automatic door that that is what causes it to open...

Now if they will start to address the myriad of other issues that are killing us ... like the strict GPU FIFO rule that negates resource share unless you run with no queue (or a very short one (0.1 days has been working, I have not increased it yet, maybe later this week)...

What is saddest is that as best I can tell the FIFO rule was added because of the execution order issues caused by bugs that have since been addressed in 6.10.7 ... sigh ...