Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!ucsd!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: clock problem
Message-ID: <9001112133.AA00612@ti.com>
Date: 11 Jan 90 21:19:03 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: inet
Organization: The Internet
Lines: 17


it's simple. the battery clock doesn't last forever. the only way to reset it
is to COLD boot (m-c-m-c-abort) and then choose E for extended testing of 
the hardware. this zeros the clock hardware, and when you finally boot 
normally (after the end of testing, which will take a while because you will
also fully test the RAM), the Listener will ask you to tell it what the time
is, and that's what will go into the battery clock.

so, why couldn't I just find which function that's called to ask me that, and
use it directly, whenever I want?

I don't know. never did figure that out. if you have an answer, I'd like to
know, because I'd like to be able to reset the battery clock (and then do
(time:initialize-timebase)), because the battery clock is accurate where the
RTC (microsecond-counter) clock is not, and loses about a minute per day.

 -- clint