Installing Cedega Components

Installing the Cedega Engine

In order to use any Windows applications (or games) with Cedega, you will need to install at least one version of the Cedega engine. With an active Internet connection, you can retrieve the latest version of the Cedega engine via the setup wizard, or by selecting Check for Updates from the TransGaming menu within Cedega. Checking for updates will allow you to select which additional components you wish to download. Be sure that your user name and password have been entered correctly into the TransGamer Account dialog; an active subscription is required to download updates. Users who need to use a Proxy server to connect to the Internet may also fill out the Proxy server information on this page. You may also download a manual update package from the downloads section at http://www.transgaming.com/.

Installing Add-Ons (Mozilla Control and Microsoft Core Fonts)

For the optimal experience, Cedega requires two additional packages: the Mozilla Control package and the Microsoft Core Fonts package.

The Mozilla Control allows programs that use embedded HTML to be correctly displayed.

Microsoft Core Fonts are needed for a number of applications to display the correct fonts.

Both packages can be installed by selecting TransGaming -> Check for Updates. If the packages are not installed, Cedega will download and install them for you. Users may force the package to download and update by ensuring that they are checked in the update dialog.

Using Cedega

Installing a Game

To install a game:

• Click the Install button.

• If the game is a supported title press the Detect Game Disc button to install with best known settings or else manually select the title from the drop down list.

• Otherwise

  • In the Game Folder entry box, enter the name of the program you are installing. This can be any description you like.

  • Enter the path to the installation executable in the Path to EXE box, or use the BROWSE button to select the installation executable. The executable is often setup.exe, install.exe or autoplay.exe, and is often located in the root directory of the program CD. This name may vary, however, depending on the game.

• Click Continue.

• Follow through the installation instructions that came with the application you are installing.

Installing a Program Update/Add-on (Patching a game)

A number of programs require updates or add-ons to be installed for optimal use. To install an update or add-on:

• Press the Install Button

• Select the Game Folder of the original title from the drop down list.

• Enter the path to the update executable in the Path to EXE box, or use the BROWSE button to select the update executable.

• You may also manually select a GDDB file to use with this installation.

• Click Continue

Advanced Installation Options

The following advanced installation options are available by selecting the Advanced tab in the installation dialog:

Run Directory

• Sets the current working directory to the game executable directory. This option is enabled by default.

Big EXE

• Allows the installer to allocate more memory for larger-sized executables. This option has not been necessary since Cedega 4.2, but was left in for backwards compatibility.

CD-Rom Eject Monitoring

• Enables or disables CD/DVD Eject Monitoring for the installation. See the Multi-Disc Installer section for more details.

Installation Settings

• Opens the edit settings dialog. This button will only edit the installation settings and have no effect on game play settings.

Multi-Disc Installers

Many games are only made available on multiple discs. When a game installer requests the next disc, you can unmount the disc drive using the (Un)mount button in Cedega. In many cases this will also eject the disc.

• Allow the CD/DVD device a few seconds to eject before pressing the physical eject button on your CD/DVD drive. Manually ejecting the disc early may cause a hang in the installer.

If you have a Linux distribution with an automount feature, you should just press the physical eject button on your CD/DVD drive instead. Cedega interfaces transparently with most automount configurations, effectively making the (Un)mount button in Cedega obsolete.

• Some automount configurations may require you to press the eject button twice to physically eject the disc.

This special eject functionality is only available in conjunction with versions of Cedega 4.0 and later; if you attempt to use it with earlier versions, it will use regular Linux methods to unmount the disk, and may fail due to files being kept open by the installer. Cedega version 4.0.1 and later have this feature turned off by default. Automount integration has been available for various configurations of automount since Cedega 5.0.

