Hi folks,
I'm willing to install WINE on yet another linux machine, but the system drive is on SSD, and I do not want CPDN under WINE to use the SSD, but another mounted drive which is normal HDD. I guess I should try either to install WINE on the HDD, which I doubt I can (or is a good idea), or under WINE configuration to set (somehow) paths to the HDD where data should be?! Any advices will be most welcomed.

Cheers

I'm willing to install WINE on yet another linux machine, but the system drive is on SSD, and I do not want CPDN under WINE to use the SSD, but another mounted drive which is normal HDD. I guess I should try either to install WINE on the HDD

By default, wine has installed BOINC under .wine/drive_c/Program Files/BOINC/ in my home partition rather than on the partition where my system is installed.

By default, wine has installed BOINC under .wine/drive_c/Program Files/BOINC/ in my home partition rather than on the partition where my system is installed.

Normally .wine/drive_c/Program Files/BOINC/ is installed in /home/user/.wine/drive_c/Program Files/BOINC/ and I want to avoid it.
I guess I have to follow this https://wiki.winehq.org/FAQ#Wineprefixes

For me, messing with the environment variable WINEPREFIX was problematic, probably because I don't know enough to get the environment variable set properly in the contexts when I'm working with linux-boinc-wine :)

What worked for me was - create a new user say "wine" and make that user's home directory be on whatever drive or partition, so it's isolated and I can backup and re-install fairly simply. Mess a bit with fstab, and let the defaults run :)
So, I've got (various other directories and drives).
/ is on my SSD (read mostly and read really really quick) /home/wine (or /home/wine/.wine is mounted on some whirly oldy hard drive or partition. (maybe 24-60 Gib, whatever you got or want

BOINC CPDN on linux using wine.

Worked real well, reported several completed WU's

With the new huge batches that accept Linux WU's , switching to raw Linux for now, maybe a wee bit faster, but hey
Wine worked well to keep my mostly linux hosts (ubu, mint) contributing.
Will use again when needed.

Thx all

---

Great Eirik,
I did mess with WINEPREFIX and also variables for 64 bit and 32 bit wine since my machine is 64 (and 64 WINE is problematic), so far works pretty ok. However haven't restarted in a month (actually at all since installing) and need to see whether will be able to launch it properly again or will have to set WINEPREFIX again and then start. Whenever I do it will write back.

Everything here across three machines running wine at the moment. Have set two machines to no new tasks so that if there is still lots of Linux work available when those in the queue finish I can then return to running tasks natively.

switched two machines back to linux but seriously thinking about switching to wine completely as power outs (cable getting knocked out of laptop and not being noticed) seems much more likely to result in tasks crashing with linux than with Wine.

Not quite sure why that should be.

I have Linux Mint 17.3 Cinnamon running BOINC/CPDN after several trials with WINE. Boinc was then downloaded directly to Firefox and installed very quickly, and tasks have been running, or rather, crawling, for about 80 hours. So WINE proved to be a bit complex for this operation.
However, I dont think CPDN can get much benefit from task completions which are under the stated target dates, but about 18% of the completion rates seen on a DELL WIN10 machine.
There is very little guidance in other pages, and maybe someone could comment.
I dont mind dedicating the older machine to CPDN but it needs to be useful work.
This effort was part experiment to prove to DELL that Linux will run almost anything on anything that has a decent motherboard.

---

Hi John, it may be worth running just one task at a time or upping the memory to 4GB 1GB/task is actually a little low for a lot of the current work with CPDN.

Thanks Dave
I will upgrade to max RAM (by coincidence, 4gb) and we shall see.

---

Running WAH2 on my Linux boxes both in native Linux and Wine show a slight improvement in speed in pure Linux, but not much. Running on a Win7 box with a linux VM shows that once again, WAH2 is slightly faster in the Linux OS. Your mileage may vary, but I'm not sure why it would vary much.

Few months ago I switched from WINE back to pure Linux on two machines and speed is up with 15%, which is noticeable especially on slower machines crunching an eu25 model for 400h. So no WINE if Linux WUs are there.

Having just done a clean install on two of my machines to upgrade to Ubuntu16.10, I found I had to add the wine repositories before I could install it. now working on both machines. - One machine I did a clean install on. the one I upgraded ended up with a few things broke so I did a clean install. When my box running work units in native Linux is clear of tasks I will upgrade it and see what happens.

One machine has started giving the following message, (from memory so not verbatim.)

boinc.exe has encountered a serious problem and has had to close.

I have tried changing BOINC version, uninstalling and re-installing wine, both stable and dev versions and the same happens. All I have achieved is to reduce the number of error messages in the terminal if I use wine boincmgr.exe to start boinc.
Wine:Unhandled exception 0xc00000409 in thread 2c at address 0x4143f9 (thread 002c), starting debugger... the exception is constant but the address changes between attempts to get it to work.

The debugger has a button to click on for more information but nothing happens.

So, with that machine I am now waiting for Linux work to re-appear.

Anyone with ideas as to what I can try?

Hi Dave

That message has been around for a while now, and appears on "real" Windows systems, and possibly on Linux as well.

I had it once myself, but I've forgotten what happened/what to do.

Thanks Les,
What struck me as strange was that it had been running fine for months, then a few days ago some tasks from WCG all started crashing then the same for another project which I suspect was wrongly configured files downloaded as resetting the project combined with an exit of boinc and restarting it cured it, then this morning I first got the message when I went to look at the event log. This machine with the same versions of Xubuntu and WINE so far is working fine. Got a couple of things I might try next week but really running out of ideas at the moment. - have left the four cores on the machine crunching WCG till the newer tasks become avilable natively.

I've had that as well. The only thing that solved it was to "uninstall" boinc from wine, remove the boinc executable and data directories, and then reinstall and reattach to cpdn. I think something gets corrupted that a reset doesn't fix. Maybe it's in client_state.xml or maybe some other file.

Will try that, Unfortunately I don't think I have the skills to search through client_state.xml to try and work out which of three projects' information has got corrupted. Shame it happened when I actually had some work for a change though :(

I will wait till the WCG tasks running have cleared from the native client, then have a go. I have saved both the program and data directories so if anyone has the skills, time and inclination to look at them they can let me know!

I can report that deleting the data directory before re-installing was successful so now I will be able to return to CPDN with that machine once the four running WCG tasks are complete under linux. Many thanks for that hint George.