Or I thought it was fixed - it is on the machine that had a fresh install of 19.04. Something in the one where I did a do-release upgrade is still sitting around that makes the 64 bit crash.

You would need a license to run a Windows VM? Not quite.

Microsoft provided several VMs to make it easier for webmasters and website engineers to complete testing tasks over their websites. Use of this VM is quite legal, and you can always revert to a snapshot before its first power on. And, as you may already know, you can insert more virtual disks for you to store BOINC data there, to avoid losing data and current progress.

This is quite legal, it's stated on its website:https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/

In fact, you can use this script to "deactivate" and "rearm" this copy of windows several times before it finally expire, and use this copy for another 90 days.

slmgr.vbs /upk
slmgr.vbs /rearm
shutdown -r -t 30
echo.Restarting Windows in 30 seconds to complete the Rearm process...
pause

Currently all the windows tasks are still 32bit so downloading the bloatware that is windows seems a bit of overkill when I can get the tasks running quite easily by installing the 32 bit version of BOINC. Next time around I will probably do a fresh install of Ubuntu 19.10 which should mean all three machines have the problem fixed. (two out of three have fresh installs of 19.04 and 64bit BOINC is working fine.) I would rather keep the extra disk space but I am sure there will be a place for the VM route as there are enough things won't run under WINE to justify it.

As stated previously, boinc under wine gives terrible benchmarks (way too low). This impacts the "Remaining (estimated)" time in boinc manager, so you'll often get wild overestimates of the time to complete models.

There are two ways to fix this.

1. Change the number of CPUs used in the Preferences to 1, rerun the benchmark, then change the number back to the number of cores you want boinc to use. The more cores your CPU has and you let boinc use when running the benchmark, the lower your floating point benchmark will be. Running it with only a single core enabled in boinc will produce a reasonable FP bench.

2. Otherwise, go into the .wine directory tree to where your boinc data directory is at and edit client_state.xml to change the <p_fpops> to something more realistic.

Remember, you'll have to do this again after boinc automatically runs it benchmark, which it does periodically.

Edit...After you've made the change to the benchmark value, you should be able to stop boinc from automatically running benchmarks by editing a file called cc_config.xml in the boinc data directory (you may have to create that file, see the link below). You can create this skip entry in the <options> section of that file.

<skip_cpu_benchmarks>1</skip_cpu_benchmarks>

More about cc_config.xml here.

I wanted to be able to run Windows tasks from testing at the same time as running main site tasks natively under Linux. I have not found a way to do this just using WINE but have now succeeded in getting wine to work in an XUbuntu VM while BOINC chugs away doing Linux Native tasks. No Windows tasks available currently so a WCG task is running to test the set up. An Africa Rainfall Project which is going to take a total of about 18 hours to finish.

This also improves my flexibility should we ever return to the days of masses of Windows work and only occasional Linux batches.

BOINC under WINE problems not all gone but 7.16.11 runs under WINE 5.03 though apparently not under WINE6.0.

Good news for those who like to have lots of options.

boinc7.20.0 now runs under WINE on my Ryzen without crashing. For those wanting to run the latest version from github please note that this is an alpha version so not on the BOINC website for downloading yet. And it may well contain bugs.

This means those running it under WINE are no longer restricted to an old 32bit version. Another change is this new version uses system certificates so the problem with the cabundle.crt going out of date shouldn't happen any more, though on the BOINC boards it has been suggested that Windows might not always update this as often as it should!

It's working is also a moot point under Windows as far as this project is concerned for the foreseeable future.

I thought it worth trying as the release notes mentioned resolving one or two things that caused it to crash under Windows.

And with impeccable timing, I now have three Windows tasks from testing branch downloading onto my Ryzen.

Hallo

I have successfully installed WINE on my LUBUNTU 24.04 test computer and afterwards "WINDOWS BOINC Version 8.0.2". I am able to start BOINC Manager. But then I get the following error: "Invalid client RPC password. Try reinstalling BOINC"

Before I installed WINE, I have already installed BOINC in the LINUX environment, This "LINUX BOINC" works just fine.

Questions:
1) I am not able to find "WINDOWS BOINC" executables and "WINDOWS .config files" (in WINE). Can anybody help and indicate me, where to find them?
2) Has WINE and "WINDOWS BOINC" installed on a LINUX computer before "LINUX BOINC" is installed?

Any help is highly appreciated!

Regards
klepel

---

1) I am not able to find "WINDOWS BOINC" executables and "WINDOWS .config files" (in WINE). Can anybody help and indicate me, where to find them?

In your home directory .wine/drive_c/ProgramFiles/BOINC is where the BOINC executables can be found.

Before starting the manager in WINE ensure you have stopped the Linux client. (It is possible to run both from the same manager but you need to set up different ports for communication with the manager for each client and last time I tried that I ended up breaking something after having it working for a while.)

I think that error has to do with permissions.

Are you trying to control both WINE and Linux BOINC from the same manager?

If so, try what Dave suggests. It takes a little work to set up but I have done it successfully with controlling WSL2 Ubuntu BOINC from WIndows 10 manager.

If not, and just want to control them separately, a fix I've seen suggested is to go into the BOINC data directory and deleting the gui_rpc_auth.cfg file, then exit & restart BOINC. You could probably also go into that file and set up a password which I think you'd have to enter when trying to run BOINC client. Which is probably unnecessary and inconvenient for most personal systems.

As long as the wine client is using a different gui port there should be no problems. I've been running linux & wine/Windows client simultaneously for a while, both running tasks.

I start boinc under wine with:

# 64bit version goes in Program Files
wine "c:\Program Files\BOINC\boinc.exe" --redirectio --detach_console --gui_rpc_port 31420

Rather than delete the gui_rpc_auth.cfg file in the boinc data directory I just create an empty one.

Then using boinc manager on the host, select 'File - Select computer'. Put 'Host name' as 'localhost:31420' or whatever your new gui_rpc_port number is set to on the boinc.exe command line. Password as blank (or whatever is in your gui_rpc_auth.cfg).

It also works the other way, start up the Windows boincmgr.exe from wine and then connect to the Linux client by not specifying the port number in the 'Host name' field. :)

A quick shout-out to 'BoincTasks' here as a great way of managing a multi-client setup, particularly if you have multiple clients on multiple machines.

---

---
CPDN Visiting Scientist