15 ms·

Wine 8.5

196 points by neustradamus 4y ago

acapybara 4y ago
What's new in this release: - Bundled vkd3d upgraded to version 1.7. - Better error reporting in the IDL compiler. - Support for shared Wow64 Classes registry key. - More cleanups in IME support. - Support for configuring a WinRT dark theme. - Various bug fixes.
worldsayshi 4y ago
Is wine receiving patches from Valve's fork or are they completely separate at this point?
- komadori 4y ago
  AFAIK, Valve pays CodeWeavers to work on Proton, so Proton is more of a curation of Wine like CrossOver Office rather than a hard-fork.
- anotherhue 4y ago
  I assume they're free to pull in as they wish? I didn't see any proton reference in the changelog though.
- giomasce 4y ago
  Proton developer here, working for CodeWeavers. Everything we develop goes preferentially in Wine, and is kept in Proton as a "hack" only when a solution clean enough for Wine is unfeasible or too complicated. Proton is periodically rebased onto Wine, so everything in Proton and not in Wine is additional rebasing work, which we'd like to avoid as much as possible.
  - steeleduncan 4y ago
    Thanks for all the great work. I hadn't realised Proton was developed by CodeWeavers. Out of curiosity, what is the relationship between Proton and your own product Crossover?
    - giomasce 4y ago
      In principle they are somewhat similar: they're both Wine + local patches (either backported from more recent Wine versions or hacks that are not suitable for upstream Wine) + some glue. CrossOver also has a GUI, which Proton doesn't need because the GUI there is Steam and Proton is supposed to be as transparent as possible. And like I said for Proton, it's in our best interest to keep the diff between Wine and CrossOver as small as possible, because that's a liability that takes its toll at each rebase. In practice Proton and CrossOver tends to have rather different sets of needs. Proton only supports Linux and is only focused on gaming. CrossOver exists for a handful of platforms, most notably macOS (which has a number of intricacies: missing 32 bit libraries, Apple Silicon, missing Vulkan drivers which requires MoltenVK, but MoltenVK itself cannot really offer all the features standard Vulkan drivers have on Linux), and is also used for non-gaming applications. CrossOver also lives in the form of specialized branches we develop for specific applications, on request of their developers. So while of course we share everything that can be shared, in my experience this tends to be not that much (except what goes upstream, of course). In pratice CrossOver and Proton live in different repositories, have independent build systems and independent release schedules.
      - steeleduncan 4y ago
        Thanks for the explanation!
    - JiNCMG 4y ago
      I've been a Crossover customer since their 2012 end of the world sale.
  - foxandmouse 4y ago
    Do you think Proton could be released on Steam for macOS? This could help rejuvenate the gaming community on macOS, which is suffering due to Apple's focus on the App Store. It seems like every decision Apple makes for macOS makes it harder to support games outside of their ecosystem.
    - giomasce 4y ago
      On the technical level it should be totally doable. Whether that's something Valve is interested into, I don't have any privileged information. I know people use CrossOver with Steam on macOS, though that requires a rather intricate setup I don't know much about. I guess what you'd like to have is the kind of seamless integration that Proton has with Steam on Linux.
  - natas 4y ago
    huge THANK YOU for the hard work on Wine, the entire community much appreciates, I'm a steam customer (400 games, no less!) and that's my humble contribution :) note that I commonly buy all games that run on linux :)
