This section addresses commonly asked questions related to the configuration, installation, and execution of CrossOver Linux Standard 7.1.0. It was last updated on October 22, 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 Linux Standard, please check the older issues page.
For more general information on CrossOver Linux Standard, see our web site.
1. Linux distribution dependent issues |
||||
|
||||
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.
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 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:
|
||||
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:
Look for the line:
and replace it with:
|
||||
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/cxoffice/lib/wine/ntdll.so: failed to map segment from shared object:
cannot allocate memory". To correct this issue, edit the file
|
||||
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.
|
||||
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 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? |
|||
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
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:
If you know the name of the Windows executable you can try running it using the following command:
If the application registers itself in the right way, the following may work:
If you don't know the name of the application, you can search under the
|
||||
3. General questions |
||||
|
||||
3.1. About CrossOver |
||||
|
||||
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
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:
|
||||
3.1.2. |
I need a new or upgrade copy of CrossOver Linux Standard. Where can I download it from? |
|||
To download the CrossOver Linux Standard 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 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 Linux Standard before upgrading. Just download the new version of CrossOver Linux Standard 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:
Or, if you installed as root:
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 Linux Standard supports. If you need to use an application that is not currently by CrossOver Linux Standard, 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 Linux Standard to work with it. C4 provides a way for us to assess the level of interest in your application. You can also check out Tom Wickline's guide to Running Unsupported Applications in CrossOver. 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:
|
||||
3.2. Installation |
||||
|
||||
3.2.1. |
The Loki installation script fails when I run it. |
|||
The error message usually looks something like this:
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:
When installing, CrossOver setup first extracts itself to
You can use the df command to display the amount of free space on each of your harddisk partitions:
Note that the You can also tell the installer to extract its temporary files to a different directory by running it as followings:
|
||||
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
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 OfficeSetup display an empty window? |
|||
OfficeSetup requires the Helvetica and Fixed fonts to be installed on your system. If these fonts are unavailable, the OfficeSetup 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. |
OfficeSetup buttons are just blank! What do I do? |
|||
Install 75dpi X fonts (XFree86-75dpi package). Be sure to restart X before you launch OfficeSetup again (restarting xfs is not enough). |
||||
3.2.6. |
OfficeSetup 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 OfficeSetup text fields? |
|||
Some versions of Linux (including SUSE 9.3) ship with SCIM turned on by default. This interferes with text entry in OfficeSetup. The solution is to upgrade to SCIM version 1.4 or later, or turn SCIM off altogether. |
||||
3.2.8. |
On Debian OfficeSetup 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:
|
||||
3.2.9. |
I removed CrossOver Linux Standard 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
|
||||
3.3. When nothing works |
||||
|
||||
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.
|
||||
3.3.2. |
OfficeSetup gives "Unable to get list of installed applications". |
|||
Running OfficeSetup 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.
If these solutions do not work for you, please generate a debug trace file with the command below and send it to support.
|
||||
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:
|
||||
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:
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 Option "UseFastTLS" "2" That should allow you to run CrossOver without problems. |
||||
3.4. Application installation |
||||
|
||||
3.4.1. |
My Office 2003 install fails when installing files from a directory. Why? |
|||
If you are installing Office 2003 from a folder on the filesystem rather than from a CDROM or ISO image and you select 'Other *.exe file' in CrossOver Setup, in some cases the installation can fail. If you see this behavior, use 'Alternative CD-ROM location' to select the installation folder. If this does not resolve the issue please file a support ticket. |
||||
3.4.2. |
My Office 97 install fails when installing files from a directory. Why? |
|||
Please see the question about Office 2003 above. |
||||
3.4.3. |
I am installing an application from a CD-ROM (e.g. Microsoft Office), and the installer complains about missing files. |
|||
Some CDs contain 'hidden' files which may not be visible by default on Linux. This may cause your Office installation to fail with a 'file not found' error (eg. "can't find OFFICE1.CAB"). Versions of CrossOver Linux Standard after 1.1.0 will detect this issue, warn you and offer you to 'fix' your fstab configuration file, however the detection or fix may fail under certain circumstances. The solution is to mount your CDROM using the 'unhide' option.
You can also add this option in /dev/cdrom /mnt/cdrom auto unhide,defaults,ro,noauto,user,exec 0 0
It is important to add the option at the beginning of the 4th field as the Linux kernel ignores all options after an invalid one.
Additionally, if you are using supermount, changing
IMPORTANT: Note that some systems expect the "nohide" option instead of "unhide". The easiest way to find out which option is appropriate in your case is to search the mount command manual page (man mount). So if you tried the procedure above and it still does not work, repeat the process with the "nohide" option instead and see if it makes a difference. |
||||
3.4.4. |
My installer complains "A previous program installation was never completed..." Why? |
|||
Some installers expect that the file
To solve this problem, you can select the option from the CrossOver menu, or run the following command:
|
||||
3.5. Printing |
||||
3.5.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.5.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.5.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.5.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 Linux Standard'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:
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.6. Sound |
||||
|
||||
3.6.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 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.6.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:
|
||||
3.6.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.6.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 OfficeSetup and going to the Settings tab. There the Sound driver load order determines which sound backend to use.
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.6.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.6.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.6.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:
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:
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.
|
||||
3.6.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:
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.7. Integration with desktop environments such as Gnome and KDE |
||||
|
||||
3.7.1. |
I lost my CrossOver configuration menus. What can I do? |
|||
OfficeSetup provides a way of regenerating the CrossOver configuration menus. Please see the section titled "Recreate CrossOver menu" in the documentation for OfficeSetup advanced settings. |
||||
3.7.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.7.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:
|
||||
3.7.4. |
I am using KDE and the 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
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 OfficeSetup, 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 |
||||
3.7.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.7.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.7.7. |
I am using SuSE 8 and my folder is called 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.7.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:
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.8. Other issues |
||||
|
||||
3.8.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.
|
||||
3.8.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:
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
|
||||
3.8.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.8.4. |
Why do some applications (QuickTime Player, Trillian) stay on top of the other windows and appear in all my desktops? |
|||
This usually happens for windows that don't have the usual window manager decorations, that is the border and buttons normally used to move and resize the window. The reason why they don't have these is that this is how the application is supposed to behave on Windows. For instance, if you look at the QuickTime Player or Trillian on Windows, you will notice that they don't have the normal title bar or borders. Wine, and thus CrossOver emulates that behavior and thus the window does not have the regular window manager decorations. But to do this bit of magic, Wine currently has to make this an unmanaged window. Unfortunately some window managers treat such windows in special ways. For instance the KDE window manager puts such windows on top of all the others, and display them in all the desktops, hence the behavior noted in the second question. We hope to remedy this problem in a future release but this is a hard problem so it may be a while. Unfortunately there is no known workaround. |
||||
3.8.5. |
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 Linux Standard uses environment variables to set internal locale support
in this priority order: The following command should print the environment variables controlling CrossOver Linux Standard's locale:
Note that the output of the 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):
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.8.6. |
How can I turn off anti-aliased fonts? |
|||
CrossOver Linux Standard 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:
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:
Alternatively, from the command line you can just run this command, which will make the equivalent registry changes.
|
||||
3.8.7. |
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:
|
||||
3.8.8. |
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:
|
||||
3.8.9. |
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
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:
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:
to something like "0x000000078(120)" |
||||
3.8.10. |
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.8.11. |
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.8.12. |
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.8.13. |
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:
Then copy the new library into the /lib/wine directory:
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.8.14. |
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
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Hansol920D"
|
||||
3.8.15. |
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.8.16. |
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 Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/mouse"
|
||||
3.8.17. |
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:
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:
|
||||
3.8.18. |
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.9. Uninstalling CrossOver |
||||
3.9.1. |
How do I uninstall CrossOver? |
|||
CrossOver 4.0 or greater. If you performed a standard non-root installation, go to the menu and choose , or run the following command manually:
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 Linux Standard 2.0 or greater using the RPM or Debian package, then use your distribution's package management tools to uninstall it. For instance:
or
If you installed CrossOver Linux Standard using the Loki installer
(
or the following command for CrossOver Linux Standard 1.x:
If you installed CrossOver as root, you will also need to delete the per user
|
||||
4. Microsoft applications |
||||
|
||||
4.1. General |
||||
|
||||
4.1.1. |
The Office 2000/XP installation hangs when rebooting. Why? |
|||
This problem may occur on RedHat's Fedora Core 1 distribution. After answering the "Do you wish to reboot dialog" during the Office 2000/XP installation process, the installation may hang. The problem is related to a bug in the default Linux kernel distributed with Fedora Core 1, and may be solved by running RedHat's up2date service, or upgrading your kernel to kernel-2.4.22-1.2179.nptl. |
||||
4.1.2. |
The Office 2000/XP Help system fails to load. Why? |
|||
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. |
||||
4.1.3. |
The Office 2000 installation never completes. What is wrong? |
|||
This problem is usually caused by bad media. If your Office Installation CDROM has errors, the installer will endlessly try to copy the file with the error. The installer will still allow you to cancel the install in this case. You can detect a corrupt CDROM with the following method:
If you get any 'Input/Output' errors, then your Office CDROM is faulty and it should be replaced. |
||||
4.1.4. |
The Office 2000/XP installation completes but my applications hang. Why? |
|||
We are still investigating this issue but in most cases this problem seems caused by the CUPS printing system hanging while trying to browse the network for other network printers and CUPS servers. If you have the CUPS and Samba packages installed it is recommended that you adjust the CUPS timeout values or disable it from browsing the network. |
||||
4.1.5. |
My Office 2003 upgrade installation starts but I am unable to select my qualifying product to upgrade. Why? |
|||
CrossOver does not support the Office 2003 upgrade release at this time. Support for this is planned in the next version. |
||||
4.1.6. |
Why does DCOM95 fail to install with errors about RPCRT4.DLL? |
|||
This problem occurs often with SuSE kernels that have an option to limit the user address space to 1GB instead of the usual 3GB. When DCOM95 is installed, you will receive the error message: Error registering the OCX: C:\Windows\System\rpcrt4.dll
Some Windows programs explicitly use certain address in the computer's memory map. Wine requires a 3GB user address space limit to allow Windows programs to work correctly. If you have this problem, it is likely that you need to recompile your Linux kernel with the configuration option 'User address space size' set to 3GB in the 'Processor type and features' section. |
||||
4.1.7. |
Why does my Office install fail when updating the Microsoft Installer? |
|||
If your Office (XP or 2000) install fails almost immediately when it tries to install a new copy of the Microsoft Installer, you may be experiencing problems due to security patches. Please check this FAQ entry for further information. |
||||
4.1.8. |
Word and Excel won't start on my dual monitor system! |
|||
Office applications start maximized by default. There are some bugs in the code dealing with maximization in Wine that causes the requested window geometry to be different from the returned window geometry. Dual headed systems are especially prone to this problem. First, make sure your window manager does not remember the window's state or size. In Sawfish, under "Placement options" you may have to unset "Automatically remember window placements", "Automatically remember other window attributes" and "Automatically remember window sizes". Start X with a single monitor (ie. not in Xinerama mode) then start Word, Excel etc. Unmaximize all the applications' main windows. Restart X in dual headed mode, and the applications should now work correctly. Don't leave them maximized when you exit or the problem will occur again. |
||||
4.1.9. |
Microsoft Office won't save or open files with non English letters. |
|||
During the installation, if you selected your native language which was not English. And are able to type 'special characters' which are part of the native language, CrossOver might not able to read/write some of the files named with these 'special characters'. This could be a case where your environment is not correctly set. Try to launch WinWord with
i.e. for Slovak language
To see if that resolves the issue. If not please file a support ticket. |
||||
4.1.10. |
Office won't let me save files on NFS filesystems! |
|||
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:
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:'. |
||||
4.1.11. |
After installing Office 97, I have trouble saving files and get errors about
|
|||
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 OfficeSetup'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. |
||||
4.1.12. |
When I open a file, Office appears to lock up. |
|||
There is a bad interaction between CrossOver Linux Standard 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. |
||||
4.1.13. |
When I exit Word, it says "The file Normal already exists". |
|||
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
|
||||
4.1.14. |
Clippy is causing Word to misbehave. How do I stop it? |
|||
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. |
||||
4.1.15. |
Why do the menus of Microsoft Office applications sometimes appear to freeze? |
|||
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. |
||||
4.1.16. |
Why does Visio 2002 crash when I try to run it? |
|||
There is a bug when trying to perform certain drawing operations which will
result in a crash in the |
||||
4.2. Microsoft Office Service Packs |
||||
4.2.1. |
Why does the Office 2003 service pack install fail to find my cdrom? |
|||
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. |
||||
4.2.2. |
"Internal error 2371" when installing Office 2000 SP1. |
|||
To solve this problem, you need to make your CDROM device file
(eg. |
||||
4.2.3. |
When installing Office 2000 SP1 the dialog "Insert Office 2000 CD" won't go away. |
|||
Before attempting to install Office 2000 SP1, you first should place your Office 2000 CDROM into your CDROM drive. Additionally, Office should be able to access the physical device associated with your CDROM. Unless you are using Automount, make sure that the CDROM is mounted by typing the following command:
To make the CDROM's physical device readable, enter the following commands:
If you are using Mandrake with Supermount, you may need to disable it first to get the service pack installation to work, as described below. The following was contributed by Didier Féminier: Open a terminal window, and enter the following commands:
After you have disabled supermount, you will then need to go back and mount the CDROM manually, as described above. |
||||
4.3. PowerPoint |
||||
4.3.1. |
The Slideshow in PowerPoint does not work. |
|||
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 OfficeSetup. |
||||
4.3.2. |
PowerPoint XP never starts or exits right after startup. |
|||
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
[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. |
||||
4.4. Outlook |
||||
|
||||
4.4.1. |
Outlook can't connect to my Exchange server. |
|||
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 127.0.0.1 localhost 192.168.0.1 mycomputer.myco.com mycomputer 192.168.0.254 mail.myco.com myco_mail_corp
|
||||
4.4.2. |
When I run the spell checker on a composed message in Outlook 2000, it crashes. |
|||
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. |
||||
4.4.3. |
I enter my password for my Exchange server in Outlook and Authentication Fails. |
|||
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. |
||||
4.4.4. |
When I exit Outlook the process still shows up in my process list or the application never closes. |
|||
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. |
||||
4.4.5. |
When I right-click on a contact in Outlook, the program crashes. What can I do? |
|||
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. |
||||
4.5. Internet Explorer |
||||
|
||||
4.5.1. |
Internet Explorer 6.0 cannot access Outlook Web Access. Why? |
|||
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. |
||||
4.5.2. |
The Internet Explorer 6.0 installation hangs my machine. Why? |
|||
This problem occurs when installing Internet Explorer in CrossOver on a machine with NVidia's binary only video drivers. If you experience this problem you should try using the standard XFree86 drivers, or a different version of NVidia's drivers. |
||||
4.5.3. |
My home directory is mounted via NFS. How can I install Internet Explorer? |
|||
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. |
||||
4.5.4. |
IE crashes when I try to print. How can I print? |
|||
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 Installation Wizard. |
||||
4.5.5. |
How can I make Outlook Web Access work in Internet Explorer? |
|||
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 Installation Wizard. |
||||
5. Other applications |
||||
|
||||
5.1. General |
||||
5.1.1. |
When I try to start my program, it asks me to insert the CD. But the CD's already in the drive! What's happening? |
|||
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. |
||||
5.2. Photoshop |
||||
5.2.1. |
How can I get my Wacom tablet to work with Photoshop? |
|||
Tablet functionality in CrossOver Linux Standard depend upon the XFree86 XInput extension. The GIMP program uses the same functionality, so if you are having problems, run GIMP and see if your tablet works as expected. If GIMP does not function correctly, then your tablet was not set up correctly in XFree86. For details about getting your tablet to work with XFree86, please see http://linuxwacom.sourceforge.net/index.php/main. |
||||
5.2.2. |
Why doesn't Alt-Click work with Photoshop? |
|||
Some window managers use the Alt-Click combination to move windows. This means that the button click never reaches Photoshop. To get the Alt-Click in Photoshop you need to disable this key binding in your window manager. Each window manager may be different, however here are a few examples to help you find how you may be able to do this: On Mandrake 8.1 you can control this behavior by opening the KDE Control Center and going to Look'N'Feel -> Window Behavior. Once there, scroll to the 'Inner window, titlebar and frame' section at the bottom. There you can either change the 'Modifier Key' field or set 'Modifier Key + Left Button' to 'Nothing'. Here the fields were set to 'Alt' and 'Move' respectively so that Alt+Left Click anywhere inside a window would move the window. After setting 'Modifier Key + Left Button' to 'Nothing' Alt+Left Click should have no special effect, and Photoshop should work correctly. On Gentoo, KDE 3.1 vanilla the way to turn it off is: Control Center Actions tab, then under the section "Inner Window, Title Bar, Frame" set the "Modifier Key + Left Button" to nothing. → and theOn RedHat 9, Metacity: → → . Switch radio button off of ALT to either CTRL or Super (Windows Logo) under "To move a window, press-and-hold this key then grab the window:" |
||||
5.2.3. |
Why is saving a file in Photoshop so slow? |
|||
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. |
||||
5.2.4. |
Why does Photoshop start with a "Program Error"? |
|||
On systems with large amounts of memory you may see a error on start-up such as 'Program Error'. This seems to be caused by a kernel issue that we are researching. In the meantime you can work around this issue by limiting the amount of memory used by Photoshop, assuming you have Photoshop installed in the win98 bottle, by adding running the following command: echo -e '[Software\\Policies\\Adobe\\Photoshop\\7.0]\n"OverridePhysicalMemoryMB"="dword:00000200"' | ~/cxoffice/bin/wine --bottle win98 regedit -
This will limit Photoshop to 512 MB of memory. For a higher value such as 1GB use the value "dword:00000400" |
||||
5.3. Lotus Notes |
||||
5.3.1. |
When trying to connect Notes to a Domino server I get "server not responding" errors. |
|||
You can solve the problem using the following method (contributed by Michael Osten):
|
||||
5.4. Dreamweaver MX |
||||
5.4.1. |
Dreamweaver hangs when I click on "Define a Site". Why? |
|||
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:
|
||||
5.4.2. |
How can I start Dreamweaver's Extension Manager? |
|||
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:
|
||||
5.5. iTunes |
||||
|
||||
5.5.1. |
Why can't I log in to the iTunes Music Store? |
|||
Due to Apple's discontinuing of support for the older versions of iTunes, we have dropped the supported status of iTunes to bronze and plan to add support for iTunes 7 to CrossOver 6.1. |
||||
5.5.2. |
When I try to play a song the elapsed time remains at 0:00. Why? |
|||
This is caused by iTunes not finding any usable sound devices. Check that
any necessary kernel modules are loaded and that you have read and write
access to the DSP and mixer devices (usually |
||||
5.5.3. |
My iTunes sound is silent, choppy, or full of static. How can I fix it? |
|||
iTunes doesn't work perfectly with all sound cards. The first thing to try is to switch your iTunes sound to "waveOut" mode.
If this doesn't help, you may want to consider other suggestions in the Sound section of this FAQ. |
||||
5.5.4. |
Can I use CrossOver to sync my iPod from iTunes? |
|||
Maybe. We have tested with iPods and iPod mini's and it works great for us. However, even on the latest distributions it will still be necessary to do some low-level tinkering. Not for the faint of heart. iPod support requires you to make some modifications as root, modify configuration scripts for Hotplug and generally have a good understanding of Linux. We are working to improve this for a future release and automate things. If you are unfamiliar with doing hardware support for Linux, we would recommend that you wait and do not try to get the iPod working. That said, here are detailed instructions about how to enable iPod support in CrossOver:
If you have reached this point and not given up then you should be good to go. Have your iPod setup, plugged in and mounted; fire up iTunes and give it a bit to recognize the iPod. It takes iTunes on my laptop (500 mhz) about 2 minutes to recognize the iPod. But from there you should be able to sync and everything with your iPod. Understand that Linux is less friendly to randomly unplugging usb devices. You need to make sure all the processes accessing the device are shutdown and you have unmounted the device. Failure to do that can lock up the iPod so bad that a you will need to totally reset it to make it work again. Linux does not send the "Ok to pull" message to the device so the iPod will always say DO NOT UNPLUG. You need to make sure on your end that everything is cleanly unmounted before you unplug. Again you can use "cxipod --umount" to do the unmounting if you run it as root. Phew... good luck! How to get the iPod mini to work.
Hotplug on SUSE 9.2.
for MAP in $MAP_USERMAP $HOTPLUG_DIR/usb/*.usermap to for MAP in $MAP_USERMAP $HOTPLUG_DIR/usb/*.usermap $MAP_WINEMAP
|
||||
5.5.5. |
Why did iTunes lose my preferences after upgrading to CrossOver Linux Standard 5.0? |
|||
This is caused by a difference where between previous versions store application data and where CrossOver Linux Standard 5.0 stores it. The old preferences are still there, but are not found by iTunes. The preferences can be made to be found again by adding a value to the registry, by running the following command: echo -e '[HKEY_CURRENT_USER\\Software\\Microsoft\\Windows\\CurrentVersion\\Explorer\\User Shell Folders]\n"Local AppData"="C:\\\\Local Settings\\\\Application Data"' | ~/cxoffice/bin/wine --bottle dotwine regedit -
|
||||
5.6. Quicken Issues |
||||
5.6.1. |
Why do I get an error saying 'Error: Could not load QWPA.INI' after upgrading to CrossOver Linux Standard 5.0? |
|||
This is caused by a difference where between previous versions store application data and where CrossOver Linux Standard 5.0 stores it. The data is still there, but is not found by Quicken. The data can be made to be found again by adding a value to the registry, by running the following command: echo -e '[HKEY_CURRENT_USER\\Software\\Microsoft\\Windows\\CurrentVersion\\Explorer\\User Shell Folders]\n"Local AppData"="C:\\\\Local Settings\\\\Application Data"' | ~/cxoffice/bin/wine --bottle dotwine regedit -
|
||||
5.6.2. |
How can I download my web connect data? |
|||
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. |
||||
5.7. Steam Issues |
||||
5.7.1. |
Why can I not click the OK button after connecting to a Counter-Strike 1.6 game? |
|||
To our knowledge this only happens with cracked Counter-Strike versions, please use the official version from Steam. |
||||
6. Plugins |
||||
|
||||
6.1. QuickTime |
||||
|
||||
6.1.1. |
Instead of the plugin, all I get is a gray square. This even happens on the QuickTime demo page. |
|||
See our test pages at the following URL: http://crossover.codeweavers.com/tests. If this continues to happen even after closing all your web browser windows and reloading the web page, then you may have a utility called Plugger or XSwallow installed. Plugger and XSwallow are generic Netscape plugins that will invoke external Unix applications to handle various MIME types. What usually happens in the above situation is that they are trying to handle the file destined to your plugin, for instance here the QuickTime movie, to so that CrossOver never even gets a chance to load. The best way to solve this problem depends on which browser you are having this problem and whether you want to keep Plugger / XSwallow.
|
||||
6.1.2. |
Netscape won't use QuickTime to play QuickTime movies. Is this because of Plugger / XSwallow / Xine? |
|||
Check the About Plugins page to make sure the QuickTime Movie (.mov, .qt) entry is enabled. (Note that there are several QuickTime entries, the video/quicktime MIME type is the one this plugin handles). The right-hand column for this entry should be YES. If not, another plugin may have already been setup to handle that type of data. See the Plugger question for more information. |
||||
6.1.3. |
Some QuickTime movies don't work. Is it because of the firewall? |
|||
Typically you would be able to view our QuickTime demo pages but not the trailers on Apple's web site under this scenario. The reason is that while QuickTime uses the browser to download the movies from our demo pages, on Apple's web site QuickTime gets the movies directly, thus being blocked by the firewall. The fix is to configure QuickTime for getting through the firewall. To do that, start QuickTime by launching it from the desktop icon, or by loading a QuickTime movie in your web browser. Then bring up the "QuickTime Settings" dialog box (via the → → menu in the player, or the menu in the plugin). In the drop down box select the "Streaming Proxy" item. There unselect "Use system settings" and fill in the appropriate entry or entries for your firewall. |
||||
6.1.4. |
I don't get sound in QuickTime. |
|||
First make sure that the problem is specific to QuickTime. Are all other CrossOver applications missing sound? If yes then this may be because an application is already using the sound device. For more details see our FAQ on this subject. Otherwise this may be a problem with DirectSound in which case it is likely to impact other applications such as Windows Media Player. One way to check this is to configure QuickTime not to use DirectSound. To do so, start the QuickTime Player. Then bring up the "QuickTime Settings" dialog box (via the → → menu. In the drop down box select the "Sound Out" item. Then in the 'Device for Playback' drop down box select 'waveOut' and, finally close the dialog.From that point QuickTime will use the regular Windows Multi-Media API (winmm) for audio playback instead of DirectSound. If the problems persist, then check out the sound troubleshooting section. |
||||
6.1.5. |
QuickTime works on some websites, but others respond with a 11001 error. And in the browser, often all I get is the broken QuickTime icon. |
|||
The problem is that QuickTime cannot resolve the hostname for your machine. Here is a way to determine whether this is the problem. First run the following command and check that it returns what you would expect:
Then run:
If successful ping should print something that looks like the following:
Once the first line has been printed you can stop ping. The thing that matters is that ping was able to determine your computer's IP address based on its hostname, as indicated on the first line. If this worked then QuickTime should work too. When ping fails it will typically print a message that looks something like 'ping: unknown host weaver'. In that case QuickTime will not be able to resolve the hostname either and will failed whenever it needs this information. In that case, you need to modify your configuration so that your hostname can be resolved.
The way to fix this depends on your Linux distribution. On Mandrake you may
want to use
Note that in some cases the changes do not take effect immediately. If that is so, run the following command to change the hostname immediately and until the next reboot:
|
||||
6.1.6. |
My QuickTime 6.3 install does not work / now looks really bad. |
|||
This is because of a change in the way CrossOver is configured. Previously we disabled Direct Draw for all QuickTime. However 6.5 needs it enabled. You have 2 basic options: Upgrade to QuickTime 6.5. If you install QuickTime again from OfficeSetup, it will now download and install the latest QuickTime. This will replace your older QuickTime and things will start working. Force QuickTime to draw in GDI mode. The best way to do this is to start OfficeSetup, go to the Control Panel tab, and start the QuickTime control panel. Then, select Video Settings and set it to "Safe Mode (GDI Only)". This should restore QuickTime 6.3 to the same settings as for previous versions of CrossOver. This would be the best option if you have a working setup that you do not want to risk destabilizing with a QuickTime upgrade, or if you have a license for 6.3 that does not extend to later versions of QuickTime. |
||||
6.2. Windows Media Player |
||||
6.2.1. |
When I go to a page which embeds Windows Media Player, it "pops back". Why? |
|||
This problem is caused by a bug in the Mozilla browser and its derivatives: Netscape 6, Galeon, Phoenix and SkipStone. Fortunately this issue has been resolved in Mozilla 1.2. Thus to view embeded Windows Media Player content we recommend that you upgrade to a browser based on Mozilla 1.2 or later, or that you use a browser that is not affected by this bug, such as Netscape 4.x. Note that if Windows Media Player is not embeded in the web page, that is if the page merely launches Windows Media Player in a separate window outside the browser, then it will not be affected by this bug. |
||||
6.2.2. |
The colors are all wrong in the Windows Media Player videos. Why? |
|||
This is caused by a bad interaction between Windows Media Player and Wine's DirectDraw library. When that happens, open the 'Advanced tab, click on Video Renderer item, click on Properties and select the DirectDraw tab. There, unselect the RGB Offscreen item and apply the change. Finally, close Windows Media Player and reopen it. From now on the colors should be fine. → ' menu. Then select the |
||||
6.3. Macromedia Flash |
||||
6.3.1. |
I installed Flash 6/7 but some websites still claim I don't have Flash installed. |
|||
Unfortunately many sites use incorrect code to detect Flash. There are two errors that they commonly make: Some look for the plugin by name: 'Shockwave Flash'. But when installed via CrossOver, the plugin name is 'Shockwave Flash (CrossOver - NPSWF32.dll)'. The reason for the difference is to avoid conflicts with the Linux Flash plugin. For instance Netscape 4.x gets confused when two plugins have the same name. It makes distinguishing the two plugins easier too when both are installed. The second common problem is that the sites will try to make sure that Flash 5 or greater is installed. They do this by extracting the version number from the plugin description but then simply compare it to '5'. Since 6 is different from 5 the check fails and they claim that you do not have Flash 5 (which strictly speaking is true but clearly not what they intended). This problem is not specific to CrossOver and happens on Windows too.
The solution to both problems is to tell CrossOver which name and description
to use for the plugin. To do so, edit
[NPSWF32.dll] ; Use the standard Flash plugin name Name=Shockwave Flash ; Masquerade the Flash 6 or 7 plugin as a Flash 5 plugin Description=Shockwave Flash 5.0 r21
Make sure you DO NOT use quotes for the Name or Description fields. However, note that if masquerading Flash 6 or 7 as a Flash 5 plugin, sites that explicitly require Flash 6 or 7 will not recognize your Flash plugin anymore. Note that you can also just uncomment the 'Name' line if the web site is just confused by the name of the plugin. In either case note that you may force Mozilla to refresh its plugin information cache. For more details see 'Forcing Mozilla to refresh its 'about:plugins' page'. If you are a web developper, please see the plugin detection section for more robust ways to detect plugins. |
||||
6.4. Other plugins |
||||
6.4.1. |
iPix draws with distorted colors. Everything is blue and green. |
|||
iPix, some older versions of QuickTime (e.g. 6.3), and a few other plugins do not draw properly when DirectDraw is enabled. To turn off DirectDraw, go to the Advanced Configuration Settings dialog and uncheck the Enable use of DirectDraw box. Keep in mind that most applications work best with DirectDraw on. Disabling DirectDraw may interfere with correct behavior of other programs. QuickTime 6.5 will not work if DirectDraw is disabled. |
||||
7. Integration with Unix Browsers |
||||
|
||||
7.1. General |
||||
|
||||
7.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 OfficeSetup 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. |
||||
7.1.2. |
Web pages open in Internet Explorer instead of my Unix browser. How do I stop it? |
|||
By default web pages are opened in your Unix browser of choice. However, Internet Explorer may have taken over if you accidentally clicked on 'Make Internet Explorer my default browser'. To revert to having web pages open in your Unix browser again, start OfficeSetup, go to the Configuration tab and click on . |
||||
7.1.3. |
Do I need JavaScript? |
|||
JavaScript is not strictly required. However, many sites use JavaScript to check whether the required plugins are present or not. Thus it is strongly recommended to enable JavaScript. |
||||
7.1.4. |
My browser seems to freeze up occasionally. |
|||
CrossOver Linux Standard uses a client-server architecture, which means that your browser plugin connects to a server which performs the Windows plugin functions. This means that if the Windows browser plugin crashes the Wine environment, CrossOver can (and should!) detect the problem and bring your browser back to life. Hence, you may notice times when it appears as though your browser has hung. After a short wait, however, CrossOver should display a status message to the effect of 'Plugin Server restarted, please reload page', and your browser should become responsive again. |
||||
7.1.5. |
Some websites deny me access because they think my browser does not support QuickTime / Shockwave, ... |
|||
Since the release of CrossOver many web site have changed their policy and no longer block all Linux browsers. This is the case for instance of Shockwave.com. So you are much less likely to encounter such problems. But if you encounter such a web site, you may be able to gain access by modifying the browser's 'user agent' string.
To do so with Mozilla, edit the user_pref("general.useragent.override", "Mozilla/4.7 [en] (Win98; U)");
or user_pref("general.useragent.override", "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)");
In Konqueror go to 'Settings/Configure Konqueror' and then to the 'User
Agent' section. There type the hostname of the website in the first field,
|
||||
7.1.6. |
I am a web developper. What is the recommended way to detect plugins? |
|||
A lot of sites check whether they can embed data of a given MIME type by explicitly checking for the plugin by name. For instance: if (navigator.plugins && navigator.plugins['Shockwave Flash']) { description = navigator.plugins['Shockwave Flash'].description; version = parseInt(description.charAt(description.indexOf(".")-1)); flash4 = version == 4; flash5 = version == 5; } However this technique has many flaws. The plugin may be installed but not configured to handle the MIME type you want to embed. Or the user may be using a different plugin from the one you expect to handle the your MIME type, for instance QuickTime includes Flash support and can be set to handle "application/x-shockwave-flash". Or the plugin may be named differently, "Shockwave Flash (CrossOver - NPSWF32.dll)" for instance, which is commonly the case with CrossOver to avoid confusion with the native Linux plugins (and also to work around limitations of Netscape 4.x). Or the user may have multiple plugins capable of handling the your MIME type: an old Linux Flash 4 plugin, a more recent Linux Flash 5 plugin and the CrossOver Flash plugin. Some scripts will even enumerate all the plugins and just take into account the last matching plugin, not the one that will actually handle the required MIME type. Finally the above code will fail to detect the Flash 6 plugin because its version is neither 4 nor 5. Thus a better approach is to start from the MIME type you want to embed and use the mimeTypes array to check if a plugin is configured to handle it. In the above example one really wants to know is whether there is a plugin that can handle the "application/x-shockwave-flash" MIME type leading to the following code: this.has_plugin=0; if (navigator.mimeTypes && navigator.mimeTypes["application/x-shockwave-flash"] && navigator.mimeTypes["application/x-shockwave-flash"].enabledPlugin) { this.has_plugin=1; } If has_plugin is 1 then you can invoke Flash, otherwise you should find an alternative. This can trivially be adapted to other plugins such as QuickTime (video/quicktime), Shockwave Player (application/x-director), etc. Things get a bit more complex if you need to check the version of the plugin that is going to handle your embeded object. You still don't need to check for the plugin by name but you will usually need to parse its description string. For instance here is how to detect whether Flash 5 or greater is enabled: this.has_flash5=0; if (navigator.mimeTypes && navigator.mimeTypes["application/x-shockwave-flash"] && navigator.mimeTypes["application/x-shockwave-flash"].enabledPlugin) { var plugin=navigator.mimeTypes["application/x-shockwave-flash"].enabledPlugin; var words=plugin.description.split(" "); for (var i = 0; i < words.length; i++) { var major=parseInt(words[i]); if (!isNaN(major)) { if (major>=5) { this.has_flash5=1; } break; } } }
And here is how to detect Shockwave Player 8.5 or greater: this.has_shockwave85=0; if (navigator.mimeTypes && navigator.mimeTypes["application/x-director"] && navigator.mimeTypes["application/x-director"].enabledPlugin) { var plugin=navigator.mimeTypes["application/x-director"].enabledPlugin; var words=plugin.description.split(" "); for (var i = 0; i < words.length; i++) { if (!isNaN(parseInt(words[i])) && words[i].indexOf(".") > -1) { var versions=words[i].split("."); var major=parseInt(versions[0]); var minor=parseInt(versions[1]); if (major>8 || (major==8 && minor>=5)) { this.has_shockwave85=1; } break; } } }
You are free to use the above code snippets in your site but note that they are provided as-is and without guarantee. We have tested them and found them to work in Netscape 4.7x, Mozilla >= 0.9, Galeon, Konqueror and Opera. Let us know if you find problems with these scripts or have improvements to suggest. |
||||
7.2. Mozilla, Netscape 6+, Galeon, Phoenix, SkipStone |
||||
7.2.1. |
Does CrossOver work with Mozilla? |
|||
CrossOver Linux Standard supports Mozilla 0.9 or greater. However, until recently Mozilla's plugin support had bugs that may prevent you from fully enjoying CrossOver Linux Standard. Thus we warmly recommend using Mozilla 1.2 or greater. |
||||
7.2.2. |
Does CrossOver work with other Mozilla-based browsers such as Netscape 6+, Phoenix, Galeon or SkipStone? |
|||
CrossOver Linux Standard should work with any browser based on a recent version of Mozilla. We recommend a browser that is based on Mozilla 1.2 or greater. Note that old version of CrossOver Linux Standard were incompatible with SkipStone. However this was solved in 1.1.0. |
||||
7.2.3. |
How do I setup CrossOver for Mozilla? |
|||
Starting with the 0.9.9 release, Mozilla supports user-installed plugins,
that is plugins that you install in
However, if you are using Mozilla 0.9.8 or older you will need to use one of the tricks listed below to get Mozilla to use the CrossOver plugins. Note that this is also true of browsers based on such a Mozilla version, in particular Netscape 6.2 or older. Whenever possible, the best solution is to upgrade your browser to a version that supports user installed plugins. But if that is not practical for you, here are a few ways to deal with the situation:
|
||||
7.2.4. |
Forcing Mozilla to refresh its 'about:plugins' page. |
|||
Mozilla keeps a cache of the name, description and MIME types for each plugin. This way it does not have to query the plugins for this information each time it starts. However this can lead to plugin information not getting refreshed which can be very annoying, especially if all you get is a message of the form: Unable to load the Windows plugin library (last attempt Wed Feb 26 13:37:44 2003).
The way to force Mozilla to refresh its cache is to close all Mozilla windows and run the following command, adapting the path as appropriate.
You can find where the Mozilla plugins are installed by looking up the value of the Mozilla plugins dir field in the General tab. After this command the 'about:plugin' page should either reflect the correct / updated plugin information, or at least show a new date in the error message mentioned above. Note also that, in some versions of Mozilla, the Enabled column of the 'about:plugins' page incorrectly displays plugins as enabled for all MIME types. So you may want to use our About Plugins page instead. |
||||
7.3. Konqueror |
||||
7.3.1. |
Does CrossOver work with Konqueror? |
|||
Older revisions of the Konqueror nsplugin module have serious bugs that prevent many plugins from running. We worked with the Konqueror team to resolve these issues. To use CrossOver with Konqueror, you will need KDE and Konqueror 2.2.2 or newer. There are still some issues with Konqueror support though. In particular, the mouse may not work correctly, especially in QuickTime VR scenes and Shockwave games. |
||||
7.3.2. |
How do I setup CrossOver for Konqueror / Konqueror 3? |
|||
All you normally need to do is to activate the plugins for Netscape and then, in OfficeSetup, go to the Konqueror tab and follow the instructions. If Konqueror still does not use the plugins, then open the → menu, and there check the following items:
|
||||
7.4. Opera |
||||
7.4.1. |
Does CrossOver work with Opera? |
|||
Netscape plugin support was introduced in Opera 5.05. CrossOver plugins work in Opera 5.05 and later versions but will not work in older versions. There are a few issues with Opera support though. QuickTime should work fairly well, but some plugins like Shockwave and iPIX are more likely to freeze in Opera than in other browsers. |
||||
7.4.2. |
How do I setup CrossOver for Opera? |
|||
All you need to do is to activate the plugins for Netscape. This is done automatically if you also have Netscape installed. Opera should then detect the plugins automatically the next time it is restarted.
If that is not the case, launch OfficeSetup to activate them. Go to the
'Netscape' tab and activate each dll. If that tab says
that the plugins directory has not been set, go to the
'Configure' tab and set 'Plugin
directories' to either Then start Opera and open 'Multimedia' and select the 'Plug-ins' tab. Then click on ' ' to tell Opera to look for new plugins. → '. There click on 'Tip: With some web sites it can help to let Opera use the extension to detect the real MIME type of embeded data. To do so, go to the Opera preferences dialog, click on Applications and select the 'File types' tab. Then make sure 'Determine action by file extension if MIME type is unreliable' is enabled. |
||||
7.5. Netscape 4.x |
||||
7.5.1. |
All I get on Netscape's about:plugins page (from Help/About) is a blank page. |
|||
JavaScript is probably disabled for your browser. Re-enable it by going to the Netscape settings 'Advanced' category where you can check 'Enable JavaScript'. → ' and choosing the ' |
||||
7.5.2. |
Netscape 4.x keeps using the QuickTime player instead of the QuickTime plugin. Preferences/Applications has no effect. What's wrong? |
|||
Your video/quicktime;
This perfectly valid entry indicates that applications should use the QuickTime Player, and that Netscape will use the plugin instead. The 'x-cxoffice' flag indicates that the MIME type association was created by CrossOver Linux Standard and lets us cleanly remove all such associations when you uninstall CrossOver Linux Standard. You would typically get such an entry if you associate '*.mov' files to the QuickTime Player when installing QuickTime (creates the first two lines) and then start Netscape (which adds the last line). Unfortunately, although Netscape itself added the 'x-mozilla-flags' last, it then fails to take it into account because it is preceded by the 'x-cxoffice' flag. A workaround is to manually edit the mailcap file so that it reads as follows: video/quicktime;
Netscape will then process the entry correctly and the problem will not come back unless you manually edit this specific entry in ' → + → ' (you can safely edit other entries). Another workaround is to remove the 'x-cxoffice' flag altogether but that will cause CrossOver Linux Standard to not remove it when uninstalled. |