WM_TIMER and QueryPerformanceCounter trouble with WS650

Hello all of you out there,

 

we have written some software on a WS530, and now we try to run this on a

WS650. The software uses QueryPerformanceCounter() to estimate some

time spans and basic Windows SetTimer(...) to replay image data with 12.5

frames per second, i.e. with a 80ms timer.

 

Has anyone ever seen this failing on a WS650? All timing estimations based

on QueryPerformanceCounter() are too high by nearly 150%, and the

WM_TIMER messages come in too fast as well.

 

I know that lots of people had to patch their Precision workstations for correct

sound playback speed (as I did with mine), but is there also a probability that

windows SetTimer(...) and QueryPerformanceCounter() could run

too fast? If someone had overclocked the WS650 at all the wrong places, how

could we find this out? Does a tool exists that checks different timer mechanisms

for accuracy?

 

Thanks to all who contribute,

 

  Joerg