Thought I would start a new thread for this rather than add to the 64 bit thread further and confuse things.

Installing WINE and then a windows version of BOINC seems to be straightforward or was for me at least.

Certainly on my boxes they won't let you run both the linux version and the windows version at the same time. Don't know if there is a work around for this for when you have spare cores and no work for them?

Not 100% sure yet but it looks like on my laptop at least,credit for time computing seems to be higher despite whatever overheads WINE imposes.

Use Virtual Box and install a Windows Virtual Machine. I have a Windows 10 PC with 6 Linux Virtual Machines on it to run CERN projects.
Tullio

---

But then, don't I need a copy of windows? Why bother when I can just use WINE?

A few other things you might note...

* The benchmarks in boinc on Wine are terrible compared to regular Linux or Windows. The more cores, the poorer the benchmark result. As far as I can tell, this is not at all indicative of cpdn performance which seems to be on par with regular Windows.

* When starting boinc in Wine, it takes awhile for boinc manager to connect to the boinc client. I've noted delays of a minute or more. Once done, you'll see the message log populated if you are displaying that message log.

* You likely need boinc 6.10.58 or higher in order for boinc in Wine to correctly identify your CPU. Previous versions of boinc in Wine liked to identify every CPU it couldn't recognize as a Pentium 4 2.4 GHz. It didn't hamper performance, just misidentified the CPU.

When starting boinc in Wine, it takes awhile for boinc manager to connect to the boinc client. I've noted delays of a minute or more.

I had noticed the delay in connecting but if I click on <tools> <add project> it then connects as soon as I click.

The benchmarks in boinc on Wine are terrible compared to regular Linux or Windows

Still on my first four tasks which are between 61 and 63% completed all have an estimated total time (elapsed + remaining) of about 31days. compared with an initial estimate of 41 or 43, I forget which. My estimate based on elapsed time at 51% is a total of more like 21/22days.

The other thing I am waiting to see is the percentage of failed tasks I get compared to windows average. For the record I am using BOINC 7.6.22 under wine.

I've completed about 60 tasks successfully.

Of workunits associated with the tasks that errored on these PCs, all but one had task erros on all other Windows computers in that workunit. So, it seems quite stable.

Wine is much better than a VM, in that it's all free. Wine (software)
And there's no resources overhead.
Also you get to use anything from Windows 2.0 to Windows 8, with XP Pro being the default.


So far, I've had all successes under Wine on 2 computers, with several completions.


On the Haswell, i7-4770K CPU @ 3.50GHz, ANZ models:

Linux Mint: 2.76(sec/TS)
m52q

Windows XP under Wine: 1.76(sec/TS)
h11y

Different dates/batch numbers, so different inputs, which will affect the results.


The initial time to completion was 719 hours, dropping to 67 hours actual.
******
For the W@H2 on the Haswell, initial was 1000 hours, dropping to 136 hours.
Same model type on the Ivy Bridge, initial was 1542 hours, dropping to 149 hours.

I have 6 Virtual Machines on my Windows 10 PC. One of them is a SuSE Leap 42.1, the latest SuSE release, which I use as a tester of Leap. On this I have loaded a second tier Virtual Box and run vLHC@home of CERN, with good results.
Tullio

---

Okay! What you all posted convinced me to try BOINC and CPDN under wine.
Looking good so far (that's 3-4 days and a few wu's near half done).
It was years ago I tried ancient wine and it was a no-go.
Now, much much better. I've got 6-7 Linux boxes and one Windows 10 license running in a virtualbox.
Saw this thread late last week, tried wine-BOINC in a linux-mint 17.3 virtualbox -- installed wine 192 per wineHQ ubuntu instructions -- wine installation worked well, installing windows BOINC with wine likewise easy. Attached to CPDN, all good.
Waited a day, tried crashing wine, and the vbox. No problems on restart, no wu-s lost.
Now have 2 more linux boxes running BOINC and CPDN under wine. Looking good..

<edit> Added bonus - once wine is working none of that 32-bit on 64-bit nuisance like with linux --

---

Welcome to the club, Eirik. :)

A second "64 bit" thing: The 'set and forget' people without all the libraries who crash everything, day after day, are also probably people who don't look at this forum, and so won't know that they're now not getting anything.
Which means that at last the project can get a higher finish rate.


Haven't tried to crash mine. And a few bad, close electrical storms in recent days didn't give me problems.

When starting boinc in Wine, it takes awhile for boinc manager to connect to the boinc client. I've noted delays of a minute or more.

I had noticed the delay in connecting but if I click on <tools> <add project> it then connects as soon as I click.

Thanks Dave. That does work well. Very strange.
.

I thought it strange too but being a trifle impatient I tried it and.....

Just a few minutes ago the BOINC instance running under Wine was able to contact the servers and I could finally add the CPDN project! It shows up on my list of computers (ID 1389186) as a Win10 device.

BTW BOINC wasn't working correctly on my Linux box until Wine upgraded to latest devel version (1.9.2), but possible some other change made the difference. (Previously the problem was BOINC couldn't make the necessary server connections so nothing could happen.)

Now the only thing missing are some tasks to run. It will be very interesting to see how it goes when they arrive. Unless of course the next batch is for Linux machines, but I'm gambling that won't be the case.

Interesting about Win 10, until I thought about it.
Without going to look, I think that one of my machines is Wine 6*, and the other Wine 8*.
As Win 10 is fairly recent, it couldn't have been included in the earlier versions.

Yes, the last few tasks disappeared with a rush.
Not to worry, there'll probably be more soon, what with the testing as well as the production models being on this site.

Not entirely sure, but I think Wine gained Windows 10 support in Sept or Oct 2015. Since I didn't install Wine until last month, Win10 was available right away. Windows version probably doesn't matter a whole bunch, I notice quite a few computers on CPDN lists continue to run Win7 without problems re: CPDN tasks.

Looking forward to release of the new batch of tasks!

How about that: this afternoon 4 tasks were downloaded and are now running under Wine! The only adjustment I made was reducing CPU utilization slightly to keep CPU temp a bit lower (around 60), similar to configuration for Linux tasks. Don't think it slows task progress excessively.

So far, so good...

And having a sub 3GHz laptop, the first of my 4 WAH2 tasks has completed under wine. One ANZ task now started and seems to be going ok so far. (2 of my 4 ANZ tasks have failed twice already, one has failed once and the other I am the first cruncher. I haven't looked to see what the cause of failure was on the resends yet.

On my desktop machine, I have just started running the wine version. as far as I can make out, the 64 bit runs, but I can't access any of the menu items once it is running - cpu usage indicates it is working. So I have now put the 32 bit version on which seems to work normally.

On mine, if I make the window slightly larger by dragging the right side of the window to the right, the menus show up.

Doesn't seem to on mine but I will play further at some point though the 32bit version seems to work fine...