pete@mck-csc.UUCP (Peter Gaston) (05/24/90)
I've built a software driver that intercepts all ADB device output, and then either eats them or let's them pass through. The theory is that this can be used for a low-end mac based meeting room, i.e., hook up 4 kbs/mouses to a mac, hook up a large screen or kodak datashow, and you're cooking. The ADB driver works fine. no problems. What I've been doing (with little success) is building some hardware to fix some ADB features/bugs. Problems: 1-When they work correctly, they randomly get a device number at power up. It would be nice if the number would always be the same. Otherwise you always have to 'pair up' the keyboards and mouses. 2-The devices don't always do their address arbitration correctly. Apple knows this, re: tech note 206. My solution was to delay power up by some milliseconds for subsequent devices, but this didn't work. So I'd like to talk with others who are interested in the ADB. I'd be willing to share my trials and tribulations getting my code to work. I can share my INIT/cdev that does the work, you can use it right out of the box as you can plug two pairs of kb/mouses into a standard Mac (you need hardware to go higher). So e-mail me, and we can chat off-line. I just think this is a little off the wall for most people... Peter Gaston -- ------------------------------------ Peter Gaston, mit-eddie!mck-csc!pete