Page 1 of 1

Can't get scrolling done with a4tech WinEasy 4D mouse

Posted: Sat 12 Dec 2009, 02:05
by skinnie
Hi guys,I have an a4tech wineasy 4d mouse,it has 2 wheels (one for vertical scrolling and other for horizontal scrolling) and 3 buttons (2 "normal" and one on the left side,but can't get the right xorg config to enable scrolling..
On xorg page I found this config:

Section "InputDevice"
Identifier "WinEasy"
Driver "mouse"
Option "Device" "/dev/mouse"
Option "Protocol" "IMPS/2"
Option "Buttons" "7"
Option "ZAxisMapping" "4 5 6 7"
EndSection

but,first,I have to use protocol microsoft (because it is connect on a COM port via an PS2 adapter) and seccond,when I put the option "Buttons" "7" and restart xorg,it won't go..
I tried that example,without the "Buttons" option,but no scroll..
Any suggestions?
This is the mouse:
Image

Posted: Sun 13 Dec 2009, 15:01
by skinnie
with puppy 4,3,1 it doesn't happen..any thought how can I make it work on 4,2 based puppies? (like puppy arcade v5 or turbopup extreme)
Thanks

Re: 2 Scroll wheel mouse and xorg

Posted: Sun 13 Dec 2009, 20:12
by jason.b.c
skinnie wrote:
but,first,I have to use protocol microsoft (because it is connect on a COM port via an PS2 adapter)


Why?????

Re: 2 Scroll wheel mouse and xorg

Posted: Sun 13 Dec 2009, 20:16
by skinnie
jason.b.c wrote:
skinnie wrote:
but,first,I have to use protocol microsoft (because it is connect on a COM port via an PS2 adapter)


Why?????
because the motherboard that I am using doesn't have ps2 ports...and the mouse is ps2..
it is a thing like this one :
Image

Posted: Mon 14 Dec 2009, 09:20
by disciple
Have you tried this?

Code: Select all

 Option "Protocol" "Auto"
Also try

Code: Select all

 Option "Protocol" "IMPS/2"
or even some of the other ones in the comment in this post

Posted: Mon 14 Dec 2009, 12:58
by Oakems
I only have one scroll wheel, but my setup is like this:

Code: Select all

Section "InputDevice"
	Identifier  "Mouse0"
	Driver      "mouse"
	Option	    "Protocol" "ExplorerPS/2" #mouse0protocol
	Option	    "Device" "/dev/mouse"
	#Option      "Emulate3Buttons"
	#Option      "Emulate3Timeout" "50"
	 Option     "Buttons" "7" 
	Option      "ZAxisMapping" "4 5" #scrollwheel
EndSection
I'd guess yours should look something like this:

Code: Select all

Section "InputDevice"
	Identifier  "Mouse0"
	Driver      "mouse"
	Option	    "Protocol" "ExplorerPS/2" #mouse0protocol
	Option	    "Device" "/dev/mouse"
	#Option      "Emulate3Buttons"
	#Option      "Emulate3Timeout" "50"
	 Option     "Buttons" "7" 
	Option    "ZAxisMapping" "4 5"#scrollwheelVertical
      Option    "YAxisMapping" "6 7" #scrollwheelHorizontal
EndSection
I'm really not sure about the "YAxisMapping" I know 6 and 7 scroll horizontally, but I would think you'd need two separate options to have both Vertical and Horizontal scrolling; like I say I know 6 and 7 work for horizontal scrolling, just not sure if they should be mapped to YAxisMapping? Maybe it should be XAxisMapping? But I'd think they'd have separate options. Any who, just my two cents, hope it helps.

Edit: I've just ran a little test to see if YAxisMapping would work, it does, but the weird thing is it will only scroll vertically no matter which numbers are placed after it. So I would suggest adding this:

Code: Select all

Option    "ZAxisMapping" "6 7"#scrollwheelHorizontal
Option    "YAxisMapping" "4 5" #scrollwheelVertical
to get your scrolling working.

Posted: Mon 14 Dec 2009, 13:54
by skinnie
couldn't be just a bug in 4.2?because the config that I posted,worked very good in 4.3.1..

Posted: Mon 14 Dec 2009, 15:21
by Oakems
Does the code above not work then?

I wouldn't necessarily say it was a bug, unless you're talking about the 4.2 main release? (and even then, it may not have been implemented yet in 4.2?) Maybe there's is a mouse driver that is present in 4.3.1 but not in the 4.2 puplets? If that were the case then you should be able to import that driver from 4.3.1? The thing with puplets is that they are made by us, for us. So things that are in the main release are not automatically in the puplets. If you still have 4.3.1 and can compare the drivers, you may find something, then you can just copy it over. Also there is a program in Puppy that can compare files and I think it compares filesystems as well. That could be useful and save you some time searching, but I'm not very familiar with it, and I'm not even sure of its name? Ultimately the best thing to do is to find out why it works well in 4.3.1 and copy over what you need for it to work in the puplet.

Code: Select all

lsmod
Will show you all the modules you have loaded so you could compare 4.2 and 4.3.1 to see what's different?

Posted: Mon 14 Dec 2009, 19:38
by disciple
couldn't be just a bug in 4.2?because the config that I posted,worked very good in 4.3.1..
Ah, you should have told us that.
If that were the case then you should be able to import that driver from 4.3.1?
If so, you wouldn't be able to copy it... you would need to get the kernel source and the devx and compile it... assuming it was available for the 4.2 kernel.