[ntp:questions] Windows - Seven Days Later [Warning: long post]

David J Taylor david-taylor at blueyonder.co.not-this-bit.nor-this-part.uk
Fri Oct 15 09:02:59 UTC 2004

John DeDourek wrote:


Thanks for your concise explanation - I am familar with drivers and 
interrupts so I can see both the need for interrupt prevention and the 
problem with two lost interrupts.  It's been a long time since I looked, 
but as I recall the CMOS clock doesn't have milliseconds - what a pity!

> This is where Windows loses.  All you can
> do is tell Microsoft, or the people supplying the
> various binary driver disks that someone is locking
> interrupts out for more than a tick and hope they have
> incentive to fix it.  Can't hope to fix that here.

Well, while we may not be able to control how well drivers are written, 
perhaps we could document drivers and software known to cause problems? 
I'll start the list:

- Sun's Java Virtual Machine

Needs to be started with the "-XX:+ForceTimeHighResolution" parameter to 
avoid loosing interrupts.


Perhaps this could be added to the documentation?


More information about the questions mailing list