MOO2 works fine for me on the following system:
Win2K
GeForce4 5900FX (128Mb)
SoundBlaster Live! X-Gamer Pro
DirectX v9.0b
I get sound and perfectly fine video. There are two problems:
1. Occasionally, DirectX spazzes out and a lot of screen elements don't render. This usually happens towards the end of the game (after many turns have passed). Solution is to save and restart MOO2, but it happens much more frequently after the first incident.
2. Multiplayer games are extremely slow to process a turn.
The first is a result of DirectX failing to provide backward compatibility... I've had this problem with other DirectX 2.0 games. The second is a problem with the ORION95 executable; it's simply badly written. Perhaps you should try up[censored] your DirectX drivers? The screen transition you are describing is to the intro video, which uses quite a lot of DirectX 2.0 functions. Also, I recommend that, if you are using the ORION95 executable, you start DXDIAG before you start ORION95 and disable DirectDraw.
Personally, I'm having a terrible time getting the ORION2 executable to run... the one written natively for DOS. If I could get it to work, I could get around the DirectX graphics bug and the excrutiatingly slow networking problems (as well as play on Kali). Unfortunately, Win2K does not support DOS natively and NTVDM is bad at pretending. My biggest problem is that MOO2 can't tell (from NTVDM's point of view) that my graphics card supports VESA VBE 1.2. Considering that the card is less than a year old, I should think it does. Anyone found any way to provide VESA VBE support to DOS programs under NTVDM?
