This tutorial is for intermediate users who want to install and useWine on their computer running macOS.You should already know the basics of how to use the command line.If you don't, read this tutorial first.
Note that Wine does notwork well with macOS 10.15 Catalina. In Catalina, which is a critical part of the macOS system that almost all of Wine relies on. You can run 64-bit applications through Wine on Catalina, but very few applications for Windows If you need to. ⭐ Kite is a free AI-powered coding assistant that will help you code faster and smarter. The Kite plugin integrates with all the top editors and IDEs to give. EDIT: This tutorial video is outdated and will be replaced with a new video which also works on M1 Macs. Use this tutorial video only on Intel Macs and if yo. Apr 12, 2021 The game does not support Intel GMA integrated video chipsets (older Mac minis and MacBooks), but does run on GeForce 9400M graphics cards or better. Notes ↑ 1.0 1.1 File/folder structure within this directory reflects the path(s) listed for Windows and/or Steam game data (use Wine regedit to access Windows registry paths).
Run your favorite Windows operating system programs direct on any computer, including Mac and Linux systems. When using any operating system, you often encounter a program you like that isn't available for your system. That's where virtual systems are your best friend. Wine is a translator for Windows API, turning it into POSIX in real-time.
What is Wine?
Wine is awesome.No, I'm not talking about the kind you drink,I mean the kind that lets you run Windows apps without theWindows operating system.It's kind of Zen, when you think about it.Oh, and did I mention it's completely free, legal, and open source?
Nowadays, Windows and Mac play nicely together.You can install Windows and Mac side by side and switch between them usingBoot Camp, but that requiresa reboot every time, and you can only use one operating system at a time.You can also use a tool likeParallels Desktop orVMware Fusionto virtualize Windows and run it together with Mac,but virtualization is slow and it takes up a lot of memory.(Your physical computer creates an imaginary 'virtual' computer within itself,and runs Windows on that. That takes a lot of resources!)On top of that, all of these solutions require you to own a legal copyof Windows, which isn't cheap!
Wine is different. When any program runs, it requests resourceslike memory and disk space from the operating system.All that Wine does is make sure that those requests get answered so thatthe program can run correctly. As far as the program knows, everythingis going smoothly because it has everything it needs.It never even realizes that it's not running on Windows!It's simpler than emulating a whole new computer, so it's faster.Since it's just translating requests, you don't need a copy ofthe actual Windows operating system. Plus, Wine is open source,which means people are continually improving it and adding new features.And you can't beat the price!
Will My Program Work With Wine?
A lot of people discover Wine because they have one specific Windows programthat they need to use, and it's the last thing preventing them from switchingto a different operating system. So, the big question is, will it work?The short answer is: probably, but it's worth checking.
The Wine project maintains a database called theAppDB that hasuser reviews of how well specific Windows programs work under Wine.Search for your program and find out! (If it's not listed, that doesn'tnecessarily mean that it won't work — only that you're apparently tryingto use a very obscure program!)
To install Wine on your Mac, you will need the following:
- macOS 10.10 (Yosemite) or above (but 10.15 Catalina is not recommended)
- Access to an Admin account, with password
- An internet connection
To check what version of macOS you're running,click on the Apple logo on the far left side of the toolbar,select 'About This Mac', and look at your versionnumber under the big 'macOS' or 'OS X'. If it's 10.10 or higher, you're all set.
Note that Wine does not work well with macOS 10.15 Catalina. Apple removed 32-bit supportin Catalina, which is a critical part of the macOS system that almost all of Wine relies on.You can run 64-bit applications through Wine on Catalina, but very few applications for Windowsare 64-bit. If you need to use Wine, you should not upgrade to Catalina.
You need an Admin account on your Mac because only Admins can install software.You will need to be logged in to this Admin account during the installation.If there is only one account on your computer, it is an Admin account.The account must have a password: if the account has no password,the
sudo utility will fail. To set or change your password,go to the Accounts section in System Preferences.
Part 1: Install Homebrew
Homebrew is a package manager that makes installingopen source programs much easier. In particular, trying to installa large program like Wine without the help of a package manager would betremendously difficult.Fortunately, Homebrew itself is simple to install: just open up theTerminal and run this command:
The Terminal will tell you what it's about to do, and ask youif you want to proceed: press Enter to do so.The Terminal may then ask for a password: this is the passwordto the Admin account on your computer. As a security measure,the Terminal does not display anything as you type, not evenasterisks (*). Type your password anyway, and press Enter. If you get somekind of error, it might be because the Admin account doesn't have apassword set. Setting a password is required.
Installing Homebrew should only take a few seconds or minutes(depending on the speed of your internet connection). When it's done,the Terminal will say that the installation was successful, and ask you torun brew doctor. Do as it suggests:
This will make Homebrew inspect your system and make sure that everythingis set up correctly. If the Terminal informs you of any issues, you'll needto fix them yourself, and then run brew doctor again to verify that youfixed them correctly. When everything is set up correctly, you'll see themessage
Your system is ready to brew, and you can move on to the next partof the tutorial.
Note: If Homebrew tells you that you need to agree to the Xcode license,you can do that by running:
The Terminal window will fill up with the Xcode license:read it, type agree and hit enter to agree to the license.
Part 2: Install Wine Using Homebrew
Now we get to actually install Wine! We'll let Homebrew do all the work,all you have to do is tell it what you want with this command:
Let's break down this command into parts.
brew refers to Homebrew, whichyou just installed.
cask refers toHomebrew Cask,an extension to Homebrew that is used to install GUI application on yourcomputer. (GUI stands for 'Graphical User Interface'. A GUI application isan app that you can see running, as opposed to invisibly runningin the background.)
install refers to the fact that you're askingHomebrew Cask to install something on your computer, and
wine-stableis the name of the thing that you want it to install. Wine has a 'stable' versionand a 'devel' version: you probably want stable, since it should have fewer bugs.
When you run this command, Homebrew will start automatically downloadingand installing software onto your computer. It might start by installingsoftware that has a totally different name: that's fine! Like most complexapplications, Wine doesn't work alone -- it relies on several other pieces of software torun correctly. These are called 'dependencies', and Homebrew is smart enoughto install them for you automatically when necessary.
While it's working, Homebrew will display messages and progress bars on the Terminal to let you know what it's doing. When it's done installing Wine, it will stop displaying messages and wait for you to type in a new command. When that happens, move on to the next step!
Part 3: Install Windows Programs Using Wine
To install a Windows program, first download the installer file:it should end with .exe. Remember the location you put it, and open upthe Terminal again.
cd to the location, and use
ls to make sure you cansee the installer file. (Note: if you do not know what
ls are,you should learn how to use the command linebefore using Wine.)
Once you are in the correct directory, run the installer through Wineby running the following command in the Terminal:
$INSTALLER is the name of the installer file. For example,if the installer file is named
setup.exe, you would run:
A window will pop up with a regular graphical Windows installer.Click through it, and you're done!
Part 4: Run Windows Programs Using Wine
Open up the Terminal and run this to get to your Program Files folder:
Run ls to see what programs you have installed. Pick a program,and enter its directory using cd. (If the folder has a space in it,you must type a before the space. For example,
Program Files.If you're having problems, try using tab autocomplete.)There should be a file that ends in
.exe: this is the program file.Type this into Terminal:
$PROGRAM is the name of the
.exe file. For example, if the programfile is named
STARCRAFT.EXE, you would run:
The program will pop up in a new window, ready to use!Enjoy using Windows on your Mac, freely and legally!
Making a Dock Icon
Many people want to be able to run Windows programs the same waythey run other programs on the Mac: by clicking an icon in the Dock.Wine isn't specifically designed to support this, but with a little trickery,we can make it do what we want.
Note: Wine prints out error messages in the Terminal when something goes wrong.By launching Windows programs via a Dock icon, you are sidestepping theTerminal, which means that if something does go wrong and Wine has to quit,it will not be able to tell you what the problem was. The first stepto solving a problem is knowing what it is, so without running Winefrom the Terminal, you won't be able to fix it, and neither will anyone else.Running from the Dock is fine as long as your program seems to be workingcorrectly, but if it crashes, the first thing you should try is running itfrom the Terminal instead: it won't prevent the program from crashing,but it will give you some clues on how to fix the problem.
In order to launch a Windows program via the Dock, we're going towrite an AppleScriptthat launches the program for us, and then putthat AppleScript in the Dock. Essentially, we're writing a program ourselves!Don't worry, it's easy enough. There is a program on your computerthat is designed for helping you write AppleScripts:it's called 'Script Editor', and you can find it in the
/Applications/Utilities directory of your computer,same as the Terminal itself.
Open up the Script Editor. You should see a window with a large areayou can type in near the top: this is where you write your AppleScript.In that area, type the following text:
You'll need to replace
$PATH_TO_PROGRAM with the path from theProgram Files directory to your program executable. You can see thatyou're simply telling the AppleScript to run a line of code in the Terminal:the same line of code that you could run to start your Windows program.
Next, press the Compile button at the top of the window.The text should become colored to indicate that Script Editorunderstands what you wrote. You can also try pressing the Run buttonto run your script: it should open the Windows program successfully.
Lastly, save your script. You can give it whatever name you'd like,but be sure to select File Format: Application in the save options,and leave Startup Screen unchecked.
Open up the Finder, go to where you saved your script, and drag thatfile to your Dock. It should stay there, just like a real application — because it is a real application! However, all it does is runthat launcher command for you, so you can move the application around,rename it, or even delete it, and it won't affect the Windows programthat you're running.
Keeping Wine Up to Date
Wine is an open source program. That means that programmersaround the world are continually improving it, adding new featuresand squashing bugs. If you don't update Wine, though, it will neverget those improvements, so it's generally a good idea to check for updatesevery so often. We can use Homebrew to keep Wine up to date: it's easy!Just run this command:
With this command, Homebrew will first update itself, if any updatesare available. It will then find all the outdated software it knows about(including Wine) and upgrade them all to the latest version.Checking for updates isn't strictly necessary, as Wine runs quite wellcurrently. However, it's a good idea to run this command every few monthsor so.
Uninstalling Wine and Homebrew
If you try Wine and you don't like it, uninstalling it is easy.Just run this command:
And Homebrew will helpfully remove Wine from your computer.However, in order to install Wine, Homebrew also had to install many othersmall programs that Wine relies upon to work correctly.(That's why the install process takes so long!)If you want to remove these as well,run this script:
Flashpoint's Mac support is heavily experimental. This page provides information about the current Flashpoint for Mac package.
Please join our Discord and provide your feedback: http://discord.gg/S9uJ794
- 2Installation Instructions
Download Beta 2019-12-15:
'wmode':'direct' to the default SWFObject parameters. This fixes certain 3D Flash games which previously did not work properly.
2019-12-14: First beta available!
- Download and unzip the latest package using the link above.
StartFlashpoint.commandto open Flashpoint.
- Do not forget this step! You must use
StartFlashpoint.command, otherwise Flashpoint will not work properly.
- Do not forget this step! You must use
If Flashpoint does not work after installation, follow the steps below:
- Click the Apple menu and open System Preferences.
- Click 'Security & Privacy,' then click the 'Privacy' tab.
- Click 'Full Disk Access'.
- Click the lock icon and enter your password to make changes. Then click the + button under the list of apps to add Terminal to the list.
- Click the lock icon again to save your changes. You should see Terminal in the list of allowed apps, as shown below.
Flash EOL Screen
If you see the Flash Player EOL information screen when you try to play a game, that means that SeaMonkey is loading your installed Flash Player plugin instead of the plugin that is bundled with Flashpoint. To fix the problem, uninstall Flash Player from your Mac and restart Flashpoint. Games should work again in SeaMonkey.
MacOS Catalina and Big Sur
Because Flashpoint's applications are from an 'unidentified developer,' if you're using Catalina or Big Sur, you'll need to approve each application before it can run. Open your system preferences, click 'Security & Privacy', then allow each of the following applications to run: StartFlashpoint.command, Flashpoint Launcher, swfbbox, and SeaMonkey. If you have trouble figuring out how to do this, watch this tutorial video.
Because Adobe Director Projectors are 32-bit applications, SPR for Mac will not work on MacOS Catalina or Big Sur. This means that Flashpoint for Mac does not support Shockwave games on Catalina or Big Sur.
MacOS Big Sur (MacOS 11.0)
Flash applications have been successfully tested and are working. To use Flashpoint with Big Sur, a few modifications are required. Follow the steps below:
- Download SeaMonkey 2.53.4 for MacOS x64 from here: https://www.seamonkey-project.org/releases/2.53.4
- Open Flashpoint Infinity's FPSoftware folder, then find the old 'SeaMonkey.app' there.
- Right-click the old SeaMonkey.app and click 'Show Package Contents.'
- Open the
Contentsfolder, then within that folder, open the
- Find the folder called
pluginsand copy it.
- Find the new 'SeaMonkey.app' file that you downloaded by searching in Finder under 'This Mac'.
- Right-click the new 'SeaMonkey.app' and click 'Show Package Contents.'
- Open the
Contentsfolder, then within that folder, open the
- Paste in the
pluginsfolder that you copied earlier.
- Go back outside of the new 'SeaMonkey.app' package and copy it.
- Open Flashpoint Infinity's FPSoftware folder, then paste the 'SeaMonkey.app' file that you just copied. Replace the original file when prompted.
Apple Silicon Macs
To run Flashpoint on Macs with the new M1 chip, you'll need to install Rosetta by following these instructions. Once you've done that, follow the instructions in the previous sections to get Flashpoint working.
To add support for Java games, you'll need to install the Java Development Kit. Follow the steps below:
- Download JDK version 8u212 from here: https://github.com/frekele/oracle-java/releases/download/8u212-b10/jdk-8u212-macosx-x64.dmg
- Open the DMG file and run the installer. Follow the on-screen instructions to install the JDK.
Running games in Wine is not yet supported, but we hope to add support for this in a future build. If you'd like to contribute to our efforts, you can download an installer here.
Using Flashpoint with Automator (optional)
You can start Flashpoint without having to click on
StartFlashpoint.command by using Automator using the below steps:
- Choose File > New.
- Select 'Application', then click Choose.
- Drag the Run Shell Script action into your workflow.
open /Users/[YOUR USERNAME HERE]/Downloads/Flashpoint Infinity for Mac Beta/StartFlashpoint.commandin the command field.
Currently, only Flashpoint Infinity is available for Mac. However, as explained here, both PHP and Apache are included with MacOS. This means it should be fairly simple to create a Flashpoint Ultimate package for MacOS as well. Let us know in our Discord if you can help!
No equivalent to the Flashpoint Redirector currently exists for MacOS. MacOS also does not provide any native way to set per-application proxy settings. In Flashpoint for Mac, the proxy settings for each supported technology must be set separately. This rules out using the Flash projectors, since they do not have configurable proxy settings. In Flashpoint for Mac, all Flash games run in a browser.
The Flashpoint FAQ contains a list of all web game technologies ('Platforms') supported in the Windows version of Flashpoint. The Mac version currently supports a small subset of these platforms. This is explained in detail below. The list of supported platforms includes an unscientific estimate of the percentage of games supported by our method.
- Flash: Supported using the SeaMonkey web browser, with a Flash plugin included. Games that use a Flash Player version other than 32 are not yet supported.
- ~95% of games supported.
- Shockwave: Supported with SPR for Mac. Because LeechProtectionRemovalHelp is only available for Windows, the majority of Shockwave games will not work properly.
- ~30% of games supported.
- Requires a 32-bit compatible OS; Catalina is not supported.
- HTML5: Supported using the SeaMonkey web browser. WebAssembly support is enabled in Flashpoint's SeaMonkey profile, so it should be compatible with nearly all of the same games as Basilisk.
- ~99% of games supported.
- Java Applets: Supported natively using the JDK. Java in the browser is not supported yet.
- ~99% of games supported.
- Unity Web Player: Has not been attempted yet. We would need to track down the Mac builds of all 12 versions of Unity Web Player that we support on Windows. Needless to say, this would be a huge challenge.
- PopCap Plugin: As far as we know, there is no version of PopCap Plugin for modern Macs.
- Authorware Web Player: Authorware is incompatible with all Intel Macs.
- GoBit Plugin: As far as we know, there is no version of GoBit Games Plugin for modern Macs.
- Silverlight: Silverlight for Mac is available here, but as explained in this StackExchange answer, Microsoft Silverlight for Mac is 32-bit only, even though the Windows version has 64-bit and 32-bit versions. This is a problem because no major browser for MacOS has a 32-bit version, and MacOS Catalina drops support for 32-bit programs entirely. As such, Silverlight is unusable on Mac.
- 3DVIA Player: As far as we know, there is no version of 3DVIA Player for modern Macs.
- 3D Groove GX: 3D Groove is incompatible with all Intel Macs.
- ActiveX: ActiveX is a Windows-only technology.
- ShiVa3D: The Windows version of the ShiVa3D Player is available in the free ShiVa Web Edition; this is where we obtained it. However, no Mac version of the ShiVa Web Edition is currently available, so we haven't been able to find a Mac version of the ShiVa3D Player. It's possible that we could extract a Mac version of the player from a Mac version of a ShiVa3D game. Or maybe we could obtain the Mac runtime from the Windows version of ShiVa3D Web Edition, since it has the capability of publishing for Mac.
A number of Flashpoint Launcher issues affect the experience of using Flashpoint Launcher on MacOS. Unfortunately, none of our Launcher developers currently have access to a Mac, so updates for the Mac version of Flashpoint Launcher will not be available in the foreseeable future. We will be unable to release a Mac version of Flashpoint 7.0 until a new version of the Launcher is built for MacOS. If you have access to MacOS and are able to build Flashpoint Launcher, please let us know!
The current issues with the Mac version of Flashpoint Launcher are listed below.
- Errors are shown in the log when services are missing from the
services.json. These services are unnecessary for Flashpoint on Mac, so the errors can be ignored.
- Flashpoint Launcher cannot find its own Version file, even if it is present in the Launcher's folder and app package.
- The Theme dropdown menu on the Config tab does not work properly. To select a theme, you must manually type the path to the theme's CSS file.
- A popup appears if the user attempts to start a Windows executable from Flashpoint. This popup tells the user to install Wine, and points them to the Linux Support page, even though the Launcher is running on Mac.
- If a shell script is specified in
execs.jsonas an alternative to a batch script, the Launcher will attempt to launch the shell script defined for Linux, even if a different shell script is defined for Darwin (MacOS).
- Flashpoint Launcher attempts to load the hidden resource forks of certain files as separate files. These files are not visible in the MacOS Finder, and have filenames beginning with
- If any Platform XML has a resource fork, all of the Platform XMLs will fail to load, causing a 'No games found' error.
- If any localization JSON file has a resource fork, a 'NotValidJSON' error will appear in the logs.
- When Wine is started from Flashpoint Launcher, it uses >70% CPU for several minutes without ever starting the intended executable. This is despite Wine working fine when started from the terminal. This issue needs to be investigated and solved before Flashpoint can support launching games through Wine.
- By default, Flashpoint Launcher will attempt to read and modify
preferences.jsoninside its own app package. Since Mac applications are not allowed to modify their own app packages, this will fail. For this reason, Flashpoint Launcher must be opened with a shell script command
StartFlashpoint.command. This script sets the current directory to the Flashpoint Launcher folder so that the Launcher accesses the
preferences.jsonin the correct location. However, this unusual way of opening the Launcher may be the cause of the previously mentioned Wine bug.
- Some keyboard controls such as the spacebar or WASD keys may not work in some games. This is a known problem with the NPAPI Flash plugin on MacOS. We plan to resolve this problem in the next build of Flashpoint for Mac by using the PPAPI plugin instead.
- Flash games with URLs pointing to filenames with special characters will not work. This is because
nosamuEmbedSWF.shdoes not properly handle special characters when it converts URLs to paths, so it cannot copy the game's HTML to the correct location in
- Some Shockwave games may not close when you quit them from the menu. If this occurs, click inside the Message Window next to the game. Then type
quitand press Enter to close the game.
- Flashpoint for Mac uses exec mappings to determine what native executable to run based on the specified Windows application path. For example,
flashplayer_32_sa.exeis mapped to
nosamuEmbedSWF.shfor MacOS. To add more exec mappings, navigate to Flashpoint's
Datafolder and open
execs.jsonin a text editor. The exec mappings use 'darwin' to refer to MacOS.
- Flashpoint for Mac uses
swfbboxto determine the width and height of an SWF file.
swfbboxis part of the
swftoolshomebrew package. To install
swftools, first install homebrew. Then type
brew install swftoolsin the terminal.
- Flashpoint for Mac requires that PHP and cURL are enabled on your system. These components should be enabled by default.
Wine On Catalina
Packaging Flashpoint for Mac
Wine For Mac Catalina 10.15
Here are some steps to keep in mind when packaging Flashpoint for Mac. This assumes that you are using the current package as a base and modifying it.
- You can follow these instructions to update Flashpoint's XMLs to the latest version.
- You can follow these instructions to update Flashpoint Router to the latest version.
FPSoftwarefolder to update SPR to the latest version. To get the latest version of SPR for Mac, see SPR for Mac.
- If you would like to distribute a modified SeaMonkey profile, be sure to clear the cache, cookies, and other data. In SeaMonkey, click
Tools -> Clear Private Data.
- If you would like to add a plugin to SeaMonkey, first install the plugin normally. Then, follow these steps:
- Navigate to
/Library/Internet Plug-Insin Finder and copy the files for the plugin you want to add.
- Navigate to Flashpoint's
SeaMonkey.appand choose 'Show Package Contents.'
- Inside the app package, navigate to
/Contents/Resources/plugins. Paste the plugin files that you copied in Step 1.
- Navigate to
- Before running or distributing Flashpoint, you should run the
dot_cleancommand inside the Flashpoint folder to remove resource forks. Flashpoint Launcher may not work properly if Flashpoint files have resource forks, as explained in Launcher Issues.