From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: PS: A mysterious event
Date: 14 Aug 2000 12:45:40 GMT
Organization: Aachen University of Technology (RWTH)
Lines: 18
Message-ID: <8n8plk$ere$1@nets3.rz.RWTH-Aachen.DE>
References: <8n6i6g$8cn$1 AT newsg4 DOT svr DOT pol DOT co DOT uk> <8n6ir5$8rp$1 AT newsg4 DOT svr DOT pol DOT co DOT uk>
NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de
X-Trace: nets3.rz.RWTH-Aachen.DE 966257140 15214 137.226.32.75 (14 Aug 2000 12:45:40 GMT)
X-Complaints-To: abuse AT rwth-aachen DOT de
NNTP-Posting-Date: 14 Aug 2000 12:45:40 GMT
Originator: broeker@
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Greg Holdridge <greg AT holdridge7 DOT freeserve DOT co DOT uk> wrote:
> Actually, sometimes a SIGSEGV occurs instead of power off on monitor- this
> highlights that the problem occurs during a lodsw loop:
[...]
> .SetCRTParmsLoop:
>    lodsw           ;get the next CRT Index/Data pair
>    out     dx,ax   ;set the next CRT Index/Data pair
>    loop    .SetCRTParmsLoop

If memory serves me well, this method of accessing IO ports is known
to be dangerous, and known not to work, too. You're supposed to insert
short pauses between succesive accesses to the CRT ports, esp. on
modern CPUs. If you don't, you'll confuse the living daylight out of
the CRT chip. Loss of VSync (--> blank screen) would be easily
explained by that.
-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.