CrossOver To Run Windows On Macbook For Mac Download 21.0.0

The built-in Crossover virus scanner (ClamAV) will sometimes get stuck when launching Windows applications. To disable Crossover’s antivirus scanner go to your Applications folder, right-click on CrossOver, and select ‘Show Package Details‘. Then drill down to /Contents/SharedSupport/CrossOver/etc.

1. Open ‘CrossOver.conf‘ with a text editor and find the line that reads
2. change it to
3. and save the CrossOver.conf file.

Sometimes the installation of X11 doesn’t create the proper symlinks, and even though X11 is installed on your Mac, Crossover can’t see it. To check and see if this your problem, open up a terminal (Applications>Utilities>Terminal), and run the following commands (i.e. type/paste in the command and press “enter”).

Running a windows app from terminal in Mac is more complicated than on Linux because a series of environment variables must be passed to the terminal before the app can be successfully launched. For this reason, Crossover’s has an “Open Shell” button.

After selecting the appropriate bottle containing your applications, right clicking ( Ctrl+ click ) on the Bottle, then holding down the ‘Option’ key will switch ‘Run Command’ to “Open Shell”. Click on ‘Open Shell’ will open a terminal that automatically sets the necessary environment variables, including a directory change into the “drive_c” of that bottle.

From here, you can run windows apps with the following command:

wine --cx-app executable.exe

Whereas executable.exe is the name of the .exe file that launches the program. Thus, if you’re in an Office 2007 bottle and you want to launch Word from a terminal, you’d use:

wine --cx-app winword.exe

CrossOver can’t connect directly to hardware ports or devices on your computer. This can cause problems if the Windows program you’re trying to use needs to communicate with a USB device. A potential workaround is to manually map a device entry from the native OS to a symlink in the bottle containing your Windows app, and then hope that the Windows app sees the COM port and can use it to connect to the device.

The first thing you need to do is discover which /dev entry is being created when you connect the USB device to the computer. Disconnect the device from your computer and run the following commands in a Terminal:

cd /dev

ls > ~/disconnect.txt

Connect the device, wait a moment for your computer to recognize it, and run the command:
ls > ~/reconnect.txt

Now compare the difference between the two file listings to see what /dev entry was created.

diff ~/disconnect.txt ~/reconnect.txt