Wineskin News

Wineskin 2.5.5 Beta 1

Published by doh123 on 2012-04-11

Wineskin update 2.5.5 beta test is here... I'd appreciate feedback and testing results.

Just download this... run it and it'll show up as the wrapper in Winery.  If you use "Update" for the wrapper in Winery it'll go back to 2.5.4.

See Beta2 download Wineskin 2.5.5 Beta 2

Main changes...

  • Wrappers no longer support running on Mac OS X 10.5 from Wineskin 2.5.5 and later.  OSX 10.5 is very little used, and most still using it are on PPC Macs that cannot use Wineskin anyways.
  • New X.org server build and related libraries, the latest available including a much updated Mesa build (for OpenGL)
  • New Installer Window added.  It describes more what is going on, and if you choose a EXE it works the same as before, but it also now has options to copy or move a folder inside the wrapper so you can use it to get in pre-installed programs or programs that do not install and just run.
  • New testing option added that will launch Terminal read to use Wine from the wrappers engine in a normal command line way.  This is for Wine specific testing and comparing and doesn't use anything in the wrapper besides the Wine build in the engine.  All usage is command line and the wineprefix is the default ~/.wine unless you change it.  If your using a stock engine this should be considered normal Wine usage that *should* be reportable at winehq.org.
  • There is now an option to use XQuartz instead of the build in WineskinX11.  Some features may not work right with it, but it will run things under XQuartz.app instead of its own icon.  This is disabled by default. This will ONLY try to use normal XQuartz installed to /opt/X11... not X11.app or Macports or whatever... may be buggy and go back to your default X11.app if XQuartz is missing, but could cause a lot of problems.
  • Default gray for windows made more neutral gray instead of Windows normal reddish gray to match OSX better.
  • Always Make Log Files option added in Wineskin.app so you do not have to only use Test Run to get them.
  • Custom EXE launchers should work right again to use multiple EXEs at once.
  • Custom EXEs should be less likely to crashing with some special characters in path names.