If the CrossOver CD Helper is running when you try to upgrade or delete CrossOver, you may get a message that says 'The operation cannot be completed because you do not have sufficient privileges' or 'The operation cannot be completed because the item "CrossOver CD Helper" is in use.'

The "CrossOver CD Helper" runs in the background and monitors CD insertion in order to detect the presence of Windows CDs. When removing or replacing CrossOver you will need to stop it manually by running the Activity Monitor (usually found in your Applications/Utilities folder). Select CrossOver CD Helper in Activity Monitor and click Quit Process to stop it.

First you should drop your CrossOver bundle into the trash and empty it. This may first require you to stop the CrossOver CD Helper as described in the previous entry.

User-specific CrossOver files are located in your home folder, under the Library/Application Support/CrossOver hierarchy. Trash that folder and its contents for each user of CrossOver on your system. Then, to be truly comprehensive, remove the preferences files located in Library/Preferences/ called com.codeweavers.CrossOver.plist.

Finally, if you have any published bottles or CrossOver has been run using your system's administrator account, you may have files in /Library/Application Support/CrossOver on your startup drive. These may also be removed.

That's it!

Apple ships a tool called 'quartz-wm' with every Mac. This tool vastly improves the look and feel of CrossOver, and its use is highly recommended. CrossOver will automatically install this tool for you if it is available.

Without quartz-wm, CrossOver is still usable and can run the same set of applications. However, certain window features such as title bars and resizing handles will be ugly and clumsy. Also, CrossOver windows may not interleave properly with your other Macintosh applications.

If you are running CrossOver in a non-English locale, you may be encountering a known bug in version 6.0.0. This can be worked around by temporarily resetting your locale, like this:

If you are suffering from a different registration problem or do not wish to go through these steps, you can also download the full version of CrossOver from your online account and simply replace the demo version with the full version. Your bottles will not be damaged by this process.

Maybe. A few Windows operations are shockingly slow, taking as many as 5 or 10 minutes to complete. If you are running an installer, take comfort that you'll only have to endure this delay once, and give it a few minutes to complete. In many cases, your patience will pay off. If you're sure that the process is stuck, there are instructions for getting unstuck here.

We're working hard at eliminating these delays and improving application performance for future releases. In this respect as well, your patience will be rewarded.

Some applications (Outlook, for example) install control panel applets to configure certain features. CrossOver places icons for these control panels applets in the Bottle Control Panel.

To launch a control panel app, open the Bottle Manager (available under the Configure menu) and select Control Panel. This will display all of the control panel tools available for the selected bottle.

Many Windows applications (especially those running in a Windows 98 bottle) will want to reboot your system during installation or configuration. Generally these messages can be ignored. CrossOver will not permit any application to power down your Macintosh, and it will generally simulate a system reboot when an application requests it.

CrossOver will also automatically simulate a bottle reboot anytime that you install an application via the CrossOver Software Installer.

If you need to manually reboot a bottle, visit the Bottle Control Panel. Click on the reboot entry and wait a few seconds -- CrossOver will simulate a reboot in the selected bottle.

There are several ways to stop a misbehaving application. The simplest is to click the Quit Bottle button on the Bottle tab of the Bottle Manager. This will send an exit message to all the applications running in the selected bottle.

Of course, if an application is stuck, it will not respond to a quit message. The Force Quit Bottle button will try a more drastic approach, instructing all processes in the bottle to exit immediately. The Force Quit Bottle button should only be used in emergencies, and is only enabled if a Quit Bottle process is already underway.

To manage individual processes within a single bottle, have a look at the Task Manager available on the Bottle Control Panel. Use caution when ending tasks in the Task Manager, because in many cases applications will quit without first offering to save your documents.

If CrossOver is truly stuck, or you suspect that an invisible process is running amok, you can try stopping processes with the Activity Monitor, which is available in the Applications/Utilities folder on your system. Search for processes with names like 'wineloader' and 'wineserver'. Be forwarned, however, that killing processes in the Activity Monitor will likely cause data loss and other alarming, unpredictable results within CrossOver and your Windows programs.

