🚀 go-pugleaf

In article <1991May13.180754.25187@eng.ufl.edu> jy@wasp.eng.ufl.edu (Jim Yousse) writes:
>Does anyone know about the Midnight Bug in DOS, where the clock does not
>register a date change when passing midnight?  We have a user here who
>leaves her machine on continuously, and every now and then it will lose
>a day.  We're pretty sure this is the midnight bug in action.  We've heard
>of fixes for this, but don't know where to get one.  Any suggestions?
>Thanks.

This is due to DOS only setting a flag instead of incrementing a counter when
midnight is passed. ie, as the clock ticks past midnight, DOS sets a flag
indicating that it's a new day. This flag is reset, and the date incremented,
when the BIOS Get-Date function(s) are called. What this boils down to is
that, if your computer is on over an entire midnight-midnight period without
the clock being read, you will lose a day. I haven't developed a fix for this
yet, although I will need to soon as I intend to start leaving my machine on
24-hours in a few months. However, a TSR should do the trick. A simple one
which does a BIOS Get-Date call whenever the time equals a certain value (ie,
once/day) would work. This may or may not display the time/date on the screen
(depends on what you want). There are probably some PD programs around which
do just that. However, you need to make sure that they use the BIOS, rather
than direct memory reads.

PS - I'm not sure that it's a BIOD Get-Date call. It may be Get-Time instead.
	 I don't have the manuals handy.

-- 
-----------------------------------///-----------------------------------------
Kevin Spencer (09) 420 8173       /// Insert profound gem of wisdom here...
kevin@ncc.telecomwa.oz.au     \\\///
-------------------------------\XX/--------------------------------------------