Date: Fri, 16 Feb 2001 12:34:14 +0200 From: "Eli Zaretskii" Sender: halo1 AT zahav DOT net DOT il To: "Rob Kramer" Message-Id: <1659-Fri16Feb2001123414+0200-eliz@is.elta.co.il> X-Mailer: Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.6 CC: djgpp AT delorie DOT com In-reply-to: <3a8cd661$1@news.starhub.net.sg> (robk@cyberway.com.sg) Subject: Re: System clock problem. References: <3a8ca532$1 AT news DOT starhub DOT net DOT sg> <7458-Fri16Feb2001081657+0200-eliz AT is DOT elta DOT co DOT il> <3a8cd661$1 AT news DOT starhub DOT net DOT sg> Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > From: "Rob Kramer" > 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?