If a Windows application switches into full-screen mode and then stops responding, you may find your entire display is black or displays a frozen image. To switch out of full-screen mode, press Command-Option-R, the keyboard shortcut for "Restore Display".

Pressing Command-Q will also probably work, but that will cause all of your Windows applications to exit.

The sample rate being used by the Windows program has to match the sample rate of the Mac input device. Some Windows programs allow you to select the sample rate to use. You can set the sample rate of the Mac device using the Audio MIDI Setup utility that comes with Mac OS X. In the Properties For pop-up, pick the same device as selected for Default Input. Then pick a sample rate from the Format pop-up.

CrossOver respects the Region setting of the Formats tab of the International preference pane, except if it's set to Custom. That is, if you select one of the presets in that pane, CrossOver will format dates and numbers according to that region. If you customize the format manually, CrossOver will probably not format dates according to your settings.

You can also customize the settings using the Windows registry. Use the Run Command dialog to launch "regedit" for the bottle of your choice. Within regedit, navigate to HKEY_CURRENT_USER\Control Panel\International. There, you can set the format for dates and numbers.

This bug appears in some locales where there is not a direct correspondence between the Macintosh locale and the CrossOver locale. The problem is known to happen with Hungarian and Norwegian setups, among others.

There are three possible workarounds. You may pick whichever works best for you. These examples are all for Hungarian locales -- a list of alternatives appears at the end of this entry.

For languages other than Hungarian, you will need to enter an appropriate locale string for options 2 or 3. Here is a list of locales that should work:

ca_ES, cs_CZ, da_DK, de_AT, de_CH, de_DE, el_GR, en_AU, en_CA, en_GB, en_IE, en_NZ, en_US, es_ES, et_EE, eu_ES, fi_FI, fr_BE, fr_CA, fr_CH, fr_FR, he_IL, hr_HR, hu_HU, hy_AM, is_IS, it_CH, it_IT, ja_JP, kk_KZ, ko_KR, lt_LT, nl_BE, nl_NL, no_NO, pl_PL, pt_BR, pt_PT, ro_RO, ru_RU, sk_SK, sl_SI, sr_YU, sv_SE, tr_TR, uk_UA, zh_CN, zh_HK, zh_TW

If you don't use a desktop (KDE or Gnome), you have installed an application that does not show up on your desktop's menu, or you wish to start your application from the command line you can use one of the methods below.

The easiest way to run a Wine command line is via the 'cxrun' utility. It should be available in your CrossOver menu with the name "Run a Windows command" or you can run it from the command-line, like this:

$ ~/CrossOver.app/Contents/SharedSupport/CrossOver/bin/cxrun

If you know the name of the Windows executable you can try running it using the following command:

$ ~/CrossOver.app/Contents/SharedSupport/CrossOver/bin/wine --cx-app appname.exe

If the application registers itself in the right way, the following may work:

$ ~/CrossOver.app/Contents/SharedSupport/CrossOver/bin/wine start appname.exe

If you don't know the name of the application, you can search under the ~/Library/Application Support/CrossOver/Bottles/bottlename/drive_c directory for Windows executables like this:

$ find ~/Library/Application Support/CrossOver/Bottles/bottlename/drive_c -iname \*.exe

On some systems it has been reported that the Office help system fails to load. We have not found the cause of this bug however loading an Office service pack seems to resolve this issue. If you encounter this behavior and loading the Office service packs does not resolve issue, please file a support ticket.

CrossOver does not support the Office 2003 upgrade release at this time. Support for this is planned in the next version.

This is known to happen with Word 97 but may happen with other Microsoft Office applications too. The solution is to run the following command:

$ ~/CrossOver.app/Contents/SharedSupport/CrossOver/bin/regedit --bottle bottlename - <<EOF
[HKEY_LOCAL_MACHINE\Software\Wine\Drives]
"x:"="hd"
EOF

Where 'x:' is the drive which is located on the NFS filesystem. For instance if your home directory is on NFS then you would replace 'x:' with 'c:'.

If you have this problem, you may receive the errors "The disk is full or too many files are open (Y:\xxx.doc)" or "MSCREATE.DIR cannot be accessed".

