Time preferences

Is there any way I can set time preferences to keep current time every time I reboot my machine. I have set the remote server and can get the time but whenever I reboot it is all lost! Is there any way or a program available to be able to connect and get time remotely every time I boot up?

Seems a little disappointing that my Amiga cannot show correct time until I manually either set the time from my watch or remotely get it every time my system boots, find it really annoying!

I have a Network-Startup script which is executed from Startup-Sequence with "C:Date SERVER pool.ntp.org" command to sync time with NTP when computer boots up.

You can find more information on how I have it set up here.

And if you have saved your Time Prefs with the working server details etc., you can also use the line "Date SERVER PREFS", which will make Date use the server saved in the prefs file for fetching the time. That way you don't have to hardcode the server name in your Network-Startup script.

Best regards,

Niels

@sicky
If I set-up an S:Network-Startup script for you (I think I did?), then just add the following line at the end of it:

Date SERVER time.windows.com

(Yeah, Microsoft is finally useful for something... and not getting paid for it!)

Quote:

Wouldn't be my first choice. Pick something more local, like uk.pool.ntp.org, ntp2a.mcc.ac.uk, ntp.your-isp.dom or something from this list.

@nbache

"Date SERVER PREFS" works awesome. Thanks for this tip.

@ChrisH
Quote:

No I don't have a Network-Startup in S:

Mayebe it's something we can do at next ANT meetingf

@nbache

Quote:

Okay, I need an idiots guide to exactly what to do!

I am using pool.ntp.org as my time server

Do I create a Network-Startup script or can I add the line to S:Userstartup or S:Startup and exactly what is the line I have to write?

@sicky

Yes, just add the line "Date SERVER PREFS" to your User-Startup,. With out the quotes. Here is what mine looks like.

;BEGIN Time Correction
Date SERVER PREFS
;END Time Correction

But only do this if you do not have "Run" in front of your AddNetInterface line in your Startup-Sequence. You have to be sure that the network is actually up before you get to the Date line, otherwise your system startup will be interrupted by an error.

This sort of timing problem is what the Network-Startup scheme will eliminate for you.

Best regards,

Niels

@Niels

It seems you are a medium reading in the mind of the Date shell command utility because I can't see in any documentation associated with it a mention of this 'PREFS' keyword
I think you have a documentation bug.

Heheh, I didn't know that either. Niels comes from another galaxy
Oh wait, there might be another explanation. Alex read the timesync autodoc...

@nbache


Quote:

This is from my startup sequence

;Run >NIL: C:AddNetInterface QUIET DEVS:NetInterfaces/~(#?.info)
Run >Nil: C:Execute S:AddNetInterface

So can I add the line stated to fix my problem?

@sicky
OK, looks like I used a different name for the network script. Please edit S:AddNetInterface, and add the Date line at the botttom.

@thread,

Another place for accurate time: "time.nist.gov"

Chris

To save problem with servers downtime I can only advise you to use one of the official pool aliases.
See http://support.ntp.org/bin/view/Servers/NTPPoolServers

Some examples:
* for the USA, use us.pool.ntp.org it's composed by more than 590 servers,
* for Europe, use europe.pool.ntp.org it's composed by more than 1500 servers,
* if you want to be more specific you can even opt for the national pool, for example for France use fr.pool.ntp.org it's more than 140 servers.

All those aliases are made of public servers who have volunteered to be in the pool, there is no restriction on their use.

@abalaban
Thanks for the tip. The reason for me using "time.windows.com" so far was that other suggested servers seem to often be down, rendering them useless. A time server pool seems like a good solution.