Wine 1.7.17 is released!

Wine 1.7.17 is released just now! The wine version will be build in an engine and will be available in “Winery“. Winery is a program where you can build wrappers with, and is available on the Wineskin website. I used Winery to build all my Wrappers for this website. The Wine engine itself is already available in Winery, so download and test it with your games when interested! There were quite some regression test fixes implanted and quite some d3d fixes as well. Another interesting improvement is that there are some fixes in the joystick support. See more details below and on WineHQ.

The Wine development release 1.7.17 is now available.

What’s new in this release:

  • More implementations for the Task Scheduler.
  • C runtime made more compatible by sharing source files.
  • Fixes in the Mac OS X joystick support.
  • Various bug fixes.

new wine engine new

Love the work we do? Become a Patron… and get extra Tiers!

  1. Hello paul !
    When i play with wineskin WOT wrapper, i can hit update wrapper ? it is good for me ?

  2. You can change engine to the latest. First download winery mentioned in the post, update it, then download the latest wine engine. Then go to the wrapper –> rightclick wrapper –> show package content –> wineskin –> advanced –> tools –> change engine –> change it to latest wine engine (1.7.17) and try run the wrapper again. Good luck.

    If this doesnt help you have to change which wrapper to use (for now).

  3. So i downloaded winery, added latest engine, clicked in wrapper change engine used, and run the game . when i clicked play, it showed window of game for short time (2 or less seconds) and quit. Seems it don’t work :-( tell if i did something wrong

  4. Engine Used: WS9Wine1.7.17

    Hardware Overview:

    Please use pastebin links and not complete output into posts

  5. Well, it looks like that the newest Wine engine isn’t working with WOT when I hear you. In that case you should use one of the 2 I have now available and wait out WOT development and some more wine development, which might fix this on your end.

Leave a Reply