From: nikki AT gameboutique DOT co (nikki)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: interrupts and unknown opcodes
Date: 5 Feb 1997 10:35:31 GMT
Organization: GameBoutique Ltd.
Lines: 35
Message-ID: <5d9npj$d17@flex.uunet.pipex.com>
References: <5d869q$3br AT flex DOT uunet DOT pipex DOT com>
    <5d8d54$7sj$1 AT troll DOT powertech DOT no>
NNTP-Posting-Host: www.gameboutique.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

> This should be covered in the FAQ. Under DPMI, interrupts doesn't work
> the same way as in real mode compilers.

oh that's ok, i've never done anything with interrupts under real mode before
anyway which is why i decided to learn :)
the faq does indeed say how to do it, but doesn't give me the experience of
all you wonderful people out there as to which would be the better method ;)

> D6 is an "undocumented" (newly-documented) opcode, called SALC (Set AL
> with Carry). It seems its behaviour is already described in your
> comments.

ack undocumented :( do you know anywhere it might be 'newly documented' as i
don't have any reference to it anywhere and wouldn't mind knowing some more
about it. doesn't seem to be on intels sheet :(

> This handler really only updates a table with which keys are down, and
> it doesn't even do that well. Instead of wasting your time, consider

yeh i noticed :( doesn't appear to push or pop anything either which seems
bad practice for an interrupt handler.

> using already-existing better-written keyboard handlers instead. I
> think there's pointers to some in the FAQ.

yeh, but i don't actually need the code as a matter of life and death :) it's
just an exercise in writing it really :) i don't mind wasting time as i have
nothing better to do :)

regards,
nik

-- 
Graham Tootell           
nikki AT gameboutique DOT com