Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Why does the GetMseconds Library procedure give me different results under different versions of MS-Windows?

0
Posted

Why does the GetMseconds Library procedure give me different results under different versions of MS-Windows?

0

GetMseconds calls a Win32 API function named GetLocalTime (see page 406). This function is accurate to 10ms under Windows NT/2000/XP, but it is only accurate to about 50ms under Windows 98/Me. The GetMseconds function in the Irvine16 library accomplishes its task using calls to INT 21h, and is also accurate to about 50ms.

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123