Path too long and devcon

[FixitUP]

This is the device ID that devcon reports, but my batch gives me

"Device not disabled." It fails when run as an admin as well.

ACPI\SYN0141\4&B310638&0 : Synaptics PS/2 Port TouchPad

devcon disable ACPI\SYN0141*

This path looks like it has some duplicates and entries that are not really needed.

Can it be thinned out?

I thought it might contribute to the slowness of the laptop.

Andy

%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\system32\WBEM;c:\Program Files\ActivIdentity\ActivClient\;C:\Program Files\Common Files\Roxio Shared\DLLShared\;C:\Program Files\Common Files\Roxio Shared\10.0\DLLShared\;C:\WINDOWS\system32\WindowsPowerShell\v1.0;C:\Program Files\Windows Imaging\;C:\WINDOWS\system32\WindowsPowerShell\v1.0;C:\Program Files\Common Files\Netop\;C:\Program Files\Netop\Vision\XL\;C:\Program Files\QuickTime\QTSystem\

Thanks,

Andy

[Yzöwl]

If your ID contains an ampersand, &, it must be enclosed in doublequotes, ", if your ID is an instance ID then it should be preceded by an at symbol, @.

There is nothing wrong with the length of your path, by all means remove the duplicate entry if you wish however your computer may suffer worse issues if your software cannot find items due to removed locations in the path.

[FixitUP]

If your ID contains an ampersand, &, it must be enclosed in doublequotes, ", if your ID is an instance ID then it should be preceded by an at symbol, @.

There is nothing wrong with the length of your path, by all means remove the duplicate entry if you wish however your computer may suffer worse issues if your software cannot find items due to removed locations in the path.

I tried your suggestions for devcon, but nothing works.

[jaclaz]

Maybe if you actually post your batch, someone can find what is wrong with it (and no, the PATH has nothing to do with it).

jaclaz

[Yzöwl]

I think that the important question here is Why are you disabling your touchpad?

Surely you need a mouse/pointing device! so the only logical reason for disabling the touchpad is that you have attached an alternative device. If that is the case then you should not need to disable the touchpad, it should do it all by itself when you connect the other device.

Some drivers for the Synaptics touchpad have not always included that functionality by default but entering the following single line at a, administrator(if using Vista onwards), console window is reported to provide the required functionality.

REG ADD HKLM\SOFTWARE\Synaptics\SynTPEnh /V DisableIntPDFeature /T REG_DWORD /D 51 /F

You will likely need to reboot your OS in order for the setting to take effect.

[bphlpt]

...

If that is the case then you should not need to disable the touchpad, it should do it all by itself when you connect the other device.

...

Both of my wife's last two laptops, HP and Dell, did not disable the touchpad when another, USB, mouse was plugged in. Both input devices were enabled unless the touchpad was explicitly disabled.

Cheers and Regards

[FixitUP]

ACPI\SYN0141\4&B310638&0 : Synaptics PS/2 Port TouchPad

devcon disable ACPI\SYN0141*

I have used other variations such as using @ before the string.

Andy

[Yzöwl]

...

If that is the case then you should not need to disable the touchpad, it should do it all by itself when you connect the other device.

...

Both of my wife's lasson t two laptops, HP and Dell, did not disable the touchpad when another, USB, mouse was plugged in. Both input devices were enabled unless the touchpad was explicitly disabled.

Cheers and Regards

That is unfortunately expected, OEMs for some reason are responsible for this behaviour.

ACPI\SYN0141\4&B310638&0 : Synaptics PS/2 Port TouchPad

devcon disable ACPI\SYN0141*

I have used other variations such as using @ before the string.

Andy

I cannot help you if you do not follow the advice provided and report back with results.

[FixitUP]

I added it the registry but nothing happens.

The Synaptics touchpad is supposed to turn off while text is being typed, but it does not.

Andy

[jaclaz]

Some reference to chocolate covered bananas and XYZ kind of problems:

http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/put-down-the-chocolate-covered-banana.html