troad 4y ago
I'm constantly so astonished by how well Wine works these days. I remember the first time I heard about Wine, decades ago, and thinking "yeah, right!" But by God, they pulled it off. I would not have been able to move to Linux full-time without Wine. Thanks!
- eurekin 4y ago
  I wouldn't be surprised, if wine became a "compatibility layer" embedded into a wsl in Windows at some point
  - squarefoot 4y ago
    It is already a compatibility layer to run old windows software that Microsoft no longer supports. I use it for making music, and the number of 20+ years old VST plugins that work exceptionally well is astonishing. The only problem I encountered was some of their installers failing because they reported a negative available disk space, presumably because of a bigger new variable overflowing the older smaller one they use. Running them as a older Windows version didn't work, I suspect the only way to make them run would be to implement a WINE flag to pass the installers smaller variables with that data. Aside that, I'm amazed at how good the compatibility is.
    - seba_dos1 4y ago
      You could just create a smaller filesystem in a file, mount it and export is as a Windows drive in winecfg.
      - squarefoot 4y ago
        I did something similar: made a very small partition on a USB drive and assigned it a drive letter, then tried to install in there. It didn't work because it's the variable that is bigger, not its contents, so whatever value it contains it still overflows the one expected. Short of patching the relevant WINE code (which I don't even know where to start looking for) A XP VM might be the last resort. The software once installed works fine as I experienced by moving to Linux a very old XP install I had on a backup.
buster 4y ago
Wine is just a great piece of software. Not just for gaming but the occasional dreaded enterprise software. I happily pay for crossover.
antibasilisk 4y ago
That's funny, I had a dream about running a program in WINE last night
ape4 4y ago
Just wondering, are there some things Wine can do that Windows can't? (Besides run on Linux)
- goosedragons 4y ago
  Yes. Run 16 bit apps on a 64 bit OS install. A lot of old PC games no longer have 3D acceleration support on modern Windows like Jedi Knight I. On Wine the 3D acceleration just works. You can get Windows to do this stuff too of course but not out of the box.
  - bitwize 4y ago
    Wine's 16-bit shim, winevdm, can even be run on 64-bit Windows to make it capable of running 16-bit apps.
    - cruise9 4y ago
      We use this for running an old version of 16-bit Protel EDA on our work computers. (Initially, I had setup a windows XP VM for this purpose, but it turned out to be a lot of friction for users, as well as requiring an annoying amount of setup) Generally WineVDM works very well for running Protel with a few visual bugs.
Labo333 4y ago
I have mixed experience with Wine, most of the times when I tried playing games it was close to impossible to install them. I go for Parallels Desktop those days (kudos to https://github.com/dreamncn/ParallelsDesktopCrack https://github.com/dreamncn/ParallelsDesktopCrack)
- cleanchit 4y ago
  Works way better on linux. System tray support, desktop entries, and everything.
kk6mrp 4y ago
What can't be run in Wine at this point?

196 points by neustradamus 4y ago

What's new in this release: - Bundled vkd3d upgraded to version 1.7. - Better error reporting in the IDL compiler. - Support for shared Wow64 Classes registry key. - More cleanups in IME support. - Support for configuring a WinRT dark theme. - Various bug fixes.

worldsayshi 4y ago

Is wine receiving patches from Valve's fork or are they completely separate at this point?

komadori 4y ago
AFAIK, Valve pays CodeWeavers to work on Proton, so Proton is more of a curation of Wine like CrossOver Office rather than a hard-fork.
anotherhue 4y ago
I assume they're free to pull in as they wish? I didn't see any proton reference in the changelog though.
giomasce 4y ago
Proton developer here, working for CodeWeavers. Everything we develop goes preferentially in Wine, and is kept in Proton as a "hack" only when a solution clean enough for Wine is unfeasible or too complicated. Proton is periodically rebased onto Wine, so everything in Proton and not in Wine is additional rebasing work, which we'd like to avoid as much as possible.
- steeleduncan 4y ago
  Thanks for all the great work. I hadn't realised Proton was developed by CodeWeavers. Out of curiosity, what is the relationship between Proton and your own product Crossover?
  - giomasce 4y ago
    In principle they are somewhat similar: they're both Wine + local patches (either backported from more recent Wine versions or hacks that are not suitable for upstream Wine) + some glue. CrossOver also has a GUI, which Proton doesn't need because the GUI there is Steam and Proton is supposed to be as transparent as possible. And like I said for Proton, it's in our best interest to keep the diff between Wine and CrossOver as small as possible, because that's a liability that takes its toll at each rebase. In practice Proton and CrossOver tends to have rather different sets of needs. Proton only supports Linux and is only focused on gaming. CrossOver exists for a handful of platforms, most notably macOS (which has a number of intricacies: missing 32 bit libraries, Apple Silicon, missing Vulkan drivers which requires MoltenVK, but MoltenVK itself cannot really offer all the features standard Vulkan drivers have on Linux), and is also used for non-gaming applications. CrossOver also lives in the form of specialized branches we develop for specific applications, on request of their developers. So while of course we share everything that can be shared, in my experience this tends to be not that much (except what goes upstream, of course). In pratice CrossOver and Proton live in different repositories, have independent build systems and independent release schedules.
    - steeleduncan 4y ago
      Thanks for the explanation!
  - JiNCMG 4y ago
    I've been a Crossover customer since their 2012 end of the world sale.
- foxandmouse 4y ago
  Do you think Proton could be released on Steam for macOS? This could help rejuvenate the gaming community on macOS, which is suffering due to Apple's focus on the App Store. It seems like every decision Apple makes for macOS makes it harder to support games outside of their ecosystem.
  - giomasce 4y ago
    On the technical level it should be totally doable. Whether that's something Valve is interested into, I don't have any privileged information. I know people use CrossOver with Steam on macOS, though that requires a rather intricate setup I don't know much about. I guess what you'd like to have is the kind of seamless integration that Proton has with Steam on Linux.
- natas 4y ago
  huge THANK YOU for the hard work on Wine, the entire community much appreciates, I'm a steam customer (400 games, no less!) and that's my humble contribution :) note that I commonly buy all games that run on linux :)

