All modules that call a Unix library contain WoW64 thunks to enable calling the 64-bit Unix library from 32-bit PE code. This means that it is possible to
run 32-bit Windows applications on a purely 64-bit Unix installation. This is called the new WoW64 mode, as opposed to the old WoW64 mode where 32-bit applications run inside a 32-bit Unix process.
Does this change run the 32-bit .exe using x86_64 instructions? From the description it just sounds like it allows 64-bit Linux libraries to be used in place of 32-bit ones, but that the Windows layer still operates in native 32-bit mode. This means there is still a need to emulate 32-bit x86 instructions which I don't think box64 can do at this time (x86_32 translates to arm32 with box86, x86_64 translates to arm64 with box64). If box86 could translate x86_32 to arm64 then this might work as Wine would handle the conversion between 32 and 64 bit addressing and argument passing into the libraries but I'm not familiar with the inner workings there.
Dont hold your breath. It’s just initial support. It’s still opt-in and I can’t see Valve using it with Proton by default unless they start supporting native Wayland clients in Gamescope
Sorry if this is a dumb question, I’m still very new to Linux. I have Wine 8 installed, currently just to run one application for one of my games. Should I bother to update to 9 if my current setup is working? I’m still adjusting to the FOSS environment and haven’t quite figured out whether or not I should always update to the latest and greatest just because I can.
If it works and you are still figuring things out, I suggest not taking specific action right now. Use your package manager to keep your system up to date and it will deal with this in due time.
A lot of the time the version of wine will cause issues with the application, so if you have something working, stick with it.
It would be worthwhile to look into a wine prefix manager like lutris or bottles for gaming. Regular apps can benefit also, but I am not up to speed on anything not for gaming.
Thanks for the advice! The application I’m using in Wine is Elite Dangerous Market Connector, nota game itself but a small helper app for the Elite Dangerous game. According to the git page, you can get it running from source with Python, but I wasn’t quite skilled enough to get that working.
As far as my actual games go, those seem to all run fine through Steam/Heroic Games Launcher with Proton GE edition, which as I understand it incorporates Wine somehow…? I’m not sure of the specifics, but I assumed Wine in that context would get updated with Proton eventually.
The fact that I don't have to deal with lib32-gst-plugins-ugly/bad/ect is amazing, but I'll have to keep 32 bit libraries for Team Fortress 2 and other online Source games.
It's a miracle we have wine at all, reverse engineering an entire operating system isn't easy. Be grateful for what we have (which is already enough to run a ton of software really well)
reverse engineering an entire operating system isn’t easy
Have you noticed the the NT / Windows XP source code was leaked years ago. There's isn't much of a need to "reverse engineering", it's just about reading their implementation and providing an alternative implementation that doesn't copy code...
Instead of leaving snide comments like this, you can use your head to open up an IDE, implement the features you want, and make a pull request. Keep it to yourself
How about this then. While your neighbors are using wine, it attracts more commercial attention to develop the open source projects that you do actually use. It's so impactful that you measurably benefit directly from its contributions, like optimizations to the Linux kernel.
You don't have to agree with it, but you cannot deny the increased investment in open source projects it causes.
For a painfully blatant example see: Steam Deck.
Also for the binary blob purists, how do you feel about all that closed source firmware underpinning your pure world? Isn't it practically impossible to get completely open source firmware down to the silicon? And even then, do you trust the silicon? Are you running everything on FPGAs?
Hi! "Binary blob purist" here! Yes, it bothers us that so much firmware is proprietary, but we are working to fix that :).
It is possible to have fully free firmware on certain select devices.
The silicon is unchangeable, much like a chair is unchangeable. So being concerned about changing it isn't really productive. But, RISCV looks promising and a good remedy to the issue of not knowing what it does.
FPGAs would be nice but they aren't powerful enough yet.
But, at the same time, unless the silicon can make outside connections itself or modify behaviour (a la Intel ME), or has been updated with what is essentially software baked into it that can change it's behaviour on the fly, I'd say it can be trusted to do the computing you tell it to do and nothing more (again, excluding those processors where we know that it doesn't like those with the ME).