Frequently Asked Questions

This section addresses commonly asked questions related to the configuration, installation, and execution of CrossOver Games 7.1.0. It was last updated on July 21, 2008.

If you don't find an answer to your question here, be sure to check the online FAQ as we will update it regularly to document known issues and the corresponding workarounds.

For issues relating to older versions of CrossOver Games, please check the older issues page.

For more general information on CrossOver Games, see our web site.

1. Linux distribution dependent issues
1.1. I am having trouble using CrossOver on Fedora Core. What is the problem?
1.2. I am having trouble using CrossOver on Gentoo. What is the problem?
1.3. I am having trouble using CrossOver on K12LTSP. What is the problem?
1.4. I am having trouble using CrossOver on Mandrake 9.2 or 10. What is the problem?
1.5. I am having trouble using CrossOver on SUSE 10.1. What is the problem?
1.6. I am having trouble using CrossOver on TurboLinux 10. What is the problem?
1.7. I am having trouble using CrossOver on Ubuntu. It says 'unknown color name "Black"'. What is the problem?
1.8. I am unable to run CrossOver on Ubuntu. My error log says "** ERROR **: glibc 2.3.6 without TLS support will not work correctly". What's happening?
2. Most common questions
2.1. The bottle creation failed. What can I do?
2.2. How can I run an application from the command line?
3. General questions
3.1. About CrossOver
3.1.1. I am having trouble downloading the demo
3.1.2. I need a new or upgrade copy of CrossOver Games. Where can I download it from?
3.1.3. How can I upgrade CrossOver? Do I have to delete everything?
3.1.4. How do I upgrade from the demo to the full version of CrossOver?
3.1.5. Application XYZ does not work in CrossOver! Can you help?
3.1.6. Will CrossOver interfere with my existing Wine installation?
3.1.7. Will CrossOver work with my security patches? (grsec, libsafe, etc).
3.2. Installation
3.2.1. The Loki installation script fails when I run it.
3.2.2. Why do I get a "bad interpreter" error when trying to run the CrossOver installer?
3.2.3. Why do I get a "xhost DISPLAY permission denied" error when trying to run the CrossOver installer?
3.2.4. Why does CXSetup display an empty window?
3.2.5. CXSetup buttons are just blank! What do I do?
3.2.6. CXSetup buttons are enormous -- so big that I can't possibly tell what's going on. What's happening?
3.2.7. Why can't I type in any of the CXSetup text fields?
3.2.8. On Debian CXSetup gives an error about loading libXaw.so.6. Why?
3.2.9. I removed CrossOver Games from my account and installed it as root, but I get no menu.
3.3. When nothing works
3.3.1. Simple diagnosis steps.
3.3.2. CXSetup gives "Unable to get list of installed applications".
3.3.3. I have an NVidia card and the Windows application installation hangs and prints strange characters on the terminal.
3.3.4. I get an error like 'Cannot convert path' or odd permission denied or odd memory segment not permitted error, and nothing runs.
3.3.5. When I try to run any Windows application that plays sounds in CrossOver my system freezes.
3.3.6. I have an ATI video card, and any time I try to install or run anything, I get an 'Unhandled Page Fault' error. What's happening?
3.4. Printing
3.4.1. How do I customize my printer setup?
3.4.2. Why can't I print my documents when running CrossOver on a 64bit system?
3.4.3. Why do umlauted and other accented letters not print properly?
3.4.4. Printing landscape still results in a portrait output.
3.5. Sound
3.5.1. Does CrossOver work with ALSA?
3.5.2. Does CrossOver work with aRts (KDE)?
3.5.3. Does CrossOver work with ESounD (Gnome)?
3.5.4. How can I change CrossOver's sound backend?
3.5.5. CrossOver applications play no sound when another application is already playing sound.
3.5.6. Does CrossOver work with i810 sound cards?
3.5.7. Dealing with sound issues in CrossOver applications.
3.5.8. I upgraded to 5.0 and my sound stopped working! What can I do?
3.6. Integration with desktop environments such as Gnome and KDE
3.6.1. I lost my CrossOver configuration menus. What can I do?
3.6.2. CrossOver deleted all my KDE 3 menu entries in Mandrake!
3.6.3. CrossOver applications lose focus under KDE!
3.6.4. I am using KDE and the Windows Applications menu is missing.
3.6.5. I am using Gnome in SUSE Linux and the menus I created in my account are missing.
3.6.6. I am using SuSE 8 and the CrossOver menus don't have icons.
3.6.7. I am using SuSE 8 and my Windows Applications folder is called Windows_Applications and does not have the expected icon!
3.6.8. Can I configure CrossOver so that some file types are opened using Unix applications?
3.7. Other issues
3.7.1. Why do my CrossOver applications report time a hour faster or slower than my system?
3.7.2. Why do applications hang when I try to browse files?
3.7.3. When I move the mouse pointer over a menu, it disappears!
3.7.4. Why don't the dead keys or national characters on my keyboard work?
3.7.5. How can I turn off anti-aliased fonts?
3.7.6. I'm displaying my applications to a Mac OS X or NoMachine Client and some text is not visible.
3.7.7. How can I make CrossOver use PostScript fonts in applications?
3.7.8. How can I change the size of my menu font?
3.7.9. What happened to the Wine config file?
3.7.10. How can I change my Wine config?
3.7.11. What is a MIME type?
3.7.12. How can I make Hebrew text display from right to left?
3.7.13. Why do iTunes and my Microsoft Office applications perform poorly or fail to display images?
3.7.14. I am having problems with white rubberbands or lines that won't erase in CrossOver applications.
3.7.15. How can I get my mouse wheel to work in CrossOver?
3.7.16. How do I copy and paste to and from my xterm?
3.7.17. Why do I have Zombie wine-preloader processes after exiting my applications?
3.8. Uninstalling CrossOver
3.8.1. How do I uninstall CrossOver?
4. Integration with Unix Browsers
4.1. General
4.1.1. Setting the default browser.

1. Linux distribution dependent issues

1.1. I am having trouble using CrossOver on Fedora Core. What is the problem?
1.2. I am having trouble using CrossOver on Gentoo. What is the problem?
1.3. I am having trouble using CrossOver on K12LTSP. What is the problem?
1.4. I am having trouble using CrossOver on Mandrake 9.2 or 10. What is the problem?
1.5. I am having trouble using CrossOver on SUSE 10.1. What is the problem?
1.6. I am having trouble using CrossOver on TurboLinux 10. What is the problem?
1.7. I am having trouble using CrossOver on Ubuntu. It says 'unknown color name "Black"'. What is the problem?
1.8. I am unable to run CrossOver on Ubuntu. My error log says "** ERROR **: glibc 2.3.6 without TLS support will not work correctly". What's happening?
1.1.

I am having trouble using CrossOver on Fedora Core. What is the problem?

The Fedora project is the testbed system for the Red Hat Enterprise Linux distribution. When new features are introduced to this platform it can tend to cause problems with the operation of CrossOver.

Fedora Core 9 has a known problem which results in periodic system hangs when running CrossOver or Wine. There will probably be fixed in a future Fedora patch -- watch the Fedora websites for updates.

On systems that support the 'NX-bit', typically AMD x86-64 or Intel EMT64 processors, you may encounter trouble running any CrossOver application.

[Tip]

In that case, adding "noexec=off" to the linux kernel command line in grub will disable the hardware NoExecute protection of the CPU in Fedora Core. An example is provided below:

  kernel /vmlinuz-2.6.17-1.2139_FC5 ro root=/dev/VolGroup00/LogVol00 rhgb quiet noexec=off

