Wineskin Error Mac

Posted on |



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.

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. 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. You can try switching to the Mac driver by right-clicking the wrapper, click Show Package Contents, double-click Wineskin, select Set Screen Options, put a check in the Use Mac Driver Instead of X11, and press Done.


Wineskin For Mac Os Sur

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.
Wineskin for mac os surThese are the steps that I took (hopefully I remembered them all):
  1. 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.
  2. 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.
  3. 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.
  4. Once that was completed, clicking on KeyKit now opens KeyKit within an X11 window (a special version -- WineskinX11 -- that is built in).
Through Wineskin, audio input & output is routed through Core Audio and MIDI input & output is routed through Core MIDI. The Port Enabler tool shows the currently available Mac MIDI devices and I've been able to send output either to built-in GM synth or to the IAC driver's Bus 1. (Actually, the output devices includes a MIDI_MAPPER device as the default, which directs MIDI to the Apple DLS GM synth.)
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.Wineskin Error Mac
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.

How To Update Wineskin On Mac