News post about Open Source change -> http://portingteam.com/2009/11/wineskin-plans/

All versions I make and update should be available in the following link download folder...

**********Wineskin Downloads Link**********

Downloads of Wineskin Wine.bundles also available in multiple Wine versions. You *should* be able to rename these to "Wine.bundle" and replace the one inside Wineskin to change the Wine version.

Please use this thread for support and suggestions, or just general discussion about Wineskin.

For the latest news updates, always check the main blog in the Wineskin section....
http://portingteam.com/category/tools/wineskin/

What is Wineskin?
This is a wrapper using Wine and XQuartz, to help make Mac OS X ports of Windows software. It works on Mac OS X 10.5 and 10.6 (10.4 support is being worked on)
Make sure you check the Wine HQ App database for information on specific games and what changes have to be made to work. This wrapper should run software pretty much like standard Wine with X11.app... if it doesn't work in one, it shouldn't work in the other.

Current Work for next version

• re-writing the entire program in Bash scripts, to release open source under LGPL

Mostly done, fine tuning a few things.
• making WineskinConfig.app, just do basic config stuff.

I moved winecfg, regedit, winetricks, and installer back out as separate apps. I just like it better this way after working on CXS/CXZ updates...
• Try to get Wineskin working properly in 10.4, so it will work right on all x86 builds of Mac OS X.

Getting good running Wine and Xquartz for 10.4 - 10.6 is the main thing I have left... getting near done.
• enable the ability to use Xquartz sucky full screen mode

When main wrapper launched, full screen and resolution change happens. Apps cannot control this, its settings in the Info.plist. I made a ScreenConfig.app in the wrapper that can be used to set this, so Info.plist editing is not needed.
• change Wineskin versioning system...

Not going to include Wine version numbers in the main line anymore... Can use any version of Wine in them... so doesn't make a lot of sense.
• create a Wineskin Lite version with engine installs locally on the machine (like CXS to CXZ).

Might not be done for next version, still haven't totally decided how i want to handle it.

FUTURE PLANS
• Need to make tons of Wine version builds for new Open Source wineskin... there is changes, and some stuff has to be different, including re-made for 10.4 support.

• Make Wine.bundle upgrades/downgrades possible through WineskinConfig.app, instead of having to do it manually.

• Make a way for the main Wineskin program to be able to handle opening file types, then opening ported apps correctly and opening the file that was chosen... so say if you were running MS word in this wrapper and wanted a .doc to directly open the ported app, it could do it right. Not sure how to go about this, looks very complicated and I'd have to learn more Cocoa… and wouldn't work for every app out there anyways, would depend how the win app works...

• Look into adding more language support.... anyone want to try to help with this? Not sure how to go about it just yet.

• Fix any known issues or bugs...

New in current version... 1.1.32RC3

• Updated default Wine version to 1.1.32

still built with OpenAL and Win16 disabled... can't get them to work... but shouldn't really matter for anything as of yet.
• Option to set flags added

WineskinConfig.app now lets you set flags after the executable for the main wrapper, and for CustomEXE launchers.
• Added way to kill WineskinConfig if its locked (or whatever)

WineskinConfig.app will offer to let you kill all Wineskin processes, if you try to launch it again while its already running. Useful if its locked up or screwed up in some way.
• Missing exe launch list updated

added option to open to contents folder, and to run WineskinConfig.app
• Running multiple Wineskin based ports at the same time now works

You can run multiple Wineskin based ports at the same time now, as long as they have a unique top menu bar name set.
• changed to single User folder for all users of wrapper

Default user name in the wrapper User folder is now called Wineskin. Any app running in Wineskin will use this folder as the user folder.
• wrote directions on how to make a Wine.bundle

Directions added to manual on how to make a custom built Wineskin compatible Wine.bundle
• Please read the included Manual for all features and how to use them!

its been updated about the changes

Known issues
Please report back issues you have so I can investigate

• Many Winetricks scripts will not work right if there is a space in the .app name, or anywhere in the path to the app. When using Winetricks, please make sure the full path including the app name contains no spaces... you can change that after your done with any Winetricks you want to do.

• Some apps can get messed up if you quickly try to launch and close WineskinConfig.app and main wrapper... just don't do it. Wont cause any damage, just things might not run.

• There can be problems with not only Winetricks, but running WineskinConfig.app in general if there are any spaces in the name (or path) of the wrapper.... for now temporarily remove the spaces...

• I have found that if your firewall is on, and you have to answer on a new wrapper to "allow" X11.bin access, that the wrapper times out, apparently the question doesn't hold up the process, and it just keeps going, and errors out because Wine tries to do something and the X11 server isn't running yet.... once you have clicked allow, and launch it again, it then works... I'll have to look more into it, see if I can get around the problem, or at least make sure if it screws up and doesn't run the first time, that it clears out everything right so it will launch the second time without needing a Wineskin Kill.