Since there are known performance issues associated with leaving this option on during game play it is recommended to only use this option during game installation (the default). Issues may also arise if you have certain types of media, such as compact flash devices, mounted when using this feature, so it is recommended that you unmount such devices before using the eject monitoring functionality. To change the enable/disable behavior, go to the "Tools -> CD/DVD Eject Monitoring" menu, and select one of the options under "CD/DVD Eject Monitoring".

Always on

• CD/DVD eject monitoring is always used during installation and game play.

Always off

• CD/DVD eject monitoring is never used.

Default

• CD/DVD eject monitoring is only enabled during installation.

This is a system-wide setting, and its status is applicable to all games in Cedega.\

Starting a Game

To start a program using Cedega, select the Game Folder you installed the application into from the left pane. Double click the shortcut from the right pane, or select it and click the Play button.

Uninstalling a Game

Select the Game Folder from the left pane of the main screen and select Tools -> Game Folders -> Delete, or right click on the game title and select delete.

Note: This will remove all configuration options and saved games associated with this title!

You may wish to manually back up save files and game configuration files before uninstalling.

Sharing Games Between Users

IMPORTANT: Please read the warning below, as well as rereading the Cedega EULA before proceeding!

To make your games directory usable by more than one user, we recommend using the following steps. (If you haven't already run Cedega for the first time, please do so and then come back.)

Following the instructions included with your Linux distribution, create a user group that will have access to the shared Cedega install. In our example, we'll use gamefriends. If your distribution's group management utility doesn't automatically create a home directory, then you will have to do so manually: (You'll need to be root for these instructions.)

#mkdir /home/gamefriends

Move your .cedega and .cedegarc files from your home directory to their new, shared location:

#mv .cedega /home/gamefriends

#mv .cedegarc /home/gamefriends

Then set their permissions so that the other users on your system have access to it:

#chgrp -R gamefriends /home/gamefriends/

#chmod -R g+xrw /home/gamefriends/

The last step is to symbolically link the files back to each user's home directory. Execute the following commands as each user who has access like so:

>ln -s /home/gamefriends/.cedega ~/.cedega

>ln -s /home/gamefriends/.cedegarc ~/.cedegarc

WARNING: Please make sure that you are EXTREMELY CAREFUL about restricting permissions with this setup to ONLY those users you trust. The .cedegarc file you will be sharing CONTAINS YOUR PASSWORD, and by exposing it in this manner, you are allowing others the capability to use your password. While your password is not stored in plaintext in the .cedegarc file, this is still a SECURITY RISK! TransGaming assumes NO LIABILITY in the event that your account is tampered with or stolen in this manner, and if someone leaks your account details on the Internet, YOU WILL BE HELD RESPONSIBLE!

Command Line Options

With Cedega, users can run installed software from the command line without needing to launch the graphical interface. This functionality can be used to create desktop and menu icons to launch your favorite games.

Syntax: cedega [-version] [-winver <Version>] [-debugmsg <Channels>] [-use-pthreads <Enable/Disable/Yes/No>] [-use-dos-cwd <Path>] [-monitor-cdrom-eject] [-no-detect-disc] [-gddb <GDDBprofile>] {[-install <Game Folder> <installerapp> [cmdline]] | [-run <Game Folder> <Shortcut> [cmdline]] | <executable> [cmdline]}

-version - Display the current Cedega GUI version and the default engine version then exits.

-winver - Run using specified winver: win95, win98, nt40, win351, winme, win2k, winxp.

-debugmsg - Create a debug trace using specified debug channels.

-use-pthreads - Enable/Disable pthreads.

-use-dos-cwd - Set the working directory to <Path>.

-monitor-cdrom-eject - Enable CD/DVD Eject Monitoring.

-no-detect-disc - Do not attempt to detect game disc or use optimal settings (used with -install).

-gddb - Use the settings specified in the <GDDBprofile>.gddb file in the default location.

-install - Install the specified application into <Game Folder>.

-run - Run specified <Shortcut> from the specified <Game Folder>.

--help - Show this help menu.

Settings - Global, GDDB and Overrides

