Trevor....the Pointer section in your XF86Config file is fine,
now execute 'imwheel -k' and the scroll wheel should begin to
work.

Alan


Trevor Farrell wrote:
> 
> Michael Holt wrote:
> 
> > Hello,
> >     I'm using a Logitech trackman marble with the scroll wheel in the
> > center and I just can't seem to get that thing working!  I know that it
> > will work, but I just don't seem to understand the docs, maybe too much
> > coffee?!?
> >
> > If there's anyone else using Mandrake 7.0-2 with this pointing device,
> > could you please walk me through the set up?
> >
> > When I installed Mandrake, by default the generic PS/2 driver was
> > selected.  I went to XF86Setup and deselected 'emulate 3 button mouse'
> > and I've also tried typing 'imwheel' in eterm but that doesn't seem to
> > work.
> >
> > Any help would be greatly appreciated!
> > Michael Holt
> > [EMAIL PROTECTED]
> 
> Likewise, I'm not able to get the wheel working on my Logitech FirstMouse
> plus. The appropriate section from my XF86Config file is:
> 
> # **********************************************************************
> # Pointer section
> # **********************************************************************
> 
> Section "Pointer"
>     Protocol    "MouseManPlusPS/2"
>     Device      "/dev/psaux"
>     Resolution  100
>     ZAxisMapping 4 5
> 
> # When using XQUEUE, comment out the above two lines, and uncomment
> # the following line.
> 
> #    Protocol   "Xqueue"
> 
> # Baudrate and SampleRate are only for some Logitech mice
> 
> #    BaudRate   9600
> #    SampleRate 150
> 
> # Emulate3Buttons is an option for 2-button Microsoft mice
> # Emulate3Timeout is the timeout in milliseconds (default is 50ms)
> #    Emulate3Buttons
> #    Emulate3Timeout    50
> 
> # ChordMiddle is an option for some 3-button Logitech mice
> 
> #    ChordMiddle
> 
> EndSection
> 
> All the documentation I have seen says thats all thats needed, but it
> don't go. What else is missing?
> 
> PS at the risk of continuing an overlong saga, it worked under ver 6.0 -
> is this another ver 7.0 "feature" (we've all agreed this is not a bug, so
> what else could it be???)

Reply via email to