Sledgehamster

The main reason Microsoft is not pushing windows as a gaming os is because much of the techincal support problems it would get would be games incompatibility with certain drivers/hardware combos etc.Regardless of how many people buy this os for games,the majority buy in bulk for corporate use and expect to be able to contact tech support when they need it and not be on hold while someone spends time trying to get thier latest games software to run. The fact is games DO run well on it in most cases but it's a simple cop out clause for both Games companies and Microsoft not to have to deal with games incompatibilities that are inherant with any new os but just stating it was never inteded to be a games platform so all games software is unsupported.

It's the EAX setting that's causing the crash.If you disable hardware acceleration of sound you can play the game.I don't know if this is due to Win2000 or EAX support under it.The game seems to demand EAX 2.0 I'm wondering if it's EAX 1.0 we got with creative's drivers.

I have this and an MS FFB Wheel and have no problem.When I calibrate mine it uses a separate axis for each pedal by default in the controller control panel.I would calibrate the wheel again to be sure and then set each action in the game rather than let it use the defaults ie:specify the pedal for acceleration and braking manually.If you look in the game it will say:Accelerate +y axis Brake -Y axis.When I set it up manually it was Accelerator +y axis Brake +R axis. hope this helps.

Sometimes the Cd protection is incompatible with the OS/CD drive combination.I have a full boxed version of Rogue Spear but it will not work on my system under Win98 without a NoCD hack.Works fine under Win"K though.