Suggestions?

Dear Doh123,

Wineskin RC2.1 finally succesfully run Monkey Island SE!!!!!!!!!!!

I have only one problem
Program lost saved games when I quit wrapper application.
On XP Monkey Island save settings and game data into
Document and settings\user\Application Data\LucasArts\The Secret of Monkey Island Special Edition\

Wineskin also save - but only temporary- data to users/myname/Application Data/Lucas Arts/The Secret of Monkey Island Special Edition\
directory, but when I quit application all myname directory erase.

hmm... didn't really think about anything saving data in there....

not sure exactly how to handle it. If I leave it, anything you pass to someone else wont see that folder unless they use the same user name....

maybe I can make the user folder stay and just rename itself to whoever is running the app... that would probably be the best thinking about it.

thought I had just got done with RC3... looks like this is the last change I gotta put in it.

RC3 up for download....

should fix kenand's Monkey Island SE problem, as well as other things

Dear Doh123,

Thank you very much your great work!!!
With RC3 Moneky island SE works perfectly!
Saving game config, saving and lading game also works!

Thank you very much!

cool! Just something I overlooked... don;t always think things through all the way, which is why I like feedback, or bug reports... I don't get a whole lot though.

I'm not getting anything out of RC3...
It doesn't even get 1 bounce before it crashes when attempting to launch an exe.

After rename wrapper not starting programms if i change back name to wineskin program agein running normal.

I dunno.. the main wrapper is working fine for me no matter what name I use.... something may be screwed up, try killing Wineskin to reset it.

I do think i just found a bug with WineskinConfig.app not working if there is a space in the path or name of the app... so take any spaces out temporarily to run that.

A great work again doh'!I'm a big fan

what kind of crash? what exe? whats the logs say?

Dear Doh123,

I made a wrapper for Monkey island SE with Wineskin RC3.
Not always works (but about 80-90% works), I think sometimes -like RC2- makes folder into user directory with your user name, and did not use Wineskin folder. But if makes user name folder, deletes folder when wrapper quit.

I make wrapper Torchlinght game with wineskin RC3, a bit more difficult than Monkey island because game start only safe mode under Wine, that must put config file into Application data directory, I put and games start, but sometimes wineskin looking for config data "username" directory and not Wineskin directory and Torchlight do not start or crash.

thanks.. I'll see if I can reproduce that... not sure how it would happen... Wine makes it on its own if its not there, though it doesn't make all links correct which is why I do it manually. I have it rename the "Wineskin" folder over to the user name of the current user before Wine is ever invoked though... maybe I messed up something somewhere and Wine is somehow over-writing it...

It may mess up because of needed clean up stuff when you close down if you launch it again (or launch WineskinConfig) within a few seconds of closing it (or maybe longer on slower machines, but really shouldn't be more than say 4 seconds from ending the program.)

If I could make Wine only look at a Wineskin folder and not for a User folder and mess with renaming that would be cool, but I'd have to figure out how to do that and modify Wine source, which I'd prefer to stick with unmodified source.

Dear Doh,

Maybe recognized fault, and the bug is some different, but wrapper sometimes do not work, and I do not know why.
I have enough fast machine MacBook 2.13 with 4 Gbyte RAM.

I make Tochlight wrapper also put into forum, and I hope many user will test it.

occasionally WIneskin wrappers will just close when trying to start them... and I haven't figured out why... you can try to run it again and usually always works a second try. Its really weird.

EDIT: I have found that if your firewall is on, and you have to answer on a new wrapper to "allow" X11.bin access, that the wrapper times out, apparently the question doesn't hold up the process, and it just keeps going, and errors out because Wine tries to do something and the X11 server isn't running yet.... once you have clicked allow, and launch it again, it then works...

I'll have to look more into it, see if I can get around the problem, or at least make sure if it screws up and doesn't run the first time, that it clears out everything right so it will launch the second time without needing a Wineskin Kill.

I try to make wrapper The Battle for Middle Earth II with Wineskin.
Setup works, game starts, but send DirectX error, (Graphic cards do not supported)
I have Nvidia 9400, and same setup works -with some glich- in CXSkin wrapper.

what all did you try? Sometimes takes awhile to track down and fix DX problems... You have to do all that manually, cuz it depends on the specific program. There DX reg settings and some winetricks things that might help.

Send check your directX cimpatible Video cards, that meet requirements error message.
When I copy installed app to CXSkin wrapper works well in CXSkin. That I think CXSkin graphic support is better.
But setup and configure part of Wineskin much much better, than CXSkin. Dear Doh you made great work with Wineskin.

sounds like a bad setting its not liking in the registry.. or something in the newer Wine build... I'm sure it'll work in Wineskin, just takes some troubleshooting and possibly changing Wine versions... getting some games working in wrappers right is a bit tougher than others.

Dear DOh,

There is a WineX project for Linux
Better DirectX support, tah simple winem, but I think not freeware.
http://sourceforge.net/projects/winex/
May help you for better DirectX support

WineX changed its name to Cedega... the Mac version is called Cider

even with that, there is too much problems with Cedega to run right on OSX.. it would need major modifications, I have tried compiling it and there waaaay too many problems. Due to licensing differences I cannot legally mix any code from current Wine and Cedega either.... and don't think I'd want to anyways, Wine has come a LONG way since the WineX split causing them to become competing products.

Dear Doh,
I have another Question.
I have the Game Battle of Middleearth 1. I tried this before Wineskin exists with Cider, but I couldn't play online, because of the copy-protection...so I deleted it...
But the real Wine supports the SafeDisk copy-protection of BFME.
So my question: Does WineSkin support SafeDisk? If no, why not?

Thx, I'm a real fan of your Wrappers and sorry form my English.
Drakulix

So lets see more compatible =]
The Wine development release 1.1.33 is now available.