This problem occurs when DCOM95.EXE is not installed correctly. Some Office 97 CDROMs do not contain the DCOM95 installer. You should install DCOM95 from the Bottle Manager's main menu by either downloading it if you have an internet connection, or using the Advanced install option and browsing to select the installer if you have it already.

There is a bad interaction between CrossOver and some window managers that results in the open file dialog being placed behind Word or Excel's main window. You can get the dialog box to appear by minimizing and maximizing the main window, or by pressing [ALT]-[Tab] a few times.

Normal.dot is Microsoft Word's Global Template. Sometimes this file becomes corrupt and produces a variety of error messages about getting saved and/or replaced. This problem most often occurs when CrossOver is upgraded.

This problem can be fixed by removing the offending Normal.dot file. This will cause Word to revert to the default Global Template. First, make sure that you aren't running any CrossOver applications.

$ ~/CrossOver.app/Contents/SharedSupport/CrossOver/bin/cxreset
# cd "~/Library/Application Support/CrossOver/Bottles"
# find . -iname "Normal.dot"
./bottlename/drive_c/Windows/Application Data/Microsoft/Templates/Normal.dot
# cd bottlename/drive_c/Windows/Application\ Data/Microsoft/Templates/
# rm -f Normal.dot

CrossOver does not work well with the Office Assistant yet. If the Office Assistant is not disabled, you may experience random hangs or window painting problems while using Microsoft Office.

This problem should not happen with CrossOver 2.0 or greater unless you manually enable the Office Assistant. To manually disable the Office Assistant, simply perform a simulated reboot.

This problem is caused by overlapping windows, either on the same desktop or on a different desktop and when the top window was created before the overlapping window. The only known workaround is to minimize windows that are not being used. We are working on a fix for the next version.

There is a bug when trying to perform certain drawing operations which will result in a crash in the GDIPLUS.DLL library. Installing Visio 2002 SP2 should resolve the issue.

When installing service packs for Microsoft Office 2003 they must be installed directly after the Microsoft Office. This is due to a bug in CrossOver virtual drive letter support. A fix for this issue is expected in CrossOver 6.1.

The slideshow requires components that are installed by Internet Explorer so you need to make sure that it is installed. You can install Internet Explorer 6.0 from the Bottle Manager.

On some systems the default registry entry for the Window position value of the main PowerPoint window can be changed to an invalid value. This seems to happen often on systems running the Beryl window manager. If this happens then the PowerPoint window will never display or the application will just exit right away. To correct this problem edit ~/Library/Application Support/CrossOver/Bottles/bottlename/user.reg and find the section starting with

[Software\\Microsoft\\Office\\10.0\\PowerPoint\\Options]

Make sure the "Bottom" value (in hex) is greater than the "Top" value and the "Left" value is less than the "Right" value. Also make sure these values are reasonable values for the size of your desktop. That is, if you have a 1024x768 desktop, "Bottom" should be less than 2FF and "Right" should be less than 3FF.

Contact the support system if you encounter this problem with other versions of PowerPoint.

CrossOver does not currently support NetBIOS or WINS name resolution. To solve this problem you should add the hostname and IP address of your Exchange server in the /etc/hosts file. For example:

127.0.0.1        localhost
192.168.0.1      mycomputer.myco.com mycomputer
192.168.0.254    mail.myco.com myco_mail_corp

This is a bug in Office 2000 which happens when no service pack is installed. You should install Office 2000 Service Pack 1 from CrossOver setup.

It has been found that if your password contains special characters such as @ or ! and you are using pam_smb to authorize then authorization fails.

We are working on this bug, for now you need to change you password to not contain such special characters. If you are running in a non-mixed mode network with only Windows 2000 and higher workstations and servers its possible that the domain is only configured for NTLMv2 or higher authentication. At this time CrossOver only supports the older NTLMv1 authentication found in Windows 95 and Windows 98. Contact your network administrator as it is possible enable NTLMv1 compatibility for older clients.

This is a known bug in which clicking on the X to close Outlook does not properly terminate the application. A workaround is to select File and Exit or File and Logoff in the application.

This problem will be fixed in future CrossOver releases. In the meantime, it can be fixed by adjusting the registry.

