Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!dsg.csc.ti.com!nagase From: nagase@dsg.csc.ti.com (N Nagase) Newsgroups: comp.sys.ti.explorer Subject: [Paul Fuqua : [stede at cs.purdue.edu: ]] Message-ID: <2841410592-15355637@Foxtrot> Date: 15 Jan 90 16:43:12 GMT Sender: daemon@ucbvax.BERKELEY.EDU Distribution: inet Organization: The Internet Lines: 45 ------- Forwarded Message Date: Sun, 7 Jan 90 00:33:53 CST From: Paul Fuqua Subject: [stede at cs.purdue.edu: ] To: nagase@dsg Date: Saturday, January 6, 1990 8:40am (CST) From: stede at cs.purdue.edu (Manfred Stede) To: pf at csc.ti.com Hi, I am working at Purdue U with the Explorer. Precisely on January 1 we encoun- tered a new behavior: All of a sudden the machine asked for date and time upon booting, whereas earlier it automatically read these data from the clock. Now we are not very happy with having to provide them whenever we start the machine. My reasoning was that the battery of the internal clock might need to be recharged, but browsing through the manuals did not reveal any hint. I'd appreciate any idea, thanks a lot, Manfred Stede, stede@cs.purdue.edu ------- End of Forwarded Message We have seen the same behavior on some of our systems here. Once Resetting the date and time, solved the problem. The problem is most likely caused by the month counter in the RTC was not updated when the month changed from "12" to "01". The initializatin routine encountered an inconsistency in date/time calculation to cause to prompt for the new date/time. If the system continues to prompt for date/time every time you cold boot, then execute the following form after setting the LOCAL TIME; (time:write-chaparral-RTC-chip time:rtclock-ram-month-counter time:*last-time-month*) Regards, Nobi Nagase