Although CrossOver has provisions to cope with the SELinux and the audit facility, these facilities are still known to sometimes cause problems, depending on how they are configured. So it is always useful to try turning them off in case of trouble. You can do that at boot time by adding:

selinux=0 audit=0

to your linux kernel command line in your grub menu.lst file.

If you encounter other issues on Fedora Core please file a support ticket.

1.2.

I am having trouble using CrossOver on Gentoo. What is the problem?

To be candid, Gentoo is such a moving target that it is nearly impossible to support, and we do not officially support it. Nonetheless, many people use Gentoo to run CrossOver successfully. We will try to document common issues here; feel free to let us know when we should update this section.

The current problem of the month with Gentoo is that many glibc packages are built without TLS support, which is sick and wrong for a modern glibc. One customer (thanks Petra!) wrote to us and said:

[Tip]

I had to change my CHOST-Variable in make.conf to something greater than "i586-pc-linux-gnu", for me namely "i686-pc-linux-gnu". I think, there are a lot of gentoo-builds out there with this variable set to ...i386..., and no tls.

1.3.

I am having trouble using CrossOver on K12LTSP. What is the problem?

In recent K12LTSP distributions, there is a configuration option that allows the system to reserve the resources per user. CrossOver must reserve an amount of virtual memory greater than is allowed by the K12LTSP configuration. If you find that none of your applications are installing or running correctly edit the file:

/etc/sysconfig/k12ltsp-limits

Look for the line:

K12LTSP_LIMITS="YES"

and replace it with:

K12LTSP_LIMITS="NO"

1.4.

I am having trouble using CrossOver on Mandrake 9.2 or 10. What is the problem?

Depending on the install type of Mandrake versions 9.2 and 10 CrossOver may fail to install or run your Windows applications. This is due to a bug in the Mandrake 2.4 kernel builds. The solution seems to be to upgrade to one of the Mandrake 2.6 kernels or to build your own kernel.

Some users have reported problems even with the newer kernels that seem to be related to video card drivers or the Linux Standard Base support package being installed. If you still have problems after performing a kernel upgrade remove the LSB support package if it is installed or if you are running an NVidia or ATI card with vendor provided drivers try reverting back to the standard Mandrake driver.

1.5.

I am having trouble using CrossOver on SUSE 10.1. What is the problem?

When running CrossOver on SUSE 10.1 you may encounter a message such as "Unable to convert 'c:/' to a Unix path" or "wine: failed to initialize: /opt/cxgames/lib/wine/ntdll.so: failed to map segment from shared object: cannot allocate memory". To correct this issue, edit the file /etc/sysconfig/ulimit and make sure that both HARDVIRTUALLIMIT and SOFTVIRTUALLIMIT are set to 0. You have to be root to do this but the advantage is that it works for all users on that machine.

1.6.

I am having trouble using CrossOver on TurboLinux 10. What is the problem?

The glibc library that ships with TurboLinux contains a bug that prevents CrossOver from functioning properly.

Please contact TurboLinux support or build a newer glibc package to correct this problem.

1.7.

I am having trouble using CrossOver on Ubuntu. It says 'unknown color name "Black"'. What is the problem?

There is a bug in default Xorg configuration on certain versions of Ubuntu that can result in this error message when you try to launch CrossOver setup. The solution is to run the following commands to correct the Xorg configuration.

$ sudo ln -s /etc/X11/rgb.txt /usr/lib/X11/rgb.txt
$ sudo ln -s /etc/X11/rgb.txt /usr/X11R6/lib/rgb.txt
$ sudo ln -s /etc/X11/rgb.txt /usr/share/X11/rgb.txt

1.8.

I am unable to run CrossOver on Ubuntu. My error log says "** ERROR **: glibc 2.3.6 without TLS support will not work correctly". What's happening?

Some versions of Ubuntu ship with TLS disabled. This change was made to enable Xen, but it breaks the distribution's compatibility with CrossOver. To reenable TLS, rename the file /lib/tls.disabled to /lib/tls.

Of course, that change may break compatibility with Xen or VMware. Xen can be fixed via the installation of the libc6-xen library.

2. Most common questions

2.1. The bottle creation failed. What can I do?
2.2. How can I run an application from the command line?
2.1.

The bottle creation failed. What can I do?

A typical symptom is that you get an 'Exception raised' popup window during the creation of a bottle, or the first time you install an application with CrossOver. It is important to fix this issue as it will cause the bottles to be left in a half-created state which in turn will cause problems later when you try to install Windows applications.

In CrossOver 6.0.0 and 6.0.1 this is usually caused by known bugs in the Linux distribution's OpenGL driver.

If you are using ATI's fglrx driver, then the workaround is to set the 'UseFastTLS' option to off. To do so, edit /etc/X11/xorg.conf, and in the fglrx device section, add the following line and then restart X.

Option "UseFastTLS" "2"

If you are using the proprietary NVidia driver, then upgrading to version 9746 or greater should fix the problem.

If the problem persists, then please file a support ticket.

2.2.

How can I run an application from the command line?

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:

$ ~/cxgames/bin/cxrun

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

$ ~/cxgames/bin/wine --cx-app appname.exe

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

$ ~/cxgames/bin/wine start appname.exe

If you don't know the name of the application, you can search under the ~/.cxgames/bottlename/drive_c directory for Windows executables like this:

$ find ~/.cxgames/bottlename/drive_c -iname \*.exe

3. General questions

