Lindy mouse

[reddrag0n]

just picked up a NIB Lindy 2 button mouse, but when i plugged it in, i don't get "right click" or the contextual menu as it would also be called.
i tried some software out there like Themouse2B and the kensington mouseware software and nothing is working. i have the latest carbonlib and gamesprockets but still no avail. even checked the internet archive on lindy's website and talked to their tech support and they have no files available.

how would i go abouts having "right click" on my 68k mac without spending money on a wombat or other diy solution?

my machine i'm hooking the mouse up to...
performa 475
mac os 8.1

 

[Iesca]

EDIT: Would help if I read your setup, haha. It should be available in 8.1, but if the Lindy isn't sending "Ctrl-Click" with the Right mouse button, it may not be possible without software intervention.

 

[reddrag0n]

thats what i was thinking but like i said, themouse2b isnt doing anything

as for the setup, like i said, performa 475 with mac os 8.1, 136mb ram and 2gb scsi drive and 1mb video memory. keyboard is a smaller apple keyboard

 

[Iesca]

Does the right button do anything at all? If it's just a regular click, and it didn't come with any software, maybe it was just meant to be swappable for left-handed people?

 

[reddrag0n]

Does the right button do anything at all? If it's just a regular click, and it didn't come with any software, maybe it was just meant to be swappable for left-handed people?

nope, doesn't do anything at all, even with pressing keys on the keyboard and right clicking

 

[reddrag0n]

i found some old lindy extensions but they seem to be powerpc only. next step when i get a chance is trying the mouse on my imate and see if it works in os9 on my mdd. maybe i might be able to figure out whats going on from there

 

[Phipli]

i found some old lindy extensions but they seem to be powerpc only. next step when i get a chance is trying the mouse on my imate and see if it works in os9 on my mdd. maybe i might be able to figure out whats going on from there

Does this work :

TheMouse2B 1.1 - Macintosh Garden

TheMouse2B is a Control Panel which makes the second button on a multi-button mouse act like a control-click (i.e. in the Finder it brings up the contextual menu). TheMouse2B allows you to configure the second button to act like a single-click, double-click or even a click-lock.

macintoshgarden.org

 

[olePigeon]

@Phipli They already tried TheMouse2B. I was also looking for universal ADB drivers when I reread the OP's post.

"i tried some software out there like Themouse2B and the kensington mouseware..."

 

[Phipli]

@Phipli They already tried TheMouse2B. I was also looking for universal ADB drivers when I reread the OP's post.

"i tried some software out there like Themouse2B and the kensington mouseware..."

Ah sorry missed that.

Have a word with @tashtari and @Crutch - if you capture the raw ADB message from the right click, perhaps a driver can be written that triggers a ctrl-click.

 

[reddrag0n]

Ah sorry missed that.

Have a word with @tashtari and @Crutch - if you capture the raw ADB message from the right click, perhaps a driver can be written that triggers a ctrl-click.

i was thinking about that, but how do i capture that info? what program and what platform can it run on? i have 68k, ppc g4/g5 and intel. i have native adb ports and an imate adapter if need be

 

[Phipli]

i was thinking about that, but how do i capture that info? what program and what platform can it run on? i have 68k, ppc g4/g5 and intel. i have native adb ports and an imate adapter if need be

Tashtari's ADB Tools (also a plea for rare devices!)

I've been trying to clean up and publish some of the tools I've been using for my ADB-related adventures. Neither of these are complex enough to warrant a TashName, but I want to put them out there just in case they might come in handy for someone else. I've made an ADB protocol analyzer...

68kmla.org

 

[Tashtari]

