Xref: news2.mv.net comp.os.msdos.djgpp:3895
From: Francisco Gochez <arcanix AT pop DOT erols DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Bugs in CWSDPMI and FSDB
Date: 14 May 1996 20:39:25 GMT
Organization: None
Lines: 21
Message-ID: <4nar1t$5sm@news7.erols.com>
NNTP-Posting-Host: as23s54.erols.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

I've encountered a bug in FSDB and one in CWSDPMI.  Under FSDB, I was 
debugging one of my programs (uhh.. really!), when I got to a function 
that puts the computer in graphics mode 0x13.  As I executed the 
instruction, the screen went black and after a few seconds, I got kicked 
out to DOS with a register dump (sorry, I don't have the dump).  This 
happened again, and then again, only the 3rd time, the computer totally 
locked up.  This is how the function went:

void gmode (unsigned short mode)
 {
   __dpmi_regs in;
   in.x.ax = mode;
   __dpmi_int(0x10, &in);
 }

It seems that CWSDPMI doesn't clean after itself as it should on exit.  
Whenever I run something that uses CWSDPMI, and then I enter Win 3.1 (no, 
CWSDPMI is not resident at this time), I get a high-pitched sound and my 
computer reboots (!!).  Also, I tend to get kicked out of FSDB with a 
register dump (not sure which error) quite often.