What's new in this release (see below for details):
- Gecko now installed at wineprefix creation time.
- Better support for certificates in crypt32.
- Improved sound support in mciwave.
- Some more Direct3D 10 functions.
- Many cleanups for issues spotted by Valgrind.
- Various bug fixes.
-----
Now we can port:
Left 4 Dead 2
Silent Hill 4: The Room
Guild Wars
Red Faction Guerrilla

Wineskin will do everything Wine will... but I'm not sure it supports SafeDisk... but if it does it'll work.

Crossover is not standard Wine... anything Crossover supports doesn't mean standard Wine will.... and visa versa... CXS/CXZ port might be possible if Crossover can run SafeDisk.... but not sure.

yep... I look at winehq multiple times a day, always know when new versions are out. Just busy recoding Wineskin for the new Open source and Lite versions... and 10.4 support.... will have to rebuild all Wine.bundles for 10.4. Once I get the code working good for release wI'll start working on Wine versions available again.

I'm worried about them forcing gecko on us though.. thats a huge waste of space making wrappers bigger when we might not even want or need gecko...

I have new idea but this is not be wrapper,what if
1. Make full wine porting program with menu programs lunched analog this

or analog this

2. Add support autorun .exe files from wine installer, how this did their WineBottler v1.1.32
or analog CX
3. Make easy install programm porter analog drag&drop
4. Make in disk section "/" folder with ported programms
5. Soon be ready Xquartz 2.4.1

As you can see here. it does support SafeDisk V2 :http://wiki.winehq.org/CopyProtection
Big thx for the fast answer, I will try.

those are good ideas for a program... but not the point of Wineskin. Its designed for making ports/wrappers, not for competition with Crossover. I don't have any intentions or wants to make a program like that. I like making programs run like native apps and sharing the wrappers and ports around.

Xquartz 2.4.1 is something that will most likely go in.

Yes, but I propose to make a more user-friendly porter, who can install and do wrappers, as a standalone program, wineskins, and so the program for the port it is tuned for installation, configuration and stuff, so why not make it built into the system let them put the program creates wrappers which then can be used without this program, so that we can maintain the maximum porting after the small size wrappers and maximum functionality for a package, so it is possible to add auto-update feature that will always see the latest version to create a common framework for software installation, too will make easier the installation and creation of varperov do not need to spread a lot of megabytes of files to that would make his porter, or simply chose the package configuration settings for the new program and all programs you have in this port needs to be 1 porgramma for portirovki of about 200 mb and up to 1 megabyte of settings and other functions for program installation.
The difference between Wineskins, and CrossOver will be a big, Crossover does not create a ready-to-use applications without crossover, but the difference between cider is normally something that we can easily set the application easier to create ports, thus will remain a problem with fullscreen but it is a matter of time and from us There is not as independent should speak with the developers of X11 can they do have proper support.

I think i kind of understand what your saying, but its jut a hobby and I'm trying to learn as I go... these are nice goals, but a lot of stuff I'd have to learn to get started, so nothing that would be anytime soon. I'd have to handle many Wine versions.. many X11 versions.. and an interface all for a local user.. much like Crossover.. then a full working standalone wrapper made from it would be a very small addition.... if that was my plan to make.. what I have currently would be like 5% of it done.

as for Xquartz supporting real fullscreen and resolution switching... it would be nice, but it has been a requested feature on their bug tracker for over 2 years... I wont hold my breath for any of the developers working on it to actually do it.... http://xquartz.macosforge.org/trac/ticket/6