and to the Standard Litany (needed but completely missing in this thread):

http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/problem-report-standard-litany.html

jaclaz

[Yzöwl]

I added it the registry but nothing happens.

The Synaptics touchpad is supposed to turn off while text is being typed, but it does not.

Andy

Your report is exactly what I would have assumed to have been the result since the command line I provided was not intended to do that.

[FixitUP]

I added it the registry but nothing happens.

The Synaptics touchpad is supposed to turn off while text is being typed, but it does not.

Andy

Your report is exactly what I would have assumed to have been the result since the command line I provided was not intended to do that.

From the command line, it said too many command line parameters.

The real question is why devcon can't disable the touchpad when it has worked on other hardware ?

Maybe a bug in devcon or in Synaptics.

[Yzöwl]

Nobody is going to help you unless you start to provide true and proper feedback!

I added it the registry but nothing happens.

From the command line, it said too many command line parameters.

One of the above statements is obviously a lie!

(There is also nothing wrong with the command line I provided))

The real question is why devcon can't disable the touchpad when it has worked on other hardware ?

Maybe a bug in devcon or in Synaptics.

Most touchpad software has a watch/keep alive monitor function which prevents it from being disabled through anything other than its own control panel applet and even then OEMs alter that applet and disable it even more.

In order to prevent the touchpad interfering with typing you can adjust the sensitivity settings through your control panel applet, just keep altering the sensitivity level until it reaches a happy medium between funtionality and sensitivity for typing.

I'm fairly certain that you will never be able to use devcon to disable your touchpad. Your goal is also a relatively 'one time only' action and therefore does not really require a scripting solution anyhow. If you really wanted that then create a script which captures your specific key presses whilst configuring using the GUI

[FixitUP]

Nobody is going to help you unless you start to provide true and proper feedback!

I added it the registry but nothing happens.

From the command line, it said too many command line parameters.

One of the above statements is obviously a lie!

(There is also nothing wrong with the command line I provided))

The real question is why devcon can't disable the touchpad when it has worked on other hardware ?

Maybe a bug in devcon or in Synaptics.

Most touchpad software has a watch/keep alive monitor function which prevents it from being disabled through anything other than its own control panel applet and even then OEMs alter that applet and disable it even more.

In order to prevent the touchpad interfering with typing you can adjust the sensitivity settings through your control panel applet, just keep altering the sensitivity level until it reaches a happy medium between funtionality and sensitivity for typing.

I'm fairly certain that you will never be able to use devcon to disable your touchpad. Your goal is also a relatively 'one time only' action and therefore does not really require a scripting solution anyhow. If you really wanted that then create a script which captures your specific key presses whilst configuring using the GUI

You are making assumptions about a one time use.

You can't help me and there is nothing wrong with that.

I write programs in assembly and found some C++ code from Synaptics to disable and re-enable the touchpad.

The C++ code uses M.S. specific include and header files and I installed a M.S. Compiler.

I found it to be clunky and inefficient. It could not even see .h files in directories full of them. :-)

Take care,

Andy

[Yzöwl]

You are making assumptions about a one time use.

You can't help me and there is nothing wrong with that.

I have provided you with help by answering your questions.

To recap:

• You asked if you could remove items from your %PATH%
  I gave you an answer to which I've received no recognition of having provided
  
• I provided you with possible corrections for your devcon command
  You told me that it didn't work
  Since devcon was not working I looked into other solutions for you. In order to do that I was forced to make assumptions since you have been less than forward with providing sufficient information on which to base our replies.
  
• I gave you another solution by implementing a registry change.
  You said that nothing happened
  You later stated that something did happen because you got an error message about the command line I gave you.
  There was nothing wrong with the command line I provided, however the solution was not appropriate for your purpose because you then decided to furnish us with a little more information. i.e. disable during typing.
  
• I responded with both a method for managing that problem and a scripting idea for solving your issue.
  You have the audacity to suggest I cannot help.
  One thing is for sure after the courtesy I've shown thus far, and your lack of it I will certainly think twice about providing you with any more help!