lane@cs.dal.ca (John Wright/Dr. Pat Lane) (02/09/90)
Hi. Have a little problem with a 386 system; perhaps someone can suggest
what's going on here. Basically, the clock/calendar seems to stop counting
whenever the machine is turned off so that wheever you turn the thing on,
it thinks it's the same time as it was when you turned it off. While the
machine is running, it seems to keep time OK incl. accross re-boots.
The SETUP configuration data in CMOS seems to be preserved OK. At one point
it wasn't and we got messages warning us that the battery was low (in a
very new machine!). We got a new battery and that seemed to cure the CMOS
problems but not the clock/calendar. Any suggestions?
Replies by mail would be appreciated as I rarely have time to read news
anymore (very :-(ly).
Thanks
JW.
--
John Wright ////////////////// Phone: 902-424-3805 or 902-424-6527
Post: c/o Dr Pat Lane, Biology Dept, Dalhousie U, Halifax N.S., CANADA B3H-4H8
Cdn/Eannet:lane@cs.dal.cdn Uucp:lane@dalcs.uucp or {uunet watmath}!dalcs!lane
Arpa:lane%dalcs.uucp@uunet.uu.net Internet:lane@cs.dal.cabesler@egrunix.UUCP (Brent Besler) (02/10/90)
This is a real stab in the dark, but the problem may be the clock is keeping time from the system crystal rather than the separate clock crystal. It may be an error in the setup configuration. Brent H. Besler
davidsen@sixhub.UUCP (Wm E. Davidsen Jr) (02/12/90)
[ problem with clock stopping but CMOS RAM not losing data ] My feeling is that you have a VERY marginal battery, but others please post as well as mail, as this is a somewhat new problem. -- bill davidsen - sysop *IX BBS and Public Access UNIX davidsen@sixhub.uucp ...!uunet!crdgw1!sixhub!davidsen "Getting old is bad, but it beats the hell out of the alternative" -anon