Why do I have to always reset to get new work?

---

Not sure about that! I'm assuming that you've tried the "Update" button? And you might want to look at the frequency that BOINC connects to the network within your preferences? Are there firewall issues here (doesn't sound like it).

Just a thought, but without more info, difficult to say why that would be the case.

Cheers,

Steve.

---

sounds like a debt problem, how many, and what other projects are you running?

do you have equal resource shares for projects, or are some more than others?

what size cache have you set? (your "connect to network every..." setting in your general preferences

download BoincDV (Debt Viewer), extract the EXE file to your boinc installation directory (usually C:\\Program Files\\BOINC) then run the boincDV EXE file and post the info that it gives you (in the box at the bottom) here so we can see what your client is doing
that'll be the most helpful thing really

resetting isn't a good idea, it should only be used as a last resort, and it isn't solving the problem, it just gets around it, so lets find the actual cause, because boinc is just obeying the rules you've set for it (which might mean not very much SETI work)

also i think i'd be worth you reading how the work scheduler works in the wiki

---

Want to search the BOINC Wiki, BOINCstats, or various BOINC forums from within firefox? Try the BOINC related Firefox Search Engines

Why do I have to always reset to get new work?

Don't know but if you continue you will slowly be getting fewer and fewer units to crunch. For every unit you do not return your host is docked that number off of the 100 allocated per day per cpu. It goes down pretty fast, and back up to, but you do not want to go there if you do not have to.
How about posting your messages here so we can see where the problem might lie.

---

From the number and times of the WU still showing that you have downloaded and then returned, it looks like either your Preferences are currently set to less than the default of DAYS = 0.1 and the crunch times on the systems you are currently using are taking longer than that, or there is some sort of Debit problem with Setiathome with all of the other Projects that you are running. Sort of difficult to understand what your "configuration" problem is with the two current setiathome active machines, and there is not much information on the other 115 inactive system ID's in your Setiathome account. Other than BOINCStats showing that you have been giving 75% of your time to setiathome.

If you have been Resetting the Setiathome project to get work from it when it has a large Debit to the other projects you run or the systems are in LDF mode for other projects, you are just causing more problems.