3.1. About CrossOver
3.1.1. I am having trouble downloading the demo
3.1.2. I need a new or upgrade copy of CrossOver Games. Where can I download it from?
3.1.3. How can I upgrade CrossOver? Do I have to delete everything?
3.1.4. How do I upgrade from the demo to the full version of CrossOver?
3.1.5. Application XYZ does not work in CrossOver! Can you help?
3.1.6. Will CrossOver interfere with my existing Wine installation?
3.1.7. Will CrossOver work with my security patches? (grsec, libsafe, etc).
3.2. Installation
3.2.1. The Loki installation script fails when I run it.
3.2.2. Why do I get a "bad interpreter" error when trying to run the CrossOver installer?
3.2.3. Why do I get a "xhost DISPLAY permission denied" error when trying to run the CrossOver installer?
3.2.4. Why does CXSetup display an empty window?
3.2.5. CXSetup buttons are just blank! What do I do?
3.2.6. CXSetup buttons are enormous -- so big that I can't possibly tell what's going on. What's happening?
3.2.7. Why can't I type in any of the CXSetup text fields?
3.2.8. On Debian CXSetup gives an error about loading libXaw.so.6. Why?
3.2.9. I removed CrossOver Games from my account and installed it as root, but I get no menu.
3.3. When nothing works
3.3.1. Simple diagnosis steps.
3.3.2. CXSetup gives "Unable to get list of installed applications".
3.3.3. I have an NVidia card and the Windows application installation hangs and prints strange characters on the terminal.
3.3.4. I get an error like 'Cannot convert path' or odd permission denied or odd memory segment not permitted error, and nothing runs.
3.3.5. When I try to run any Windows application that plays sounds in CrossOver my system freezes.
3.3.6. I have an ATI video card, and any time I try to install or run anything, I get an 'Unhandled Page Fault' error. What's happening?
3.4. Printing
3.4.1. How do I customize my printer setup?
3.4.2. Why can't I print my documents when running CrossOver on a 64bit system?
3.4.3. Why do umlauted and other accented letters not print properly?
3.4.4. Printing landscape still results in a portrait output.
3.5. Sound
3.5.1. Does CrossOver work with ALSA?
3.5.2. Does CrossOver work with aRts (KDE)?
3.5.3. Does CrossOver work with ESounD (Gnome)?
3.5.4. How can I change CrossOver's sound backend?
3.5.5. CrossOver applications play no sound when another application is already playing sound.
3.5.6. Does CrossOver work with i810 sound cards?
3.5.7. Dealing with sound issues in CrossOver applications.
3.5.8. I upgraded to 5.0 and my sound stopped working! What can I do?
3.6. Integration with desktop environments such as Gnome and KDE
3.6.1. I lost my CrossOver configuration menus. What can I do?
3.6.2. CrossOver deleted all my KDE 3 menu entries in Mandrake!
3.6.3. CrossOver applications lose focus under KDE!
3.6.4. I am using KDE and the Windows Applications menu is missing.
3.6.5. I am using Gnome in SUSE Linux and the menus I created in my account are missing.
3.6.6. I am using SuSE 8 and the CrossOver menus don't have icons.
3.6.7. I am using SuSE 8 and my Windows Applications folder is called Windows_Applications and does not have the expected icon!
3.6.8. Can I configure CrossOver so that some file types are opened using Unix applications?
3.7. Other issues
3.7.1. Why do my CrossOver applications report time a hour faster or slower than my system?
3.7.2. Why do applications hang when I try to browse files?
3.7.3. When I move the mouse pointer over a menu, it disappears!
3.7.4. Why don't the dead keys or national characters on my keyboard work?
3.7.5. How can I turn off anti-aliased fonts?
3.7.6. I'm displaying my applications to a Mac OS X or NoMachine Client and some text is not visible.
3.7.7. How can I make CrossOver use PostScript fonts in applications?
3.7.8. How can I change the size of my menu font?
3.7.9. What happened to the Wine config file?
3.7.10. How can I change my Wine config?
3.7.11. What is a MIME type?
3.7.12. How can I make Hebrew text display from right to left?
3.7.13. Why do iTunes and my Microsoft Office applications perform poorly or fail to display images?
3.7.14. I am having problems with white rubberbands or lines that won't erase in CrossOver applications.
3.7.15. How can I get my mouse wheel to work in CrossOver?
3.7.16. How do I copy and paste to and from my xterm?
3.7.17. Why do I have Zombie wine-preloader processes after exiting my applications?
3.8. Uninstalling CrossOver
3.8.1. How do I uninstall CrossOver?
3.1. About CrossOver
3.1.1. I am having trouble downloading the demo
3.1.2. I need a new or upgrade copy of CrossOver Games. Where can I download it from?
3.1.3. How can I upgrade CrossOver? Do I have to delete everything?
3.1.4. How do I upgrade from the demo to the full version of CrossOver?
3.1.5. Application XYZ does not work in CrossOver! Can you help?
3.1.6. Will CrossOver interfere with my existing Wine installation?
3.1.7. Will CrossOver work with my security patches? (grsec, libsafe, etc).
3.1.1.

I am having trouble downloading the demo

One of the great things about Linux is that there are so many different versions of Linux. However, one of the challenges that creates is that the process of installing software is a bit different on nearly every one of those, particularly for the novice user.

To try to help this, we have packaged CrossOver in a variety of formats, including a self installing 'shell script' (also known as the Loki installer). This is essentially the same thing as a Windows program which will install new software.

These instructions should help you install CrossOver:

1.) Start the download, and save the file to your hard disk.

You need to remember where the file is downloaded to, as this is different on different versions of Linux.

The file will be named something like install-crossover-standard-demo-5.0.1.sh, and it is a self installing shell script (just like a self installing program on Windows).

2.) Start the script

Once our installer script starts running, it should take over, and we feel that it is a nice friendly, point and click program that makes it easy to use CrossOver. But getting the script running can be tricky, as this also varies depending on your version of Linux.

On many versions of Linux, you can simply open a file browser and double click on our program. You may have to tell it to 'run in Terminal'.

If all else fails, you can start it via a command line. To do this, look for an icon labelled 'Terminal' or 'Console' and start it. This should give you a command prompt. You will need to use the 'cd' command to change to the directory with our installer. Try using the 'ls' (list files) command combined with 'cd' until you reach the correct directory. Then you can start it running with the following command:

$ sh install-crossover-standard-demo-6.0.0.sh

3.1.2.

I need a new or upgrade copy of CrossOver Games. Where can I download it from?

To download the CrossOver Games installer, go to our store at https://www.codeweavers.com/login.

There you can log in using the email address you used to order CrossOver. If you need your password, just click on Lost Password and you will receive your password in the mail (you can change it once logged in).

Once logged in you will see a Downloads link in the sidebar. Click on that link and then follow the instructions to download the file.

Note, to be automatically notified of new releases, subscribe to our Announce mailing list.

3.1.3.

How can I upgrade CrossOver? Do I have to delete everything?

If you are upgrading from the demo version to the full version of CrossOver please see the next question.

You do not need to uninstall CrossOver Games before upgrading. Just download the new version of CrossOver Games as described in the previous section.

Then simply install in the same directory as your existing installation. Your Windows applications, the files you have on the c:\ 'drive' as well as your settings will all be preserved.

If for any reason you wish to reinstall from scratch, first follow the uninstallation procedure, and then proceed normally.

3.1.4.

How do I upgrade from the demo to the full version of CrossOver?

To unlock an installed demo, click the Register and unlock this demo icon in the CrossOver menu. If you don't have this icon, you can run the registration tool from the command-line, like this:

$ ~/cxgames/bin/cxregister

Or, if you installed as root:

$ /opt/cxgames/bin/cxregister

If you want to use a different version of CrossOver from the installed demo version (for instance, if you bought CrossOver Professional but installed the 'standard' demo version) you should download the full installer and install it over the top of the demo installation. The installer will upgrade the demo automatically.

When upgrading, make sure you install using the same mode (root or user) that was used when installing the demo.

3.1.5.

Application XYZ does not work in CrossOver! Can you help?

Firstly, please check if you application is in the list of officially supported applications.

The CodeWeavers CrossOver Compatibility Center (C4), was created to dramatically expand the range of applications CrossOver Games supports. If you need to use an application that is not currently by CrossOver Games, check C4 first. Adding support for an application requires us to have the application to test with (and preferably purchase several variants), and to spend a significant amount of time and effort testing and debugging CrossOver Games to work with it. C4 provides a way for us to assess the level of interest in your application.

You can discuss unsupported application with other users on discuss@crossover.codeweavers.com.

If the application is critical to you, we can work with you on a contractual basis to make the application work. In such a case, please contact us at sales@codeweavers.com to discuss the terms of the contract.

3.1.6.

Will CrossOver interfere with my existing Wine installation?

No, CrossOver will not interfere with your existing Wine installation. CrossOver and Wine each have their own Drive C: that will not be visible to the other.

3.1.7.

Will CrossOver work with my security patches? (grsec, libsafe, etc).

Sometimes. Many security patches disallow loading executables at certain locations in the memory map. Some Windows executables are stripped of their relocation records, thus must be loaded at a specific address in the memory map.

For this reason, you may experience trouble running certain programs in CrossOver with security patches enabled. If you are using grsec, please contact us as we may be able to help you. If you are using the "not executable stack patch" for Linux, you may disable it for CrossOver by running the following command:

$ /usr/sbin/chstk -e ~/cxgames/bin/wineloader

3.2. Installation
3.2.1. The Loki installation script fails when I run it.
3.2.2. Why do I get a "bad interpreter" error when trying to run the CrossOver installer?
3.2.3. Why do I get a "xhost DISPLAY permission denied" error when trying to run the CrossOver installer?
3.2.4. Why does CXSetup display an empty window?
3.2.5. CXSetup buttons are just blank! What do I do?
3.2.6. CXSetup buttons are enormous -- so big that I can't possibly tell what's going on. What's happening?
3.2.7. Why can't I type in any of the CXSetup text fields?
3.2.8. On Debian CXSetup gives an error about loading libXaw.so.6. Why?
3.2.9. I removed CrossOver Games from my account and installed it as root, but I get no menu.
3.2.1.

