SoylentNews is people
SoylentNews
WINE (Wine Is Not an Emulator) is a compatibility layer that allows some application programs written for Microsoft Windows to run under other operating systems.
Phoronix reports
Following [the March 30] debut of Wine 3.5, a new Wine-Staging release is now available that continues to carry close to one thousand patches on top of the upstream Wine code.
Wine-Staging 3.5 was able to drop some of the patches now that the BCrypt patches have been upstreamed, but they still are dealing with around 950 experimental/testing patches for code not yet in Wine trunk.
There are new patches to Wine-Staging 3.5 to support Implicit MTA, stubbing out some more functions that are needed for the BattlEye game anti-cheat software, adding in a function needed to make Rise of the Tomb Raider happy, fixed 1D texture support, and other fixes and code additions.
Wine-Staging 3.5 binaries for popular Linux distributions are available here.
Phoronix earlier noted
Wine 3.5 continues the recent theme of enabling Vulkan support. Wine 3.5 most notably on this front introduces their new basic Vulkan loader. This means Wine users no longer need to manually install the LunarG SDK for Windows in order to have Vulkan support but rather this custom-developed loader library is shipped by default. This implementation though doesn't support multiple drivers and notably doesn't include support for Vulkan layers, so those needing such features will still want to manually install LunarG's SDK.
The Vulkan library in its current form paired with the recent of Wine's ongoing Vulkan support is good enough for handling Wolfenstein, Doom, and the various Windows VK demos, etc.
Wine 3.5 also includes support for RSA and ECDSA crypto keys, improves its manifest file parser, and supports the Places toolbar within file dialogs.
In its announcement, WINE Headquarters has a list of fixes.
Bugs fixed in 3.5 (total 58)
Some keywords: Empire Earth; Age of Mythology; Mega Man Unlimited; Need for Speed; Rush for Berlin Gold; Battlefield 3 (Origin); Galactic Civilizations III; Starcraft 2; Doom (2016); Grand Theft Auto V; Titanfall2; Wolfenstein 2: The new Colossus; The Witcher 3; Divinity: Original Sin 2.
The list also includes some productivity apps.
See anything in their list that makes you say "That's worth a try"?
(Score: 3, Insightful) by acid andy on Monday April 02 2018, @01:03PM (2 children)
Are you a masochist?
This could probably be configured but is likely to cause all sorts of problems. For starters, filenames in Linux are case sensitive but Explorer makes no distinction. Also, Linux can create files with names that Windows and presumably Explorer cannot handle (e.g. ':'). Explorer won't read Linux disk formats either so you'd be stuck with NTFS or FAT. Wine's file browser can read them I think but that's not Explorer.
If a cat has kittens, does a rat have rittens, a bat bittens and a mat mittens?
(Score: 0) by Anonymous Coward on Monday April 02 2018, @05:08PM (1 child)
you'd be stuck with NTFS or FAT
Yeah. The major advantage of *n?x filesystems is that the system will look for a spot that is large enough to hold the entire file then write it there.
This is 1 reason that Linux systems are faster: They go a long time without any need for defragging.
.
Windoze filesystems will put a creation date on a file while Linux filesystems don't.
Linux file managers won't display that information, even if it is available.
That's one of the few things that I miss about MICROS~1's stuff.
filenames in Linux are case sensitive but Explorer makes no distinction
The default way that things are sorted/alphabetized is different too.
Linux n00bs have been know to bitch about that.
(That can be tweaked.)
-- OriginalOwner_ [soylentnews.org]
(Score: 0) by Anonymous Coward on Monday April 02 2018, @07:24PM
The filesystem drivers just don't currently implement it, even though it could be handled in the filesystem driver (since it only states when the file was created on THAT filesystem, not the assumed behavior of it being when the file was originally created, just like whatever the third timestamp is besides mtime and atime. mtime being the closest equivalent to the old DOS timestamps.)