Why not test the user's system at start to see what it can handle, and use the appropriate method for their particular case? Or, if you have a 'minimum system requirement' for your game, write for that common denominator so that there is no need for 'slow system' fixes. The downside to this is that if a user has a kickbutt system, he will not see any added benefit. But so what? If your minimum system is, say, 1.5Ghz with a 64Mb video card and 512Mb of ram then you can certainly program a 3.58Mhz Super Nintendo-level game for that... :)
If Windows can't provide the required performance, then shame on Windows...
Russell
If Windows can't provide the required performance, then shame on Windows...
Russell