If anybody knows a handy call to find out the CPU speed (that doesn't
use QueryPerformanceFrequency), it would be nice to use it here.
Otherwise this fix will do.
Actually QueryPerformanceFrequency should be merged with the rest of
the CPU detection, and then you should be able to use it to set the
right value in the registry.