- On Catalina you can use homebrew to install either wine-stable or wine-devel (to see all available options run brew search wine). At the moment of writing wine-stable was still too buggy so I went instead with wine-devel.
- I have however tried wineskin unsuccessfully. I've looked at various tutorials on how to wrap a game in wineskin. I first tried to copy and paste the info from the pc to the mac in the appropriate folders in the wrapper, then edit the info.plist as you would with Cider, and that didn't work.
- Note: For peppy's Wineskin, if it fails to open, you must run sudo xattr -dr com.apple.quarantine 'osu!app' in Terminal. Or Wineskin will not open! Of my guide for more details. If you're uncomfortable with using a file downloaded from a complete stranger (and you should be) you can follow my guide here to obtain (mostly) the same.
Hi Ruth - I would agree with you. This is a new security setting that was introduced in the newest Mac OS. Right now you can do a manual wineskin install using the newest build and it will not require this change but the Steam build hasnt been updated yet. Wineskin is a user-friendly tool used to make ports of Microsoft Windows software to Apple's macOS/Mac OS X. How Does It Work? As described in the original Wineskin's website. The ports are in the form of normal macOS application bundle wrappers. It works like a wrapper around the Windows software, and you can share just the wrappers if you choose.
Wineskin is a free, open-source application that lets you port Windows applications to OS X without requiring you to own a copy of Windows. I'm using a MacBook Pro with OS X 10.11.6 (El Capitan) and I downloaded the Windows installer version of key73d.
These are the steps that I took (hopefully I remembered them all):
Wineskin Winery Mac
- With the Wineskin Winery application, I created a blank 'wrapper' (an application package where KeyKit would be installed) which I named 'KeyKit.' This was automatically created in the Applications > Wineskin directory under my user directory, but I just moved it to the main Applications directory.
- Double clicking on KeyKit then opened the Wineskin application hidden inside the package. From the small Wineskin window that opened up I selected Advanced, then the Options tab, then checked 'Emulate three button mouse...' which turned out to be necessary in order to be able to use the trackpad's right mouse button equivalent inside of KeyKit.
- From there I clicked on Install Software then selected the key73d.exe file I had downloaded. This ran the windows installer for KeyKit and created the whole directory structure inside of the application package. There was one error message that came up during the installation which didn't seem to cause any problems.
- Once that was completed, clicking on KeyKit now opens KeyKit within an X11 window (a special version -- WineskinX11 -- that is built in).
Opening the file browser within KeyKit shows a Windows-style directory. Opening My Computer shows you a C: drive, which is the Windows C: drive hidden inside of the application package, and a Z: drive, which is the Mac's root directory. Opening My Documents shows you the Mac Documents folder within your user directory.
From the Mac finder, you can access all of the KeyKit files such as the documentation and the library by right-clicking on KeyKit and selecting Show Package Contents. There's a alias for drive_C that leads to the virtual C: drive which includes the KeyKit7.3d folder. I created a keylocal.k at the root of that C: drive which includes the lines: inport('Bus 1') & outport('Bus 1'). This successfully makes KeyKit default to the IAC driver for MIDI input & output. While you're inside the package you could create an alias so you can more directly access the KeyKit folder the next time.
I just installed this last night, but so far, so good. I occasionally get weird errors in KeyKit, but probably fewer than I did when I was running the Mac version on an older Mac.
Wineskin For Mac Os Sur
