This is an unsupported release, for assistance from other users, post to the UseNet newsgroup: comp.protocols.time.ntp

There will eventually be documentation with this release, in the file NTPOG.WRI. It is Windows Write format.

To update to a newer version, run the setup program again.

Building XNTP for Windows NT

Requirements:

• Latest InstallShield SDK for Windows NT 4.0 support
• Perl5 for Win32 from http://www.perl.hip.com or your favorite place
  

First off there are two options for installing.

• Graphical InstallShield SDK based installation process (needs to be updated to reflect the new directory structure)
• Batch file for installing the executables (always works)
  

The software is known to work on Windows NT 3.5, 3.51, and 4.0. However, the latest version of the InstallShield SDK must be installed in order to support a graphical install on Windows NT 4.0.

To compile the sofware you have two options

1. Debugging version

Run blddbg.bat

1. Nondebugging version

Run bldrel.bat

Either of these will compile the entire package, placing the executables into the scripts\wininstall\distrib directory. After which the graphical installer will be built.

Batch Install

scripts\wininstall\distrib\install.bat

NOTE: You will now have to modify the configuration files installed by the install.bat program and also the ntp.conf file (config file) installed in the WinNT home directory.

****YOU MUST ****** modify the directory line in the ntp.conf or ntp.ini

(it will accept either name)... and change the single slash to double slashes

ie. c:\winnt\ntp.conf becomes c:\\winnt\\ntp.conf

Graphical Install

If you currently have XNTP on this machine (any older version that was NOT installed using this GUI) you must STOP NOW, and REMOVE IT from your system before running this install program. There is no way to easily do this automatically.

scripts\wininstall\intel\disk1\setup.exe

This installation program will create what it thinks are sensible defaults for the configuration files for XNTP. If you have a tricky setup, let it finish, then go back and stop the service (try the control panel applet) and edit the configuration files. The files will all be in the Windows System directory (default is %windir%\) and will be named as follows:

ntp.conf - the NTP configuration file.

ntp.drift - the NTP drift file

Other Batch Files

• mkdist.bat - To package binaries for in a ZIP archive.
• mksrc.bat - To package source, excluding files specified in the "excludes" file.
• scripts/wininstall/build.bat - Creates GUI installer, must be modified to reflect InstallShield source directory.
  

There are some important notes concerning the InstallShield SDK You must modify the build.bat file to change the InstallShield source directory, and you must modify the setup.lst to reflect the full pathnames based on where you are building the software.

ANNOUNCE: Enhancements to the Windows NT port of XNTP

This set of changes fixes all known bugs, and it includes several major enhancements.

Many changes have been made both to the build environment as well as the code. There is no longer an ntp.mak file, instead there are two batch files bldrel.bat and blddbg.bat file that will build the entire source.

Perl5 for Win32 is required, but is easily available from the NT Resource Kit or from the Internet at http://www.perl.hip.com.

The multiple interface support was adapted from Larry Kahn's work on the BIND NT port. I have not been able to test it adequately as I only have NT servers with one network interfaces on which to test.

Enhancements:

• Event Logging now works correctly.
• Version numbers now work (requires Perl during build)
• Support for multiple network interface cards (untested)
• NTP.CONF now default, but supports ntp.ini if not found
• Installation procedure automated.
• All paths now allow environment variables such as %windir%

Bug fixes:

• INSTSRV replaced, works correctly
• Cleaned up many warnings
• Corrected use of an uninitialized variable in XNTPD
• Fixed ntpdate -b option
• Fixed ntpdate to accept names as well as IP addresses
• Fixed problem with "longjmp" in xntpdc/ntpdc.c that

See below for more detail:

Note: SIGINT is not supported for any Win32 application including Windows NT and Windows 95. When a CTRL+C interrupt occurs, Win32 operating systems generate a new thread to specifically handle that interrupt. This can cause a single-thread application such as UNIX, to become multithreaded, resulting in unexpected behavior.

Possible enhancements and things left to do:

• Reference clock drivers for NT (at least Local Clock support)
• Control Panel Applet
• InstallShield based installation, like NT BIND has
• Integration with NT Performance Monitor
• SNMP integration
• Fully test multiple interface support
  

Known problems:

• bug in ntptrace - if no Stratum 1 servers are available,

Greg Schueman - schueman@acm.org

------------------------------------------------------------------------

Disclaimer of Warranties. THE SOFTWARE AND ASSOCIATED DOCUMENTATION ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION ANY WARRANTY OF MERCHANTABILITY, FITNESS FOR ANY PARTICULAR PURPOSE, OR NON-INFRINGEMENT. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE SOFTWARE AND DOCUMENTATION IS WITH YOU. NO ONE WARRANTS THAT THE SOFTWARE WILL MEET YOUR REQUIREMENTS OR THAT THE OPERATION OF THE SOFTWARE WILL BE UNINTERRUPTED OR ERROR FREE, OR THAT DEFECTS IN THE SOFTWARE WILL BE CORRECTED.

PRODUCTION, OR DISTRIBUTION OF THE SOFTWARE BE LIABLE TO YOU ON ACCOUNT OF ANY CLAIM FOR ANY SPECIAL EXEMPLARY OR PUNITIVE DAMAGES, INCLUDING ANY LOST PROFITS, LOST SAVINGS, BUSINESS INTERRUPTION, LOSS OF BUSINESS OR PERSONAL INFORMATION OR ANY OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE, THE INABILITY TO USE, QUALITY, OR PERFORMANCE OF THE SOFTWARE AND DOCUMENTATION, EVEN IF SAID AUTHORS, HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

------------------------------------------------------------------------