Has anyone managed to resolve the problem of running 64bit BOINC using WINE? It used to work and then a few versions ago it started crashing as soon as one went tot he advanced view. Some other things made it crash too but I forget what. I ask because of the decision not to release 32 bit versions any more for Windows meaning my WINE installation is stuck on 7.14.2

I have successfully been running 64 bit WINDOWS BOINC 7.16.11 under WINE on Ubuntu 18 with all the latest patches for over a year with no problems.

When the certificate issue arrived 2 weeks ago, all I did was shut down BOINC on WINE and copied the remp certificate to the proper folder, restarting BOINC as if nothing happened.

There are a few projects that I still can't attach to under WINE -WCG being one of them.

Thanks, just downloaded 7.16.11 and it seems to be working. Whether that is something that has changed since when it was crashing in BOINC or something in WINE I will probably never find out. (Unless I download some of the intermediate versions and try them.

There are a few projects that I still can't attach to under WINE -WCG being one of them.

Just tested WCG and downloaded an ARP task that is now running under WINE. I did have to update the certificate bundle though.

We had a problem a while back (maybe a couple of years) where the client crashed when trying to use OpenSSL in 64-bit mode on certain processors. I think Wine may have triggered the same bug.

The solution was to ship the v1.0.1s versions of the SSL libraries libeay32.dll and ssleay32.dll. The ones on this machine are dated Christmas Day 2019 - what was that about? It might jog some memories.

Edit - found it. "Confirmed v7.16.4 x64 installs and runs correctly on the Celeron." [J3455]. My final note on https://github.com/BOINC/boinc/issues/2470.

what's the reasoning for running the Windows version of BOINC under WINE on Linux when Linux versions of BOINC exist, run natively, and will likely have less issues?

---

what's the reasoning for running the Windows version of BOINC under WINE on Linux when Linux versions of BOINC exist, run natively, and will likely have less issues?

1. Some projects only have Windows apps (Gerasim for example).

Also for me personally:
2. The BOINC version running on Linux / Ubuntu don't let you use RPC (Remote control like BoincTasks) that easy).

3. Don't have to pay outrageous license fee for M$ Windows.

what's the reasoning for running the Windows version of BOINC under WINE on Linux when Linux versions of BOINC exist, run natively, and will likely have less issues?

Similar here, I run tasks from the testing site for CPDN and with that project, tasks are not multiplatform but different types for different OS types. I am taking a slight hit by running mine in a VM which allows me to carry on with my main site tasks at the same time. And I haven't had a Windows machine since ,99 and have no intention of getting one now.

PM from another on the CPDN testing site,

7.16.11 works with WINE5.03 which is what I am using but not with 6.x at the moment.

1. Some projects only have Windows apps (Gerasim for example).

OK

Also for me personally:
2. The BOINC version running on Linux / Ubuntu don't let you use RPC (Remote control like BoincTasks) that easy).

This sounds like a misconfiguration somewhere. I have no problem connecting BT to any of my linux hosts via RPC. check your rpc password file for errors as a first guess.

3. Don't have to pay outrageous license fee for M$ Windows.

"technically" there's no penalty to use windows without a license (win10). it works indefinitely. just ignore the little activation warning.

---