I've read over the FAQ's and I think I'm doing this right. Boinc see's CUDA device and if I look at the seti@home data directory there's a *cuda*.exe executable there making me think that seti@home knows I have cuda however I have yet to see a cuda wu.

The only wu i get from seti@home is astropulse which my cpu does. My Macbook which has boinc (no cuda) gets non-astropulse work units so I think it's just limited to my cuda machine. In my preference it marked okay to allow gpu units. I even added a cc_config.xml file changing the parameters needed and still no go. gpugrid seems to work fine on my machine.

I'm at a lost, any ideas?

---

What version of BOINC are you using?

---

6.4.7 on a Windows Vista x64 machine.

---

You could try to move the CUDA-capable machine temporarily to a separate venue (home,work etc.), where you disable AstroPulse. I think to have read that 6.4.7 has scheduling difficulties with mixed workload (AP/MB).

With 6.6.x that problem should be resolved. So, you could alternatively wait for it to be released (or dare try a prerelease version :-).

Gruß,
Gundolf

---

Computer sind nicht alles im Leben. (Kleiner Scherz)

SETI@home classic workunits 3,758
SETI@home classic CPU time 66,520 hours

Thanks, I may just wait then.

---

I ran out of CUDA and all it was fetching was AP 5.03 units, filling the 'buffer', not allowing any other units. I aborted all but 1 AP unit, went into the prefs and said NO to any AP units, then clicked update and a TON of CUDA units filled up my computer. Then went back in and said YES to AP units and got a couple more of those to keep the CPU busy. I guess that will be my sequence until a fix is released. It works for me, and it is easy enough.

---