Message-ID: <36CA5518.D0C535A5@ameritech.net>
From: John Scott Kjellman <jkjellman AT ameritech DOT net>
X-Mailer: Mozilla 4.04 [en] (Win95; I)
MIME-Version: 1.0
Newsgroups: comp.os.msdos.djgpp
Subject: Re: How to check the carry flag? (long)
References: <Pine DOT SUN DOT 3 DOT 91 DOT 990215102108 DOT 10128P-100000 AT is> <36C90198 DOT 90D8905C AT ameritech DOT net> <36CA256B DOT 689968E AT cartsys DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 32
Date: Tue, 16 Feb 1999 23:35:20 -0600
NNTP-Posting-Host: 199.179.164.107
X-Trace: nntp0.chicago.il.ameritech.net 919230064 199.179.164.107 (Tue, 16 Feb 1999 23:41:04 CDT)
NNTP-Posting-Date: Tue, 16 Feb 1999 23:41:04 CDT
Organization: Ameritech.Net www.ameritech.net  Complaints: abuse AT ameritech DOT net
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Nate,

I am using CWSDMPI under DOS 6.22 using the default parameters.  I'll give a try
to using __dmpi_int to see if carry is being handled properly.  There is one
other option, though.  Is there some way to install a real mode handler without
using the wrapper code?  My handler uses no stack space and could even be
written in in-line assembler if need be (it is very simple).  Just a thought.

KJohn

Nate Eldredge wrote:
> 
> John Scott Kjellman wrote:
> >
> > Eli,
> >
> > See the below program text.  I compiled it using RHIDE (file name CFTEST.CC).
> > If you run it and then press a few keys, it will display the character (if
> > printable) and the getxkey() value for each key.  The '1' key should be
> > translated to a '2' and the '0' key should be dropped, but isn't!  BTW, in my
> > previous posting I stated 0x30 was the scan code for the '0' key, it is not 0x0B
> > is, 0x30 is the ASCII value ;-)  This just doesn't seem to follow the docs....
> 
> It might be worthwhile to simplify some more and call the interrupt
> yourself (with __dpmi_int), so you know for sure whether the flag is
> getting changed.  That will rule out the BIOS screwing up.
> 
> And what DPMI server are you using?
> --
> 
> Nate Eldredge
> nate AT cartsys DOT com