SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.

The Southern California OS/2 User Group
USA

SCOUG-Programming Mailing List Archives

Return to [ 12 | September | 2006 ]

<< Previous Message << >> Next Message >>


Date: Tue, 12 Sep 2006 20:04:38 -0700
From: Peter Skye <pskye@peterskye.com >
Reply-To: scoug-programming@scoug.com
To: scoug-programming@scoug.com
Subject: SCOUG-Programming: Ouch! SysSleep(), NTP, cpu clock

Content Type: text/plain

> Hi Peter,

Well hi there Nathan,

> . . . every day that it would add about 30 seconds to the RTC.
> I found it to be a problem with the motherboard.

Yes, that makes sense since iirc the oscillator is on the motherboard.

> I replaced the motherboard with a newer one and have never had that problem again.
> I think it loses a second now every couple of days with the newer motherboard.

The oscillator frequency is, among other things, temperature sensitive.
I have to synchronize to an accurate external clock such as NTP does.

> I also have a program that I wrote that reads nist.time.gov every hour.

I use OS2NTPD because it constantly updates the RTC using a software
phase-locked loop. Essentially, your RTC is always correct since the
updates are done as soon as the RTC is off by more than 1/2 cycle.

> The OS/2 API has DosSleep(xx) where xx is milliseconds.
> It uses the hi-res timer and not the RTC.

Thanks for this info. I think I remember that the Intel architecture
contains some on-chip counter/timers (3 of them maybe?) and perhaps one
of them is how DosSleep() is implemented. DosSleep() using the hi-res
timer is consistent with my observations about the inconsistencies of
the sleep function and the RTC.

Thanks again,

- Peter

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-programming".

For problems, contact the list owner at
"postmaster@scoug.com".

=====================================================


<< Previous Message << >> Next Message >>

Return to [ 12 | September | 2006 ]



The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA

Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.