With the introduction of Cedega 5.2 game settings have moved to a layered method. Settings come from a combination of three layers the Global Settings, a GDDB file and any per-shortcut settings that may be applied.

Global Settings

Cedega options can be modified using Edit -> Global Settings. Settings are applied to all games played unless overridden by the GDDB or using the per shortcut settings.

Game Disc Database (GDDB)

Supported games have a games disc database entry that include the best known settings for both installation and play. The GDDB settings are applied on top of the global settings and take precedence. GDDB settings can be disabled by selecting None in the GDDB field in the installation dialog or the shortcut properties dialog.

Per Shortcut Settings

Per shortcut settings can be modified by right clicking and select "Edit Settings for this Shortcut" or through the shortcut properties dialog (Edit Settings). The shortcut settings are applied on top of both the GDDB and global settings and override all other settings.

Configuration Options

General Tab

Winver

• Specifies which version of Windows to simulate. This will change the windows version reported to applications, as well as triggering different behavior in some APIs.

Cedega Version

• Forces all programs using this profile to be run with the specified Cedega version. Setting this to default will allow you to control which version to use from the main dialog's TransGaming menu, without having to tweak each profile manually.

Use XvidMode

• Enables video mode switching via the XVidMode extension. You should only have one of the

  XVidMode and XRandR options enabled.

Use XrandR

• Enables video mode switching via the XRandR extension. You should only have one of the XVidMode and XRandR options enabled.

DXGrab

• Restricts the mouse from leaving the boundaries of a DirectX window . This is most useful when running in Desktop mode.

Managed

• Allows any window the program creates to be handled (managed) normally by your window manager.

Mozilla Control

• Enable the Mozilla control to stand in as the IE control, if you have it installed.

Scheduler

• Defines the behavior of the Cedega scheduler. The scheduler allows Cedega to set the priority for threads itself rather than relying on the kernel scheduler to do so.

  • Default - Allows Cedega to control the behavior of the scheduler. Cedega will automatically use the scheduler with 2.6 and above kernels and will not use the scheduler with any kernels before 2.6. When the scheduler is enabled, Accelerated Interprocess Communication must be enabled and Decrease Wineserver Priority must be disabled. This option takes care of this for you.

  • Yes - Forces the scheduler to be on. When the scheduler is enabled, Accelerated Interprocess Communication must be enabled and Decrease Wineserver Priority must be disabled.

  • No - Disables the scheduler for this configuration profile. Users may manually select the values for Accelerated Interprocess Communication and Decrease Wineserver Priority when the scheduler is disabled.

Decrease WineServer Priority

• Decrease the priority of the WineServer Linux process; this option may increase performance for some games.

Accelerated Interprocess Communication

• Enables/Disables Accelerated Interprocess Communication using the Shared Memory WineServer.

Use Pthreads

• Whether or not to use POSIX Threads (Pthreads). Auto lets Cedega auto-detect what's best for your system. Default uses the value found in the /home/USERNAME/.cedegarc file.

Desktop

• Desktop mode creates a virtual desktop of the size specified, within which the game executes. If set to No the game will run in fullscreen mode.

Path to Web browser

• Web Browser to be used by games that start up web browsers.

FreeType

• Use new improved fonts (requires the FreeType, XRender, and FontConfig libraries).

Activate TransGaming HUD

• Enable the display of the TransGaming Heads Up Display (HUD). This HUD includes the spinning Cedega logo and the current framerate of the application.

  Show Memory Usage

  • Enable memory statistics on the TransGaming HUD. The TransGaming HUD must be activated for this to be displayed.

Audio Tab

ALSA

• Selects the ALSA sound system for use by Cedega.

CTL Device (ALSA)

• The Linux path to the CTL Device (setting for ctl0) that is used to control volume.

PCM Device (ALSA)

• The Linux path to the PCM device (setting for pcm0) that is used to generate sound.

UseMMap (ALSA)

