X-AL

Could it be, that you connected your SB live with a dolby-surround/AC-3 hifi amplifier. Those discribed symptoms sometimes occur, when a game doesn´t fully support surround sound and your amplifier is in surround mode and not in stereo mode. If this is the case, switch your amplifier form surround to stereo.

Could it be, that you connected your SB live with a dolby-surround/AC-3 hifi amplifier. Those discribed symptoms sometimes occur, when a game doesn´t fully support surround sound and your amplifier is in surround mode and not in stereo mode. If this is the case, switch your amplifier form surround to stereo.

I loaded the patch 1.2 (Voodoo.exe&.textures)down, hoped it would run now, BUT the same picture as before. After starting the program, the screen goes black and the program hangs itself up (before the patch the screen went white). Is anybody out there, who got Spec Ops 2 running under W2K? My specs: W2K/P3P600/V5500

My solution was: I installed it, but couln´t run the game (wrong OS message). So I updated to version 1.1 (its the latest, I think)and Commandos worked without any problems.

I sold my (gameport version) MS FF Wheel, and bought the USB version, which runs superb on W2K. I tried to run the gameport wheel with a MS USB-converter and Version 4.0 of the game controller software. NO WAY, doesn´t work!

I have a P3P 600, 256MB, V5500, W2K: I tried to run Force Commander with my Voodoo 5500 under W2K. If it doesn´t crash after the intro, it will certainly crash in the middle of the first mission. It returns w/o comment to the desktop. I also tried the updated version 1.1, no chance, same symptoms! My questions is: Has anybody played Force Commander (with above mentioned system or at least with a Voodoo card!) on W2K?

Hi there, actually I don´t know why you´re using setwin95, when you could use apcompat.exe (you can find that tool on the W2K-CD). Run apcompat.exe, checkmark NT5, and link the autoplay.exe of the Viper-CD to be run. The Viper Racing start´up screen appears, then click play and have fun! (FYI: The same procedure works for Microprose´s EAW, too)

It seems, after reading some online discussions and some games magazines, that the driving wheel problem is wide spread. Even on Win 98 those "two-axis-only" problems are reported. Let´s hope MPS/Hasbro are already working on a patch! I only remember GP2, which never needed a patch! I tried this USB-connector tip. W2K actually finds automatically an USB connection, but fails when looking for the appropiate driver. Perhaps the V4.0 MS controller software could help there, but I actually doubt it. I think, there must be a registry-edit solution, which just combines y&z-axis. (Nothing else does the Version4.0, doesn´t it?).

Hey cuke, I am getting closer to the solution: What gamecontroller software are you using with your MS Wheel on W2K? Could it be you are using Version4.0 instead of 3.02? I can´t install V3.02 on my W2K, but perhaps it is possible to install V4.0 of the Sidewinder gamecontroller software? I read some messages that V4.0 lets you configure your MS (FF) Wheel in a way, that it can be run in GP3. Next question would be: Is there any update available, or is it only bundled with new MS Sidewinder hardware?

Did I already mention, that I try to run GP3 with the MS FF Wheel on W2K?

Thx for the hint, cuke, but NO GO yet! The controller setup (standard/profile) of GP3 only configures one vert./horiz axis per joystick. In my case: If it comes to the calibration point, I have to turn the wheel left/right, that´s no problem. But when it comes to acceleration/braking (push joystick forward then backward) only the gas pedal is functioning. So accel. and braking is on the right pedal. I tried to configure the brake pedal as joystick B vert., but NO GO either! Has anybody got that MS FF WHEEL working with GP3?