The Loki installation script fails when I run it.

The error message usually looks something like this:

$ sh install-crossover-games-7.1.0.sh
Verifying archive integrity...Error in check sums 2527639012 444965528

This indicates that the installer was corrupted. This is known to happen if you use the ftp download link in Netscape 4.x because Netscape performs CR/LF conversions in that case. The remedy is to download the file again using either the http link or a different browser.

You may also get an error like this:

$ sh install-crossover-games-7.1.0.sh
Verifying archive integrity...OK
Uncompressing CrossOver
Office...................tar:
lib/wine/ntdll.dll.so: Wrote only 5120 of 10240 bytes
tar: Skipping to next header
tar: Error exit delayed from previous errors
Extraction failed.

When installing, CrossOver setup first extracts itself to /tmp. If you get the above error message, there is insufficient space on the partition contain /tmp.

You can use the df command to display the amount of free space on each of your harddisk partitions:

$ df
Filesystem           1k-blocks      Used Available Use% Mounted on
/dev/hda6              2063504   1638816    319868  84% /
/dev/hda7             14017840   6120332   7185432  46% /home
/dev/hda1              4096548   3267460    829088  80% /dos

Note that the /tmp directory is usually located on the root (/) partition (as in the above example), though there may be space elsewhere on your harddrive, the "Available" size for the root partition is what is important.

You can also tell the installer to extract its temporary files to a different directory by running it as followings:

$ sh install-crossover-games-7.1.0.sh --target cxtemp

3.2.2.

Why do I get a "bad interpreter" error when trying to run the CrossOver installer?

This indicates that the installer was corrupted. This is known to happen if you use the ftp download link in Netscape 4.x because Netscape performs CR/LF conversions in that case. The remedy is to download the file again using either the http link or a different browser.

3.2.3.

Why do I get a "xhost DISPLAY permission denied" error when trying to run the CrossOver installer?

Some Linux distributions ship with RGB profile that contains the a entry for the color Black instead of black. You should edit your /etc/X11/xorg.conf file and look for the line containing the RgbPath. It should be like the following:

        RgbPath      "/usr/X11R6/lib/X11/rgb"

The file you would need to edit will be:

/usr/X11R6/lib/X11/rgb.txt

Simply edit this file and rename the line the color Black to black in lower case.

3.2.4.

Why does CXSetup display an empty window?

CXSetup requires the Helvetica and Fixed fonts to be installed on your system. If these fonts are unavailable, the CXSetup window will not display properly, and it may produce an error message like the following:

font "" doesn't exist.

To fix this problem you should install the Helvetica and Fixed fonts, which should be available in your distribution.

3.2.5.

CXSetup buttons are just blank! What do I do?

Install 75dpi X fonts (XFree86-75dpi package). Be sure to restart X before you launch CXSetup again (restarting xfs is not enough).

3.2.6.

CXSetup buttons are enormous -- so big that I can't possibly tell what's going on. What's happening?

This problem has to do with monitor DPI settings. The easiest fix is to set your monitor height and width to zero, and let X figure things out automatically.

To change these settings on RedHat, run redhat-config-xfree86 as root, and go to the Advanced tab.

3.2.7.

Why can't I type in any of the CXSetup text fields?

Some versions of Linux (including SUSE 9.3) ship with SCIM turned on by default. This interferes with text entry in CXSetup.

The solution is to upgrade to SCIM version 1.4 or later, or turn SCIM off altogether.

3.2.8.

On Debian CXSetup gives an error about loading libXaw.so.6. Why?

Apparently, Debian 3.0 (Woody) defaults to using version 7 of these libraries. Debian contains a package which will install the libXaw.so.6 libraries. You simply need to install this package using the command:

$ apt-get install libxaw6

3.2.9.

I removed CrossOver Games from my account and installed it as root, but I get no menu.

This problem can happen if you are using a Linux distribution that uses VFolders for the menus (mostly old Gnome 2 versions). This is typically the case for RedHat 8 and SuSE 8.1 and later.

The solution is to delete ~/.gnome2/vfolders/applications.vfolder-info. However note that if you delete this file you will lose any non-CrossOver related change you made to menus in you account.

3.3. When nothing works
3.3.1. Simple diagnosis steps.
3.3.2. CXSetup gives "Unable to get list of installed applications".
3.3.3. I have an NVidia card and the Windows application installation hangs and prints strange characters on the terminal.
3.3.4. I get an error like 'Cannot convert path' or odd permission denied or odd memory segment not permitted error, and nothing runs.
3.3.5. When I try to run any Windows application that plays sounds in CrossOver my system freezes.
3.3.6. I have an ATI video card, and any time I try to install or run anything, I get an 'Unhandled Page Fault' error. What's happening?
3.3.1.

Simple diagnosis steps.

Here is a list of simple steps that can help you identify the source of the problem and maybe even solve it. If not, please mention their results when reporting problems to http://support.codeweavers.com.

  1. When reporting a problem, specify which version of CrossOver you are using, whether you installed as root or in a regular account, and the browser and Linux distribution you are using. This information can greatly help us identify the most likely issues and thus provide you with a fix faster.

  2. If regular applications or CXSetup fail to start, then run the following command and send us its output:

    $ ~/cxgames/bin/wine --cx-log - --verbose uninstaller.exe --list
    

3.3.2.

CXSetup gives "Unable to get list of installed applications".

Running CXSetup gives the following error message:

Unable to get list of installed applications:
child killed: software termination signal.

Similarly, running any other application gives a "Terminated." message.

This problem happens when Wine fails to initialize correctly. This may occur for a number of reasons.

  1. You may have insufficient permissions to write to the /tmp or /tmp/.wine-username directories on your filesystem. CrossOver stores its Wine socket files in the latter directory.

  2. The latest version of glibc (2.3.2) is incompatible with versions of CrossOver up to and including 2.0.1. glibc 2.3.1 is incompatible with versions of CrossOver up to and including 1.2.0. If you are using an older version of CrossOver please upgrade. You can determine which glibc version your system uses by running the following command:

    $ ls -l /lib/libc-*.so
    

If these solutions do not work for you, please generate a debug trace file with the command below and send it to support.

$ ~/cxgames/bin/wine --debugmsg +relay,+seh --cx-log start.log.gz uninstaller

3.3.3.

I have an NVidia card and the Windows application installation hangs and prints strange characters on the terminal.

Some Windows installers load the OpenGL Windows dll which uses the OpenGL capabilities exposed by the NVidia drivers. Unfortunately some of these drivers have bugs that will cause the installation to hang and print strange characters on the terminal.

One possible solution is to upgrade to the NVidia drivers to the latest available version. The bug seems to be present in versions 3123 to 4496 but unfortunately the status of later driver versions is unknown (we welcome feedback on known good and bad driver versions).

Another solution is to prevent Wine from using the NVidia OpenGL driver by running the following command:

$ touch ~/cxgames/lib/libGL.so.1

3.3.4.

I get an error like 'Cannot convert path' or odd permission denied or odd memory segment not permitted error, and nothing runs.

Unix systems have the ability to constrain user processes to keep them from using excessive memory or CPU. These facilities are usually controlled by a facility called 'ulimit' (for User Limit).

Unfortunately, Windows programs will only function if they are loaded at very specific locations in memory. This makes it mandatory for Wine to have access to all of the virtual memory space. Certain ulimit settings (usually ulimit -v) prevent Wine from doing this, thereby causing a failure in CrossOver.

You can often work around this by running the following command in a console window:

