You should update your BOINC anyway as the client you are using now doesn't do FLOP counting as the 5.10 and 6.2 clients do. This means that it is possible that you are requesting for and getting zero credits on Seti, giving your wingman zero credits as well.

Upgrading to a newer client should be painless. Read this FAQ and keep a good eye out in the 6.2 installer for the Advanced button in case you don't want to install the new version as a service.

BOINC 6.2 should install directly over 4.45, it should uninstall the older version if there are no corruptions of the older software's uninstaller. In any case, it should keep you attached to your projects. Do keep in mind that you'll need a reboot, or at least a log off/log on for the changes to catch on.

And if you have any questions or problems, just post about them, or look in the BOINC FAQs.

p.p.s.: The concept of Long Term Debts is a mess anyway (especially in combination with CPDN), I have a workaround for it though, that resets all values to 0 on a client restart.

That fails to respect your resource shares. A better solution would be to add code to the scheduler (or some other module) that diagnoses the situation and prescribes corrective actions to the user. The corrective actions would be to either:

1) reduce the resource shares for projects which cannot supply enough work to meet the shares, or
2) detach from the project, or
3) reset the debts

Reseting the debts on EVERY client restart is not a good idea when users are attached to projects that DO supply enough work to meet their shares.

The concept of Long Term Debts is sound as long as you attach to projects that can provide enough work to meet your resource shares. The scheduler attempts to respect shares that simply cannot be met. In other words it attempts to do the impossible in certain combinations of projects and shares. It cannot do the impossible so why not just have the software tell the user like "this cannot work, you need to make some adjustments". THAT would be sane. Attempting to do the impossible over and over and over every friggin day is NOT sane.

Easy to say, probably not so easy to code it. And I don't know how CPDN affects it, just some thoughts, FWIW.

EDIT: oops, did not see the date there... got here from google and resurrected a 2 year old thread, sorry.

In the mean time, the next upcoming BOINC 6.4 has GPU support. Thus far only for nVidia GPUs; ATI support will follow.

The CPU Usage function is a thermal throttle. As far as I know it has no integration into the work-fetch policy module of BOINC. Perhaps that eventually, after long enough use, that you'll see work-fetch decrease, but not from minute one.

It takes about a month for the work-fetch policy to adjust for throttling. It should make your % that BOINC is allowed to work drop down to approximately match the throttle setting. That will reduce the work fetch.

Is this advice based on latest clients or from longer past? I use Threadmaster GUI at 70% this moment on a quad and the DCF hiked to 1.44 rather rapidly and is staying in that area (Coincidence?). Maybe quads learn quicker than single core P4s ?!?