View Single Post
Old 02-20-2017, 08:24 AM   #23
latepaul
Wizard
latepaul ought to be getting tired of karma fortunes by now.latepaul ought to be getting tired of karma fortunes by now.latepaul ought to be getting tired of karma fortunes by now.latepaul ought to be getting tired of karma fortunes by now.latepaul ought to be getting tired of karma fortunes by now.latepaul ought to be getting tired of karma fortunes by now.latepaul ought to be getting tired of karma fortunes by now.latepaul ought to be getting tired of karma fortunes by now.latepaul ought to be getting tired of karma fortunes by now.latepaul ought to be getting tired of karma fortunes by now.latepaul ought to be getting tired of karma fortunes by now.
 
latepaul's Avatar
 
Posts: 1,270
Karma: 10468300
Join Date: Dec 2011
Device: a variety (mostly kindles and kobos)
Taking a break from watching the progress bar on the dotnet35sp1 installer crawl across...

VMs are definitely easier. But for me at least, a lot slower. With my current PC I can pretty much forget trying to do anything else when I run my Windows 7 VM. Also, at the moment I'm running a liquorix kernel which improves responsiveness a lot for me. Unfortunately I didn't build it, and it was built with gcc 6.something, and when I try to run vmplayer under it - vmplayer wants to me to rebuild its kernel modules and complains it can't find the relevant gcc version. I hit the equivalent problem with Virtualbox but vmplayer gave me a better error message.

Or to put it another way, I have to reboot before running a VM.

I hadn't realised until reading DiapDealer's post but the aim is to *not* install mono. BTW "wine control" doesn't show mono as having been installed. But I tried again a couple of times and it still wouldn't play nice. I went back to using staging as that worked for DiapDealer. FWIW I found this on WineHQ Wiki:

Quote:
The Mono package should always be removed before installing native .NET. This can be done with the following command-line:
Code:
$ wine uninstaller --remove '{E45D8920-A758-4088-B6C6-31DBB276992E}'
(link)

Probably worth including this as a step in the wiki instructions, Daryl.

Current attempt - still crawling, fingers crossed! - is in a Debian-based Docker container. Really not sure why that's working and the native attempts failed. However if it works I'll take it. Otherwise probably revert to the VM.

And yes, this is definitely one of the things I love/hate about Linux. There's almost always a way to get something working, the question is, how far down the rabbit hole do you want to go? I often think things seem simpler on Windows/Mac simply because you hit a wall of nothing else to try a lot sooner. So something either works or doesn't and you move on. With Linux there's always a tantalising hope that if you re-compile with these flags, update that library etc, maybe it'll work.

And if you're the wrong kind of obsessive that can be fatal. Yesterday I was actually building an Arch VM so I could create a base image for Docker, to create a container to run Wine in, in order to install ADE 2.0.1, which I don't strictly need... all because I don't want to be "beaten". That's several layers of insanity.
latepaul is offline   Reply With Quote