Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!ngstl1.csc.ti.com!hyde
From: hyde@ngstl1.csc.ti.com (Clint Hyde 343-7709 Strong Typing is for people with Weak Memories!)
Newsgroups: comp.sys.ti.explorer
Subject: that dang clock
Message-ID: <9002161630.AA08943@ti.com>
Date: 16 Feb 90 15:47:30 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: inet
Organization: The Internet
Lines: 18


the problem(s) folks have had with the RTC can all be fixed easily enough.

first, reboot (m-c-m-c-abort) the machines which are time-servers. at the
prompt following the self-tests, hit `E' for extended tests. this will, at
some point, completely zero-out the battery-backup clock. when done, boot as
normal, and fill in the correct time when it asks. 

you will need to adjust the namespace to correctly specify the time-zone and
daylight-savings or whatever. this is probably what bill @ washington was
having trouble with. I've seen it change an hour or two when the time-server
responds to "Ask the time".

also note: the battery only lasts about two weeks--it's not capable of long-
term storage, so that if the machine is powered off for more than two weeks,
the backup clock will have been zeroed already.

 -- clint