Gregor J Jones wrote:
> Well, it was in my queue for reply, but I was busy!
I knew _somebody_ would be into DOS internet. <g>
> Works fine here in a dos machine here. I have ntime
> pointed to ns.bu.edu, which is the university timeserver
> machine (actually an alias to one of the main Unix
> machines). I put it in autoexec.bat after loading the
> packet driver. Sets the machine time every time it boots.
>
>You could try that machine to see if it works.
Hmm, interesting. I get a timed out message everytime on
that one. But it was really helpful to know that the
program works. This is one step closer.
> But, you really want a timeserver nearby, to avoid
> transmission delays.
Good idea. I tried another one again, and lo and behold,
IT WORKED!! This is actually a NIST server in Boulder
Colorado so it is resonably close and probably one of the
best. The delay is an average of 0.13 seconds. Quite good
enough for my purposes. In case anyone is interested, it
is: 132.163.135.130
> My guess is that your ISP probably has at least one
> machine that will respond to ntime, so you might want to
> contact them.
I'll phone them tomorrow and see.
> Now, back to lurking and being busy.
Thanks for your time! <g>
Cheers,
Ole Juul
To unsubscribe from SURVPC send a message to [EMAIL PROTECTED] with
unsubscribe SURVPC in the body of the message.
Also, trim this footer from any quoted replies.
