To install wine, run the following command in macOS terminal (Applications-Utilities-Terminal) sudo port install wine. To see what files were installed by wine, run: port contents wine. To later upgrade wine, run: sudo port selfupdate && sudo port upgrade wine. Where Is Wine Installed On Macbook. The source is available now.Binary packages are in the process of being built, and will appear soon at their respective download locations. Where Is Wine Installed On Mac. January 14, 2021. The Wine team is proud to announce that the stable release Wine 6.0 is now available. How To Install Wine On Mac.
A NOTE ABOUT MAC OS 10.15 CATALINA through 11.4 BIG SUR:
Apple has decided to force 64 bit operation and is blocking unsigned software in Catalina – so Wine is much more challenging in that version. Hams are recommended to stay with Mojave for this reason. Alternately, use the commercial wine application Crossover to avoid these issues. See here if you are ready for the extra work to *try* to make Catalina Wine-friendly again.
DUE TO THE ABOVE CHANGES IN MAC OS X, THE INSTRUCTIONS BELOW *ONLY* WORK ON PRE-CATALINA VERSIONS OF OS X! IF YOU HAVE A NEWER VERSION, SEE THESE INSTRUCTIONS INSTEAD
NEW: As of Wine version 4.19 or newer, Forms and Templates, such as the ICS-213) are now working! This means Winlink Express (RMS Express) is fully functional!
Wine is a program that tricks Windows applications into thinking they are running in a full-blown Windows OS environment. It only loads bare-bones drivers and a Windows-like folder structure into a “Bottle”, so this is NOT a Windows emulator. It runs Windows apps directly in Mac OSX or Linux!
STEP 1: INSTALL HOMEBREW
Run in Terminal app:
ruby -e '$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)' < /dev/null 2> /dev/null
and press enter/return key.
If the screen prompts you to enter a password, please enter your Mac’s user password to continue. When you type the password, it won’t be displayed on screen, but the system would accept it. So just type your password and press ENTER/RETURN key. Then wait for the command to finish.
STEP 2: INSTALL WINE
Run this command in Terminal:
then run this command:
brew install wine-stable
STEP 3: Install Winetricks
Command+Spaceand type Terminal and press enter/return key.
- Run this command in Terminal:
brew install winetricks
- Run this to add a GUI for Winetricks
STEP 3: Load DotNET 3.5sp1 and Visual Basic into the Bottle
Open a window in Terminal and enter the command:
A new window will appear (if it’s blank, click OK). A window with a long list of optional Windows components and common software that can be added to a Bottle. Click on “Install a Windows DLL or component” and then click OK. Scroll down and check the boxes next to “dotnet35sp1″ and ‘vb6run” then click on the “Apply” button at the bottom of the window.
After a download completes, a number of Windows installer screens will appear… always click yes or I agree, etc., to install the software. If it asks for your name, just enter any first name and click OK. When all installations are complete, you will get a message that says “Winetricks Applied Successfully”.
NOTE: If you got an error message, you will need to run Winetricks again and select “Create a new wineprefix”. In the window that pops up, select Architecture: 32 and name the prefix “Ham” or something like that. Then repeat Step 3 again.
STEP 4: INSTALL RMS EXPRESS (and any other Windows software you like)
Download the latest version of Winlink Express (formerly RMS Express) here. Just look for the latest version of Winlink Express and click on it.
Once it downloads, unzip it and do a “Get Info” on the .exe file by Control-Click on the icon (or highlighting the icon and selecting “Get Info” in the File pull-down menu). Change the “Open with:” pull-down to “Wine” and click on the “Change All…” button so all exe files will launch under Wine. Close the Get Info window.
Now double-click the Winlink Express Installer and if all went well the program will function! There are extra steps (below) for COM Port setup if you want rig control or access to a TNC and there are also more components needed if you plan to use VARA on HF. See below.
OPTIONAL STEP A: COM PORT SETUP
IMPORTANT: First try using COM33 for USB Serial cables for TNCs, etc. IF that doesn’t work, then try this option below:
If COM33 doesn’t work, we can create COM1 port for rig control or TNC access. SKIP THE REST OF THIS STEP IF COM33 ALREADY WORKS!
First we need to find out what our USB/Serial controller cable is named. Install the driver for your cable. Plug the cable in and bring up a terminal (Terminal app can be found in Applications/Utilities).
This command lists the contents of the “dev” directory. Scroll up and look for the name of the USB cable. Some common names are:
It WILL start with either tty or cu …so if you can’t find them in the long list, try the command:
ls /dev/cu* or ls /dev/tty*
Highlight the name and copy it (we will paste it in the next step)
This command will make a symlink (aka, an alias or shortcut) for COM1 in the dosdevices folder, which points to the USB device – usually ttyUSB0 on linux, for Mac see below:
Copy the name and paste below and use your user login name and bottle name in the bolded text (replacing the brackets):
ln -s /dev/[pasted name] ~/.wine/dosdevices/com1
Just to be clear, the entire bold part of the line above including the brackets will become the name you copied, and there will be a space between the last letter of the name you paste and “~/.wine/dosdevices/com1” Once you hit the ENTER or RETURN key, that should link the device to the new virtual COM port.
Now add the COM port to the windows registry (this will make it appear in pull-down menus in RMS Express and other Windows programs running in that bottle).
sudo nano ~/.wine/system.reg
After “#arch-win32”, add the following lines (using the arrows keys to place the cursor where you want to copy/paste this) , save and exit.
NOTE: If you need more than one COM port for different control cables, just repeat the process with COM2, COM3, etc.
To save these changes, hit the CONTROL and X keys, then tap Y and then tap ENTER.
If all went well, your COM port will work now! Please note that some recent changes to the Wine software MAY force your USB-serial device onto COM33 …so if the above steps didn’t work, look for COM33 in the COM Ports pull-down of your software and try that.
OPTIONAL STEP B: GETTING VARA MODE TO WORK IN WINLINK EXPRESS
For VARA support, download these components:
and place them in /Users/[user name]/Documents/Wine/drive_c/windows/system32 and if any exist, replace them. VARA won’t work without these.
TROUBLESHOOTING: If you are still having problems installing RMS Express or getting VARA to launch within the program, check to make sure you didn’t skip a step in the DotNET and Visual Basic Runtime installations. You need all those components to be working first. Also be sure you are running Wine in a folder named “Wine” in your Documents folder for any of the above instructions to work. THIS IS CASE-SENSITIVE!
If DotNET won’t install or returns any errors at all, you may be better off using the commercial “Crossover Mac” software ($39) See here
Translations of this page:Français (Translators, please see Discussion page.)
Installing WineHQ packages
Official WineHQ packages of the development and stable branches are available for macOS 10.8 to 10.14 (Wine won't work on macOS Catalina 10.15). Please test these packages and report any bugs at http://bugs.winehq.org.
- XQuartz >= 2.7.7
- Gatekeeper must not be set to block unsigned packages.
Both .pkg files and tarball archives are available at https://dl.winehq.org/wine-builds/macosx/download.html.
Installing from a .pkg file is recommended for inexperienced users.
To install from a .pkg file, double-click on the package, and the usual macOS installer wizard should open. The process should be self-explanatory. It is possible to install the package either for all users (needs administrator privileges), or just for your current user. After the installation is finished, you should find an entry 'Wine Staging' or 'Wine Devel' in your Launchpad. By clicking on it, a new Terminal window opens with a short introduction into some important wine commands. You can now directly start wine/winecfg/... from the Terminal, as the PATH variable is set correctly. For user convenience, the package also associates itself with all *.exe files, which means you can run windows executables just by double-clicking on them.
To install from a tarball archive, simply unpack it into any directory. There is no need to set DYLD_* environment variables; all paths are relative, so it should work as long as the directory structure is preserved (you can skip the /usr prefix though using --strip-components 1).
For more information, see https://www.winehq.org/pipermail/wine-devel/2015-December/110990.html and https://www.winehq.org/pipermail/wine-devel/2016-January/111010.html.
Installing Winehq packages using homebrew
Winehq packages can be installed using homebrew
XQuartz can be installed using;
To install wine the following command can be used;
wine-stable, wine-devel or wine-staging packages can be installed using the above example.The advantage of installing via homebrew means wine is available from a standard terminal sessionThe --no-quarantine line to used to above brew adding the quarantine bit
Mac Wine Install Exe
See Building Wine on macOS
- Remove the source tree and binaries.
Using MacPorts, uninstall the wine package you previously installed:
Replace wine with wine-devel if you installed the development version.
Otherwise and if you used `sudo make install`, revert it:
Then simply delete your local Wine source code directory:
- Clean-up pseudo C: drive and registry entries as well as all programs installed to C:
- Check the hidden directory `$HOME/.local/` where Wine stores some desktop menu entries and icon files as it interoperates with the X.Org Foundation and the Free Desktop.
Mac Brew Install Wine
Note: Files in this directory are unused on macOS unless you use a UNIX window manager and other X11 applications instead of the native MacOS apps.
Mac Wine Installieren
Third Party Versions
Third party versions of Wine, such as Wineskin, Winebottler, and PlayOnMac, are not supported by WineHQ. If you are using one of those products, please retest in plain Wine before filing bugs, submitting AppDB test reports, or asking for help on the forum or in IRC.