Thank you.

For reference, the Windows CPU app version 1.05 and prior were bugged, and the Windows 1.06 version is the version that hopefully fixes it. I'll let you know once these 2 hosts get some 1.06 tasks :) They may be blacklisted at the moment lol.

Thanks again,
Jacob

One of the 2 laptop clients was finally able to get some CPU work, and... IT WORKS! The 1.06 CPU app (which is compiled against the non-bugged BOINC API) appears to have solved the problems I was having. Thanks!

One of the 2 laptop clients was finally able to get some CPU work, and... IT WORKS! The 1.06 CPU app (which is compiled against the non-bugged BOINC API) appears to have solved the problems I was having. Thanks!

Neat. Thanks for ferreting out the source of the problem Jacob.

Matt

You're welcome. Finding/fixing problems is the main reason I am attached to 26 projects across 4 devices of various Windows installations, running alpha versions of BOINC :)

I am aware that we are partway through the weekend or leading into it. Will there be more CPU work in the coming days or does the returned at work need to be looked at to see where to focus is going next? There currently looks like that there are only re sends.