Your best solution would be to dual bot XP. I wish MS people could just stop supporting all the crap out there instead of having to use their time building fixes for those things (because if a game gets messed because of multithreading, sorry, it's the game fault, like old games that go crazy fast because they didn't control right the CPU speed).
Its the same in XP. I'm asking if they changed something in Win7 to make it different from XP. running in XP would be worse at best, and the same at worst. I'm also leery to duel-boot because I've 8GB of ram in my tower... and I don't feel comfortable running a 32-bit OS with more than 4GB of ram. (running 64-bit XP could only make it worse)
I know its the game's fault, but it is something the OS should be able to fix. I mean it CAN fix it, its just in win 2000, XP, and vista you have to manually fix it every time. And it isn't that the game can't control CPU speed (I'm talking about a windows game, not dos) it is that it does not understand "2 CPUs" so no matter what speed it sets the CPU to be, its getting more than it needs. I'm trying to figure out if Win 7 has a way to fix it on a regular basis.
I guess duel-booting in XP would let me use some of the older non-UAC-ready programs to limit CPU and memory usage, but thats really avoiding the issue. (and is very tough considering the system I'm running. CPU killer, for example, does not turn down my setting enough to compensate for the fact the game is running at twice the speed it should)