What I meant by my last post is that there ought to be some kind of hardware or software related issue which require a specific version of something to work right.
If it tries to install DirectX 3.0 then I strongly suggest that you try running the game with it instead of your most up to date DirectX and graphic card drivers. And by that, I of course mean in one of those VirtualBox which was mentioned before, not in your actual rig.
A lot of old dependancies got rid of with "modern" version of drivers. It would not surprise me in the least that the new drivers or DirectX versions simply do not act or react as they did back then.
The only other explanation that I could think of would be a "Xcom" effect in which the game call up another .exe program when you enter combat. Very old programs used to do that in DOS... And if it is the case then the program which runs too fast must be an old DOS version or alike this process. I would not know how to solve that problem though, as you would basically have two or even several specific speed requirements as the programs call each other out. It has always been a bi*** in DOSBox to run Xcom because the cycles for the world map doesn't match the cycles of the tactical phase... I've never found a good solution to that short of playing manually with the cycles every time. And since you are stuck with a Windows program, you don't even have that luxury.
|