• Use the mmap() command for sound playback when using the ALSA drivers to play sound. Can improve performance, but is not available with all sound cards and plugins.

OSS

• Selects the OSS sound system for use by Cedega.

DSP Device (OSS)

• The path to the Linux device for the DSP on the sound card you wish to use with Cedega.

Mixer Device (OSS)

• The path to the Linux device for the Mixer on the sound card you wish to use with Cedega.

Full Duplex (OSS)

• Allows sound to be recorded and played back at the same time. Not available on all sound cards. Some sound cards may require UseMMap to be disabled when enabling Full Duplex support.

UseMMap (OSS)

• Use the mmap() command for sound playback when using the OSS drivers to play sound. Can improve performance, but is not available with all sound cards.

Graphics Tab

Video RAM on Video Card

• How much Video RAM your video card has. If set as Default, Cedega will use the value that is automatically detected and listed on the System/Hardware Information page.

AGP Vertex Data

• How much data Cedega should attempt to store in faster AGP memory. This is only applicable when the NV_VAR option is enabled and in use (see below). This value should be approximately half of your AGP Aperture Size or half of the listing for AGP Memory Available in the System/Hardware Information page. Setting this value to Default will allow Cedega to automatically detect and set your AGP Vertex Data.

Enable Pixel Shaders

• Pixel shaders are used to compute complex per-pixel lighting and coloring. In some games the use of pixel shaders is optional; and disabling it can result in faster game play, albeit at the expense of graphics quality. Other games may not function at all without pixel shader support. This functionality is provided via the ARB_fragment_program extension, so not every video card that has the ability to render pixel shaders under Windows will be able to process pixel shaders under Linux. This is important to note when you are purchasing a game, since a game which lists a Geforce 3/4 or Radeon 8500 as its minimum video card may in fact require pixel shaders, which aren't available in Cedega with anything less than a Geforce FX series card.

• Enabled (checked), Cedega tells the applications that pixel shader support is available.

• Disabled (not checked), some applications may rely on their own fallbacks.

Pixel Shaders Version

• This option specifies which level of Pixel Shader support Cedega reports to the application. The choices are 1.1, 1.2, 1.3 or 1.4. The current default value for Pixel Shaders is 1.3. While 1.4 is now available, it may cause drastic performance reductions in some games on certain types of graphics hardware. You may still wish to enable this feature, however, as other games may require 1.4.

• Due to driver quality, ATI users may have varying degrees of success with pixel shaders. In particular, pixel shaders 1.4 will probably not work on 9x00 and Xx00 series cards due to limitations on the number of instructions available through the ARB_fragment_program extension on this hardware.

Enable Vertex Shaders

• Vertex shaders are used to add complex-to-compute graphical routines that, until recently, have mostly been optional. While the Cedega implementation of vertex shaders is hardware accelerated when the underlying OpenGL driver supports it, it may be emulated in software for some cards. It is impossible for Cedega to determine whether it is software or hardware vertex shaders that are available; the ARB_vertex_program extension doesn't make this information available.

• Enabled (checked), Cedega tells applications that hardware vertex shader support is available.

• Disabled (not checked), some applications may rely on their own optimized software fall backs.

NV_VAR Extension

• Use the NVIDIA Vertex Array Range extension for Accelerated Vertex Buffers. This extension is only available on NVIDIA graphics cards.

• You should leave this option enabled unless directed to change it by a TransGaming support member.

ARB_VBO Extension

• Use the OpenGL ARB Vertex Buffer Object extension for Accelerated Vertex Buffers. The NV_VAR option, if enabled and usable, has precedence.

• You should leave this option enabled unless directed to change it by a TransGaming support member.

Dynamic VBO

• This option enables an alternate approach to handling certain types of vertex data when using VBO. This has the potential to speed up certain graphics operations, but this depends upon the video drivers and may result in poor performance and/or graphical corruption. This option only takes effect if ARB_VBO is enabled and in use.

