Putty for Mac 8.6.0 status on OS X 10.10 Yosemite. Wine Reviews has release information and reviews of Windows applications and games running on Linux Mac OS X and Android using Wine from WineHQ.org Q4Wine PlayOnLinux PlayOnMac WineBottler WineSkin WineTricks and Wine-Staging. Wineskin is a tool used to make ports of Windows software to Mac OS X. The ports are in the form of normal Mac application bundle wrappers. It works like a wrapper around the Windows software, and you can share just the wrappers if you choose.
In 2016, you can do pretty much everything on a that you can do on a. But if there are Windows applications that you desperately need for work (or play), you’d probably prefer an alternative to installing another whole operating system on your computer. DON’T MISS: On Friday, suggested two popular pieces of software that will allow you to bring many of your favorite Windows apps over to Mac without creating a partition or any of that nonsense. WineBottler First up is a free program called Wine, which originated as a Linux project, but has been repackaged for Mac in the form of WineBottler.
It won’t run everything, but the current compatibility list shows over 23,000 apps in the database. The top voted apps are (as you might expect) games, but there’s plenty of productivity software on the list as well.
In order to download the free software, and grab either the latest stable build or the development build (the latter of which will work on OS X Yosemite and El Capitan). CrossOver Mac If WineBottler isn’t cutting it and you’d rather give shareware a shot, is the program for you. I personally haven’t used CrossOver since the early days of OS X Mountain Lion, but even back then it was a fantastic alternative to Boot Camp. Thousands of applications have already been tested and are confirmed to work with CrossOver, but you can try using any app with CrossOver just to see if it works.
Chances are good that it will. Unlike WineBottler, but that entitles you to unlimited use of the version you buy and one month of updates.
$50 extends upgrades and email support to 6 months and $60 extends both to a full year. If you need the full functionality of Windows, these two programs probably won’t be enough, but they’re great for gamers or users that need access to a select set of apps on their Macs.
The Complete Guide A to Z to Install Wine On Mac OS X Every Mac user I know loves their Mac and wouldn’t trade it for the world. But every now and then, there is a Windows application that they would like to be able to run. Sure there are Mac apps out there that can enable you to run them, like Boot Camp and VMWare, but what if you just want to run a couple apps? Can you really justify buying software for that? I would imagine not, unless you just absolutely can’t do without it. This article takes you through the entire process from start to finish to get a working Wine environment on your Mac.
Now, there are other ways to run Wine on Mac OS X, but I feel this is probably the most common. Plus, if you visit the support forums, most of those guys are running Wine this way, so the solutions they give usually apply to the command line. Once you have Wine setup this way, I think it will be easier to find help and support.
Rather than having to try and figure out how to apply it to your particular install. Wine Compatibility It’s not guaranteed that the application you want to use will work with Wine. Wine is an ongoing project and the team is constantly updating it and making improvements. They do have a list of applications that you can search to see how compatible your application is. You can find it here. If you cannot find your application listed, don’t give up hope.
This just means it’s not very popular. For the ones that are listed, they are usually accompanied by any issues or bugs that people have encountered and how well it works. When it’s all said and done, the best way to see if your application works, is to just try!
Plus, there is a huge community that you can turn to for support. There are a few prerequisites for this installation of Wine. There are tutorials available for each one of these requirements if you need help installing them. Make sure you have an Intel-based Mac. – Click on the Apple logo in the upper left hand corner of your menu bar and select “About This Mac” – If you see Intel in the processor description, you are good to go.
Install XCode and XCode Command Line Tools. If you are running OS X 10.9 Mavericks, then you will need to login to the Apple Developer site and download the XCode Command Line Tool for Mavericks, otherwise you will not be able to install Python27. Java – If you don’t have it, you can download and install it for free. Make sure you get the appropriate for your version of OS X.
Step #1 – Install MacPorts MacPorts is an open source software utility that simplifies the process of installing Wine. Typically, Wine would have to be built from scratch, compiled and installed. Which is one reason why a lot of people have avoided it. MacPorts takes care of this for you. Bottom line, it makes life a whole lot easier. Go to the MacPorts website.
Look under “Installing MacPorts” in the “Getting Started” section. Choose the appropriate version. For this tutorial I’m using Mountain Lion. Double click the.dmg file and run through the installation.
Step #3 – Install Wine with MacPorts For this step, I would recommend disabling Sleep Mode on your Mac. This process can take quite a while to complete. It will be downloading, compiling and installing Wine. There are two different options here. The first one installs the latest official release of Wine. The second installs the very latest “beta” version.
The Wine project moves pretty fast, so the developers publish “mini” versions in between official releases. These have bugs and issues that have been fixed so if you’re having trouble with a particular application you might want install this version.
Otherwise, if you go with the official release, you’ll have to wait until a new official release is published. Open a terminal window and decide which install option you want to do. For the latest “official” release. Step #4 – Install Winetricks Winetricks is truly the key to using Wine. It is a shell script utility that is used to download and install required Windows software.
Normally you would have to find DLLs, runtime engines, fonts, etc and figure out how to install them. Winetricks simplifies this process by doing all that tedious work for you.
What’s the difference between this and MacPorts? MacPorts installs open source software on your Mac.
Winetricks installs Windows software in your Wine environment, or wineprefix. Remember those utilities that you installed earlier? One of them was “wget” and is about to make this step super easy. Open a new terminal window. Then type “ls” (without the quotes).
You should see something like this. Next, navigate to the Desktop by typing “cd Desktop”. Now type, this command. Step #6 – Installing and Running a Windows Application This is basically how you would install and run a Windows application.
Keep in mind, that there may be dependencies that will need to be installed before it will run. One good rule of thumb is to pay attention to any software requirements. If your application requires.NET, then you will need to install that in your wineprefix first. Just as if you were installing it on your Windows computer. You’ll need to copy the installer for your software over to your Mac. Usually setup.exe or an.msi file.
Then you’ll open a terminal window and navigate to the directory where you copied it to. To run the installer, type the following. Step #7 – Updating Wine on Mac and Winetricks Like I said before, Wine is constantly being updated by the development team. They have a long list of bugs to fix and new functions to add.
One thing about the team is that they are exceptionally fast. You never have to wait very long for a newer version or release. With that being said, if for some reason your application doesn’t work or doesn’t fully work, you can always try again after a newer version is out. I have personally experienced this. I had an application that did not fully work and after updating to the next release, everything was working fine.
I would recommend checking for an update every month or so, or even sooner. You can always go to the website and see if there is a new version out as well. Type the following in a terminal window. Only now when I type in “sudo port install wine” I get: Warning: /opt/local/etc/macports/variants.conf specifies invalid variant syntax ‘“+universal”’, ignored. Warning: /opt/local/etc/macports/variants.conf specifies invalid variant syntax ‘“+universal”’, ignored. Warning: The Command Line Tools for Xcode don’t appear to be installed; most ports will likely fail to build.
Warning: See for more information. — Computing dependencies for wineError: Unable to execute port: can’t read “build.cmd”: Failed to locate ‘make’ in path: ‘/opt/local/bin:/opt/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin’ or at its MacPorts configuration time location, did you move it? Everything is installed, so I’m not sure what to do. Should I just delete everything and re-install/retry? For OS X Mavericks computers you need to log into the apple dev site and download command line tools for OS X Mavericks. Otherwise you will not be able to install python27.
Also you the command you typed up above puts “+universal” at the bottom of variants.conf. This causes and error so you need to change it from “+universal” to +universal. If you have already run the command above you can modify your variants.conf file by typing sudo nano /opt/local/etc/macports/variants.conf and then remove the quotes and hit Control + O then Control + X.
Hi Dane, Thanks for the awesome and informative comment! It is definitely something readers can benefit from. I guess I need to proof read my articles better.
You’re right, those quotes should not be there. I was also unaware of the solution you provided on how to fix it if that command has already been run with quotes. Thank you very much for sharing, and teaching me something new. Also, I appreciate the heads up about Mavericks concerning the Command Line Tools. I have not had a chance to work a lot with Mavericks yet. I have made the necessary edits and updated the article.
Thanks again! Nice write up. After executing wineboot I get the following: wine: created the configuration directory ‘/Users/mikathem/.wine’ fixme:storage:createstoragefile Storage share mode not implemented. Err:mscoree:LoadLibraryShim error reading registry key for installroot err:mscoree:LoadLibraryShim error reading registry key for installroot err:mscoree:LoadLibraryShim error reading registry key for installroot err:mscoree:LoadLibraryShim error reading registry key for installroot fixme:storage:createstoragefile Storage share mode not implemented. Err:winediag:SECUR32initNTLMSP ntlmauth was not found or is outdated. Make sure that ntlmauth = 3.0.25 is in your path.
Usually, you can find it in the winbind package of your distribution. Fixme:iphlpapi:NotifyAddrChange (Handle 0x11ff560, overlapped 0x11ff56c): stub wine: configuration in ‘/Users/mikathem/.wine’ has been updated.
When I try to setup.exe the application, the installshield wizzard appears (empty window) and nothing further happens. Any thoughts? Hey Mike, Which wine install did you do?
Regular or wine-devel? Also, which version of OSX are you on? It looks like the.wine prefix got created judging by the last line in your stack trace. You can try using winetricks to install the secur32 package as well.
What software are you trying to install? Depending on what it is, it may require some other winetricks packages to be installed prior such as.NET, GDIPLUS, etc.
That might explain your empty installshield window. Let me know how it goes, and I’ll try to help you troubleshoot as best I can.
Hello and thanks for the reply. I actually got my application running. I’m not sure which step I took solved the problem. 1) Finally decided to upgrade to Mavericks. 2) Wiped wine and macports completely from my system. 3) Opted to give homebrew a shot as it gets a ton of positive reviews. 4) Installed SMBUp (samba) from.
After doing all of this I still get some of the same errors I was receiving before, but the application no longer hangs at the install shield window. I am running Microcap 11 from Spectrum Software. I was running OSX 10.7.5 before and I tried wine and wine-devel both with macports. All good now.
Thanks again. Jay, I attempted to install Wine on 10.9.4 with: sudo port install wine (after updating macports). Hi, I’ve been trying to install the latest development version of wine (thanks for the guide, by the way) and encountered a problem. I’m not super experienced with command line etc., so I’m hoping someone will be able to tell me what went wrong. I had an old official version of wine installed before, and I uninstalled it and then tried again through macports.
Everything seemed to be going smoothly until this: — Activating python27 @2.7.82+universal Error: org.macports.activate for port python27 returned: Image error: /Applications/MacPorts/Python 2.7/IDLE.app/Contents/Info.plist already exists and does not belong to a registered port. Unable to activate port python27. Use ‘port -f activate python27’ to force the activation. Hi Nskaran, Are you installing Wine on OS X Mavericks? If so, be sure to check out list item #2 under the prerequisites section. The error you are experiencing looks like it could be the cause.
When installing on Mavericks you need to install the separate XCode Command Line Tools for Mavericks, otherwise you will not be able to install Python. Another thing, you said you had an older version of wine installed. Did you install that version using MacPorts or another method such as Homebrew or did you compile it yourself? The reason I ask is because if this is the case then it’s possible there are some leftovers somewhere on your system, and might be missed especially if you tried to uninstall using MacPorts. If this is not the case, let me know and I’ll see if I help you resolve it. Thanks for catching that!
I’d installed the Command Line Tools a long time ago and assumed I wouldn’t have to do it again. I downloaded the newest version, but I still seem to be getting the same error. I’ve installed wine a couple times in the past.
The most recent one was through Homebrew and I uninstalled it through Homebrew. I did have a version through Macports before that, though, and it’s definitely possible I missed something somewhere.
It looks like I’m running up against an old python file, maybe? Is there a good way to look for any leftovers and clean them up? Hi nskaran, Whew, I don’t really know of a way to cleanly look for leftovers and get rid of them. It usually makes a mess of things. In the past when things have gotten really bad, I have just nuked everything.
Uninstall, XCode, XCode Command Line Tools, MacPorts, and Homebrew and start from scratch. I know that is a tall order of annoying, but it may be the only way. I noticed you said you did a previous install of Wine with MacPorts, you might be successful just nuking MacPorts. Keep me updated and let me know how it goes! I have a 27″ Late 2013 3.5 GHz Intel Core i7 running OS X Yosemite 10.10.2 and am having issues with Steam working properly. I had to use the alternate method to get Steam installed and it worked.
I chose it to use Windows 7 for my operating system as instructed. I sign in to my account and the Store doesn’t behave correctly. Most of the content is empty aside from a single game advertised in the News. Aside from the pull-down menus, nothing is clickable, nothing can load, and there is always a progress icon working in the upper right hand corner.
The scroll bar on the right side doesn’t actually scroll, in fact when I resize and expand the window it remains stuck in place as if I’m just viewing a still image of the Store. The menus on the top of News don’t take me anywhere or even act as if they can be clicked. The Library is the only place where the scroll bars move as they should and all sections are fully functional. I can also view and change the view style of my already owned games, and I actually got an installation completed. The only section usable in Community is Discussions and Market.
Under Broadcast the search fields act as if they’re just images and cannot be clicked inside to perform any typing or searches. Everything else just shows that processing icon in the upper right hand corner which appears but then goes away once the sections which do work have loaded.
Content is mostly empty boxes with just bits of text here and there. Under my account I can use a few of the sections but others again act as if they’re not functional and always have the processing icon. To try to fix the missing text, I used Winetricks to install the corefonts and it appeared to successful but there’s no change.
I tried to use Winetricks to install Flash 12 but it failed, giving me the sha1sum error I got when I tried to use the first method to install Steam. Basically, the Library is the only part of Steam which is fully functional and I can’t use the Store other than to Add a Game or look at images of what should be functional sections such as my Wishlist or News.
The important parts aren’t working and I’m not sure why. Sorry, I’ve been frustrated trying to both compile Wine and get Steam for Windows working properly and in my haste I posted the above issue in the wrong location. I posted this issue to the correct place here: I just can’t find any way to delete this other post.
It’s important to note that under Yosemite, Mac no longer uses ‘wget’ and has changed to ‘curl’ which accomplishes the same thing but can be confusing when all the tutorial instructions tell you to type wget. I found a site explaining how to acquire wget so I could use it instead of curl but it didn’t do it. It says I have installed MacPorts but typing any of the commands in the Terminal from the tutorial don’t do anything.
I can’t navigate to my Desktop in the Terminal and have it see Winetricks to move it because nothing was created on my Desktop, although I was able to successfully compile Wine. My computer shows Winetricks already inside a directory and I can only assume it must have been already installed from trying to install either Steam or a game with a Wineskin wrapper.