I suspended my work on XNTP because of the MPE :SETCLOCK bug documented on my
web page.  Only *after* this bug gets fixed will I consider spending any
personal time to update XNTP/iX to a more modern version.

This bug is on an internal CSY I&I list of prioritized "porting enablers" that
I&I would like to see fixed in order to facilitate the porting of new
applications to the e3000.

I believe that clock synchronization for distributed LANs and WANs is very
important for auditability reasons.  If you share that belief, it wouldn't hurt
to get time synch onto the next Interex System Improvement Ballot and to lobby
people to vote for it in order to raise the visibility.

In the meantime, my old version of XNTP/iX continues to work on all versions of
MPE without any interoperability problems being reported when talking to time
servers running modern versions of XNTP.

If anybody is really desperate and wants to port the latest & greatest XNTP
themselves, I will gladly release my old source code to you to help get you
started.

- Mark B.

"Emerson, Tom # El Monte" wrote:
>
> With all of the discussion on this, I happened to check out that link
> earlier today [found it via google, not that it would be difficult to find
> knowing how many other "gems" are to be found at http://www.bixby.org/mark
> ... ;) ]
>
> I noticed that the last update was just over a year ago [sep 17, 1999] and
> that the source is not being distributed for the port based on version
> 3.5.x, however it was expected that 3.6 would be out "Real Soon Now" and you
> really wanted to have the public source based on 4.0.
>
> What exactly is the status of 3.6/4.0?  Taking the link to
> http://www.eecis.udel.edu/~ntp/ shows the latest release to be 3.5.93, and
> there is a link to the source(s) for 4.0.9x (4.0.99k seems to be the
> absolute latest)  However, the "released" date is still listed as "NA"
> (3.5.93 is dated apr 1998) even though the comments show this to be "the
> latest release".
>
> Inquiring minds want to know! :)