ftp.nice.ch/pub/next/tools/system/pixeltime.README

This is the README for pixeltime.tar.gz [Download] [Browse] [Up]

	Welcome to PixelTime

Instructions for use

PixelTime is a utility which sets your system date and time, via a Hayes-compatible modem, to the National Bueauro of Standards (NBS) atomic clock. As a default PixelTime contacts the Naval Observatory in Washington D.C. at 1200 baud. There is no charge for this call except for normal long-distance rates.  

PixelTime is very easy to use. First, check the preferences to be sure the proper serial port is selected (the default is /dev/cufb). Press the "Call the NBS" button and monitor the progress of PixelTime in the "Record of Progress" window. If you do not recieve a series of UTC time codes such as:

48961 340 221426 UTC
*
48961 340 221427 UTC
*
48961 340 221428 UTC
*
48961 340 221429 UTC
*

then press the "Cancel Call" button and retry. 

If all goes well PixelTime will automatically disconnct you from the NBS and display the NBS time in the "NBS Date" window. If you wish to set your system time to this date then press the "Set Clock to NBS Date" button. The date is set via the setuid to root date program used by the Preferences application. Thus if you are able to change the system date via Preferences then so can PixelTime. 

Why use PixelTime?

-- It is well known that the NeXT clock drifts horribly. 

-- Many applications make use of time consistency, e. g. make and atrun. PixelTime allows the
non-ntp (network time protocol) NeXT to remain time consistent.

-- You don't know the correct time or date.

-- You're compulsive about having the correct time.

Known problems:

1) Only sets the time to the nearest second.

2) Will not allow for change of UTC format if calling another atomic clock.

3) Does not check or record system time drift.

4) It is possible to have PixelTime run automatically at set periods. This feature will be fully documented for the final release.

5) Error checking will be enlarged, particularly for modem responses.

6) Automatic detection and timout of connected call if no information is being received should be added.

7) Ability to use non-Hayes compatible modems (perhaps via tip) should be made possible.

8) Does not check to see if comm path is already in use by another descriptor (i.e. /dev/cufb and /dev/ttyfb). If it succeeds in opening, the "Cancel Call" feature may not work and other problems may result.
 
Comments and suggestions to:

	dnp@math.mit.edu

These are the contents of the former NiCE NeXT User Group NeXTSTEP/OpenStep software archive, currently hosted by Netfuture.ch.