$ ulimit -v unlimited

Then, from that same console window, you should be able to run the CrossOver applications successfully.

Unfortunately, the ulimit setting varies from distribution to distribution, so we cannot give you a specific guide to address this; you will need to find a distribution specific set of help pages for more help.

3.3.5.

When I try to run any Windows application that plays sounds in CrossOver my system freezes.

This system crash is usually caused by a bug in the SoundBlaster OSS sound driver which is triggered by CrossOver on some systems. In particular this is known to happen if the sound card is a "Creative Labs SoundBlaster VIBRA16".

We had reports that the ALSA driver is not affected by this bug. Thus this is the best solution although it may not be the simplest.

3.3.6.

I have an ATI video card, and any time I try to install or run anything, I get an 'Unhandled Page Fault' error. What's happening?

Several ATI cards (in particular the FireGL line) produce this error when running Wine. To work around this, edit your xorg.conf file and add the following line to the Device area:

Option "UseFastTLS" "2"

That should allow you to run CrossOver without problems.

3.4. Printing
3.4.1. How do I customize my printer setup?
3.4.2. Why can't I print my documents when running CrossOver on a 64bit system?
3.4.3. Why do umlauted and other accented letters not print properly?
3.4.4. Printing landscape still results in a portrait output.
3.4.1.

How do I customize my printer setup?

CrossOver provides support for most printers with no additional configuration necessary. However, you can customize your printer setup for CrossOver by replacing the generic printer description file with a specific one for your printer. This process is described in an appendix to the manual.

3.4.2.

Why can't I print my documents when running CrossOver on a 64bit system?

Certain Linux Distributions such as Ubuntu do not provide a 32bit CUPS library which is needed by CrossOver. The best solution for this problem is to contact your vendor and ask them to provide you with a 32bit CUPS compatibility package or install the 32bit KDE support libraries and use the Kprinter driver.

3.4.3.

Why do umlauted and other accented letters not print properly?

This behavior is due to a bug with older versions of the ghostscript package. The solution is to upgrade this package to at least version 8.15.3.

3.4.4.

Printing landscape still results in a portrait output.

This is known to happen with cups and perhaps other printing systems. The suggested workaround for this is to filter CrossOver Games's output to remove an '%%Orientation:' line from the PostScript that is believed to confuse pstops. To do this you will need to edit the registry for the current bottle. Run the following command:

$ ~/cxgames/bin/cxrun

Select the correct bottle, type in regedit for the command, run it and go to the following Key: HKEY_CURRENT_USER\Software\Wine\Printing\Spooler and change the line that reads:

"LPT1:"="|lpr"

to:

"LPT1:"="|grep -v ^%%Orientation: |lpr"

3.5. Sound
3.5.1. Does CrossOver work with ALSA?
3.5.2. Does CrossOver work with aRts (KDE)?
3.5.3. Does CrossOver work with ESounD (Gnome)?
3.5.4. How can I change CrossOver's sound backend?
3.5.5. CrossOver applications play no sound when another application is already playing sound.
3.5.6. Does CrossOver work with i810 sound cards?
3.5.7. Dealing with sound issues in CrossOver applications.
3.5.8. I upgraded to 5.0 and my sound stopped working! What can I do?
3.5.1.

Does CrossOver work with ALSA?

By default CrossOver interfaces with the Open Sound System (OSS). This default will also work if your Linux system is using the Advanced Linux Sound Architecture (ALSA) drivers and libraries, as long as the OSS compatibility mode is enabled. You can check whether your system is using ALSA by running the following command: cat /proc/asound/version. If you get an error then you are not using ALSA. Otherwise you will get the version of the ALSA driver and you can then check whether OSS compatibility is enabled by typing lsmod | grep oss. If you see modules called snd-pcm-oss and snd-mixer-oss then OSS compatibility is enabled.

But you can also configure CrossOver to interface directly with ALSA 0.9 or greater. To do so, check out how to change the CrossOver sound backend. However note that ALSA 0.5 or older is not supported so in that case you must use the OSS compatibility mode.

3.5.2.

Does CrossOver work with aRts (KDE)?

As mentioned below, the sound drivers will often only allow a single application to play sounds. A twist on this theme is that, by default, KDE (2.2 and greater) uses a new sound system called aRts which may already be using the OSS driver without your knowledge. Under this system, applications are supposed to send their audio to a 'sound daemon' which mixes them in realtime and sends the result over to the OSS or ALSA driver. This lets multiple applications play sounds simultaneously but also means they cannot play sounds directly anymore which is what CrossOver is doing.

Here are a couple of ways to deal with this:

  • First check that this is actually the problem. To do so, start the KDE Control Center, and go to the Sound / Sound Server section. There you can disable the sound server by deselecting the Start aRts soundserver checkbox and then clicking on Apply. Then, restart the browser or application to see if sound works.

    Note that this may be the best solution. KDE will still be able to play its system notifications whenever the sound device is not already in use. And other applications, one at a time, will be able to play sounds too by directly accessing the sound device. But it is up to you to determine whether this is acceptable.

  • Another solution is to configure CrossOver to use its aRts sound backend. CrossOver will then send its sounds to the aRts server which will mix them with those of the other applications.

    However the aRts sound backend should still be considered to be experimental. In particular it is known to cause some applications to fail.

  • Alternately you can leave the aRts sound server running but try to minimize the periods of time during which it uses the sound device. This will minimize the interference between it and CrossOver applications.

    Still in the Sound Server section of the KDE Control Center, make sure the Autosuspend checkbox is selected, and choose a short time there. Three seconds has been reported to work well. Then click on Apply.

3.5.3.

Does CrossOver work with ESounD (Gnome)?

The Enlightenment Sound Daemon (EsounD) is a sound server which is commonly found in Gnome and Enlightenment environments. Its principles are very similar to those of the aRts sound server mentioned above so for more details please refer to the first part of the aRts entry.

Older versions of CrossOver did not have support for a ESounD backend. With the release of version 5.0 we included support for this however it has not undergone as much refinement as the OSS and ALSA backends. It is recommended that if you are having sound issues and you run Gnone or Enlightenment that you check for the presence of ESounD.

To do so, start the Gnome Control Center, and go to the Sound section. If the Enable sound server startup checkbox is selected you can enable support for ESounD in a CrossOver bottle by changing your sound driver to ESounD. Open the correct bottle for your applications as documented here go down to Sound driver load order and select the Change button. Select the current sound driver, chose edit and rename it to ESounD.

Note that this may not be the best solution. If you still have problems with sound you can disable ESounD support in Gnome by starting the Gnome Control Center, going to the Sound section. And unselecting the Enable sound server startup checkbox.

3.5.4.

How can I change CrossOver's sound backend?

CrossOver has multiple sound backends that allow it to interface with many sound systems. You can specify which sound backend is to be used by starting CXSetup and going to the Settings tab. There the Sound driver load order determines which sound backend to use.

  • The default value is 'wineoss.drv' which interfaces with the Open Sound System (OSS). This backend will also work with the Advanced Linux Sound Architecture (ALSA) drivers if their OSS compatibility mode enabled. Check out our ALSA FAQ for more details.

  • To interface directly with the Advanced Linux Sound Architecture (ALSA) version 0.9 or later, set this field to 'winealsa.drv'. Then consult our ALSA FAQ.

  • Similarly, to interface directly with the aRts sound server, set this field to 'winearts.drv'. Then consult our aRts FAQ.

  • CrossOver can also interface with the Network Audio Sound (NAS) system. To do so set this field to 'winenas.drv'. However note that this driver has not been tested at all so that we do not provide support for it at this time.

Note that you can also list multiple sound backends separated by colons in your order of preference. However this can cause some applications to malfunction and is thus strongly discouraged at this time.

