Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I'm using High Sierra and quoted :
http://wineskin.urgesoftware.com/tiki-view_blog_post.php?postId=87
But disable the option changes nothing.
Quote Wineskin log errors was looking like rights errors for folders/files, I read that in that case the general suggestion is to make a new wrapper because it's too tricky to fix. I tried update the engine of the original wrapper, it didn't fix the rights problem.
OS: HighSierra 10.13.6
Procedure:
1. Download Wineskin Winery 1.7 if you haven't it already
http://wineskin.urgesoftware.com/tiki-index.php?page=Downloads
No install for mac, ready to go.
Consider it as a manager for Wineskin.
2. Launch Wineskin Winery to update the available engines for Wineskin in your Mac.
Click on + at bottom of the list.
Select WS9Winesin2.22 (or a more recent)
Click Download and Install -> OK
Wait and follow the instructions if any.
3. Create a new blank wrapper with Wineskin Winery
Click Create New Blank Wrapper
Name: Jagged Alliance 2 Classic
OK
Wait and follow the instructions if any.
Click View wrapper in Finder
4. Transfert game files from old wrapper to new wrapper
On both original and new Jagged Alliance 2 Classic: Right clck -> Show package content -> browse in Contents/Resources
Then copy from old to new:
drive_c/Jagged Alliance 2
JA2_Icon.icns
Wineskin.icns
5. Setup Wineskin of new wrapper
Launch Wineskin of new wrapper
Click Advanced
Select the Exe: Click Browse -> Select Jagged Alliance 2/ja2.exe
Click Test Run -> Launch the game cleanly.
6. Run the game
Exit from package content.
Double click the new Jagged Alliance 2 Classic should launch the game cleanly.
7. Integration to Steam
Clearly it's only to have Steam accept the new package. It's also to get the right icon.
Copy from old to new the file Info.plist and override the existing.
Delete the old Jagged Alliance 2 Classic file and replace it with the new one.
The icon will appear after some time.
Steam client identifies fine the game for launching and detect quit.
Most probably it's the same fix for Jagged Alliance 2 Wildfire because error had the same problem of rights.
But it's not working for Wildfire, the same operation launch the game but ask a serial number sigh.
Clearly for Wildfire when moving files from old package to fresh new package, more files need be copied than what I listed above.
system.reg.
user.reg
userdef.reg
Then Wildfire starts fine, no key requested, I have played only Classic, but at least Wildfire launch and welcome screen is fine.
But Doroks Guide worked for me fine! thanks a lot!
I googled "Jagged Alliance 2 Wildfire not starting on MacOS" and only found some old guides which all not worked. Took me ages to find this guide and get Jagged Alliance 2 Wildfire running. I'm just writing this last paragraph, that may in future this pages rankes higher in google search so other will find it faster.