delorie.com/archives/browse.cgi | search |
From: | "Charles Sandmann" <sandmann AT clio DOT rice DOT edu> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: Keyboard Lockups |
Date: | Fri, 14 Apr 2000 18:20:31 |
Organization: | Aspen Technology, Inc. |
Lines: | 11 |
Message-ID: | <38f7616f.sandmann@clio.rice.edu> |
References: | <38f5f295 DOT sandmann AT clio DOT rice DOT edu |
NNTP-Posting-Host: | dcloan.hou.aspentech.com |
X-Trace: | selma.aspentech.com 955754758 9056 10.32.115.107 (14 Apr 2000 23:25:58 GMT) |
X-Complaints-To: | postmaster AT aspentech DOT com |
NNTP-Posting-Date: | 14 Apr 2000 23:25:58 GMT |
X-NewsEditor: | ED-1.5.8 |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Reply-To: | djgpp AT delorie DOT com |
> 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. If I remember correctly I modified CWSDPMI to be more defensive about hardware interrupts to work around problems like this. So it's probably a matter of various features and workarounds needing to be in sync. Since V2.00 shipped with an older version of CWSDPMI, it would notice the problem, where most people had migrated to newer CWSDPMIs with the newer releases (while I keep various test environments to make sure the new versions of CWSDPMI don't break things that used to work under the older versions).
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |