Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!usenet.ins.cwru.edu!cwlim!trier From: trier@cwlim.INS.CWRU.Edu (Stephen C. Trier) Newsgroups: comp.sys.ibm.pc.hardware Subject: Re: DOS and BIOS clocks Message-ID: <1991Jan15.041357.1949@usenet.ins.cwru.edu> Date: 15 Jan 91 04:13:57 GMT References: Sender: news@usenet.ins.cwru.edu Reply-To: trier@po.CWRU.Edu Organization: Case Western Reserve Univ. Cleveland, Ohio, (USA) Lines: 23 Nntp-Posting-Host: cwlim.ins.cwru.edu In article greg@turbo.atl.ga.us writes: >I'm having a problem with my system's clock. Sometimes when I'm running >a program overnight, the date is not updated. Early versions of MS-DOS (2.x, x being something I've forgotten) had a bug that did exactly that. Norton's Programmer's Guide to the IBM PC and PS/2 insists that the bug is gone, but I've had it happen to me on AT&T MS-DOS 3.3 and on the generic MS-DOS 3.3 my parents run on thier Packard- Bell. (Methinks the bug is *not* gone!) It doesn't always happen; I've never found a condition that causes it. In most cases, rebooting the computer is sufficient, since that will restore the time from the hardware clock. This doesn't always work on the Packard- Bell. I don't know why. The basic message is, "Yes, it happens. No, I don't think it means much." Sure confuses make, though! :-) -- Stephen Trier Case Western Reserve University Work: trier@cwlim.ins.cwru.edu Information Network Services Home: sct@seldon.clv.oh.us %% Any opinions above are my own. %%