Cedega and wine does not work correctly

hondo · 01-11-2008, 09:47 PM

Hi

Im using Fedora 8 and the "2.6.23.9-85.fc8" kernel. I have a Dell laptop and details about the hardware is below:

Quote:

cpu: Genuine Intel(R) CPU T2400 @ 1.83GHz
cpu_ghz: 1.83
memory: 2017
videocard_manufacturer: Tungsten Graphics, Inc
videocard_type: Mesa DRI Intel(R) 945GM 20061017 x86/MMX/SSE2
videocard_ram: 2048
agp_aperture_size: N/A
videocard_driver_version: 1.3 Mesa 7.0.2
soundcard: HDA Intel at 0xdfebc000 irq 2
soundcard_driver: ALSA Version 1.0.15
machine_bitness: 32
kernel: 2.6.23.9-85.fc8
x_version: Xorg Version 1.3.0
distro: Red Hat Fedora release 8 (Werewolf)
GUI version: 6.0.2

I purchased cedega today and i installed it. The first thing i did was trying to install Counter-Strike condition zero. The installer came up and i pressed "Install counter-strike condition zero". After that i got the following error message "Could not execute the external program msiexec.exe".

After this i tried to install a game i bought directly from steam, since then i wouldnt need any CD/DVD. I got steam installed and when i was going to press "Install item" in steam for the game i was going to install, then steam just started to freeze and it just stopped. I tried serveral times to install this game with no luck. Steam also seemed to be very unstable and the fonts were awful.

Then i tried to install Quake 3 Arena which installed without problems, but when i was going to launch the game it didnt happen anything at all.

I tried to use wine before i got cedega and it did work a whole lot better than cedega has done now. I got counter-strike condition zero installed without problems and steam also went without problems. So, no problems with the installation of the game or steam, but when i was going to launch the game from steam and it said "Preparing to launch condition zero.." and the cancel button got disabled the dialog went away like it normally does, but nothing else happend. The game never started up.

I checked all the tests in cedega for opengl, sound etc. and they all turned out "ok" except one sound test, but i got ALSA i can use, so thats not a problem.

I also checked "glxgears" wit this output:
4312 frames in 5.0 seconds = 862.324 FPS
4449 frames in 5.0 seconds = 889.696 FPS
4479 frames in 5.0 seconds = 895.744 FPS

Does someone know why cedega isnt working almost at all or why counter-strike condition zero didnt start up after i tried to lanuch it from steam?

I have serveral times tried to get games to work in linux, but its always been tricky. I have managed to get counter-strike up and running before, but with much lag and poor graphics. I appericiate all help, thanks

oskar · 01-12-2008, 03:08 AM

Quake 3 has been ported to linux:
http://www.linux-gamers.net/modules/...e=HOWTO+Quake3

For your cedega problems you should contact cedega. You pay for the support.

DragonSlayer48DX · 01-12-2008, 04:32 AM

Quote:

Originally Posted by oskar

For your cedega problems you should contact cedega. You pay for the support.

Exactly. Also, keep in mind that these emulators are a work in progress and always will be for games that are written for Windows, since MS insists on making each new OS incompatible with previous versions. But I'd definitely contact Cedega with your problem.

Cheers

hondo · 01-12-2008, 06:43 AM

Ok, thanks for answering guys. I have now contacted cedega about the problems, hopefully i will get a helpfull mail back.

proc · 01-12-2008, 07:20 AM

Try this type

Code:

glxinfo | grep direct rendering

If this says "Yes" then it's not the problem I was thinking, however if it says no, then MESA is not configured properly to allow 3D acceleration (hence why Quake 3 dies) wine3d doesn't support software anymore without some tweaks to the reg)

WINE however is not an emulator it is a implementation of the win32 API, it does not emulate anything, because if it did, you wouldn't need an X86 to run it properly, hence it needs the native support from the CPU, therefore it's not an emulator.

ALso your graphics card is not really "gamer" material, so it might be slow and lack functions that are needed to play certain games.

DragonSlayer48DX · 01-12-2008, 08:11 AM

Quote:

Originally Posted by proc

WINE however is not an emulator it is a implementation of the win32 API, it does not emulate anything, because if it did, you wouldn't need an X86 to run it properly, hence it needs the native support from the CPU, therefore it's not an emulator.

While this is all true (the proper description is Windows Compatibility Layer for Linux), for the sake of simplicity, it is referred to as a Windows Emulator, even in the repo from which I downloaded Wine.

Cheers

hondo · 01-12-2008, 11:07 AM

Ive checked this and it has 3D acceleration enabled, so it says "YES". I know its not a gamer card, but it worked without problems in windows. I cant just buy a new card either, because its a laptop and its also an onboard graphics card. I probably could send it in to the vendor and have it replaced, but that would probably cost a lot of money.

Quote:

Originally Posted by proc

Try this type

Code:

glxinfo | grep direct rendering

If this says "Yes" then it's not the problem I was thinking, however if it says no, then MESA is not configured properly to allow 3D acceleration (hence why Quake 3 dies) wine3d doesn't support software anymore without some tweaks to the reg)

WINE however is not an emulator it is a implementation of the win32 API, it does not emulate anything, because if it did, you wouldn't need an X86 to run it properly, hence it needs the native support from the CPU, therefore it's not an emulator.

ALso your graphics card is not really "gamer" material, so it might be slow and lack functions that are needed to play certain games.

archtoad6 · 01-13-2008, 02:21 PM

Quote:

Originally Posted by proc

Code:

glxinfo | grep direct rendering

Code:

$ glxinfo | grep direct rendering
grep: rendering: No such file or directory

I think that should have been:

Code:

glxinfo | grep 'direct rendering'

Not to be rude or excessively critical, but I always try to actually run a piece of code before posting it & then I paste it into the "Code:" block -- it avoids typos & other frustrations, as well as embarrassment.