• This option is experimental, and should be left disabled unless you find it helps a specific game.


Index VBO

• This option enables index buffer information to be stored in faster AGP memory to improve data transfers to the graphics card. This option only takes effect if ARB_VBO is enabled and in use. However various graphics drivers still do not have fully functional support for these operations, and corrupt geometry and/or crashes may result.

• This option is experimental, and should be left disabled unless you find it helps a specific game.


Fixed GL Extension Buffer

• Some OpenGL applications query for a list of supported extensions. As drivers gain support for more and more features, this string gets longer and can actually cause the application to crash if it was improperly coded. This option allows Cedega to report a truncated list of OpenGL extensions to the application. The extension string reported is based off of the reported extensions on a GeForce4 4400 with the NV 61.11 drivers. If you find your application requires an extension that is not reported as enabled, use the Manual GL Extensions option to tweak the reported extensions.

Manual GL Extensions

• This option is only for Advanced Users. List of additions (+) or deletions (-) to the list of extensions reported when FixedGLExtensionBuffer is enabled. Note that extensions cannot be enabled if they are not supported by your video card/drivers. Use the glxinfo command to determine which extensions are supported on your combination of video card and drivers.

Fixed Program

• Use the fixed function over vertex shader pipeline. This allows Cedega to keep data in faster AGP memory (where it may otherwise have been unable to do so), provided that vertex programs are implemented in hardware. For most games, this provides a nice speed boost to fixed function rendering. In some instances however, video cards may experience incompatibilities between the vertex shader pipeline and other graphics features in use by the game, and be bumped to a software path. If you experience extremely slow performance in a title, try disabling this option.

• Fixed Programs are enabled by default on Geforce FX and later cards, and disabled for earlier cards.

• Fixed Programs do not currently work on ATI cards due to driver issues.

• GeForce, GeForce2, GeForce4 MX, and GeForce4 Go series cards: While the drivers for these cards do support the ARB_vertex_program extension, these cards do not have hardware support for vertex programs and as such they are emulated in software by the driver, resulting in very poor performance. It is STRONGLY recommended that Fixed Programs be disabled for these cards.

• GeForce3 and GeForce4 series cards: These cards do support hardware vertex programs, but high resource requirements for some games may prevent Fixed Programs from working correctly. However, many games are fully functional and gain a significant performance boost by using Fixed Programs. It is recommended that you enable Fixed Programs on a game-by-game basis. If you experience missing or corrupt geometry in a specific title, you should disable Fixed Programs for that game.

• GeForce FX and later cards: Fixed Programs may safely be enabled on these cards.

Fragment Offset

• Apply fragment translation in vertex program. This option is only for Advanced Users. When a 1.4 pixel shader is in use, depending on the type of translation selected, it may instead be done in the fragment program. 'Tex' applies an offset to the texture coordinates, while 'Pos' applies an offset to the output position coordinates. 'Auto' will select the appropriate type depending on the game title and your video card.

Non Power of Two Textures

• Provide non power of two texture support using rectangle textures. Older hardware, such as the Geforce 2/3/4 cards, may be unable to support this feature at the same time as vertex shaders due to device limitations.

Clip Space Fix

• The Clip Space Fix option allows Cedega to better emulate the differences in the graphical depth component (z) between D3D and OpenGL.

• As of Cedega 4.0, this option can safely be enabled at all times. However, in older versions, it should be disabled when using applications which make use of vertex shaders as this may result in incorrect graphics.

Anisotropic Filtering

• A technique which improves the look of textures when viewed from an angle. While there may be visual improvements in some cases, this option may cause a considerable drop in frame rate (up to 50%).

Frame Buffer Objects

• Enables/Disables the use of framebuffer objects (FBO). FBO is a relatively new method of implementing render-to-texture functionality in OpenGL that has the potential for significant speed improvements.

• This feature is experimental and should only be enabled for use with Battlefield 2.