3.5.5.

CrossOver applications play no sound when another application is already playing sound.

In many cases the sound drivers will only allow one application to access the sound device at any given time. This is always the case for the OSS (Open Sound System) drivers and quite often the case of the ALSA (Advanced Linux Sound Architecture) sound drivers too.

So for instance, this means that if xmms is playing an MP3 file, CrossOver will not be able to play sound. One typical symptom of this problem is the absence of a Sound Out option in the QuickTime settings or that the sound volume will be disabled in Windows Media Player.

See also the sections about aRts and ESounD for related issues.

3.5.6.

Does CrossOver work with i810 sound cards?

The i810 sound cards (and some other cheap sound cards) have limitations that make it tricky to support them. In particular they only support a specific sound format, or support several but only allow direct access in one of them. CrossOver is normally able to work around these limitations.

However the Open Sound System (OSS) drivers for i810 that are part of the Linux kernel have some serious bugs that prevent CrossOver from playing sound correctly. Thus it is recommended to either switch to the Advanced Linux Sound Architecture (ALSA) drivers, or to upgrade your kernel to 2.4.27-pre3 or later, or 2.6.7-rc1 or greater as these kernels fix significant bugs in the driver:

Gary Wong:
  o [sound i810] silently ignore invalid PCM_ENABLE_xxx bits from
    userland

Herbert Xu:
  o [sound/oss i810] fix wait queue race in drain_dac
  o [sound/oss i810] fix race
  o [sound/oss] remove bogus CIV_TO_LVI
  o [sound/oss i810] clean up with macros
  o [sound/oss i810] fix partial DMA transfers
  o [sound/oss i810] fix playback SETTRIGGER
  o [sound/oss i810] fix OSS fragments
  o [sound/oss i810] remove divides on playback
  o [sound/oss i810] fix drain_dac loop when signals_allowed==0
  o [sound/oss i810] fix reads/writes % 4 != 0
  o [sound/oss i810] fix deadlock in drain_dac

If you are still having trouble with sound then check out the sound troubleshooting section.

3.5.7.

Dealing with sound issues in CrossOver applications.

Generally speaking, if your sound system works fine in Linux applications then it should work in CrossOver applications.

However there are some cases where the sound system has bugs and will not work at some sampling rates or in some sound formats, whether in CrossOver or other Linux applications. One case that we know of is the combination of a CMI8738 sound card with the OSS drivers. Such a configuration will not play sounds at an 11kHz or 22kHz sampling rate, regardless of the application being used ('cat >/dev/dsp', bplay or xmms). Fortunately, in this specific case switching to ALSA drivers solves the problem and this is the recommended solution.

CrossOver also has to use some advanced and rarely used features in order to provide compatiblity with the Windows interfaces, and in particular with DirectSound. This can cause the sound to fail in CrossOver although everything appears to work fine in Linux applications such as xmms.

Thus CrossOver has a number of knobs and options in the Wine configuration tool and in the registry to let you work around these problems... if at all possible. To use winecfg use the following command line:

$ ~/cxgames/bin/wine --bottle bottlename --wl-app winecfg

Note however that not all options are supported under the audio tab at this time. Most of the following information will require manually editing of the registry unless otherwise noted. To edit the registry for the current bottle, run the following command:

$ ~/cxgames/bin/cxrun

Select the correct bottle, type in regedit for the command, run it and go to the following Key: HKEY_CURRENT_USER\Software\Wine

It is hard to predict exactly which option will fix a given problem so that some experimentation will most likely be needed. Below you will find a description of the various knobs and their effects.

If you have sound problems and one of the tweaks below solves the problem, please let us know about the characteristics of your sound system and the settings you had to use so that we can share this information with the other CrossOver users.

  • If you are using the OSS sound backend, you can force CrossOver to use a specific sound format. You could use this if the sound appears to play too fast or too slow (as in the CMI8738 case mentioned above).

    For instance, to force CrossOver to convert all audio to 48kHz, 16bits, stereo, before handing it to the sound card, locate the 'OSS Driver' Key and add the following string values:

    [OSS Driver]
    "LockFormat" = "16"
    "LockStereo" = "1"
    "LockRate" = "48000"
    

  • If you are using the OSS sound backend, you can also force CrossOver to not make any attempt to use full-duplex sound. This should let you work around any full-duplex related bug in the sound driver without significantly reducing functionality as very few applications use full-duplex.

    So to disable full-duplex sound, locate the 'OSS Driver' Key and edit it as follows:

    [OSS Driver]
    "FullDuplex" = "0"
    

  • If you get no sound in DirectSound applications you may try to tell it not to do direct accesses to the sound device. To do so, follow the directions in the DirectSound upgrade FAQ below.

    If you get sound then that's progress. It may be choppy though. If that's the case, then you can try to solve the problem by adding the 'HELmargin' and 'HELqueue' parameters under the DirectSound key:

    [DirectSound]
    "HELmargin" = "16"
    "HELqueue" = "16"
    

    The HELmargin is the Number of waveOut fragments ahead to mix in new buffers. The HELqueue is the Number of waveOut fragments ahead to queue to driver.

    This may eliminate the choppiness at the cost of increasing the sound latency, usually an acceptable trade-off. Note that the value that provides the best results depends on each system so make sure to experiment.

  • If the sound is choppy in DirectSound applications and you are not using the emulation mode described above, then you may be able to solve the problem by increasing the 'SndQueueMin' and 'SndQueueMax' parameters in the DirectSound key:

    [DirectSound]
    "SndQueueMax" = "64"
    "SndQueueMin" = "32"
    

    SndQueueMax being the Max number of fragments to prebuffer and SndQueueMin being the Min number of fragments to prebuffer.

    This may eliminate the choppiness at the cost of increasing the sound latency, usually an acceptable trade-off. Note that the value that provides the best results depends on each system so make sure to experiment.

3.5.8.

I upgraded to 5.0 and my sound stopped working! What can I do?

If you have an i8x0 or similar sound card where in CrossOver Office 4.2 you had to set your Direct Sound acceleration mode to emulation, that setting was probably lost on upgrade.

You need to re-set the setting. Run winecfg like this:

$ ~/cxgames/bin/wine --bottle bottlename --wl-app winecfg

Select the 'Audio' tab and locate the drop down for Hardware Acceleration. Select Emulation for that setting and click Apply. This will properly update your install to use emulation mode and your sound should being working again.

3.6. Integration with desktop environments such as Gnome and KDE
3.6.1. I lost my CrossOver configuration menus. What can I do?
3.6.2. CrossOver deleted all my KDE 3 menu entries in Mandrake!
3.6.3. CrossOver applications lose focus under KDE!
3.6.4. I am using KDE and the Windows Applications menu is missing.
3.6.5. I am using Gnome in SUSE Linux and the menus I created in my account are missing.
3.6.6. I am using SuSE 8 and the CrossOver menus don't have icons.
3.6.7. I am using SuSE 8 and my Windows Applications folder is called Windows_Applications and does not have the expected icon!
3.6.8. Can I configure CrossOver so that some file types are opened using Unix applications?
3.6.1.

I lost my CrossOver configuration menus. What can I do?

CXSetup provides a way of regenerating the CrossOver configuration menus.

Please see the section titled "Recreate CrossOver menu" in the documentation for CXSetup advanced settings.

3.6.2.

CrossOver deleted all my KDE 3 menu entries in Mandrake!

This problem first occurred in Mandrake 8.2 with the early KDE3 RPMs. This bug has been fixed in kdebase3-3.0-8mdk. You can download the latest KDE3 RPMs for Mandrake 8.2 by following the instructions here.

