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-HELP Mailing List Archives

Return to [ 10 | May | 2003 ]

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


Date: Sat, 10 May 2003 10:19:05 PDT7
From: Peter Skye <pskye@peterskye.com >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: More on setting clock from startup.cmd

Content Type: text/plain

=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================

I posted my startup.cmd file a couple of days ago.

One of the commands in it runs Daytime which gets the "atomic clock"
time over the Internet and accurately sets the hardware clock on the
motherboard.

I've been meaning to add some additional time server sites to Daytime
because the various Internet clocks (technically Network Time Protocol
servers, or NTP servers) sometimes aren't available which means the
motherboard clock doesn't get set.

So yesterday I added some more time server sites to make sure at least
one of them is available when startup.cmd runs. Here is the updated
section of my startup.cmd:

daytime tick.usno.navy.mil
daytime time-b.nist.gov
daytime utcnist.colorado.edu
daytime clock.psu.edu

There are a _lot_ of NTP servers. If you want the best accuracy try to
pick ones that are close to you to minimize lag time (you can check the
routing and delay with tracerte, or just the delay with ping).

Remember that once Daytime sets your clock from startup.cmd your clock
will still "drift" a bit because it has nothing to synchronize to (my
machines have drifts of anywhere between 20 seconds and two minutes over
a 24 hour period). If you run a clock synchronizing program in a window
after your bootup is done your clock will always be correct. I use
OS2NTPD; one thing I like about it is that it uses a lot of different
NTP servers and averages their values which gives a higher accuracy.
Another OS2NTPD benefit is that it continues to keep the motherboard
clock synchronized even when you aren't connected to the Internet by
using a software phase locked loop to figure out the necessary
compensation per unit of time. A third thing I like about OS2NTPD is
that its resolution is 1/60 second which is much better than the others
I've looked at.

- 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-help".

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

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


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

Return to [ 10 | May | 2003 ]



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.