ConQueso

Try this.

Try my FAQ suggestion. I suggest trying to create fix support for the launch file _and_ the game file.

Check out the Unofficial Pre-release Unreal 2 FAQ section 3.1 question 5. Or, just read the whole FAQ. Interesting stuff if you're a UT fan, or a fan of one of the MANY games which will use the Unreal Engine. (the next 3 Tom Clancy based games will use the new Unreal Engine)

Keep in mind that if UT gets beyond 150fps or so, it can increase the speed (as in velocity, not framerate) of players/bots/projectiles. This poses more of an issue with multiplayer, though. Because of it, I run in D3D to keep things fair. Also, OpenGL takes more of a performance hit (relatively speaking) when Direct Lighting is enabled. I've heard the 436 build of the Unreal engine is where openGL support ends. So don't expect it on U2/UT2003.

I put in an HP dvd200i, and am getting errors while writing to DVD+RW disks using the included software. The software warns not to run other things in the background--which I don't. But I figure closing all but the necessary processes in the taskmanager might help. My system is an Alienware DV2001 with P4 1.4Ghz/512MB RAM/40GB sys drive/2x60GB RAID 0 vid capture drive... What are the only files necessary in the processes tab of the task manager? Should I log in as a power user or even a restricted user?

Unless you have W2K SP3, ACT 2.5 won't install. Download ACT 1.5 and use QFixApp with Win98 layer, then click the Fixes tab and try unchecking EmulateJoystick. Then browse for your game executable and run the game through QFixApp. If your Joystick still doesn't work, try it with EmulateJoystick checked.

Are you launching the game with QFixApp?

Has anyone not had this problem with an XP system trying to join a DF2 game?

If you bought the "Classics" re-released SS2, it should already have the latest version, and the patch would be redundant. If the main menu has a multiplayer submenu, you have the patched version.

As the start of an attempt to get WinXP on my older system (currently Win95) I knew I'd have to lose the old Voodoo3 card. Mobo has no AGP port, so I got a VisionTek GeForce4 MX 420 PCI card and popped it in. (yes, I know about the GF4MX, but hey, name a better PCI video card ) Prior to doing so, I went through and cleaned out all of the 3dfx, voodoo, and glide listings in the registry, and deleted similar files. Anyway, after signing in, an error pops up after a few seconds, and says: "The nwiz.exe file is linked to missing export USER32.DLL: EnumDisplayMonitors." Well, I read that 'EnumDisplayMonitors' is something in 98 and ME, but not 95. So is this a problem not to worry about? If so, how do I stop the darn error? Also, I haven't updated to DX8.0a (currenty DX7). If the error is caused by something I did with the registry, I don't want to upgrade to DX8, because it'll change the registry enough that I couldn't go back to the exported registry file I saved before the registry edit. Anyone have any ideas?

Well, I returned the GF4MX, and got an Asus A7N266-C / Duron 1.0GHz / GeForce2 GTS-V... (problem solved )

ACT 1.5 is for 2000. ACT 2.0 is for XP. ACT 2.5 is for XP or 2000 with SP3. (so where's SP3? ) After you create a 'fix support', you can run the game like any other game--if QFixApp is running also.

I think the latest compatibility fixes need SP2, though I could be wrong.

What sound card are you using? What vesion of DirectX do you have installed? What does DXDIAG report under the sound tab? What level of hardware acceleration are you running under the same tab?

Oops. I was thinking X-wing Vs. TIE fighter.

Ya, what's the deal with that? What a crock. I completely uninstalled ACT version 1.5, only to find that out after trying to install ACT 2.5. Do any XP users have problems installing this? Not likely an April Fool, on the Application Compatability page, the 2.5 update is dated the 4/3. Why would they keep an April fool going past 4/1? And why don't they list "Windows 2000 SP3" under system requirements? What a crock.

Make sure to enable 3D hardware rendering in both single player and multiplayer graphics settings, before entering combat.

Be sure you're running the program with "normal" CPU priority. Changes in this setting can result in delays from the mouse/keyboard.

Go here and download the appropriate application compatibility toolkit under "Essential Links" on the right side. Then use QFixApp to run the game. Try clicking on Win98 mode under the layers tab. If a joystick doesn't work, change the EmulateJoystick setting under the fixes tab.

Does your GPU meet the game's requirements?

Not sure... What version of DirectX are you running? What's your GPU? Is your desktop set in the same resolution/color depth as what your 3D hardware is set to in game?

Is the game made for Win2K? If not, use QFixApp, and try running it in Win98 layer compatibility.

Use QFixApp, click the Win98 layer, then un-check EmulateJoystick in fixes, and run game through QFixApp. This should get the game running fine.

Are CS and RtCW running at normal CPU priority? Do they have the latest patches?

Some games have speed problems when framerates get too low or even too high. Might try increasing your graphics settings to slow framerates down, or even change render type to something slower. Try to get framerates consistantly lower than 90 fps and see if that doesn't solve the problem. (using anti-aliasing, higher resolutions, higher texture res, etc should lower framerates quite well) D3D will typically max out somewhere from 60-85 fps no matter what your settings (well unless the direct draw rate is changed), so you could give that a try.