From:	Tom Sgouros <tomss AT ids DOT net>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Failure during timing-sensitive application...
Date:	Tue, 24 Sep 1996 19:57:40 -0400
Organization:	IDS World Network Internet Access Service, (401) 885-4243
Lines:	31
Message-ID:	<Pine.SUN.3.95.960924195338.14046D-100000@conan.ids.net>
References:	<Pine DOT SUN DOT 3 DOT 95 DOT 960922195102 DOT 857B-100000 AT conan DOT ids DOT net>
NNTP-Posting-Host:	conan.ids.net
Mime-Version:	1.0
In-Reply-To:	<Pine.SUN.3.95.960922195102.857B-100000@conan.ids.net>
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

For those  who are interested, and to those who might be able to explain
this to me in such a way as to keep the problem from arising again...

The problem outlined below has become more difficult to reproduce since I
changed all the _bios_timeofday() calls with uclock() calls (with
appropriate source modifications). It's the nature of intermittent
problems that one can't be absolutely sure they've gone away, but I
haven't seen it since the change.

Can anyone tell me what's going on?


On Sun, 22 Sep 1996, Tom Sgouros wrote:

> Can anyone advise me on this?
> 
> I am working on an application that controls six or so RS232 devices. They
> are connected to the PC through a multiplexer, so there is only one COM
> port being accessed. Anyway, it is sitting on the other side of the room
> now, happily chunking away at round 7500 or so on my test program.
> 
> The problem is this: One time in three (give or take), the program hangs
> mysteriously in the first minute of execution. An unexplainable disk
> access (i.e. there is no program file access) coincides with the hang. If
> it doesn't hang within a minute, it seems to run indefinitely.
> 

---------------------------------------------------------------------
tomss AT ids DOT net - 401-861-2831 - 42 Forge Road, Potowomut, RI 02818 USA

- Raw text -