From: Eli Zaretskii Newsgroups: comp.os.msdos.djgpp Subject: Re: Keyboard Lockups Date: Fri, 14 Apr 2000 07:24:55 +0200 Organization: NetVision Israel Lines: 17 Message-ID: <38F6ABA7.D8293A29@is.elta.co.il> References: <38ED9D75 DOT 13827ACF AT is DOT elta DOT co DOT il> <38f5f295 DOT sandmann AT clio DOT rice DOT edu> NNTP-Posting-Host: ras1-p116.rvt.netvision.net.il Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: news.netvision.net.il 955689840 2555 62.0.172.118 (14 Apr 2000 05:24:00 GMT) X-Complaints-To: abuse AT netvision DOT net DOT il NNTP-Posting-Date: 14 Apr 2000 05:24:00 GMT X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,ru,hebrew To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Charles Sandmann wrote: > > I saw this behavior under V2.01 on a 486/33 under DOS (and no other system). It > was infrequent but common enough to be a real pain. V2.00 didn't do this. I > didn't have time to investigate and I didn't use the system very often. But > I don't think it's completely uncommon. It would happen on all programs > built with V2.01 that I tested, even simple "hello world" ones if I ran them > frequently enough. > > Since the CTRL-C handler hooks the HW interrupt for the keyboard, I tried > to disable this and the symptoms went away. So I'm sure it was some strange > window of vunerability at exit. I have no idea if this still exists in recent > versions. In the meantime the original poster reported that an old version of CWSDPMI was used when these problems were seen. Removing the old CWSDPMI and using the latest version r4 caused the problems to go away.