Joystick Tab

You can use this tab to add, remove, and edit joysticks.

In order for your joystick(s) to work properly with Cedega you will need to configure it. You need to tell Cedega about the axes that are supported by your joystick and what they are used for. The joystick name and axis functions can be determined with jstest.

The available axis types are:

"none", "X", "Y", "Z", "RX", "RY", "RZ", "slider", "hat", "POV", and "ball". The "hat" and "POV" types are synonymous. Hats use two axes.

To configure your joystick(s), click on "Joysticks" from the "Configure" Menu. From this popup you can add, edit, and delete configured joysticks. Click on the Add button, and you will be presented with a dialog box where you can enter the name of the joystick (exactly as given by jstest) and configure the functionality of your joystick's axes.

The axes are listed in a comma separated list, such as:

X,Y,slider,Z,RZ,hat,none (which is the configuration for a "Logitech Inc. WingMan RumblePad")

Troubleshooting Common Problems

Configuring your Computer for Cedega

The easiest way to determine if your system is setup correctly is to choose the "System Tests" tab. Once you click this tab, you will be presented with 4 tests. These tests are: "Test CD/DVD drive," "Test for hardware 3D acceleration," "Test sound support," and "Test If POSIX Threads (pthreads) Are Required." These will test your CD-ROM/DVD-ROM setup, your 3D graphics-card setup, your sound setup, and whether we detect you need pthreads or not on your distribution (and if so, if your distribution's pthread implementation is modern enough to support Cedega) - all the essential components required for Cedega to run games.

If you are unsure if your computer is setup correctly, it is suggested that you run all of these tests and verify that each of them passes. If, for some reason, one or more of these tests fail, please refer to and follow the instructions below.

Make sure that your video card has working 3D acceleration

Some on-board and lower end video cards may fail the 3D acceleration test even when they are working correctly. Cedega's video card test threshold is set too high for certain cards. To manually test your video card please follow the steps below.

To test your graphics card for OpenGL support execute the following command:

$ glxinfo | grep "direct rendering"

output will return "direct rendering:"

If this is 'Yes' or 'Enabled' then OpenGL is likely set up correctly. If it is listed as 'No' or 'Disabled' then double check your 3D setup.

You may also want to try a performance test. Type the following to run a simple benchmark included on most popular Linux distributions:

$ glxgears

The glxgears program will output an FPS (Frames Per Second) rating to the command line. If 3D acceleration is correctly enabled for your video card then the reported FPS should be well over 500 FPS, at the default window size. If the output shows less than 500 FPS then you should double check your 3D setup.

If you are on a 64-bit machine, and your machine succeeds in the previous two tests but failed the 3D acceleration test in Cedega, then you may also wish to check that you have 32-bit OpenGL libraries installed. See below for more details.

In some cases it is possible to have multiple OpenGL libraries installed on your system. If you are having problems with Cedega, you may wish to check whether this is the case for your system. You can do so by executing:

$ locate libGL.

This will display a list of all of the OpenGL libraries you have on your system. In particular, you should be wary of having libGL in both /usr/lib and /usr/X11R6/lib. Sometimes the software-only Mesa OpenGL libraries are installed in /usr/X11R6/lib, and hardware accelerated drivers are installed elsewhere. We do not recommend removing the Mesa libraries from /usr/X11R6/lib unless you are seeing slow rendering in games running under Cedega.

If you are running a 64-bit distribution of Linux, and only see entries in a directory like /usr/lib64 and not /usr/lib, then this is a good indicator that you are probably missing 32-bit versions of the OpenGL libraries. If you are using a NVIDIA video card, then installing the 32-bit libraries means reinstalling your drivers and selecting "Yes" when prompted as to whether or not you wish to install 32-bit libraries.

If you are using a NVIDIA video card, please make sure that the latest drivers from http://www.NVIDIA.com have been installed on your system, and that OpenGL is working properly. Some distributions custom build versions of these drivers for use with only their distribution. These builds can sometimes cause conflicts, and users may wish to use the drivers available directly from NVIDIA.

Users with ATI Radeon 8500 or above video cards should use the proprietary ATI drivers available from www.ati.com. Some distributions build versions of these drivers for use with that specific distribution. These builds can sometimes cause conflicts and users may wish to use the drivers available directly from ATI.

Other video cards may only be able to use open source drivers such as MESA/DRI to enable 3D acceleration. A number of conflicts between Cedega and these drivers remain, so users should expect increased setup times and non-working games when using these cards. TransGaming does not recommend using Cedega with these video cards.

Check your CD/DVD devices and mount points for permissions

Many Windows games use copy protection systems that require Cedega to have 'read' access to your CD/DVD device, as well as 'read' and 'execute' access to your CD/DVD mount point. Check your CD/DVD devices and mount points to ensure that Cedega has appropriate permissions. Some forms of copy protection require the ability to see hidden files on the disc. To make these files available to Cedega, you will also need to add the "unhide" option to the CD/DVD fstab list. (In particular, SuSE 9.3 users should note that the unhide option is incompatible with the subfs auto mounting solution provided with this distribution. SuSE 10 and later do not share this drawback.) You will need root permissions to make changes to your /etc/fstab.

To ensure that the correct permissions are available:

Check the /etc/fstab file for the line that represents your CD/DVD drive. That line should indicate the device such as /dev/hdc or /dev/scd0.

For example:

/dev/cdroms/cdrom0 /mnt/cdrom iso9660 user,unhide,noauto,ro 0 0

In the above example the device is /dev/cdroms/cdrom0

Perform ls -la /dev/DEVICE on the CD/DVD device. Check to see if all users have rx permissions. The example below does not have the correct permissions:

brw------- 1 wulfram disk 22, 0 Aug 26 06:20 /dev/hdc

Your permissions should look like:

brwxr-xr-x 1 wulfram disk 22, 0 Aug 26 06:20 /dev/hdc

(you may also have W permissions, but they are not necessary for Cedega to run).

To change the permissions on your device and mount points, execute the following commands as 'root':

# chmod a+xr [device]

# chmod a+rx [mount point]

In some cases the device may be a symbolic link to another device (indicated by -> /cdroms/cdrom0 for example) If this is a symbolic link, you will also need to check the permissions on the linked device.

For example:

lr-xr-xr-x 1 root root 13 Aug 21 14:45 /dev/cdrom -> cdroms/cdrom0

In this case, you would check the permissions of /dev/cdroms/cdrom0 as well.

Check your XF86Config-4 or Xorg.conf file

Games often attempt to change your screen resolution to fit their needs. Make sure that the 'Screen' section of your X config file has a number of resolutions. The most common resolutions are: 1600x1200, 1280x1024, 1024x768, 800x600, 640x480. If the game is not running at full screen, check the game settings to see what resolution it is attempting to use, and make sure you have that resolution listed in the configuration file.

Note: You may experience improved performance with some games when running the X server at 16-bit color depth, however other games may require 24-bit color depth for correctness. Games which require pixel shaders, in particular, will typically require 24-bit color depth.

Disable Sound Servers

Many Linux desktop systems such as KDE and Gnome run sound servers such as 'ARTS', 'esd', or 'JACK'. These sound servers can cause sound problems within Cedega by reserving exclusive access to the sound device. If you are having sound problems, make sure to disable any sound servers or other applications that may be using sound, such as 'xmms'.

Check free disk space limitations

Some systems may be set up with restrictive disk space quotas on the /home directory. These limitations can cause Cedega to incorrectly report available free space. You may experience problems installing games if the available space is reported incorrectly, or if there is not enough space available on your system. If you experience any error messages reporting that there is not enough hard drive space to install a game, then disable quotas, or symbolically link to a device with more free disk space available.

Pthreads

By default, Cedega should be able to detect automatically whether your Linux distribution requires you to use pthreads or not. If no installer or game seems to be working for you, it is possible this detection scheme isn't working on your distribution.

You can try forcing pthreads to be on or off, thereby not relying on the autodetection scheme. Edit ~/.cedegarc, and add (or modify) a pthreads_forced line under the [transgaming] header, like this:

To force pthreads usage on:

pthreads_forced=on

To force pthreads usage off:

pthreads_forced=off

You can also override the pthreads settings (to make it Automatically detected, forced on, or forced off) on a game by game basis.

Exec (error = 21)

Some distributions' versions of mount now run with the "noexec" option unless otherwise specified. Running games from a partition mounted with noexec can cause an error = 21 message.

To fix this issue, edit /etc/fstab and modify the partition line by changing 'noexec' to 'exec' in the mount options.

For example, change:

/dev/hda1 / ext3 errors=remount-ro,no-exec,defaults 0 1

to:

/dev/hda1 / ext3 errors=remount-ro,exec,defaults 0 1

If neither "exec" nor "no-exec" appears in the line it is recommended that you add "exec" to ensure that the partition can be used by Cedega.

To remount the / partition run:

$ mount -o remount /

Scheduler

With the introduction of the 2.6 Linux kernel, drastic changes have been made in the of process scheduling. Some distributions have taken advantage of this and optimized their schedulers to run some applications better than others. Unfortunately, this means that some 2.6-based kernels may starve more 'aggressive' applications like Cedega at inopportune times, leading to stuttering movies, jerky framerate and/or random freezes.

Starting with Cedega 5.0, we include a user-mode scheduler to alleviate most of these problems by performing rescheduling of game processes manually. For most games, this will give users the performance they have come to expect with previous Linux kernels. Unfortunately, some games are not yet fully supported by this method, if you experience unusual behavior in any application, be sure to check the release notes to see if the game has known conflicts with the Cedega scheduler. You can also disable the internal scheduler in the configuration profile for the title in questions.

Of note to users with multiprocessor or multicore systems, the Cedega scheduler currently does not support scheduling threads across multiple processors. If you wish Cedega to make full use of both processors, you will need to disable the scheduler.

Generating a Debug Trace Log for TransGaming

On occasion there will be a need to generate debugging information by running a game with Cedega. To do this, select the game you need to generate logs from, and select File -> Debug. You will now have a popup window titled "Debug Program".

The "Debug Channels to Use" text entry box should be filled in with the debug channels as requested by the TransGaming support staff. Please enter them exactly, as not all the combinations we may request are presented in the control's drop-down dialog.

You can then enter a filename to save the debug trace log to, and choose to also have the debug information be displayed on the console. (We recommend that you do not display the information on the console while you are running a debug trace, as it will slow down the game even more.)

This feature is for helping TransGaming staff diagnose problems with your game, and as such is not something you will need to use unless directed to by a TransGaming support member.

Getting Additional Help

PHPbb Forums

Visit www.transgaming.org/forums and log in using your TransGamer account information. You can post in any of the forums to communicate with other TransGamers on a variety of topics. TransGaming staff members are not notified and may not respond to these posts.

#cedega IRC Channel

TransGamers can join #cedega on IRC at irc.freenode.net or an affiliate for unofficial interactive support both from other TransGamers and TransGaming Technologies staff members. Be sure to be as descriptive as possible when describing any problems you may be having.

Support Forums

Go to the Support Forums and post a message in as much detail as possible for a TransGaming support staff member to answer. Be sure to include as much information about the problem and your computer as you can. Information from the System/Hardware information page inside Cedega is often useful and should be included.

Email

Send an email to support@transgaming.com fully describing your problem in as much detail as possible, and one of our support staff members will respond to you in a timely fashion. Be sure to include as much information about the problem and your computer as you can. Information from the System/Hardware information page inside Cedega is often useful.