From: Charles Sandmann <sandmann AT new-orleans DOT NeoSoft DOT com>
Subject: Re: A fault report
To: A DOT APPLEYARD AT fs2 DOT mt DOT umist DOT ac DOT uk (A.Appleyard)
Date: Wed, 25 Jan 1995 19:07:13 -0600 (CST)
Cc: DJGPP AT sun DOT soe DOT clarkson DOT edu

> An explanation of an odd fault that someone may have had: I have succeeded in
> ...
> a DOS prompt. When I called the Gnu C++ program, it ran OK until the first time
> it needed me to input a character, when it stuck tight and didn't want to know
> even about ctrl-alt-del. Presumably it was still in the interrupt routine
> stack level. This may explain odd events that people may have had.

GO32 hooks the int 9 keyboard interrupt each time it runs to provide 
support for the event library routines (even if they are not included
in the 32 bit image).  If the program is aborted in some unusual way,
the int 9 keyboard interrupt is left pointing to unallocated memory, 
and the next execution of a program is likely to hang the system.  Running
another GO32 program will chain to the vector left pointing to the 
exact same place in memory (infinite loop).  

Since there is no GO32 in V2, this problem goes away.