Mail Archives: djgpp/1999/02/16/21:18:59

Sender: nate AT cartsys DOT com
Message-ID: <>
Date: Tue, 16 Feb 1999 18:11:55 -0800
From: Nate Eldredge <nate AT cartsys DOT com>
X-Mailer: Mozilla 4.08 [en] (X11; I; Linux 2.2.1 i586)
MIME-Version: 1.0
To: djgpp AT delorie DOT com
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>
Reply-To: djgpp AT delorie DOT com

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

- Raw text -

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