In reply to your message of Sun, 29 Aug 2004 14:52:44 EDT:

While I don't want to generate unhelpful clutter, here anyway is some
apocrypha that may or may not bear on the situation: IIRC, many of
Kensington's products included extra buttons or what-have-you, and the way
Kensington tackled this in certain models was to have their firmware
"pretend" that the add-ons were on a "separate" ADB device. I believe this
was done to prevent "confusing" the MacOS 5-9 device drivers. I seem to
remember running into this back in pre-System 7 days, hence the fog is
rather thick for which I apologize.  But since my memory matched the
behavior Brian is seeing (one trackball reports itself as 2 devices), I
thought I'd comment anyway, with apologies if this is completely useless. :-/

FWIW,
	Paul

| > On Sat, Aug 28, 2004 at 05:37:55PM -0400, Michael wrote:
| > > 
| > > > ams0 at adb0 addr 15: EMP trackball <KML1> 2-button, 200 dpi
| > > > wsmouse0 at ams0 mux 0
| > > This is the device you want.
| > 
| > this doesn't seem to work either.
| 
| Still the same error message?
| Does cat /dev/wsmouse0 do anything? ( it should spew garbage when you move th
| e mouse )
| 
| > > That should work. No idea why wsmouse didn't attach to ams1 though.  
| > probably no config entry for it?
| maybe, if wsmouse is hardwired to ams0 it won't attach to ams1.
| 
| have fun
| Michael

Paul Frommeyer            Work: Senior Network Engineer  pfrommeyer@deskey.com
Internet Engineer, CCIE   Play: Network Sorcerer At Large     corwin@palas.com