In article <
52e65cd5c0...@btinternet.com>,
spampling <
spam....@btinternet.com> wrote:
> In article <
52e6534...@triffid.co.uk>,
> Dave Symes <
da...@triffid.co.uk> wrote:
> > Having done a test today, the answer to your Q2 Steve is no!
> > I put the clock 10 minutes slow earlier today, and after close on 8
> > hours passing, two cold boots the clock is still 10 minutes slow.
> open a task window and type h. NetTime.
> If the module is loaded it will give you the available commands. Always
> best to check the boot did wot it orta.
Did you see what I wrote earlier today?
"It is obviously seen during Boot as CLI *Help produces the three
commands."
(I shorthanded my note) but I did use * Help NetTime and the three
commands were listed.
Anyway...
> Try the NetTime_Status command first and then try NetTime_Kick then run
> the NetTime_Status command again. Trying that on my RPC (running 4.02)
> the variability of the clock looks like it can't manage much better than
> +/-0.0002 sec. (Oh well, could be worse - it could be Windows and only
> accurate to the nearest few seconds.
I have an Obey file on the Pinboard that does NetTime_Status.
It produces:
*NetTime_Status
Current time: Monday, 29 October 2012 21:43:34.33
Status: Expecting
Last server:
ntp.plus.net
Last protocol: Time/UDP
Poll interval: 30 minutes
Timer latch: 20000
*
*NetTime_Kick produces Nothing, the time remains the same (behind 10
minutes) and NetTime_Status is the same.
I'm going to lay this out for some checking.
1) The module *is* loaded at Boot.
I've used Verma to check, as well as the *Help to make sure the three
commands are listed.
2) I have an Obey file in ...Tasks called TimeSetup containing the
following: With stuff from one of your postings.
|NetTime setup
Set NetTime$Server
1.pool.ntp.org
SetEval NetTime$Loaded 1
RMEnsure NetTime 0.39 X RMLoad System:Modules.Network.NetTime
RMEnsure NetTime 0.39 SetEval NetTime$Loaded 0
NetTime_Kick
If <NetTime$Loaded> Then NetTime_PollInterval 1800
Even double clicking that Obey file does nothing to correct the clock time.
However when, a short while ago I was re-reading the thread, I noticed
Evan Clark in a posting had in his Obey listing an actual ip address.
(I have no idea what it means).
So adding his ip address to my Obey I get... (My <<<<<<<< as a pointer).
|NetTime setup
Set NetTime$Server
1.pool.ntp.org
SetEval NetTime$Loaded 1
RMEnsure NetTime 0.39 X RMLoad System:Modules.Network.NetTime
RMEnsure NetTime 0.39 SetEval NetTime$Loaded 0
SET Inet$NTPServer 130.88.200.4 (<<<<<<<<<<<)
NetTime_Kick
If <NetTime$Loaded> Then NetTime_PollInterval 1800
Which if double clicked changes the clock to the correct time.
I've re-set the clock to 10 minutes slow.
Pause now while I Draft this and re-boot the computer to see.
That seems to be it, upon boot up the clock time is correct.
Perhaps someone could explain for me as I assumed from what I'd read that
all I needed was the first line for the time server... I've not seen any
other mention of an ip address being required?