In message <[EMAIL PROTECTED]> "Chris D. Faulhaber"
writes:
: > flags 0x20 (the NOIDPROBE) which forces it to behave as if it were a
0x200 (one of these days I'll learn to shift by 9)
: For my Kensington (on -stable) I used 'flags 0x10' (NOCHECKSYNC) to kill
: the out of sync messages
On Wed, 21 Jul 1999, Kazutaka YOKOTA wrote:
>
> >On Tue, 20 Jul 1999, Warner Losh wrote:
> >
> >> I had problems with the my Kensignton mouse in a box, but some fixes
> >> were made to -current that fixed the problems. A workaround is to set
> >> flags 0x20 (the NOIDPROBE) which forces it to b
>On Tue, 20 Jul 1999, Warner Losh wrote:
>
>> I had problems with the my Kensignton mouse in a box, but some fixes
>> were made to -current that fixed the problems. A workaround is to set
>> flags 0x20 (the NOIDPROBE) which forces it to behave as if it were a
>> plain old 2 button (or in my cas
>Is there any support for the wheel in FreeBSD/X, the moused man page seems
>to suggest there is but I've not managed to get it to do anything yet.
>
>Paul.
You will find the following URL useful to utilize the wheel in
the X environment.
http://www.inria.fr/koala/colas/mouse-wheel-scro
On Tue, 20 Jul 1999, Kazutaka YOKOTA wrote:
> One is Logitech mouse support in the psm driver. The psm driver had
> been unable to handle some wheel mice models, including Logitech
> M-S48, until recently.
Perhaps it's worth getting another mouse in this situation. My $30
Logitech wheeled mous
On Tue, 20 Jul 1999, Warner Losh wrote:
> I had problems with the my Kensignton mouse in a box, but some fixes
> were made to -current that fixed the problems. A workaround is to set
> flags 0x20 (the NOIDPROBE) which forces it to behave as if it were a
> plain old 2 button (or in my case 3 but
In message <[EMAIL PROTECTED]> Tomi Vainio writes:
: My mouse is always detected as a MouseMan+. Here is couple dmesg logs
: from boots with and without monitor switch.
I had problems with the my Kensignton mouse in a box, but some fixes
were made to -current that fixed the problems. A workaro
Greg Lehey writes:
>
> ISTR there was a fix for this committed recently. Have you tried
> updating to a really recent -CURRENT?
>
I'm using current cvsupped on last Sunday.
Kazutaka YOKOTA writes:
>
> One is Logitech mouse support in the psm driver. The psm driver had
> been unable to
> > The problem springs, I think, from confusion between (Intellimouse) and
> > (!Intellimouse). The box pretends to be an Intellimouse even when you
> > don't have one [or this is what seems to happen in my case], and so
> > FreeBSD detects that you have an Intellimouse. However, then it all
>
On Monday, 19 July 1999 at 23:04:40 +0300, Tomi Vainio wrote:
> I have tried to use Logitech PS/2 wheel mouse (model M-S48) but
> support has been broken for a long time now. I have binded fvwm menus
> to mouse + keyboard combinations. If I press keyboard and move mouse
> at the time I will alwa
Ian Whalley writes:
>
> The problem springs, I think, from confusion between (Intellimouse) and
> (!Intellimouse). The box pretends to be an Intellimouse even when you
> don't have one [or this is what seems to happen in my case], and so
> FreeBSD detects that you have an Intellimouse. How
>Yes, I have monitor switch but it's dummy manual one. I removed it
>completely and now mouse works without problems. It's quite strange
>this switch will broke mouse if I don't use it and switch just sits
>between these wires. It also works with other operating systems.
Well, the Cybex one I
Ian Whalley writes:
>
> Do you have a monitor switch? If so, I bet it is a cybex one. Look
> in the manual for the 'reset mice' control sequence -- that seems to
> do the trick for me.
>
Hi,
Yes, I have monitor switch but it's dummy manual one. I removed it
completely and now mouse work
>I have tried to use Logitech PS/2 wheel mouse (model M-S48) but
>support has been broken for a long time now. I have binded fvwm menus
>to mouse + keyboard combinations. If I press keyboard and move mouse
>at the time I will always get these errors and keyboard is lost after
>this.
>Jun 20 21:4
I have tried to use Logitech PS/2 wheel mouse (model M-S48) but
support has been broken for a long time now. I have binded fvwm menus
to mouse + keyboard combinations. If I press keyboard and move mouse
at the time I will always get these errors and keyboard is lost after
this.
Jun 20 21:48:36
15 matches
Mail list logo
