Hello,

 JB> you're in luck it doesn't complicate things.

I figured as much, but you never know.. had to ask. :)

 JB> find some sample TSR code, (look up keep() or _dos_keep() in your
 JB> reference.)

I have lots of sample TSR code.. and I have messed around with them, but it
's not good to do that when you don't know quite what your doing... it
really can screw up your memory.

JB> you need to hook interrupt number 0x09 (the keyboard
handler) call  JB> the default handler and then check if anything was put
into the  JB> keyboard buffer, then it's simply a matter of translating the
 JB> scancode/value in the buffer to your modified version.

Okay.. that doesn't sound too bad...

 JB> Q: how are you going to logon with this tsr messing up what you type?

Well.. I will have to have the TSR be able to remove itself from memory -
which i've read can be immpossible depending on what tsr's are loaded
before..

JB> A: make the tsr activate/deactivate by a special keystroke - maybe
JB> JB> the scroll-lock button
JB> JB> JB> HELPPC is an excellent shareware reference for this sort of
thing.  JB> it's been around for many years, should be a copy near you.

Okay... well thanks for the help.. I think I'll look at those TSR programs
more carefully, and get started. :)

Ciao!

... I am Fudd of Borg.  Wesistance is usewess!
-*- TurboEDIT v1.60a+ [MSP96]
--- Ezycom V1.48g0 01fa0167