Mail Archives: djgpp/1999/08/26/01:33:52
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
- Raw text -