From:	Till Harbaum <harbaum AT ra DOT ibr DOT cs DOT tu-bs DOT de>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Strange Timer with DJGPP
Date:	07 Feb 1997 10:53:37 +0100
Organization:	TU Braunschweig, Informatik (Bueltenweg), Germany
Lines:	21
Sender:	harbaum AT kastor
Distribution:	world
Message-ID:	<ykszpxhx7q6.fsf@ra.ibr.cs.tu-bs.de>
References:	<yksohdyfc2i DOT fsf AT ra DOT ibr DOT cs DOT tu-bs DOT de> <5ddh7e$252$1 AT mack DOT rt66 DOT com>
NNTP-Posting-Host:	kastor.ibr.cs.tu-bs.de
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

> A bit disconcerting when make starts telling me files were created in the
> future.
I can live with it, since i use this dos machine only to compile the port,
i even edit my dos programs under sunos. I wrote a little script, that runs
on the sun (my nfs server) and looks for object files which are older than 
their source and deletes them. This causes the dos make to work (but still
complaining about files living in the future).

> 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.
Yeah, i remember there was something like that: If you read the system timer
via the bios int you get informed if the counter passed midnight. If your
program gets this info it will not be passed to dos. I once wrote a program,
that worked around this problrm but i don't remember how it worked (perhaps
resetting the counter to one tick before midnight and wait a second, to
"forward" the midnight notice to dos?)

Ciao,
  Till

- Raw text -