The basic ADB mouse protocol has a bit that is sometimes labelled as being used for the second button, though the only two-button ADB mouse I have seems to implement a drag-lock for its second button (it might support a special handler ID, I haven't tested). Your mouse might be using this but the OS doesn't know how to make use of it - or it might be waiting for a driver of some kind to change the handler ID to some other protocol that does carry the right mouse button status.

 

[reddrag0n]

ok, so i have adb parser running, what do i do with it? i followed the steps, but my window shows the mouse on "3" not 2 or 1.

when i set the register to 0, i get no output
when i set the register to 1, i get 4B4F495400C80102
when i set the register to 2, i get no output
when i set the register to 3, i get codes from 6004 up to 6F04, the second digit is always random, but the rest all stay 6 * 04.

 

[reddrag0n]

this is what my imate shows in os9, and even with themouse2b loaded, still no right click

 

[reddrag0n]

even tried the mouse hooked up to the imate is 10.5.9 (aka sorbet leopard) and no right click from the imate and not seeing it in mouse in the system preferences

 

[Phipli]

ok, so i have adb parser running, what do i do with it? i followed the steps, but my window shows the mouse on "3" not 2 or 1.

when i set the register to 0, i get no output
when i set the register to 1, i get 4B4F495400C80102
when i set the register to 2, i get no output
when i set the register to 3, i get codes from 6004 up to 6F04, the second digit is always random, but the rest all stay 6 * 04.

View attachment 54268View attachment 54269View attachment 54270View attachment 54271

I'm not familiar with the program, but try setting it to listen, then clicking the right button. See if data received says anything.

Edit - thinking about it, you need to read the registers in the mouse with the right button pressed and not pressed. ADB is mostly driven by the host polling the peripherals. I'm not familiar enough to remember what exactly needs doing.

 

[sfiera]

I find it easiest to open up “ADB Record” from the Window menu. When I move around my Pippin controller (which acts as a 2-button mouse by default) I see something along the lines of:

Poll Data Count:       $02
Data Buffer Contents:  $80 80

It looks like the data being sent is something like:

struct MouseListen {
    int8_t left : 1;
    int8_t y : 7;
    int8_t right : 1;
    int8_t x : 7;
};

This machine is on System 7, so no contextual menus. I’m not sure if they would work out of the box.
One thing to be aware is that some devices need to be told to provide more information. The controller’s other buttons don’t appear in the data and won’t unless told. I think the extended keyboard is like that too.

 

[Tashtari]

I find it easiest to open up “ADB Record” from the Window menu.

Oh, neat, I completely missed that that feature exists in ADB Parser.

It looks like the data being sent is something like

Assuming that struct is MSB to LSB top to bottom (my C is very, very rusty), you're exactly correct - that's the standard ADB mouse protocol indicated by handler ID 0x01 (for 100 cpi) or 0x02 (for 200 cpi).

when i set the register to 3, i get codes from 6004 up to 6F04, the second digit is always random, but the rest all stay 6 * 04.

This is normal, the second digit changing is part of a collision-avoidance mechanism.

The fact that the low byte (the handler ID) is 0x04, though, indicates that the mouse is using the extended ADB mouse protocol, which can be used to represent up to eight buttons and up to 16 bits of movement data.

when i set the register to 1, i get 4B4F495400C80102

This is also part of the extended protocol - this identifies the mouse and its capabilities. The meaning is as follows:

• Device identifier: "KOIT"
• Device resolution: 200 cpi
• Device class: Mouse
• Number of buttons: 2

No idea what "KOIT" is about, but the rest seems pretty unsurprising.

Anyway, the fact that the handler ID is 0x04 means you're using a system new enough to know about the extended protocol, which means it knows you have a second button, but the fact that it's not doing anything means that it doesn't have any functionality associated with that button. I don't know what software is available to make use of mouse buttons beyond the first in the extended protocol, but there must be some out there.

 

[Iesca]

What's peculiar is that they had it new-in-box, meaning that, if there was any software that was supposed to go with it, it should have been in the box with the mouse.... (You would think?)

 

[reddrag0n]

What's peculiar is that they had it new-in-box, meaning that, if there was any software that was supposed to go with it, it should have been in the box with the mouse.... (You would think?)

nope, no software, and it was still stapled closed too. one thing i will check is in osx, i can get the device id's