While I was away for a week, for some reason the E@H work unit decided to go into 0 cpu usage and caused the 4.19 version of the client not to continue on. Of course during this time various results passed there deadline.

After I got back I upgraded the boinc client to 4.43. I then aborted the results that had expired. Everything started scheduling fine.

Then the boinc client decided that it needed another CDPN result to work on (I don't know why since it still had 300 hours left on the one it was currently working on).

The E@H result started doing its no cpu thing again but at least with the 4.43 client the client still swapped to other projects.

At this point I suspended the E@H project to stop it wasting time while I waited for a responce to my query on the E@H web site.

Scheduling continued, predictor, seti and CDPN were all getting their share, until predictor and seti ran out of results to process. No more results seem to have gotten downloaded,

I assume it is because it has decided that there is enough work in the CDPN that it does not need any more. And since the CDPN work units will take a couple of months, then no work will be done on this computer for anything but CDPN.

Geoffrey

---