Mail Archives: djgpp/2001/02/16/08:13:05
"Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il> wrote in message
news:1659-Fri16Feb2001123414+0200-eliz AT is DOT elta DOT co DOT il...
> > From: "Rob Kramer" <robk AT cyberway DOT com DOT sg>
> > Newsgroups: comp.os.msdos.djgpp
> > Date: Fri, 16 Feb 2001 15:18:41 +0800
> >
> > Correct, there's about 50 of these devices (embedded PCs). 3 are
starting to
> > show the problem now. I'm suspecting a hardware problem, but can't
explain
> > why all is fine again after I exit my application.
>
> Based on your description, I won't suspect the hardware first, because
> the system clock is evidently okay once you exit the program.
>
> What other time-related functions or interrupts does that program use?
> Does it delay itself, for example, or use usleep?
Lots of delays and timings yes, but they are all derived from a 5ms Allegro
timer, which reprograms one of the hardware timer/counters. I use the
Allegro timer interrupt to add 5 to a global counter, so I have a
millisecond counter with 5ms precision. All timings are done by using that
counter. No usleep used.
The clock-string written to the screen is directly converted from time(),
using my own conversion routine (strftime() was not suitable for 'historical
reasons'). Going through the code, there's no way a clock speedup could be
introduced here..
Thanks,
Rob
- Raw text -