Date: Thu, 9 May 1996 21:51:30 -0400
From: Andrew Szymkowiak <aes AT solia DOT gsfc DOT nasa DOT gov>
Message-Id: <199605100151.VAA00706@solia.gsfc.nasa.gov>
To: djgpp AT delorie DOT com
Subject: losing track of time...

   I have a V2 program which I have left running for several days.
This program uses the uclock routine for some timing.  When I stop the
program, the time command at the DOS prompt is correct, but the date
command gives the date when the program was started.  I know that the
uclock routine is reprogramming the timer, and I would guess that the
fact that the time is correct means that the new interrupt routine is
correctly chaining to the old routine 18.2 times a second.  Could
uclock be causing me to be losing days?  If it is, and it is not easy
to fix, is there some routine I could call that would reload the DOS
clock from the hardware time-of-day clock, so that I could be sure to
get the right time on files and/or before I exit?  Also, are there
other routines that re-program the timer chip, and cannot be
used at the same time as uclock? How about profiling?
  Thanks,
     Andy S.