The open source compatibility layer Wine has a brand new development release available. Here's what's new and changed in Wine 8.14. We're over half-way through the year now, so in around another ~5 months we're likely to see the stable Wine 9.0 release.
The main changes listed are:
- PCSC framework used on macOS for smart card support.
- Dumping of Windows registry files in WineDump.
- Fixes for Wow64 window messages.
- Various bug fixes.
30 bugs were also noted now to be fixed including issues for the likes of: DiRT 2 Demo, Candytron Demo, The Settlers II: 10th Anniversary, Civilization 6, Freelancer with the Crossfire mod, Spider-Man: Shattered Dimensions, Warframe, Steam client, Yuzu and more.
Want help managing Wine on Linux? You can try Bottles, Lutris and the Heroic Launcher.
Article taken from GamingOnLinux.com.
Some you may have missed, popular articles from the last month:
The comments on this article are closed.
Hmm:
That's weird since I have gcc-mingw-w64-i686-posix installed for building dxvk / vkd3d-proton. What am I missing?
checking for i686-w64-mingw32-gcc... i686-w64-mingw32-gcc
checking whether i686-w64-mingw32-gcc works... no
configure: error: MinGW i386 compiler not found.
This is an error since --enable-archs=i386 was requested.
make: *** No targets specified and no makefile found. Stop.That's weird since I have gcc-mingw-w64-i686-posix installed for building dxvk / vkd3d-proton. What am I missing?
i686-w64-mingw32-gcc --version
i686-w64-mingw32-gcc (GCC) 12-posix
Copyright (C) 2022 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
0 Likes
It's currently set to i686-w64-mingw32-gcc-posix, but setting it to i686-w64-mingw32-gcc-win32 doesn't work either.
Last edited by Shmerl on 22 August 2023 at 3:34 am UTC
Last edited by Shmerl on 22 August 2023 at 3:34 am UTC
0 Likes
Quoting: ShmerlIt's currently set to i686-w64-mingw32-gcc-posix, but setting it to i686-w64-mingw32-gcc-win32 doesn't work either.
You'd have to look at the config.log, as what's happening there is the compile test is failing for whatever reason. It could be as stupid as something bad in your environment causing the command to fail. (It doesn't really mean it's not found of course)
1 Likes, Who?
Oh bugger, here's a show stopper (for me, in Lutris). I can't seem to create new wine prefixes
I actually updated that prefix OK and the game worked, but I decided to do a test of creating a new wine prefix for a 32 bit game. Good thing I did, because this will not do.
I then forced it to be a "64 bit architecture" (Lutris has a setting that is Auto by default) and got
wine: could not load kernel32.dll, status c0000135
This is all 64 bit wine binaries
It's got to be something related to Lutris hard coding paths or something, because I can do
rm -r /home/grogan/.wine
wine winecfg.exe (and get the progress dialog, and winecfg opens)
wine notepad.exe
Sigh... time to go poking the python.
P.S. Got it to work, to generate a prefix with the "64-bit" architecture setting in Lutris (still can't get "Auto" to work)
The 32 bit Just Cause 2 game works just great in this "64-bit" arch Wine prefix, so the thunking is working.
Last edited by Grogan on 22 August 2023 at 5:39 am UTC
Started initial process 1225 from /usr/bin/wine winecfg.exe
Start monitoring process.
fsync: up and running.
wine: '/storage3/shit/justcause2' is a 32-bit installation, it cannot support 64-bit applications.
Monitored process exited.I actually updated that prefix OK and the game worked, but I decided to do a test of creating a new wine prefix for a 32 bit game. Good thing I did, because this will not do.
I then forced it to be a "64 bit architecture" (Lutris has a setting that is Auto by default) and got
wine: could not load kernel32.dll, status c0000135
This is all 64 bit wine binaries
It's got to be something related to Lutris hard coding paths or something, because I can do
rm -r /home/grogan/.wine
wine winecfg.exe (and get the progress dialog, and winecfg opens)
wine notepad.exe
Sigh... time to go poking the python.
P.S. Got it to work, to generate a prefix with the "64-bit" architecture setting in Lutris (still can't get "Auto" to work)
The 32 bit Just Cause 2 game works just great in this "64-bit" arch Wine prefix, so the thunking is working.
Last edited by Grogan on 22 August 2023 at 5:39 am UTC
0 Likes
Well, I have to say I've now seen that this isn't completely appropriate yet for 32 bit games. I'm going to have to go back to the old method, moreover, I'm just going to go back to my recently recompiled wine 8.6.1 before I go converting more wine prefixes to this. It's a shame, because I'm mostly OK.
In testing Fallout 3, it didn't run correctly. I could hear the background audio, but the launcher program drew no window. So I ran the Fallout3.exe directly, and found that it needed to be "installed". It's a game that has to be installed correctly or it doesn't find mods and dlc, only the base game.
'Twas then that I found out that a lot of 32 bit programs won't indeed run, including GoG installers! Even for 64 bit games, the installers are 32 bit.
wine client error:124: sendmsg: Bad file descriptor
I get the same with a newly generated ~/.wine prefix (not only in lutris)
But other important programs won't run either, like the 32 bit wine mono installers
So, right now, for me, prefixes that updated properly STILL have old files that work. Updating a prefix doesn't remove files, if another dll was there it will still be there etc.
Some 32 bit games were OK running after being given new prefixes because they didn't run afoul of anything that wouldn't run. Like Just Cause 2 and Bioshock Infinite, for example.
This will not do for my system wine, obviously.
Last edited by Grogan on 23 August 2023 at 5:13 am UTC
In testing Fallout 3, it didn't run correctly. I could hear the background audio, but the launcher program drew no window. So I ran the Fallout3.exe directly, and found that it needed to be "installed". It's a game that has to be installed correctly or it doesn't find mods and dlc, only the base game.
'Twas then that I found out that a lot of 32 bit programs won't indeed run, including GoG installers! Even for 64 bit games, the installers are 32 bit.
wine client error:124: sendmsg: Bad file descriptor
I get the same with a newly generated ~/.wine prefix (not only in lutris)
But other important programs won't run either, like the 32 bit wine mono installers
009c:err:environ:init_peb starting L"Z:\\usr\\share\\wine\\mono\\wine-mono-8.0.0\\support\\removeuserinstalls-x86.exe" in experimental wow64 mode
00a4:err:environ:init_peb starting L"Z:\\usr\\share\\wine\\mono\\wine-mono-8.0.0\\support\\installinf-x86.exe" in experimental wow64 modeSo, right now, for me, prefixes that updated properly STILL have old files that work. Updating a prefix doesn't remove files, if another dll was there it will still be there etc.
Some 32 bit games were OK running after being given new prefixes because they didn't run afoul of anything that wouldn't run. Like Just Cause 2 and Bioshock Infinite, for example.
This will not do for my system wine, obviously.
Last edited by Grogan on 23 August 2023 at 5:13 am UTC
0 Likes
I assume it's not ready indeed. Otherwise Wine project would have switched to a single binary already.
1 Likes, Who?
Quoting: GroganWell, I have to say I've now seen that this isn't completely appropriate yet for 32 bit games. I'm going to have to go back to the old method, moreover, I'm just going to go back to my recently recompiled wine 8.6.1 before I go converting more wine prefixes to this. It's a shame, because I'm mostly OK.
In testing Fallout 3, it didn't run correctly. I could hear the background audio, but the launcher program drew no window. So I ran the Fallout3.exe directly, and found that it needed to be "installed". It's a game that has to be installed correctly or it doesn't find mods and dlc, only the base game.
'Twas then that I found out that a lot of 32 bit programs won't indeed run, including GoG installers! Even for 64 bit games, the installers are 32 bit.
wine client error:124: sendmsg: Bad file descriptor
I get the same with a newly generated ~/.wine prefix (not only in lutris)
But other important programs won't run either, like the 32 bit wine mono installers
009c:err:environ:init_peb starting L"Z:\\usr\\share\\wine\\mono\\wine-mono-8.0.0\\support\\removeuserinstalls-x86.exe" in experimental wow64 mode
00a4:err:environ:init_peb starting L"Z:\\usr\\share\\wine\\mono\\wine-mono-8.0.0\\support\\installinf-x86.exe" in experimental wow64 mode
So, right now, for me, prefixes that updated properly STILL have old files that work. Updating a prefix doesn't remove files, if another dll was there it will still be there etc.
Some 32 bit games were OK running after being given new prefixes because they didn't run afoul of anything that wouldn't run. Like Just Cause 2 and Bioshock Infinite, for example.
This will not do for my system wine, obviously.
In my case work however i use 1 prefix for all and this prefix is created when use wine staging from deb packages
Respect fallout 3 of gog runs ok and sound is ok
personally maybe needs a previously wow64 staging prefix, however debian based distro is completly different than arch based distro
Curiously in my case just cause 2 dont work, in my case show this:
Quote0328:fixme:vulkan:wine_vkAllocateMemory Using VK_EXT_external_memory_host
0364:err:d3dcompiler:D3DCompile2 <anonymous>:6:121: E5017: Aborting due to not yet implemented feature: Load() sampling index parameter.
however another thing can be affect is amd radv drivers are different than intel anv
Last edited by mrdeathjr on 23 August 2023 at 12:42 pm UTC
0 Likes
what I think happened with Fallout 3 is something in the wine prefix got overwritten. The game did run, but it needed reinstalling. Fallout 3 has something "sneaky" because it used to be a Games for Windows Live game. They've defanged it with a fake dll but there's something that makes the game need installing (it can't just be dropped in by copying). It won't find content.
If I could have reinstalled it (GoG installers wouldn't run) it would have worked. I switched it to another wine (my Proton-TKG) and it reinstalled OK. Converting it back to my wine 8.6.1 didn't break it again. Weird.
There is no benefit for me to use this new Wine implementation at this time, and a lot of problems with 32 bit applications. My 8.6.1 built the normal way is 100% for everything I use it for. Pretty easy choice :-)
I really wanted this to work. I convinced myself that I was just going to work around all the problems, but this will just be the start of the problems I would likely encounter. (I thought it was great until I started uncovering them)
The only good thing about beating your head against the wall is that it feels good when you stop :-)
Last edited by Grogan on 23 August 2023 at 6:53 pm UTC
If I could have reinstalled it (GoG installers wouldn't run) it would have worked. I switched it to another wine (my Proton-TKG) and it reinstalled OK. Converting it back to my wine 8.6.1 didn't break it again. Weird.
There is no benefit for me to use this new Wine implementation at this time, and a lot of problems with 32 bit applications. My 8.6.1 built the normal way is 100% for everything I use it for. Pretty easy choice :-)
I really wanted this to work. I convinced myself that I was just going to work around all the problems, but this will just be the start of the problems I would likely encounter. (I thought it was great until I started uncovering them)
The only good thing about beating your head against the wall is that it feels good when you stop :-)
Last edited by Grogan on 23 August 2023 at 6:53 pm UTC
0 Likes
Quoting: Groganwhat I think happened with Fallout 3 is something in the wine prefix got overwritten. The game did run, but it needed reinstalling. Fallout 3 has something "sneaky" because it used to be a Games for Windows Live game. They've defanged it with a fake dll but there's something that makes the game need installing (it can't just be dropped in by copying). It won't find content.
If I could have reinstalled it (GoG installers wouldn't run) it would have worked. I switched it to another wine (my Proton-TKG) and it reinstalled OK. Converting it back to my wine 8.6.1 didn't break it again. Weird.
There is no benefit for me to use this new Wine implementation at this time, and a lot of problems with 32 bit applications. My 8.6.1 built the normal way is 100% for everything I use it for. Pretty easy choice :-)
I really wanted this to work. I convinced myself that I was just going to work around all the problems, but this will just be the start of the problems I would likely encounter. (I thought it was great until I started uncovering them)
The only good thing about beating your head against the wall is that it feels good when you stop :-)
In my case fallout 3 with gog gfwl dont affect however i remember various titles have this virus called GFWL
Curiously in my case gog installers work ok, with this wine i test mighty switch force collection installer and others
0 Likes
My GoG installers would run too on an updated (but not newly created) prefix with the Wow64 build.
0 Likes
Patreon
PayPal
See more from me