Path: utzoo!attcan!uunet!midway!ux1.cso.uiuc.edu!julius.cs.uiuc.edu!wuarchive!sdd.hp.com!hplabs!hpda!hpcupt1!swh
From: swh@hpcupt1.cup.hp.com (Steve Harrold)
Newsgroups: comp.sys.ibm.pc.misc
Subject: Re: Clock update at midnight
Message-ID: <51930002@hpcupt1.cup.hp.com>
Date: 18 Oct 90 14:34:54 GMT
References: <1990Oct15.205312.9223@tree.uucp>
Organization: Hewlett Packard, Cupertino
Lines: 16

>>> We have an application that runs over the weekend.  It prints a message
>>> after processing, and then waits for user input.  This usually lasts 1
>>> to 2 days, and the system date does not update during this time. 
----------

As I recall, when midnight rolls around, DOS merely sets a flag indicating 
such.  The next time the clock is referenced by an application via a system 
call, the clock logic sees the flag and updates the day.  If 2 or more 
midnights occur before such a reference, you will see but a single advance
of the day.

To resolve your problem, modify your application to time-out periodically,
(less than 24 hours) and reference the clock.  Thus there will never be
any lost midnight flags.

Hope this helps.