Table of Contents
After you have installed Windows software using CrossOver, the CrossOver main window will display a series of icons like those pictured below:
This window displays an icon for any shortcut created during the installation of a Windows program.
You can run any one of the Windows applications you have installed by double-clicking on its icon. You can also drag icons from CrossOver's main window to the OS X Dock and save them there for future use.
When you install a Windows application, CrossOver creates a launcher for that application which is visible in the Finder.
To see the launchers CrossOver creates in the Finder, first select the icon for the Windows application you are interested in. You can then display the "Action Menu" by pressing the gear-shaped button on the toolbar of CrossOver's main window. The "Show in Finder" action will cause CrossOver to open a Finder window showing the launcher for your selected Windows application.
After the Finder window with your launchers has opened, you can use these launchers the way you would use any other OS X application from within the Finder.
The icon labeled regedit or notepad, and can also be used to run applications which don't create icons or shortcuts.provides a simple way to run a Windows command-line in CrossOver. This can be a useful way to run standard Wine tools such as
If you need to run the same command regularly you can create a shortcut for it by clicking on thebutton.
This dialog provides several logging and debugging functions as well. These options may be useful if you talk to CodeWeavers tech support or if you are trying to make an unsupported application behave. To display these options, click on the Debug Options reveal control.
Open Shell. This option will launch an interactive shell, preconfigured for use with the selected bottle. This may be useful for running text-only programs.
Create log file. If this option is turned on, CrossOver will prompt you for the name and location of a log file before the command is run. This log file will contain a variety of debugging information about the run.
Turning on specific logging channels will determine what information is written to the log file. Many of these channels include a large volume of information, so generally they should be used singly or in pairs.