Hardware: Sam460ex 1150 MHz reported by MorhpOS as 1265 MHz.

1. Is the clock drifting due to the wrong cpu frequency reported, or is it just a bad battery? Something else?
2. Synching clock against time server works as expected, but how often does it sync automatically (if at all)?

> Sam460ex 1150 MHz reported by MorhpOS as 1265 MHz.
> 1. Is the clock drifting due to the wrong cpu frequency reported [...]?

It's more like both are the symptoms of another clock frequency wrongly assumed:

https://morph.zone/modules/newbb_plus/viewtopic.php?topic_id=11840&forum=11

2) I don't think it syncs frequently during the session at all, it just syncs when commanded. But you can add, for example, this kind of line to your S:user-network-startup file:
Run >NIL: WaitX M=60 ALWAYS CMDLINE "C:SetClockNTP"

Replace the minute value for the M argument for what you feel is required. Or use H= for hours. Then it repeatedly syncs the clock in the background.

Change the battery anyway.

Quote:

Thanks, just what I was looking for.

If you check the NTP server too many times per hour, they have been known to block you. Fair warning.

Quote:

Good point. Once per hour is hopefully okay, and it's not like I keep the machine running all around the clock.

The default time servers are AFAIR pooled, so you probably get a random one at anytime. There are also three different pools build in and you can specify a server if needed.

But right there is no use to abuse their free service anyway.

If our systems are on for about 12 hours a day the time diff should only be a few seconds and only on the condition of having not a single reboot.