I tried posting this on the BOINC boards, but it won't take my login over there, so I thought I'd give you guys a heads up.

BOINC Versions:  5.8.15 and/or 5.8.16 (could be one, the other or both, not quite sure)

What's happening is this:  Seti is set up as the primary project at 100%, and rosetta and WCG as backups at 1%.  Each box has seti downloads in the transfer queue, but as we all know you can't actually get the wu.  All of the backup projects have negative short term and long term debt and overworked status.

What's happening is that it's counting the stuck seti downloads as work, and it won't download wus from the backup projects unless you suspend the primary project.

I noticed this when some of my dual cores were only running one process.

I'm trying to keep an eye on this to see if it's just one particular version or both.  So make sure you have the right number of processes running on all of your boxes.

Maybe one of you more familiar with BOINC, or someone active in the beta project can shed some light on this.

Yes, I know, but the point is that boinc shouldn't count wus queued to download as if they've been downloaded, and should automatically download from the other projects when a core or cpu goes idle.  You shouldn't have to suspend a project or set it to no new work in those circumstances. 

Plus, if you haven't been watching, and you have backup projects, your machines might be going idle.

Ok, apparently it will get some work under both versions, but it's flakey.  At one point the quad had only 1 tasks running and it requested 2 wus but wouldn't request the third.  I upgraded boinc from 5.8.15 to 5.8.16 on that box, and it still wouldn't request new work so I had to suspend seti, and then it downloaded  a buttload of wus from WCG.

As I said before, I'd report the problem, but I can't seem to log into the BOINC boards.