Loading...
 

Wineskin News

RSS feed
Published by doh123 on 2012-08-03

Wineskin 2.5.6 RC1 seems like it was doing great, and I'm releasing it as full 2.5.6.  I also put out a Wineskin Winery update for version 1.7, but the only change in it is that it is now a signed app so it won't give a Gatekeeper warning in OS X 10.8 Mountain Lion.

 

Wineskin 2.5.6 Changes

  • Updated to xorg 1.12.3 and Mesa 8.0.4
  • The wrapper should be MUCH more stable
  • Wrapper *should* work even if XQuartz/X11 isn't installed, though its suggested to have them installed for access to X fonts.
  • When Winetricks runs it should honor whatever is in Custom Commands
  • Wineskin.app was cleaned up a bit on options gets disabled (grayed out) when you run tools that launch the wrapper.
  • General system info is added to the X11 log when the wrapper is run in Debug Mode (Test Run).  What Mac it is, CPUs, Ram, GPUs, etc... nothing personally identifiable like serial numbers or anything like that.
  • Wineskin.app is code signed for Gatekeeper.  If you change anything inside of Wineskin.app (including updating Winetricks) try to put it back to a stock signed version before sharing the wrapper with anyone else, or the codesign may be broken.
  • Gatekeeper - Wrappers you make will run fine on your machine, but when you share them with others, there will still be Gatekeeper warnings.  You have to do your own personal app bundle signing to get around that, or just inform the users how to do the right-click-open method to bypass Gatekeeper.

You can get Wineskin 2.5.6 inside of Wineskin Winery.  Wineskin Winery autoupdate should work as well.

Published by doh123 on 2012-07-29

Tons of fixes, but its much more stable and less error prone... so I'd like to release this if no one can find any major issues!

 

Wineskin-2.5.6RC1.app-Installer.app.zip

RC1 Changes

  • Updated to xorg 1.12.3 and Mesa 8.0.4
  • The wrapper should be MUCH more stable and hopefully no more Gray Screens of Death
  • Wrapper should work even if XQuartz/X11 isn't installed, though its suggested to have them installed for access to X fonts.

Beta 2 changes

  • Used stable xorg-server 1.12.2 due to many OpenGL issues with earlier beta.
  • When Winetricks runs it should honor whatever is in Custom Commands

Beta 1 changes

  • WineskinX11 built off newest available xorg-server (XQuartz) and related packages (including Mesa)
  • WineskinX11 will not try to double run, preventing a single wrapper from being able to cause launchd to crash (Gray Screen of Death from a single wrapper).
  • Gray Screen of Death should be less likely to happen, though it needs more testing on non-English systems which were seeing it happen most frequently. (Its actually launchd in OSX thats crashing that causes this.  Apple should really make it a bit more robust since the whole OS depends on it...)
  • Wineskin.app was cleaned up a bit on options gets disabled (grayed out) when you run tools that launch the wrapper.
  • General system info is added to the X11 log when the wrapper is run in Debug Mode (Test Run).  What Mac it is, CPUs, Ram, GPUs, etc... nothing personally identifiable like serial numbers or anything like that.
Published by doh123 on 2012-07-25

OS X Mountain Lion was released today.

Wineskin does work with Mountain Lion.  Winery has no issues, but Wineskin 2.5.6beta2 works a bit better than 2.5.5, but several older versions still work as well.

Currently Wineskin Winery.app and Wineskin.app are NOT signed apps for Gatekeeper.  I hope to get that changed next updates.

If you try to launch Wineskin Winery or Wineskin.app and get an error saying its not from the Mac app store and its not digitally signed, then the first time you run it, you need to Right click (secondary click) it, and select the "Open" option, and it will ask if you are sure... and oyu confirm you are sure.  It will only ask the first time, and you can actually run any app this way with Gatekeeper running.

When Wineskin Winery.app and Wineskin.app become signed apps, it will be just those being signed.  Since wrappers are made by you, your created wrappers will run fine on your own machine, but if you share them with anyone else, they'll get Gatekeeper warnings, meaning you'd need to sign the app yourself.  If your a developer using Wineskin, thats probably not as tough as it is for a hobbyist, so its probably just better to tell people your sharing with how to use "Right click and open" method the first time they run it.

Published by doh123 on 2012-07-24

Hopefully the last beta...

(See Release Candidate Post)

Beta 2 changes

  • Used stable xorg-server 1.12.2 due to many OpenGL issues with earlier beta.
  • When Winetricks runs it should honor whatever is in Custom Commands

Beta 1 changes

  • WineskinX11 built off newest available xorg-server (XQuartz) and related packages (including Mesa)
  • WineskinX11 will not try to double run, preventing a single wrapper from being able to cause launchd to crash (Gray Screen of Death from a single wrapper).
  • Gray Screen of Death should be less likely to happen, though it needs more testing on non-English systems which were seeing it happen most frequently. (Its actually launchd in OSX thats crashing that causes this.  Apple should really make it a bit more robust since the whole OS depends on it...)
  • Wineskin.app was cleaned up a bit on options gets disabled (grayed out) when you run tools that launch the wrapper.
  • General system info is added to the X11 log when the wrapper is run in Debug Mode (Test Run).  What Mac it is, CPUs, Ram, GPUs, etc... nothing personally identifiable like serial numbers or anything like that.
Published by doh123 on 2012-07-21

I was going to just release 2.5.6, as I think its good, but I am gonig to stick up a beta test instead just for a couple days at least, to get some feedback.