A similar issue is also happening in the Mandrake 9.2 release candidate versions when using the Mandrake KDE menus and installing CrossOver in a non-root account. The recommended fix is to upgrade to the final Mandrake 9.2 release.

3.6.3.

CrossOver applications lose focus under KDE!

KDE includes a setting called focus stealing protection that protects misbehaving X Windows applications from always popping in to focus. This can cause problems with certain applications under CrossOver.

A workaround for this behavior is to either disable focus stealing protection or add an exception for each application under CrossOver that shows this behavior. Directions with an example of Microsoft Word are as follows:

  • Go to the KDE Control CentreDesktopWindow Specific settings.

  • Select New and in the window that opens type "Disable focus stealing prevention for WINWORD" into the Description box.

  • Click on "match whole window class" and add "winword.exe" (without the quotes) in the box to its left.

  • In the Workarounds tab - click the box for focus stealing prevention and choose "force" and "none" as the two options to its right.

3.6.4.

I am using KDE and the Windows Applications menu is missing.

This is usually caused by (too much) editing of the menus with kmenuedit. An easy way to see if that's the case is to look for a xxx-kmenuedit.menu file, usually in ~/.config/menus. If you find such a file, move it out of the way, then log out and log back in. If the menus become visible, then that was the problem.

Another possibility is that you have three bottles or more putting their menus in 'Windows Applications'. While allowed by the XDG standard, this seems to confuse KDE which then loses some or all of these menus. A workaround is to reconfigure the extra bottles to put their menus in a different location. To do so, run CXSetup, select one of the bottles, click on Configure, go to the Menus tab, and set the Menu root field to 'Win98 Applications' for instance.

This can also happen on early versions of SuSE 9.0. On these systems a workaround is to rename ~/.kde/share/applnk/Windows Applications to ~/.kde/share/applnk/WindowsApplications (i.e. remove the space). However the recommended fix is to upgrade your distribution to the latest SuSE 9.0 revision.

3.6.5.

I am using Gnome in SUSE Linux and the menus I created in my account are missing.

This is known to happen on SuSE 8.0, 8.2 and SUSE Linux 9.2. This is because, on these versions of SUSE Linux, Gnome is configured to prevent users from modifying the menus. This means that on these systems, only the system administrator can create new menu entries. So depending on how you installed CrossOver you may be missing all the CrossOver menus or just the Windows applications menus.

3.6.6.

I am using SuSE 8 and the CrossOver menus don't have icons.

If you are using Gnome in combination with the SuSE menus, then the reason for this issue is that the SuSE menu system modifies our menus to point to PNG icons instead of the XPM icons we provide.

The solution is to install ImageMagick so that CrossOver can convert the icons on the fly to the format forced on us by the SuSE menu system. After installing ImageMagick, please see the documentation for rebuilding menus.

Another solution is to switch from the SuSE menus to the regular Gnome menus.

3.6.7.

I am using SuSE 8 and my Windows Applications folder is called Windows_Applications and does not have the expected icon!

This issue happens to root menus when using the SuSE menu system on SuSE 8.0 and 8.1. The symptom is that menu folders that are supposed to contain a space contain an underscore instead, and have the default Gnome or KDE folder icon instead of the expected icon. However, actual menu entries should not be affected.

This issue is caused by a bug in the SuSE menu system where it fails to copy file containing the folder name and icon information to the relevant Gnome and KDE locations.

The simplest workaround is to switch to the native Gnome or KDE menus. Alternately you could upgrade to SuSE 8.2, or even better, to SuSE 9.0 or greater. However since this is just a cosmetic issue we recommend simply ignoring it.

3.6.8.

Can I configure CrossOver so that some file types are opened using Unix applications?

CrossOver provides scripts that make this possible. For instance to have the Unix Acrobat Reader program open PDF documents, all you have to do is type the following command:

$ ~/cxgames/bin/cxwinassoc --extension pdf /usr/bin/acroread

Note that this may not work for all file types in all applications. For instance Internet Explorer always opens text documents using its internal viewer, no matter what the file associations say.

3.7. Other issues
3.7.1. Why do my CrossOver applications report time a hour faster or slower than my system?
3.7.2. Why do applications hang when I try to browse files?
3.7.3. When I move the mouse pointer over a menu, it disappears!
3.7.4. Why don't the dead keys or national characters on my keyboard work?
3.7.5. How can I turn off anti-aliased fonts?
3.7.6. I'm displaying my applications to a Mac OS X or NoMachine Client and some text is not visible.
3.7.7. How can I make CrossOver use PostScript fonts in applications?
3.7.8. How can I change the size of my menu font?
3.7.9. What happened to the Wine config file?
3.7.10. How can I change my Wine config?
3.7.11. What is a MIME type?
3.7.12. How can I make Hebrew text display from right to left?
3.7.13. Why do iTunes and my Microsoft Office applications perform poorly or fail to display images?
3.7.14. I am having problems with white rubberbands or lines that won't erase in CrossOver applications.
3.7.15. How can I get my mouse wheel to work in CrossOver?
3.7.16. How do I copy and paste to and from my xterm?
3.7.17. Why do I have Zombie wine-preloader processes after exiting my applications?
3.7.1.

Why do my CrossOver applications report time a hour faster or slower than my system?

Some users have reported that applications running under CrossOver are reporting time a hour slower or faster than the local system time. If you see this problem please file a support ticket so we can take a closer look at the issue.

[Tip]

Liam Fallon reported that it is possible to work around this problem by deleting a key in the registry. To enable the workaround run the following commands:

$ ~/cxgames/bin/cxrun

Select the correct bottle, type in regedit for the command, run it and go to the following Key: HKEY_LOCAL_MACHINE->System->CurrentControlSet->Control->TimeZoneInformation and simply delete it.

3.7.2.

Why do applications hang when I try to browse files?

If you are using Mandrake's supermount and CrossOver, browsing files with some applications will cause the application to stop responding for a long time. This problem most commonly happens on laptops that have their floppy drives removed.

You can solve the problem by running the following commands as root to disable supermount:

# supermount -i disable
# umount /mnt/cdrom
# umount /mnt/floppy

You need to run the umount command even if you don't have a CDROM or floppy inserted or mounted. If you are sure that the problem is caused by a missing floppy drive, you can remove the floppy drive entry from /etc/fstab and re-enable supermount.

3.7.3.

When I move the mouse pointer over a menu, it disappears!

This problem occurs with the Sawfish and Twm window managers. If you are using Sawfish, change the "Focus" setting ("When does the mouse pointer affect the input focus") in the "Customize" menu to "Click".

There is currently no solution to this problem for Twm, and we recommend you upgrade your window manager.

3.7.4.

Why don't the dead keys or national characters on my keyboard work?

This usually indicates that your locale wasn't correctly set up. CrossOver Games uses environment variables to set internal locale support in this priority order: LC_ALL, LANGUAGE, LANG.

The following command should print the environment variables controlling CrossOver Games's locale:

$ set | egrep -e LC_ -e LANG

Note that the output of the locale command may differ from the above.

A quick test to ensure that setting the correct locale will help is to execute the following command line and type the offending characters in Word (eg. for Portuguese):

$ LC_ALL=pt_PT ~/cxgames/bin/winword

If you are using UTF-8 locale please make sure that it matches your base language. For example, Hebrew characters won't work in en_US.UTF-8 locale. You need to use he_IL.UTF-8.

3.7.5.

How can I turn off anti-aliased fonts?

CrossOver Games uses anti-aliasing for TrueType fonts by default. Anti-aliasing generally provides higher quality font display, however some users may prefer not to use it.

If you do not wish to use anti-aliased fonts, you can disable support for them in the registry. To edit the registry for the current bottle, run the following command:

