samah said:
Thank you all for your guidance. I am using the bat file as a temporary
solution for a few days only. Definitely I would go for a battery change
as soon as I can.
Thanks & best regards
-samah
What you may not know is that the hardware clock (for which the wafer
battery is a backup to the RTC and CMOS) is *only* used when the
computer is booted up to the POST screen. When the OS loads, it uses
its own clock and not synchronized to the hardware clock. That means
the hardware clock may be accurate (to a couple minutes per year) but
the OS clock can get way off if program(s) consume so much resources
that time slices cannot be allocated to the OS clock to get it updated.
While Windows comes with its time service, it syncs to Microsoft's time
server (although you can change it to use the NIST service, or add more
servers in a registry key so you can select from one of them). Yet it
can be a week, or more, before the time service decides to sync your OS
clock to one of the NTP (network time protocol) servers that sync to the
atomic clock. You might want to start looking at a 3rd party time sync
utility. I use Socketwatch (not free) because it figures out from its
list of worldwide servers which one has the least latency. The
physically closest NTP server may not have the least latency over the
network. There are free time sync utilities (I installed one on my
aunt's host but can't remember what it was anymore).
Even if the hardware clock is off (because of a dead battery), the time
sync utility will update the OS clock. So after the OS loads, and after
a time sync, your OS clock is on time despite the dead battery.