I've felt frustrated not being able to run the Mac version of KeyKit on a modern Mac (okay, it's from 2008), but I've been pleasantly surprised at how easy it is to install and run the Windows version using Wineskin.
If you have wanted to run DMDX on your Mac, follow these steps and you should be ready to go! We will setup DMDX through the incredibly useful Wineskin project, which is a suite of tools built around an open-source tool originally meant to allow Windows-based programs to run on Linux. Wineskin bundles up each app into its own isolated environment. 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. Check ON 'Use Mac Driver instead of X11' and 'Use Direct3D Boost (if available)' and click Done 6. Check OFF Options 'Force use of system installed XQuartz instead of using built in Wineskin X11' and 'Force use of wrappers quartz-wm for window decorations and not what is on the system'. Status Not open for further replies. 1 - 4 of 4 Posts. Wineskin is a tool used to 'wrap' Windows games so that they can be run on Mac OS X. We have used it to prepare the Mac versions of the Windows games you can find on this site. This means if you have updated your Mac to Hi Sierra, it's possible that you can't play games like Disney's Hercules, Pharaoh, Pitfall: The Mayan Adventure and more.
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):
- 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).

Wineskin Winery Mac
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.