<html><body><p>A quick test on windows 7 using sysinternals clockres.exe shows that before running the dpc latency checker, the clock resolution is 15.6ms, and while running the dpc latency checker the clock resolution is 1ms.</p>
<p><br>
</p>
<p>So this suggests that there are likely 'sleep(1)' statements written in the code that in fact sleep for about 15.6ms (or until the next 15.6ms interval passes, for a possible average of about 8ms), rather than only sleeping for 1ms. But they then work correctly when the DPC latency checker is running and has altered the system timer resolution, in the same manner that the Media Player or other multimedia programs do, which explains why some web pages seem to solve similar problems, as Roger pointed out with his Yahoo page example.</p>
<p><br>
</p>
<p>Possibly using 'sleep(0)', which only gives up your slice to other programs could work, or possibly setting the system timer resolution to 1ms is required.</p>
<p><br>
</p>
<p>73,</p>
<p>George K9TRV<br>
<br>
</p>
<div class="reply-new-signature"><br></div>
</body></html>