Not much has changed overall.

  • WineskinX11 built off newest available xorg-server (XQuartz) and related packages (including Mesa)
  • WineskinX11 will not try to double run, preventing a single wrapper from being able to cause launchd to crash (Gray Screen of Death from a single wrapper).
  • Gray Screen of Death should be less likely to happen, though it needs more testing on non-English systems which were seeing it happen most frequently. (Its actually launchd in OSX thats crashing that causes this.  Apple should really make it a bit more robust since the whole OS depends on it...)
  • Wineskin.app was cleaned up a bit on options gets disabled (grayed out) when you run tools that launch the wrapper.
  • General system info is added to the X11 log when the wrapper is run in Debug Mode (Test Run).  What Mac it is, CPUs, Ram, GPUs, etc... nothing personally identifiable like serial numbers or anything like that.

Still working on getting things set up so Wineskin.app and Wineskin Winery.app can be signed for Gatekeeper in Mountain Lion by Urge Software.  If something refuses to run because of Gatekeeper, just right click the app and press Open, and then confirm you really want to run it... at that point in time it will always work.  Wrappers will not be signed by Urge Software, so if you want to share your own wrapper or port with others, you'll have to sign it yourself, or the users will have to do the right-click-open method.

Download link

Please see Beta 2 Post

Published by admin on 2012-06-22

**warning, your RSS feeds are broken, sorry...**

Wineskin is still run the same way it has been, by the same people, but if you notice the URL has changed to a different domain.

Urge Software LLC is a start up company that was founded, and is owned by me, doh123, who started Wineskin.  While I'm keeping Wineskin seperate as its own open source project, instead of paying out of my own pocket in the long term for Wineskin related things, I'm shifting it over to Urge.  The only change this entails at the moment is the website is now...

http://wineskin.urgesoftware.com/

Wineskin donations will still be kept separate to only be used for Wineskin, this is basically just Urge donating some web space.  Urge Software is primaily concerend with developing original games, not porting but I and/or others will still work on Wineskin related things as well, sort of like a hobby project.

For the moment downloads are still coming from the doh123.com server for Wineskin Winery.  I plan on having all of that moved to urgesoftware.com, but hopefully with the correct forwarding in place, the downloads inside of Wineskin Winery will not break.  If they do I will make sure there is an update ASAP to fix it.

Published by doh123 on 2012-06-19

This isn't exactly a Wineskin related post, but... with the new Retina Macs not having a way to truly change the resolution, I threw together a little app that uses the WSReso command line tool I made for older versions of Wineskin for changing resolutions before RandR was added to XQuartz... it uses WSReso and its just an Applescript GUI front end that lets you change resolutions, including knocking that Retina Display Macbook Pro up to a true 2880x1800.  Works on any Macs for changing resolutions around... its very simple, but effective.

http://wineskin.urgesoftware.com/Special/Change Resolution.app.zip

EDIT: update

if you want to just have an app that automatically goes to your max resolution that you can put in your startup items... use this

Published by doh123 on 2012-06-04

 

The latest Humble Indie Bundle includes a game (Limbo) that was ported to Linux using Wine.  People who use Wine to play games -- whether on Mac or Linux -- should cheer this development, since the more game developers use Wine, the more bugs they will fix in it.
 
If you want to help Wine, please sign the petition at
 
 
to tell the Humble Bundle folks that you think porting with Wine is fine as long as the resulting game works as well as a native port.
 
There have been many Linux gamers complaining or starting petitions against using Wine at all.
Published by doh123 on 2012-05-06

If you are using a ATI/AMD GPU in your Mac, and you use an engine with Wine version 1.5.1 or later in it, it may be extremely slow.

why?

There are bugs in Apples drivers, so OpenGL rendering gets thrown back to software rendering which is very slow.  Older versions of Wine had a hacky work-around put in, but leaving it in causes problems for future work in Wine, so it was removed...

Unless Apple fixes its drivers... or the Wine graphics guys find a better way to accomplish what they want, this problem probably isn't going away.

If you need to custom build an engine that doesn't have this issue, and has the hack back in it, you can try the following as a patch...

Patch file download

I might put up some engines that already do this, but its going to start getting confusing on engines... which have xinput2 disabled to fix mouse issues... which have AMD GPU speed hack back in... which has both... which has neither... sometimes people just need to build their own engines.  It shouldn't be that hard to do, a free Xcode download and build them through Winery.

Any comments/suggestions are welcome.

 

Published by doh123 on 2012-04-18

2.5.5 is out!  There should be noticable performance improvements in many games!

List of changes...

 

  • Wrappers no longer support running on Mac OS X 10.5 from Wineskin 2.5.5 and later.  OS X 10.5 is little used, and most still using it are on PPC Macs that cannot use Wineskin anyways.  Wineskin now only supports OS X 10.6+. Any engine seen as WS9 will also only work on 10.6+.  WS8 10.5 engines will still work on Wineskin 2.5.5 though.
  • New X.org server build and related libraries, the latest available including a much updated Mesa build (for OpenGL)
  • Advanced menu redesigned slightly. Installer and Screen Settings can be changed from there too, so no going back to the main menu to get to those.  Once you go in Advanced you can do everything needed.  The Main menu is more for end users of shared wrappers who just need to install something, or change screen settings.
  • 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 ready 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 built 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.  This will only take effect on new or rebuilt wrappers.
  • 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.
  • New Engine base for making custom engines from Wine source.  Should work with Xcode 3.x and 4.x for SDKs.  Uses a gcc compiler not available in recent versions of Xcode, so it will let you install it before building if you need it.

Use the Update button in the wrapper section of Winery to get it! (Or do the manual download option like always)

First PagePage: 4/9Last Page
1234569