I always build Wine for Wineskin at 10.6+ compatibility. I have not been able to get Wine 2.0 to successfully compile that way... haven't gotten a fix yet, so no, Wine 2.0 standard engine isn't available for Wineskin yet. I believe some people at portingteam.com forums have later OS version 2.0 and ...

In the latest couple versions of OS X (macOS), DYLD_FALLBACK_LIBRARY_PATH can only be set for 1 app directly, and Apple decided to (for security reasons) wipe it out past the 1 app you directly run, any spawned process has it wiped out. So if you set it and say run Winetricks... its set for Winetric...

over at portingteam.com some people make special engines to help with things. I only use stock Wine for the normal engines, and so far have only done 32 bit support... there are some 64 bit ones people have made on portingteam.com, but not sure how good they work.

Because I'm slow at keeping things up when my real job has me working about 15 hours a day right now

I compiled versions with Wine source to cover all the 1.8.x and up through 1.9.20 now.

Wineskin is self contained. All of Wine is uses is inside the app and not installed on your system. It will not interfere with other Wineskin apps or any other Wine install.

you should try the latest 1.7.x series, and try to find when the problem occurred... and put in a bug report, or this is likely to be in 1.8 release.

Thanks a lot for your answer. Could you please provide a link or a quick guide on how to upgrade the wrapper? Thanks a lot once again. Best, -a- I explained it to someone else on the Wineskin forums. Wineskin and other 3rd party tools that use Wine aren't technically supported at winehq.org. http:/...

If this is Wineskin... which it seems it is, then You need to upgrade the wrapper. It needs to be Wineskin 2.6.1+ to work in El Capitan. Everything broke when El Capitan came out, and I had to make a fix.

How did you install Wine? Normal Wine supported here is all command line... there is no clicking or icons. Your probably using some 3rd party utility which uses Wine.

If you use Wineskin, it broke with El Capitan, and you have to update to version 2.6.1 for a fix.

As far as I know, there is no way to do what you want. Wine has to be coded to do this itself. Wine doesn't ask for anything from OSX, so it just uses its default 2.1, and Wine thinks 2.1 is all it can do.

Make sure AIR is installed inside the same wineprefix (wrapper/app/whatever if your using some 3rd party tool)… if its installed elsewhere, it won't be found.

oldefoxx wrote:There are several posts of this nature, and this is the 3rd and final one that I will answer.

well thats good… I doubt most of these 5 year old posts need more answers

Wineskin should have all Winetricks commands. On the GUI you can "Update Winetricks" to get the latest version.

All it does is download Winetricks and parse the script to generate available options for the menu.

Your Intel HD 3000 doesn't even meet minimum requirements for the game… it would run bad even if you weren't using Wine. With the added extra layer slowing it down a bit more, its still going to run bad.

Since when does Wine have any of that? Maybe your using WineBottler and its Wine.app… which isn't normal vanilla Wine. If your using normal Wine that is supported here, it will be ran command line.

I just noticed I have this same issue…

EDIT:
I file a bug report and attached a patchfile that fixed the issue for me.
https://bugs.winehq.org/show_bug.cgi?id=38410

If you just want something easy to use… buy Crossover. It uses Wine at its core, but is made for normal end users… Wine here at winehq.org is a much more technical.

http://www.codeweavers.com

The native Mac driver is made for Quartz. Quartz is like… the main graphics model… its various parts of Core Graphics, and often the term people use for talking about Core Graphics. That is where XQuartz gets its name… its X for Quartz. Quartz on Mac is different than Quartz in Windows, and has noth...

The only errors I see are the ones preventing your compile because it doesn't meet C99 standards. You can edit the code to fix this, or you can set your compiler to ignore C99 … I don't recall the exact way to do that, and its different depending what compiler your using I'd assume.

no idea what gallium nine is… some fork off Mesa? some Mesa library? If its just custom Mesa code, you can always try building Mesa and XQuartz for it easiest just using the build options in Macports. Like sometimes I do custom builds, and add a local repo of code for certain libraries, like Mesa, t...

??????

X11/XQuartz on the Mac does use Mesa … can you be more specific?

1. That log is useless in this situation as its just X11 info and not the Wine log.

2. Wineskin is not supported here, so don't expect much if any help.

If your wineprefix you used to install is in the normal location... it will be hidden to Finder. Try typing this in Terminal and seeing if it pops up in Finder. open ~/.wine if you set a wineprefix to be /User/Winefiles or whatever, then of course its different. As to your script, it should work wet...

I don't do this much so I don't recall exactly... but it may be minimizing the old fashioned way... as a window icon in the dock next to your trashcan... clicking the main app icon won't restore those... you have to click on the minimized specific window over on the right hand area of the dock.

"That answer" has already been in this thread for 3 1/2 years. https://forum.winehq.org/viewtopic.php?f=2&t=9937#p55805. yeah.... I forget things after years... I guess including how to re-read. But I think the main more recent complaint is... if the Windows program says no title bar,...