Hey,for the first time in a long time,I got 50 WU´s without one single bad one,great !

There are propably now new workunits in the send queue, so it should be ok now.

I am not getting any work to process no matter how many times I select update.
It has been a week and nothing. I removed a@h and rejoined again and only got 1 task that completed and was uploaded but no new downloads.

I am not getting any work to process no matter how many times I select update.
It has been a week and nothing. I removed a@h and rejoined again and only got 1 task that completed and was uploaded but no new downloads.

Look in your event log. Boinc is probably not requesting Asteroids tasks because you have so many Seti tasks waiting to run.

Thanks the seti work seemed to be the problem. I stopped getting new seti tasks and when they completed I started getting a@h work.
My projects tab says that resources are to be spread equally among the 3 projects I run, any ideas on why it overloads on seti?

---

Says and does are two different things. Try adjusting your A@H resource share upwards of your SETI resource share downwards until you achieve the balance you are looking for. As you have just found out, this is going to take time. It's not a race so let it.

any ideas on why it overloads on seti?

Yes I know of a few possible reasons for that but before spending a lot of time and energy discussing those reasons I would think about whether or not it always overloads on SETI. I would also suggest that what we think we see happening is not always what is really happening so if you think it's overloading on SETI all the time you might be wise to verify that with some hard data. You can gather statistics that show exactly how much time each of your project is receiving. Though it might appear to you that it's always overloading on SETI you might find the data proves otherwise.

If it's not always overloading on SETI then don't worry about it because it's not abnormal for BOINC to pig out on tasks from one project for a while then ignore that project and pig out on tasks from one of your other projects for a while. What is most important IMHO is the longterm results. To me it doesn't matter so much over the shortterm, I worry only that the project shares I set are respected over the longterm.

If it is a longterm problem then swiftmallard's suggestion is probably the easiest way to fix it.