KRSEAR01@ULKYVX.BITNET (Kendall 'Opusii' Sears) (03/30/89)
>Your article says: >> "When the 500 is on the clock keeps perfect time, but when the 500 is off >> the clock stops. When I reboot the clock still holds the last time it had >> when I powered down." > >Are you sure it doesn't hold the last time you set it to? Did you do a >"setclock" just before powering down? > >With regards to the battery, it is extremely unlikely that you need to replace >it. The reason they solder it in is because it has an estimated life of about >12 years. (At Tektronix, we used to figure 7 years, but we were being >conservative.) > > >There is an easy way to find out if I am right. Do a "readclock" and "date" (or >whatever sequence reads the clock and displays it); wait about five minutes, >then do BOTH of them again, and see if it has changed. JUST doing "date" again >doesn't tell you anything. > > Sorry, I didn't make myself clear. All my references to clock were to the BB Clock on board. All references to "date" were actually the dates returned by SetClock opt load. I have done the suggestion above many times. In fact I have DCRON running to reset my "system Clock" from the BB clock because my sys clock runs slow but the BB clock runs perfectly UNTIL I turn off my 500 then *THAT* time and date (power down time) is what is returned on the next boot. This clock worked perfectly all around for about 6 months then decided to die. Again sorry about the "vagueness" (word?) Thanx. Opusii. Kendall "Opusii" Sears KRSEAR01@ULKYVX.bitnet ...!psuvax!ulkyvx.bitnet!KRSEAR01 (UUCP) K.SEARS (GEnie) --------------------------------------------------- "VIC's LIVE... Really. I just used one..."