Well, you appear not to be asking for CPU work. So, you shall get none. CPU fetch share 0.000.......
While the Nvidia shortfall is 1210351.79....
So that work request still appears to be seeking GPU work.
Did you disable GPU in your Seti@home preferences and update?Always remember.....kitties are all Angels with fur.

You probably know this, but that deferral can be reset by going NNT/Manual update/allow new tasks. Also resets the work fetch deferrals that you see on project properties if they have escalated due to unsuccessful fetches. Another Fred
Support SETI@home when you search the Web with GoodSearch or shop online with GoodShop.

Well, you appear not to be asking for CPU work. So, you shall get none. CPU fetch share 0.000.......
While the Nvidia shortfall is 1210351.79....
So that work request still appears to be seeking GPU work.
Did you disable GPU in your Seti@home preferences and update?

Well I cant now find the setting. I can only find diable GPU while computer is in use.

Sorry for the finnish. Boinc somehow puts the options in Finnish although I would actually prefer English.

Well I cant now find the setting. I can only find diable GPU while computer is in use

Website project preferences, in English "use Nvidia GPU" (or ATI). That doesn't block crunching what you have, just tells BOINC on the next update to stop asking for gpu work.Another Fred
Support SETI@home when you search the Web with GoodSearch or shop online with GoodShop.

Try this.....
Go to your home account page.
You should see......
SETI@home preferences.
Click that.
Should show you primary (default)preferences.
If you have not selected any other venues......that's the one your rigs are working with.
You should see 'use ATI GPU' yes or no.
And 'use Nvidia GPU' yes or no.

Click them to NO and the server will not attempt to send you more GPU work.
GPU processing on the tasks you have on hand is not affected.Always remember.....kitties are all Angels with fur.

Go NNT to work down the unreported tasks. You don't have to wait the 5 minutes when on NNT. The option Kittyman mentioned is

<max_tasks_reported>50</max_tasks_reported>

din the options section of cc_config.xml. You may want to try 100 instead of 50. Max accepted is now 256 per a recent post. The less you try, the better the probability - but you have a lot more than I have to deal with.Another Fred
Support SETI@home when you search the Web with GoodSearch or shop online with GoodShop.

Allowing the update with No New Tasks was news to me. Thanks for the tip.

-Mark

I do it with the new tasks report included, and works......
But, things are rather hit and miss these days.
I have, at least as the servers think, about 44,000 tasks in cache. Distributed across 9 rigs. Have no clue how many of those are on board or are ghosts.
Rigs are all still crunching hard and reporting on a regular basis.

I know they are all begging the servers for more kibbles, and getting denied every time. Due to the darn limits now imposed. No new work as far as I can tell since the 5th. But the server requests are still reporting the work.

Look, I got 9 rigs burning here.......
I cannot mind meld with them all.
I have to trust that the project will give them something to do, or I will shut them off to save the electric bill.
I still see over 43,000 tasks in play.......if ghosts are not a factor.
Which I cannot verify.
So far, the kitties have kibble.