Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!clyde.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!ucsd!nosc!halibut.nosc.mil!koziarz
From: koziarz@halibut.nosc.mil (Walter A. Koziarz)
Newsgroups: comp.sys.ibm.pc.hardware
Subject: Re: DOS and BIOS clocks
Message-ID: <3358@nosc.NOSC.MIL>
Date: 7 Jan 91 11:52:01 GMT
References: <1991Jan5.181959.10764@xrtll.uucp>
Sender: nobody@nosc.NOSC.MIL
Organization: Naval Ocean Systems Center, San Diego
Lines: 14

In article <1991Jan5.181959.10764@xrtll.uucp> silver@xrtll.UUCP (Hi Ho Silver) writes:
>
>   The problem you're experiencing is caused by the fact that most (all?)
>versions of DOS are too dumb to increment the date when the clock turns over
>midnight.  I guess Microsoft assumed that nobody uses their computers at
>night and figured they could forget it and nobody would notice.  Thanks,
>guys.  I'm not sure if this was fixed in DOS 4.

Don't think so....  I just tried MS-DOS versions 1.10, 2.24, 3.1 and ALL
increment the date at midnight.  Of course these are Zenith-prepared MS-DOSes;
not I(nferior) B(ut) M(arketable)-prepared.  MS-DOS *HAS* the capability and
it's (apparently) the reponsibility of the system integrator to activate it.

Walt K.