Wineskin 1.1.31RC2 released
New in this version 1.1.31RC2
- WineskinConfig.app
- all the internal .app files have been bundled up into a single app
- Xquartz monitoring for auto-quit fixed
- Xquartz will only quit now if either wineserver quits, or if WineskinConfig.app quits if it started from there.
- Common Direct3D registry changes done via menu
- Part of WineskinConfig.app, you can quickly change around common Direct3D settings
- Winetricks updated
- Winetricks (built into WineskinConfig.app) has been updated to the latest version, and not hard coded. The manual has directions on how it can be manually updated in the future
- Custom EXE launchers updated
- a creator for Custom EXE launchers was made into WineskinConfig.app, to make it much easier to make these. They can also now be ran just inside the wrapper (where they are created) or they can run outside of the wrapper in the same folder as the wrapper. The launcher as well as the main wrapper can be renamed without breaking the launcher.
- Info.plist no longer needs to be manually edited
- WineskinConfig.app allows you to set the 4 main Info.plist settings needed, and easily. Choose the main exe the wrapper runs without having to type any paths. Icon can be set for you just choosing any icns file on your machine. Set the top menu bar name… and set the version number you want shown. You can still manually edit the Info.plist if you want, it is still used, these quick ways just edit it for you.
- wrapper detects if set EXE is present
- When distributing a finished wrapper, the wrapper checks if the EXE is present before launching it. If it is not found, it pops up a menu asking the end user if they want to open the drive_c for manual copy, or choose an installer to run
- Wine.bundle slightly changed…
- the Wine.bundles are slightly changed. A Wine bundle from a pre-RC2 version of Wineskin will NOT work right… I’ll have new Wine.bundles up when I can for other versions of Wine
- Wine compression disabled…
- The way the WIne bundle auto compressed itself for space has been disabled in this version. Was having some issues with it I didn’t feel like fixing yet. I want to make it optional in the future. It does save a lot of space when working right though… empty unused wrapper about 75mb instead of 130mb. I’ll look into getting it working right in the future
- Please read the included Manual for all features and how to use them!
- its been updated about the many changes
click this link to see the main post on the forums for downloads!
3 Comments
20:00
I haven’t messed with WineBottler, and I don;t know exactly how it packages… and not sure what your really saying. All Wineskin is for is to make a .app port (or wrapper) for a Windows program, so you can have every program you need completely running alone and isolated from the others. No Wine or anything else having to be installed and used, everything inside the wrapper, kind of like Cider ports.
I’ll have to look at WineBottler some, but I think it just makes apps that run off the installed Wine bottler version doesn’t it? not stand alone from machine to machine? If it does, cool… right now with Wineskin you can make a full port of a program and install it just fine dragging and dropping it to another machine and running it… which is part of the primary goal, not realy on anyting else having to be installed that isn’t normally always there.
00:30
Sorry for the long delay in responding….
WineBottler needs X11. Other than that it makes a complete Windows application into a Mac application that the end-user can drag & drop to install.
My preferences is to use WineSkin, but with no Tiger compatibility, I’ll have to wait for a release that is.
Looking forward to the next release.
« Wineskin1.1.31RC1 Next Post
zeroPSX Hybrid »
This Page is mostly used for News.
If you want to look for some Action,
the Fourm would be your destination.
Also check out our Highlights:
 Ported Games |
 Emulation Corner |
 The Forge (Software) |
Blog RSS Feed
Follow Me on Twitter
02:21
Hi, I’m testing WineSkin 1.1.31RC2 with Folio Views 4.x. It works really well. I don’t understand all the options you have built-in or all the manual , which I am very grateful for. WineSkin works the best of any solution that I have tried so far. However, I like WineBottler’s wrapper better as it makes the Windows’ app a complete and separate package “.app” which seems to me that it would be easily installed by drag & drop.
If WineSkin can do this, I guess I’m not enough of a geek to understand it. Looking forward to the next release.