Wine 10.0-rc5 Brings Another 31 Bug Fixes

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • phoronix
    Administrator
    • Jan 2007
    • 67049

    Wine 10.0-rc5 Brings Another 31 Bug Fixes

    Phoronix: Wine 10.0-rc5 Brings Another 31 Bug Fixes

    Wine 10.0 is working its way toward a stable release likely in the next week or two, but today there is Wine 10.0-rc5 with the latest round of fixes...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite
  • pinguinpc
    Senior Member
    • Jun 2009
    • 912

    #2
    This wine version solve some issues related alpha protocol launcher for example (however in my case stay work ok maybe for dxvk)



    Last edited by pinguinpc; 10 January 2025, 08:39 PM.

    Comment

    • the-burrito-triangle
      Phoronix Member
      • Jul 2024
      • 73

      #3
      I'm all for games working with Wine, but it seems like this is the only thing the current devs care about. The latest Wine can't even run Windows Vista calculator... And can barely run Vista/7 card games if you add overrides for wmasf.dll and wmvcore.dll. One nice thing I recently encountered is getting Windows apps to work with a USB to serial adapter. Took some reading (and the Wine documents are complete shit at explaining exactly what needs to be done--took a stack exchange thread to figure it all out), but I was able to run Termite to test an old serial to GPIB/HPIB/IEEE488 controller. I like Termite because it's specifically set up for easy control of serial comms--like what termination characters, if any, are appended to the output. And it doesn't send a single char at a time like putty does: you type in the *whole* string and then send that with a single termination. I could roll my own native app or script to do this, but why piss into the wind when you don't have to?

      Comment

      • ssokolow
        Senior Member
        • Nov 2013
        • 5057

        #4
        Originally posted by the-burrito-triangle View Post
        I'm all for games working with Wine, but it seems like this is the only thing the current devs care about.
        That'd be because the big boost in Wine development came from Valve contracting with Codeweavers to develop and maintain Proton. With the big Wine devs working for Codeweavers in a "Codeweavers Crossover is Chrome and Wine is Chromium" sort of configuration, it makes perfect sense that you'd get almost exclusive focus on fixing bugs that affect game compatibility if that's what their probable biggest customer wants.

        Comment

        • avis
          Senior Member
          • Dec 2022
          • 2142

          #5
          Originally posted by the-burrito-triangle View Post
          I'm all for games working with Wine, but it seems like this is the only thing the current devs care about. The latest Wine can't even run Windows Vista calculator... And can barely run Vista/7 card games if you add overrides for wmasf.dll and wmvcore.dll. One nice thing I recently encountered is getting Windows apps to work with a USB to serial adapter. Took some reading (and the Wine documents are complete shit at explaining exactly what needs to be done--took a stack exchange thread to figure it all out), but I was able to run Termite to test an old serial to GPIB/HPIB/IEEE488 controller. I like Termite because it's specifically set up for easy control of serial comms--like what termination characters, if any, are appended to the output. And it doesn't send a single char at a time like putty does: you type in the *whole* string and then send that with a single termination. I could roll my own native app or script to do this, but why piss into the wind when you don't have to?
          The built-in Windows apps are a big exceptions because of how they are coded and what dependencies they use. It's not Wine's primary use case and I'm glad developers aren't wasting time resolving these issues because the vast majority of the people who use Wine, use it to run third-party applications, not the applications that come with Windows.

          Comment

          • Weasel
            Senior Member
            • Feb 2017
            • 4419

            #6
            Originally posted by avis View Post

            The built-in Windows apps are a big exceptions because of how they are coded and what dependencies they use. It's not Wine's primary use case and I'm glad developers aren't wasting time resolving these issues because the vast majority of the people who use Wine, use it to run third-party applications, not the applications that come with Windows.
            I guess it's also because Windows apps tend to use obscure Windows features or latest features since they (Microsoft) designed them so they know them best. Other devs are usually slower to move to them or couldn't care less about them.

            Comment

            • Nth_man
              Senior Member
              • Nov 2012
              • 1006

              #7
              Originally posted by Weasel View Post
              I guess it's also because Windows apps tend to use obscure Windows features or latest features since they (Microsoft) designed them so they know them best. Other devs are usually slower to move to them or couldn't care less about them.
              Using obscure or unusual features ends up being advantageous to Microsoft, as it makes more difficult that people use alternatives to Windows like Wine.

              Comment

              • ssokolow
                Senior Member
                • Nov 2013
                • 5057

                #8
                Originally posted by Nth_man View Post

                Using obscure or unusual features ends up being advantageous to Microsoft, as it makes more difficult that people use alternatives to Windows like Wine.
                Of course... but they can't force third-party developers to use them. The best they've settled for is making it more difficult to continue to compile for older versions of Windows as you continue to upgrade your Visual Studio.

                Comment

                • Nth_man
                  Senior Member
                  • Nov 2012
                  • 1006

                  #9
                  Originally posted by Weasel View Post
                  I guess it's also because Windows apps tend to use obscure Windows features or latest features since they (Microsoft) designed them so they know them best. Other devs are usually slower to move to them or couldn't care less about them.
                  "How do you hit a moving target?" by Codeweavers
                  By James Ramey | The struggle is real. The biggest challenge is that Microsoft Office 2016 and Microsoft Office 365 are ‘moving targets’. As soon as our developers think they have an issue solved, the issue changes.


                  "the Windows API is a dangerous, finicky, and moving target":
                  Lampros Liontos's answer: The Windows API is protected by copyright. It is also unique to the Windows operating system, as it depends on all of the core Windows systems being present. Additionally, it is constantly being updated in order to introduce new features and security fixes. This means th...

                  Comment

                  • fafreeman
                    Phoronix Member
                    • Feb 2021
                    • 109

                    #10
                    rc5 appears to have completely broken dotnet support. making a new prefix and reinstalling dotnet 9 and 8 didn't fix it. my dotnet applications would fail to launch. i had to revert back to rc4 to get dotnet working again.

                    Comment

                    Working...
                    X