If your goal is to expand your gaming options on the Mac platform you've found the right place. So, Welcome!
Here's a little run down on what's going on here within our community; We have excellent developers that have created some really great options for porting games and managing ports and libraries. We have some excellent administration staff that made this website what it is today. Most importantly, we have an amazing user base, some of which have really excelled in porting and have shown leadership in the forums, helping other users out when they can.
Porting can be extremely easy when the titles are compatible with Wine. When certain titles require workarounds the process can be a bit more daunting. But before getting down to the nitty gritty here's some general information to consider.
So now that you're a bit more familiar with who we are and what we do why don't we check out the port database, this is where you will find the wrappers mentioned in the tutorial above.
We do not promote piracy here at the Porting Team and as such the wrappers most certainly require the Windows files to obtained and installed. Full backups available here are just that, for backup purposes only.
Before you start downloading please take a close look at the 8 tutorials available on navigating through the database, and the most efficient ways to obtain the files.
Once you've obtained the desired wrapper there are certain steps that need to be followed to get the game up and running. And questions will most certainly arise if, and when the game fails to works. This is where a lot of people become discouraged or upset because they are unaware of the proper information that needs to presented in order to assess issues.
This tutorial will help you to understand the Wineskin wrapper, which likely makes up 75% of the database library.
Once you've gotten your game installed, you're ready to test it out. At this point you'll jump for joy or scratch your head in bewilderment. No worries this is where the proper information comes into play. Check out this tutorial for what procedures need to be taken when asking for help within the forums and database
All the preceding information really is only the tip of the iceberg when it comes to porting games and application. There are a lot of settings that can configured through the Wineskin app that can mean the difference between success and failure. Please check out both pages of the wrapper tutorials for a better understanding of the porting process.
The Wine Registry
Here's a quick rundown on the importance of the registry files. Like native Windows, the programs need a "platform" to cross communicate with each other or to know that the required software is installed to run certain games and application. The Wine project has done a superb job to create vanilla Wine registries that allow hundreds, if not thousands of programs to run perfectly well out of the box. When things don't work correctly the registry is a great place to try different settings during the testing process. On the second page of the [url="http://portingteam.com/tutorials/category/4-wrapper-tutorials/%5DWrappers Tutorial Section%5B/url%5D you will find a RegEdit tutorial. RegEdit is the Wine interface to make changes to the registry files. Accessible through the Advanced Tools option of Wineskin. Although the files are all plain text based which makes them easily editable in Text Edit. Simply locate the registry files, located in the Package Contents @ Contents > Resources and double click on them to open in Text Edit. The most commonly edited file is the user.reg file under the Direct3D registry heading. Click Command+F and search Direct3D. Vanilla wine leaves this heading empty because the defaults (which can easily be added) are built into the Wine build which is located in the wswine.bundle in the Frameworks folder.
Under the Direct3D heading the registry values must maintain a specific set of guidelines. This text will demonstrate the String and DWORD values.
Here's an up to date look at the registry entries you can use while trying different configurations for your wrappers.
"New Value Type"="(:)value data"
This is only a small example of what can be changed but the Direct3D is very important entry because it dictates to Wine how to proceed in translating the Windows APIs to have the game run correctly.
For an expanded look at the the registry entries available for configuration please check out the WineHQ entry on the subject
I would like to urge users to expand on this topic...if you have some useful information that might make it easier on new users please share your tricks and tips
So once again, welcome to the Porting Team, please enjoy your stay!