And I'm sure that discussion will ensue sooner or later. :)

And I'm sure that discussion will ensue sooner or later. :)

This is when the BOINC message board needs a "like" button!

Well, the first one is going to be a dislike - the new models are going to be 32 bits. (Because this works.)

OK, I'll bite.

I am building a Ryzen 2600 (Ubuntu) machine for it. I am intrigued by the fact that even though it has only 6 real cores instead of the 8 cores for the Ryzen 2700, they kept the 16 MB L3 cache of the Ryzen 7 series. That could be very useful for the CPDN models.

I already have a Ryzen 2600, and it does almost 90% of the work that my 2700 does on most projects. That percentage may improve here. And I will be running on only real cores at first, since I would prefer faster results to more work units (assuming that they send me any to begin with).

the new models are going to be 32 bits. (Because this works.)

But think how boring it would be with no computers without the 32bit libs to report.

the new models are going to be 32 bits. (Because this works.)

But think how boring it would be with no computers without the 32bit libs to report.

They could do something they should have done years ago.

They can spend 10 minutes and add some test code that executes first and prints messages in the event log. The messages would tell what libraries are missing. It would be a trivial couple lines of code to add.

---

They can spend 10 minutes and add some test code that executes first and prints messages in the event log. The messages would tell what libraries are missing. It would be a trivial couple lines of code to add.

While I am sure the average Linux user knows more about their system than the average Windows user and so a great many of us will be able to find the 32 bit libs, with Ubuntu withdrawing support for 32 bit computing, adding those libraries will not be straightforward for some even if the event log would tell us what the missing libs were.

Also unless I am mistaken the, "trivial couple of lines of code" would need to be in the BOINC client rather than the executables sent by CPDN. Even if a request is put in to the volunteers maintaining BOINC now, I don't see it happening in a hurry!

They can spend 10 minutes and add some test code that executes first and prints messages in the event log. The messages would tell what libraries are missing. It would be a trivial couple lines of code to add.

While I am sure the average Linux user knows more about their system than the average Windows user and so a great many of us will be able to find the 32 bit libs, with Ubuntu withdrawing support for 32 bit computing, adding those libraries will not be straightforward for some even if the event log would tell us what the missing libs were.

Also unless I am mistaken the, "trivial couple of lines of code" would need to be in the BOINC client rather than the executables sent by CPDN. Even if a request is put in to the volunteers maintaining BOINC now, I don't see it happening in a hurry!

I was thinking of weakly linked libraries and CPDN issuing BOINC EVENT LOG messages when they detect the libraries are absent. Seems like that adding the WEAK option to the link and then testing each of the libraries before plowing into computation is a one-time effort. If the user knew which libraries were missing, it is far easier to add them.

I think the average BOINC user is able to read the BOINC log for error messages.

Whatever CPDN does is fine with me. I agree with you, I don't see it happening in the near future.

---