What version of BOINC is it?

Have you tried resetting it?

I think there is a limit to the maximum number of work units BOINC will send at once, so it is important that your connect interval is frequent enough not to make this a problem.

Well.....that may have been my fault.

On this computer, I was running one of the alpha/beta versions, 5.7.0 that was suggested to try here (just to see how it works.)

I had forgotten that it was there, and this scheduling difference was the only problem I had noticed.

After I take a look-see at the new UD project, I will go back to the recommended 5.4.11 version for Windows.



As for loading more workunits, here's what you need to check.

In the network section of the default BOINC profile, there's a parameter to connect to the network every so many days.

Connect to network about every [ ] days

The default is set to 0.1, which only works out to every 2.4 hours. Most of us set that to at least 2 days. Do not be tempted to set it too close to the 7 day due date, or workunits may run too long if there is a computer problem or something.

The number of workunits will be downloaded that your computer can run in the time you set. It is based on estimates, so it may take a few days to finally settle down and learn what your computer has been sending.

The little problem I was having was a special case. When I go back to the standard BOINC version on this computer it will probably take care of itself. The other computers have "x" days worth of workunits to work on, minus those that have been finished during the outage period.