$ ~/cxgames/bin/cxrun

Select the correct bottle, type in regedit for the command, run it and go to the following Key: HKEY_CURRENT_USER\Software\Wine\X11 Driver and add the following lines:

"ClientSideAntiAliasWithRender" = "N"
"ClientSideAntiAliasWithCore" = "N"

Alternatively, from the command line you can just run this command, which will make the equivalent registry changes.

$ ~/cxgames/bin/regedit --bottle bottlename - <<EOF
[HKEY_CURRENT_USER\Software\Wine\X11 Driver]
"ClientSideAntiAliasWithRender" = "N"
"ClientSideAntiAliasWithCore" = "N"
EOF

3.7.6.

I'm displaying my applications to a Mac OS X or NoMachine Client and some text is not visible.

The NoMachine and Mac OS X Xserver have problems using the X Render extension. To work around this problem follow the steps listed in the Anti-Aliased font FAQ above and set the following line:

"ClientSideWithRender" = "N"

3.7.7.

How can I make CrossOver use PostScript fonts in applications?

CrossOver does not support using PostScript fonts in applications when the Render extension is enabled. To correct this follow the directions in the Anti-Aliased font FAQ above and set the following line:

"ClientSideWithRender" = "N"

3.7.8.

How can I change the size of my menu font?

Depending on your display settings, the CrossOver menu font may be inconveniently large or small. This font can be adjusted by editing the file ~/.cxgames/bottlename/drive_c/Windows/win.ini and adding the following lines:

[Desktop]
menufontsize=12

Try adjusting the 12 to suit your setup.

There is also an option you can set in the registry. To edit the registry for the current bottle, run the following command:

$ ~/cxgames/bin/cxrun

Select the correct bottle, type in regedit for the command, run it and go to the following Key: HKEY_CURRENT_CONFIG/Software/Fonts and change the line that reads:

"LogPixels"="0x00000060(96)"

to something like "0x000000078(120)"

3.7.9.

What happened to the Wine config file?

The Wine configuration has been moved in the registry. As part of the upgrade process your old configuration should migrate. If you encounter a problem in this process please file a support ticket.

3.7.10.

How can I change my Wine config?

We don't recommend that you change the default Wine configuration that comes with CrossOver unless noted in this FAQ;. The CrossOver software makes many assumptions about the Wine config settings that may cause it to fail if those settings are changed. For example, CrossOver expects that the locations of drives Z: and Y: will always be the filesystem root and the user's home directory. If you encounter a problem with the default configuration please file a support ticket.

3.7.11.

What is a MIME type?

MIME types are sent along with a stream of data so that the application receiving it is able to readily identify the type of content contained within it. In the absence of a MIME type (an optional field in the protocol), the application can deduce content type from the filename extension.

That way, the browser can maintain a table of MIME types (and file extensions) where it looks up the plugin or application that will interpret and display the data it has received.

3.7.12.

How can I make Hebrew text display from right to left?

There is a special extension for Wine that provides partial support for bidirectional text. This extension imposes several additional system requirements on CrossOver, so it is not included in our standard build.

A replacement library with partial bidirectional support can be downloaded here.

First back up your existing gdi32.dll.so file, like this:

$ cp ~/cxgames/lib/wine/gdi32.dll.so ~/cxgames/lib/wine/gdi32.dll.so.bak

Then copy the new library into the /lib/wine directory:

$ cp gdi32.dll.so ~/cxgames/lib/wine/

This library provides only partial support for bidirectional text. In situations where right-to-left and left-to-right text are mixed on a single line, letters may become scrambled.

3.7.13.

Why do iTunes and my Microsoft Office applications perform poorly or fail to display images?

When running iTunes or Microsoft Office applications you may notice poor performance, trouble redrawing the application on the screen or images in PowerPoint may not appear if your X server isn't configured for 24bit colour.

You can solve this problem by switching your X server's colour depth to 24 bits per pixel. This can be done by editing /etc/X11/XF86Config and adding a DefaultDepth entry in the Screen section, as shown below.

Section "Screen"
        Identifier "Screen0"
        Device     "Card0"
        Monitor    "Hansol920D"
        DefaultDepth 24

3.7.14.

I am having problems with white rubberbands or lines that won't erase in CrossOver applications.

There is a bug in some XFree video drivers where the XOR drawing method is not implemented properly. Because XOR drawing mode is required for the rubberbanding, the only known workarounds are to switch to a Vesa graphics driver (which is slower) or to change to a video card with a driver that properly implements this function.

3.7.15.

How can I get my mouse wheel to work in CrossOver?

The mouse wheel will work in CrossOver if it works in other X applications, such as Mozilla or X-Chat.

If you have a mouse with a mouse wheel and use XFree86 4.x, you can enable it by editing /etc/X11/XF86Config and adding the following lines in the InputDevice section.

Section "InputDevice"
        Identifier  "Mouse0"
        Driver      "mouse"
        Option      "Protocol" "auto"
        Option      "Device" "/dev/mouse"
        Option      "Buttons" "5"
        Option      "ZAxisMapping" "4 5"
EndSection

3.7.16.

How do I copy and paste to and from my xterm?

By default CrossOver only uses the clipboard accessed by explicit operations via the edit menu or control keys. CrossOver does have a setting that allows pasting to an X application via the middle mouse button. With this setting CrossOver will also recognize selected text from an X application. You will need to enable support for this setting in the registry. To edit the registry for the current bottle, run the following command:

$ ~/cxgames/bin/cxrun

Select the correct bottle, type in regedit for the command, run it and go to the following Key: HKEY_CURRENT_USER\Software\Wine\X11 Driver and add the following line:

"UsePrimarySelection" = "Y"

3.7.17.

Why do I have Zombie wine-preloader processes after exiting my applications?

Linux kernel versions 2.6.0 to 2.6.7 had a bug that caused the process name not to be removed from the list of running processes after exiting CrossOver. Upgrading to a later version of the Linux kernel fixes this issue.

3.8. Uninstalling CrossOver
3.8.1. How do I uninstall CrossOver?
3.8.1.

How do I uninstall CrossOver?

CrossOver 4.0 or greater.  If you performed a standard non-root installation, go to the CrossOver menu and choose Uninstall Office, or run the following command manually:

$ ~/cxgames/bin/cxuninstall

If you installed CrossOver as root, for instance using an RPM or Debian package, then you will probably want to remove the CrossOver environment from the user accounts first. To do so, simply log in as that user and proceed to uninstall as described above.

CrossOver 3.0.1 or older.  If you have installed CrossOver Games 2.0 or greater using the RPM or Debian package, then use your distribution's package management tools to uninstall it. For instance:

$ rpm -e crossover-games-demo

or

$ dpkg -r crossover-games-demo

If you installed CrossOver Games using the Loki installer (install-*.sh), then use the following command to uninstall it:

$ ~/cxgames/bin/cxuninstall

If you installed CrossOver as root, you will also need to delete the per user ~/.cxgames directory for each user that installed CrossOver. Each user can do this using the command:

$ rm -rf ~/.cxgames

4. Integration with Unix Browsers

4.1. General
4.1.1. Setting the default browser.
4.1. General
4.1.1. Setting the default browser.
4.1.1.

Setting the default browser.

Some Windows plugins and applications will occasionally need to start a web browser. Such requests are handled by CrossOver which tries to find a suitable browser, trying multiple candidates in turn, starting with Netscape, then Mozilla-based browsers, etc.

However you can also instruct CrossOver to start a specific browser. To do so, start CXSetup and go to the Configure tab. There, select Specify Browser and type the command to run to start your preferred browser, for instance 'mozilla' or '/usr/bin/konqueror', in the corresponding edit field.