So, do we conclude that Microsoft's "Embrace, extend, and extinguish"
strategy now applies to Time itself?
On 08/06/15 12:34, Michael Schnell wrote:
Just to let you know....
In search of a problem completely unrelated to fpc and Lazarus I found
out that the reason of the severe timing inaccuracy making this
application being absolutely unusable for the desired task, has been
Microsoft "Active Directory".
After I installed Automachron, syncing the PC with an "official" NTP
Server, the problem vanished. (But the IT department told me that this
PC will see severe issues, e.g. Active Directory preventing user login. )
I seem to remember, that many FPC built Projects either directly use
the PC clock as a source for timing or use EPIKTIMER that in some
incarnations use a CPU based hardware timer and in other incarnation,
use the PC clock as well.
Now I found that with "Active Directory" in my installation the PC
clock erratically fluctuates at rates of at least some 40 seconds per
hour and at least for a total amount of 40 Seconds.
So it is a lot worse than the uninfluenced clock of even a really
cheap PC and unusable for many timing tasks.
-Michael
--
_______________________________________________
Lazarus mailing list
[email protected]
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
--
_______________________________________________
Lazarus mailing list
[email protected]
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
