Wine 3.0 Released (softpedia.com)
prisoninmate shares a report from Softpedia: The Wine (Wine Is Not an Emulator) project has been updated today to version 3.0, a major release that ends 2017 in style for the open-source compatibility layer capable of running Windows apps and games on Linux-based and UNIX-like operating systems. Almost a year in the works, Wine 3.0 comes with amazing new features like an Android driver that lets users run Windows apps and games on Android-powered machines, Direct3D 11 support enabled by default for AMD Radeon and Intel GPUs, AES encryption support on macOS, Progman DDE support, and a task scheduler. In addition, Wine 3.0 introduces the ability to export registry entries with the reg.exe tool, adds various enhancements to the relay debugging and OLE data cache, as well as an extra layer of event support in MSHTML, Microsoft's proprietary HTML layout engine for the Windows version of the Internet Explorer web browser. You can read the full list of features and download Wine 3.0 from WineHQ's website.
The Wine people have done a fantastic job, and do not get enough credit.
I'm off to play some GTA Vice City under Wine on Mint.
First law of people: People are generally stupid.
Game crash in Windows:
- full system lockup
- hard reboot
- inevitable data loss
- no recourse
Game crash in Wine:
- laugh at the foolishness of Microsoft slaves
- kill Wine and restart it
Another alternative to prevent games from crashing the OS all the time is to upgrade from Windows 95. Either that or stop spouting outdated notions of what life is like running Windows.
Game crash in Windows:
- full system lockup
- hard reboot
1996 called. They want their Microsoft dig back...and if you still have it, that Sublime CD you borrowed.
I don't always use unix-like operating systems; but when I do, I prefer FreeBSD.
Adobe CC is the only reason I still have Windows. If there's a way to get it to run on Wine 3.0, it's bye-bye M$. It *almost* ran on the previous version.
I should be specific. I could live with just Lightroom and Photoshop. A stretch goal would be Premiere.
Oliver's law of assumed responsibility: If you're seen fixing it, you will be blamed for breaking it.
From my limited experience: if it comes to older Windows applications, the chances to get something to run properly might actually be higher under Wine than under a current Windows, and that was already true before 3.0. (And if something doesn't run, as was already said, there's still Virtual Box, VMware etc.)
Yup. For those who didn't grow up with this stuff: as an example, back in the 1980s, there were a lot of programs marketed as CP/M emulators, which worked with chips like the V30, a 8086 compatible chip that also could natively run 8080 software. The emulators emulated the CP/M API (BIOS and BDOS), not the CPU, allowing software for CP/M 2.x to run under MS DOS (and access the MS DOS file system.)
The misnomer that you can only use the term emulator for CPU emulation, and not API emulation, seems to be relatively new, I'm almost inclined to stay it started in this millennium.
You are not alone. This is not normal. None of this is normal.
Sadly, I just had my Windows 10 totally fsck on me a few days ago.
In this particular instance, the "lock up" was because the game takes over full-screen mode and for whatever reason the game became unresponsive. I did CTRL-ALT-DEL and it gave me the options screen for logout/taskmanager/etc but even when starting the task manager the screen just went back to the game and the task manager was inaccessible. ALT-TAB would show the task manager running, but when selected Windows auto-switched right back to the game. The result was, after trying literally everything possible to kill the process from within, I had to force a reboot to finally get out of it.
I have never had a similar experience on Ubuntu, though I've had my share of other bad experiences there too so I'm in no way a fan-boi for that OS.
The reason it's saying it's not an emulator is because it's executing the x86 natively, using its own standin for the nt kernel, a pe loader, etc. Emulation in this context is referring to not having to emulate the whole "pc platform" in order to do this, which a few moments of research could've told you. But I guess it's just easier to be snide than it is to look something up.
The distinction, in the case of WINE, was first made in 1993, months after the project began.
The one piece of Windows-only software I'd like to run, sadly, requires Java, and WINE still doesn't, apparently, allow you to install Java under it. Guess I'll just have to try Windows XP in a virtual machine.
Ill bet that 50% of Windows apps still crash and refuse to run at all on Wine. I doubt that many Wine users care about android, and would rather more advances had been made toward supporting 99% of windows apps (Windows Desktop apps on a phone, good god).
I remember the ancient days when Wine really excelled at running notepad.exe. Over the first few years, I had serious doubts about the project's future. But for the last few years , I have been able run substantially more - even rather complex - applications to the point that it is useful. As of the last couple releases before this, I have been downright impressed by the number of application I have been able to run. This is even to the point where I now consider it a powerful tool. Anything that can improve on that now with hope for ongoing development is absolutely great in my book.
Brought to you by Carl's Junior.
If that happens again, try to start the Task Manager, and then type the name of the EXE (even if the window itself is not visible) and press DEL + ENTER.
The idea is that the Task Manager's window may not be visible for some reason, but it still has focus - so you can try to interact with it.
The saddest poem