22
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 24 Jul 2024
22 points (100.0% liked)
technology
23236 readers
125 users here now
On the road to fully automated luxury gay space communism.
Spreading Linux propaganda since 2020
- Ways to run Microsoft/Adobe and more on Linux
- The Ultimate FOSS Guide For Android
- Great libre software on Windows
- Hey you, the lib still using Chrome. Read this post!
Rules:
- 1. Obviously abide by the sitewide code of conduct. Bigotry will be met with an immediate ban
- 2. This community is about technology. Offtopic is permitted as long as it is kept in the comment sections
- 3. Although this is not /c/libre, FOSS related posting is tolerated, and even welcome in the case of effort posts
- 4. We believe technology should be liberating. As such, avoid promoting proprietary and/or bourgeois technology
- 5. Explanatory posts to correct the potential mistakes a comrade made in a post of their own are allowed, as long as they remain respectful
- 6. No crypto (Bitcoin, NFT, etc.) speculation, unless it is purely informative and not too cringe
- 7. Absolutely no tech bro shit. If you have a good opinion of Silicon Valley billionaires please manifest yourself so we can ban you.
founded 4 years ago
MODERATORS
It's a longshot, but you can try running WINE in WSL. While WINE isn't perfect, it tends to have better backwards-compatibility than the built-in Windows compatibility feature. I have never tried using WINE on Windows before lmao. While this would technically involve running a Windows compatibility layer inside of a Linux compatability layer on Windows, there technically are no virtual machines involved
.
I second this, but it is really funny that the translator is more fluent than the native speaker. I love being able to run Windows binaries without downloading all the VC redistributables directX nonsense from a decade ago and WINE allows one to do this especially on GNU/Linux.
hmm okay thanks
Just to note that there will actually be a VM involved. WSL1 was a compatibility layer more similar to Wine, but it didn't have the best compatibility cause it didn't have all system calls etc, including notably here missing multilib support. WSL2 is just a VM using Hyper-V and uses a full real Linux kernel, and is necessary here to actually run 32-bit binaries