Use the Run Command... option to run 'regedit' in the bottle that contains Outlook. Expand the tree to see HKEY_CURRENT_USER -> Software -> Wine -> AppDefaults -> outlook.exe and you should see the key "riched20" as REG_SZ with the data of "native". Select the menu entry Edit -> New -> String Value to add a new entry, and then rename the string value to "activeds" and set the data to "builtin".

Exit regedit and restart Outlook. That should allow the right click to start functioning.

Newer versions of CrossOver have a initial implementation of the wldap32.dll file that is incompatible with Internet Explorer. This is not normally a problem except with websites that try to check NTLM or Active Directory authentication such as Outlook Web Access. If you are having problems logging in to such a site under CrossOver you can change the default dlloverride for this file to use the version that is installed by Internet Explorer or Microsoft Office using winecfg, which is available on the Bottle Control Panel.

Click on the Libraries tab and add a New override for library: wldap32 and set the load order to Native, Builtin.

When installing IE6 (and some other applications) over an NFS mount, an error message is produced stating "The download information is damaged. Please clear your Internet Explorer browser cache and retry Setup".

See our general NFS FAQ for the solution to this problem.

This problem is usually fixed when DCOM98 is installed in the bottle with IE. DCOM98 is available as an automatically downloadable package in the CrossOver Software Installer.

This problem can also be fixed by installing DCOM98 in the bottle with IE. DCOM98 is available as an automatically downloadable package in the CrossOver Software Installer.

This is probably the result of copy-protection code. Many games and other programs like to verify the presence of original media during each run in order to make sure you aren't using a copied CD or installing the software on multiple systems.

Such media-verification systems tend not to work on CrossOver because they rely on quirks and undocumented features of Windows, CD Drivers, and drive hardware. We are in the process of trying to work around many of these problems, but in the meantime the use of copy-protected software is unlikely to work in CrossOver.

Some software vendors will provide a version of their software without copy protection to customers with a legitimate need. Your best bet is to search on-line or contact your software vendor directly.

In CrossOver 5.0, Photoshop's file handling process interacts badly with the NFS filesystem. This means that saving files (and some graphical operations) can drag on forever when used with NFS. We are working on resolving the issue but in the meantime you may want to use one of the following workarounds.

The simplest solution to this problem is to make sure that Photoshop is interacting with a local (non-NFS) volume. When saving files, save to a local drive and then copy the files by hand to the desired NFS drive. Also, make sure that Photoshop's "scratch drives" are pointed to local volumes. The "scratch drive" locations can be set via the Photoshop "Preferences..." dialog.

If you don't have the option of using a non-NFS filesystem with Photoshop, you may be better served by CrossOver version 4.2. Old versions of CrossOver are available at the CodeWeavers store via the 'My Downloads' link.

You can solve the problem using the following method (contributed by Michael Osten):

When creating a new site, Dreamweaver tries to access Web server on your machine (localhost). If you have firewalled localhost's http port (80), Dreamweaver will hang until the TCP/IP request to localhost times out.

You can solve this problem by configuring your firewall software to accept queries from the loopback interface. If you use IPTables, you can use the following command:

# /usr/sbin/iptables -A INPUT -p tcp -i \! lo --dport 80 -j DROP

Extension Manager uses a Windows Shell feature (App Path) that is only partially supported in CrossOver at this time, so the Extension Manager icon does start correctly when started from its icon.

You can start it from the command line like this:

# ~/CrossOver.app/Contents/SharedSupport/CrossOver/bin/wine start "Extension Manager.exe"

To download web connect data using Quicken 2004 and 2005 you must have Internet Explorer installed and configured for low level security in the Internet Zone.

On some systems, Quicken may fail to automatically load the web connect data. In that case, select the option to save the data to a file. Once the file has finished saving, you can load it into Quicken using the File->Import->Web Connect File option.

To our knowledge this only happens with cracked Counter-Strike versions, please use the official version from Steam.

On the Mac Pro with the NVidia graphics card, there is an issue with certain scenes in the game. They become unplayably slow (fewer than 1 FPS) when you look at certain objects or areas. For most of these scenes, one can get back to good performance by turning the Shader Detail to Low in the game's Advanced Video options.