having to implement a protocol like that seems to be a lot of bother just to encode a keypad. Nevertheless, I want to put it on the list of things to do before I die. I found this Kensington keypad with 21 keys, that seems to be a slight upgrade from what I was using before. What I want out, of course, is a 5-bit code and a strobe.

If there's a manageable portion of the doc, that you'd be willing to scan and forward to me, I'd really appreciate that. As it happens, I don't need information about the mouse, or other peripherals on the ADB, but I suppose that the keypad, being what it is uses the same codes as the keyboard, and those probably have to be translated into what I want from what the ADB normally sees. I doubt it's different in a general sense from what the PC keyboard does, i.e. it tells the system which key was pressed and an OS-resident language table is used to convert that to whatever the key is supposed to represent.

I fear it will be a real pain in the gluteous maximus. There are a few gadgets, though that will work for one purpose or another once one has the interface, though. It's do this, or desolder the 24-pin 805x type that currently encodes it, cut up the key matrix and rewire it, and then use the thing as a 20-key keypad. Perhaps you can, based on your knowledge, choose the path for me. It may be easier to do the latter.

RE


RE