MiamiDX and timesync.

[Turran]

So I've been testing for a while now to get MiamiDX to sync the time when I connect.

I have full DNS lookup, I can ping names and IPs when connected.

I check "Get time" and enter something like time1.stupi.se which I know is a good time server. I connect the interface and... nothing.

I've tried the IP for time1.stupi.se, other time servers, my Windows 2008 domain controller etc etc.

Is there some secret to this? Should the clock not automatically sync away from 1978 when I connect?

[Wepl]

probably Miami uses time protocol which is disabled by most servers today, most time servers only provide the ntp protocol. just google a bit...

[Turran]

I ended up using FACTS instead.

http://aminet.net/package/comm/tcp/facts

Install it. Run it and configure the settings. Test that it works one you've connected with Miami. Once you're happy with your settings in FACTS, click "Settings / Save Settings"

Option 1:
In MiamiDX:
In Events / Start, set "Shell" and "SYS:Programs/FACTS GUI" (Change path to where you chose to install it to).
Edit your interface and click "Events". Online should be "ARexx" and S:Facts.miami

Now when you start miami, it will start FACTS hidden.
When you go online, it will run Facts.miami which syncs the time.

Option 2 (easier).
In MiamiDX:
Edit your interface and click "Events". Online should be "Shell" and SYS:Programs/FACTS (Change path to where you chose to install it to).
It will then run FACTS once when you go online, sync the time and then kill it.

[Jope]

Another option is ntpsync. It's a small exe you can make your TCP/IP stack run automatically after going online.. No need to keep anything resident and the Amiga's clock doesn't drift that much before the next reboot. :-)

[Turran]

That was amazingly easier than FACTS. Thanks!

Copy ntpsync to C:
In your interface settings, set Event online to Shell and
C:\NTPSync -d60 -c time1.stupi.se time2.stupi.se

Change -d60 to the minutes + from GMT you are.