68kMLA Classic Interface

Yes, it did... until the Mac Classic II HDD decided to stop working a few hours ago. Ahem...

Hum... it works... And I do not know why really (perhaps because it is 3AM here)... I'm currently listening to Africa Radio at 107.5 MHz (when I thought I was at 107.7 MHz with value 25 00). That's cool. I will comment once I have things cleared. Thanks again.

• A Wacom Intuos GD-0405-A.
• A Logitech MouseMan(TM), ADB. "M/N: M-AC13-4MD".
• A Logitech MouseMan(TM), Macintosh Version. "M/N: M-AH32 P/N:840015-00".

Would this be interesting?

Are these worth trying to do some kind of analysis on?

• Install the immensely useful ADB Parser on your ADB Mac.
• Identify the device on the bus and note what its original (not current) address is.
  • Keyboards typically have original address 2.
  • Mice or other relative pointing devices typically have original address 3.
  • Tablets or other absolute pointing devices typically have original address 4.
  • Whatever the device type is, you should see the small Apple logo move next to the correct device when you move it or otherwise activate it such that it has data to send to the Mac.
• Note what its original handler ID is.
  • For a mouse or other relative pointing device, this will likely be 01, though I know of at least one that has original handler ID 02, so it's not 100%.
  • For a tablet, this could be anything.
    • A tablet may, in fact, appear on the bus as two devices, one that is the actual tablet and one that pretends to be a mouse (with handler ID 01, 02, or 04).
• For a mouse or other relative pointing device, try changing the handler ID to 01, 02, and 04 and make note of which ones the device understands.
  • Click the device in the list and send it a Listen command on register 3 with data of the form 6AHH.
    • Replace A by the device's current address.
    • Replace HH by the desired handler ID.
    • Example: to set the device on address 3 to handler ID 04, you would send it a Listen command on register 3 with data 6304.
  • On the off chance the mouse stops responding, hit the return key to activate ADB Parser's "ADB Reinit" button, this will reset the bus and should restore functionality.
  • Send the same device a Talk command on register 3. It should respond with data 6?HH.
    • ? is replaced by a random number which will change every time you send the Talk command.
    • If HH is not the handler ID that you sent with the earlier Listen command, the device does not understand that handler ID.
  • If the device understands handler ID 04, send it a Talk command on register 1 while its handler ID is set to 04 and note the data received.
• Post your results in this thread, and thanks! =)

• Original Address:
  • Keyboard: 02
  • Mouse: 03
• Handler ID:
  • Keyboard: 02
  • Mouse: 01
• Change Mouse to Handler...
  • 01: yes
  • 02: no
  • 04: no

@nyef - Does the Intuos appear only as one device with handler 0x6A, or does it emulate a mouse as well like the ArtZ II is known to?

@nyef - Is it the MouseMan's "mouse" device (the one with original address 0x3) that's giving the "9A2022E13C3B8138" response on register 0x1? I ask because that's definitely not the standard handler 0x4 format, which is strange, I'd almost expect that to cause trouble with the standard System 7 driver...

I did this once before, but it's been about a year, so I figured it's time to shake the tree again...

Do you, dear reader, own or have access to any ADB devices that aren't on the list?

I can send you a MacHASP-M rather than submit to electronics recycling.
If you want it, send a postal address. Thx, peter at easthope d ca