troad 4y ago

I'm constantly so astonished by how well Wine works these days. I remember the first time I heard about Wine, decades ago, and thinking "yeah, right!" But by God, they pulled it off. I would not have been able to move to Linux full-time without Wine. Thanks!

eurekin 4y ago
I wouldn't be surprised, if wine became a "compatibility layer" embedded into a wsl in Windows at some point
- squarefoot 4y ago
  It is already a compatibility layer to run old windows software that Microsoft no longer supports. I use it for making music, and the number of 20+ years old VST plugins that work exceptionally well is astonishing. The only problem I encountered was some of their installers failing because they reported a negative available disk space, presumably because of a bigger new variable overflowing the older smaller one they use. Running them as a older Windows version didn't work, I suspect the only way to make them run would be to implement a WINE flag to pass the installers smaller variables with that data. Aside that, I'm amazed at how good the compatibility is.
  - seba_dos1 4y ago
    You could just create a smaller filesystem in a file, mount it and export is as a Windows drive in winecfg.
    - squarefoot 4y ago
      I did something similar: made a very small partition on a USB drive and assigned it a drive letter, then tried to install in there. It didn't work because it's the variable that is bigger, not its contents, so whatever value it contains it still overflows the one expected. Short of patching the relevant WINE code (which I don't even know where to start looking for) A XP VM might be the last resort. The software once installed works fine as I experienced by moving to Linux a very old XP install I had on a backup.

buster 4y ago

Wine is just a great piece of software. Not just for gaming but the occasional dreaded enterprise software. I happily pay for crossover.

antibasilisk 4y ago

That's funny, I had a dream about running a program in WINE last night

ape4 4y ago

Just wondering, are there some things Wine can do that Windows can't? (Besides run on Linux)

goosedragons 4y ago
Yes. Run 16 bit apps on a 64 bit OS install. A lot of old PC games no longer have 3D acceleration support on modern Windows like Jedi Knight I. On Wine the 3D acceleration just works. You can get Windows to do this stuff too of course but not out of the box.
- bitwize 4y ago
  Wine's 16-bit shim, winevdm, can even be run on 64-bit Windows to make it capable of running 16-bit apps.
  - cruise9 4y ago
    We use this for running an old version of 16-bit Protel EDA on our work computers. (Initially, I had setup a windows XP VM for this purpose, but it turned out to be a lot of friction for users, as well as requiring an annoying amount of setup) Generally WineVDM works very well for running Protel with a few visual bugs.

Labo333 4y ago

I have mixed experience with Wine, most of the times when I tried playing games it was close to impossible to install them. I go for Parallels Desktop those days (kudos to https://github.com/dreamncn/ParallelsDesktopCrack https://github.com/dreamncn/ParallelsDesktopCrack)

cleanchit 4y ago
Works way better on linux. System tray support, desktop entries, and everything.

kk6mrp 4y ago

What can't be run in Wine at this point?