From: kagel AT quasar DOT bloomberg DOT com
Date: Fri, 7 Feb 1997 09:52:37 -0500
Message-Id: <9702071452.AA27937@quasar.bloomberg.com >
To: brennan AT mack DOT rt66 DOT com (BrennanUnderwood)
Cc: djgpp AT delorie DOT com
In-Reply-To: <5ddh7e$252$1@mack.rt66.com> (brennan@mack.rt66.com)
Subject: Re: Strange Timer with DJGPP
Reply-To: kagel AT dg1 DOT bloomberg DOT com

   From: brennan AT mack DOT rt66 DOT com (Brennan "The Rev. Bas" Underwood)
   Date: 6 Feb 1997 14:07:58 -0700

   In article <yksohdyfc2i DOT fsf AT ra DOT ibr DOT cs DOT tu-bs DOT de>,
   Till Harbaum  <harbaum AT ra DOT ibr DOT cs DOT tu-bs DOT de> wrote:
   Brennan Underwood <brennan AT mack DOT rt66 DOT com> added:
[SNIP]
   I seem to remember that this is a bug in DOS, when the clock turns around
   at midnight and you read it. I could be wrong; I just once had to go through
   some extensive source code that went to great pains to not do that.

HISTORICAL NOTE:
This was a bug in early DOS's which was fixed in (I think) DOS 3.1.  If the 
machine was left on over midnight the data did not increment.  The real-time 
clock was OK so the next boot repaired the problem but the DOS internal clock
counter was mucked up.

-- 
Art S. Kagel, kagel AT quasar DOT bloomberg DOT com

A proverb is no proverb to you 'till life has illustrated it.  -- John Keats