![]() current Wineskin 2.0 Beta thread at portingteam. besides RandR in Xquartz being totally done. I'm hoping to have all beta stuff updated with everything currently on my "working on" list within 2 weeks. I also love input and suggestions on Wineskin if anyone thinks things need to be changed or added. Developed by Kronenberg Informatik Lsungen. No need to install emulators or operating systems. and have been making it up as I went along ever sense. WineBottler packages Windows-based programs snugly into OS X app-bundles. but I used to use Mike's Darwine builds a lot before he started WineBottler back before I got into how the heck to do any of this stuff myself. Whats the difference Which is most simple Just looking for a quick 1-2-3, super simple, easy to use, no 'extra' screens involved. Other than that I don't know a lot about current WineBottler, as I stopped using it any about a year ago when i started Wineskin. 1.2 still has some limitations that 2.0 beta doesn't have. so thats its cutting edge in support and performance, and the same exact version built in across 10.5 and 10.6.ΔΆ.0 beta is still buggy, and 1.2 less buggy overall. Another thing i wanted was a built in X11, not just using X11.app on the system. thats one major point to Wineskin over WineBottler (and one of the major reasons I started Wineskin) is that anyone should be able to take and modify some Wine source code and use it easily with a Wineskin wrapper. There are some ways to fix mouse issues on certain games, but they take Wine patches, which means you have to custom compile your own WineskinEngine.bundle. which would at least let people hit CMD+Q and have it exit properly if its stuck on a black screen. As a minor work around, in case i do not find it anytime soon, I have stuck on my list to add in that if the X server is killed (CMD+Q or however) that it should kill off its wineserver on its own and do a normal shut down. I have had a few people complain about programs not quitting right in Wineskin using Wine versions 1.3+ but I haven't been able to reproduce it yet so I haven't narrowed down why this is happening for some people. ![]() Once someone get it working they should be able to share wrappers around pretty easy. You may want to look at the forums at and see if someone already has working wrappers using Wineskin or Cider or CXZ/S, which you can use. This is mainly because its very hard to get games working right in Wine. Click to s a game by game basis, and I've designed Wineskin to be more of a porting tool to be used by people who port a lot, not just a casual user.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |