Post by J. P. Gilliver (John)Post by Gene WirchenkoOn Tue, 13 Jun 2017 19:53:10 +0100, "J. P. Gilliver (John)"
Post by J. P. Gilliver (John)Post by Gene WirchenkoOn Fri, 9 Jun 2017 19:35:41 +0200, "Linea Recta"
[snip]
Post by Linea RectaHave a look at Configuration - Mouse - tab "Buttons" - list "other pointing
devices". Choose your touch pad. Go to tab "device settings" and you find a
button to disable/enable the chosen touch pad device.
Oh, I can disable the touchpad if there is another mouse, and I
have that set. I meant that I want to disable the tapping on the
touchpad causing a click with the touchpad otherwise working.
[]
I think this is the second time I've written this in two days -
Control Panel, Hardware and Sound, Mouse.
If you only have five tabs - Buttons, Pointers, Pointer Options, Wheel,
and Hardware - you haven't got a touchpad driver, so are using the
default mouse driver (where tapping defaults to on). Get the touchpad
driver ideally from your manufacturer, failing that the default one from
Symantec (which I've never known not to work). Once that's installed
properly, you should have a sixth tab under Mouse: Device Settings.
Apparently, I do have a touchpad driver. It is identified as
"Elan Smart-Pad" version "ETDWare PS/2-X64 10.6 10.8_WHQL".
It has five tabs Buttons, Pointers, Pointer Options, Hardware,
and ELAN. The last tab has "Disable when external USB pointing device
plug in" [their broken English]. There is nothing else to covering
tapping.
I suppose I will have to look up that Symantec driver.
[]
Ah. First time I've ever encountered another touchpad manufacturer. I
hope the Symantec driver _does_ work for you - make
backups/images/restore points/whatever first! (If it doesn't, might be
worth removing the Elan driver and trying again.)
Synaptic != Symantec (buyer and crusher of programs, such as the PowerQuest acquisition or Ghost)
Touchpads start out as HID devices when first powered up.
The various brands of devices can use Filter Drivers
to implement virtual controls. The filter driver
analyzes coordinates in x:y space, and the time
sequence, to extract gestures or virtual button
clicks or taps.
It was never clear to me, how these filter drivers
"bind" to a particular device. There was a driver pushed
out in Windows Update once, which disabled things like
keyboards, because the filter driver was applying itself
to every HID it could find. So while on some drivers, you
can see in the INF it's making an effort to sort them
out, not all these filter drivers are written with
equal skill. And the INF can admit to searching for
a number of different "busses". For example, a laptop SuperI/O
with two PS/2 ports, could have keyboard on one port, and
Touchpad on the other, and the filter driver just grabs
the second PS/2. I don't think PS/2 has quite as strong
a Plug and Play identification system as say USB would.
On USB, you have VID/PID and Class, which gives better
opportunity for selecting something to bind to.
You should be able to look at the INF file, and
decide whether the driver writer had some clues or not.
Or whether the driver you haven't installed yet,
looks to be a little too greedy.
If you're working on a system where the driver was
installed for you, there might not be much to go by.
The INF folder contains the INF files of installed
drivers. The filenames are converted to "OEM23.INF"
format, to prevent naming collisions, but this
also hampers user attempts to find the touchpad
filter driver. You can try doing a content search
of all the OEMxx.INF files, looking for Synaptic
or touchpad or Elan or the like, to narrow down which
OEMxx.INF file, corresponds to the current operational
filter driver for the touchpad.
Paul