www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1996/05/02/16:17:05

Xref: news2.mv.net comp.os.msdos.djgpp:3352
From: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Handling INT 0x24
Date: Thu, 02 May 1996 13:21:46 CDT
Organization: Rice University, Houston, Texas
Lines: 12
Message-ID: <3188fd3a.sandmann@clio.rice.edu>
References: <199605021015 DOT AA28083 AT moo DOT dsi DOT unive DOT it>
Reply-To: sandmann AT clio DOT rice DOT edu
NNTP-Posting-Host: clio.rice.edu
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

> Why this? There's a bug in my code or this behaviour is due to the DPMI
> interface used by DJGPP programs?

There are bugs in your program.  You cannot terminate from a real mode 
interrupt, which you are effectively doing with the return register to 
int 24.  You also can't free the RMCB while you are using it.  The 
only option with Int 24 in protected mode is to set a flag and continue
(or use the HW interrupt to exception kluginess).  

Int 24 is supposed to be reflected to PM by the DPMI provider - but the
reason it never got done in CWSDPMI is that Int 24 is of so little use
since you can only store the error info anyway.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019