delorie.com/archives/browse.cgi | search |
Xref: | news2.mv.net comp.os.msdos.djgpp:1271 |
Newsgroups: | comp.os.msdos.djgpp |
From: | peprbv AT cfa0 DOT harvard DOT edu (Bob Babcock) |
Subject: | Re: CWSDPMI on non-386 |
Message-ID: | <Dn34K3.IIM@cfanews.harvard.edu> |
Sender: | news AT cfanews DOT harvard DOT edu |
Reply-To: | rbabcock AT cfa DOT harvard DOT edu |
Organization: | Smithsonian Astrophysical Observatory, Cambridge, MA, USA |
References: | <Dn23DB DOT 20F AT cfanews DOT harvard DOT edu> <3129e203 DOT sandmann AT clio DOT rice DOT edu> |
Date: | Tue, 20 Feb 1996 17:28:50 GMT |
Lines: | 11 |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Charles Sandmann (sandmann AT clio DOT rice DOT edu) wrote: : > cwsdpmi.exe hangs with no message on an IBM model 30/286. : Yes, there's a bug in the jump statement after detection - it uses a : conditional long jump for the 386+ case, but this nukes the pre 386 : systems. Sigh. I even tested it on an XT sometime back, but must : have broken it. Oh well, next release, sorry. It's no big deal; the program wasn't going to run in any case. If this is fixed, will a djgpp program survive long enough on a non-386+ system to attempt to call cwsdpmi and trigger a useful message?
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |