Problems with Touchpad,keyboard and USB after Ideacom update (solu

[Zelator]

No please i have done everything as per instruction from toshiba site (the
driver was not varified from microsoft for the touchpad ) the touchpad is
connected with a thin strip directly to the mother board .
The mouse i have pluged in is to usb is not optical like windows is saying
..And the keyboard deactivates when you press any button .....and works fine
after being put in standby .
I have one update from Driver detective that i cannot update for the life
of me and it just so happens it is a standard usb bus controller.

I have uninstalled the driver for the touchpad and windows /driver detective
/and another progam device detector is all saying unknown device .I also
have a none plug and play hidden driver (amongst a list of ) that has a
yellow ! called "serial".

The internet is full of references to the Alps touchpad and XP problems but
before i installed the update ideacom (yes pa i shouldnt of ) it was working
normally .

 

[Zelator]

Whether this is of any relevance i dont know but i have a hid compliant mouse
showing ..........and also under usb Human interface divice i have a USB
human interface device showing ............should that be (i only have the
one mouse attatched and nothing else

 

[Paul]

Whether this is of any relevance i dont know but i have a hid compliant mouse
showing ..........and also under usb Human interface divice i have a USB
human interface device showing ............should that be (i only have the
one mouse attatched and nothing else

My theory was, that the Alps device is a HID (Human Interface Device), which means
with no drivers installed, it may still show up in Device Manager.
I was hoping by now, between Device Manager and UVCView, you'd
have some idea how it was connected. (When I looked at some of the
Cirque info, the connector size is the same for PS/2 and USB, so
you might not even be able to tell by looking for physical differences.)

With regard to the USB, have you tested the USB with anything
else ? Have you looked in Device Manager, like I suggested ?
Do you have entries under the USB section, corresponding
to the USB ports ? These logic blocks provide support for
operation at USB 1.1 and USB 2.0 rates. A port can operate
at one rate of the other, but not both at the same time. That
is why, in UVCView, you see twice as many entries, as you might
expect based on the number of ports the chipset has got. I have
a total of eight ports, and one USB2.0 logic block handles
USB2 duties for all of them. The Alps won't even need USB2,
but will run just fine with USB1.1. That is typical for HID
devices like mice and keyboards.

VIA Rev 5 or later USB Universal Host Controller (USB 1.1, one per two physical ports)
VIA Rev 5 or later USB Universal Host Controller (USB 1.1, one per two physical ports)
VIA Rev 5 or later USB Universal Host Controller (USB 1.1, one per two physical ports)
VIA Rev 5 or later USB Universal Host Controller ( USB 1.1, one per two physical ports)
VIA USB Enhanced Host Controller (USB 2.0, one logical device handles all physical ports)
USB Root Hub (there are five of these)

The top four use usbhub.sys, usbport.sys, usbuhci.sys, usbui.dll.
The fifth uses usbhub.sys, usbport.sys, usbehci.sys, usbui.dll, hccoin.dll

The files all belong to Microsoft, so the default driver handles
the USB ports with no separate installation by me.

If I plug in my USB (test) mouse, and use UVCView, this is what I get.

"HID Compliant Mouse" - my cheesy two button mouse, a freeby at a tech show

*******
---===>Device Information<===---
English product name: "HID-compliant Mouse (USB)"

ConnectionStatus:
Current Config Value: 0x01 -> Device Bus Speed: Low
Device Address: 0x02
Open Pipes: 1

===>Endpoint Descriptor<===
bLength: 0x07
bDescriptorType: 0x05
bEndpointAddress: 0x81 -> Direction: IN - EndpointID: 1
bmAttributes: 0x03 -> Interrupt Transfer Type
wMaxPacketSize: 0x0003 = Invalid bus speed for USB Video Class
bInterval: 0x10

===>Device Descriptor<===
bLength: 0x12
bDescriptorType: 0x01
bcdUSB: 0x0100
bDeviceClass: 0x00 -> This is an Interface Class Defined Device
bDeviceSubClass: 0x00
bDeviceProtocol: 0x00
bMaxPacketSize0: 0x08 = (8) Bytes
idVendor: 0x03EE = Mitsumi
idProduct: 0x6407
bcdDevice: 0x0110
iManufacturer: 0x01
English (United States) "Mitsumi"
iProduct: 0x02
English (United States) "HID-compliant Mouse (USB)"
iSerialNumber: 0x00
bNumConfigurations: 0x01

===>Configuration Descriptor<===
bLength: 0x09
bDescriptorType: 0x02
wTotalLength: 0x0022 -> Validated
bNumInterfaces: 0x01
bConfigurationValue: 0x01
iConfiguration: 0x00
bmAttributes: 0xA0 -> Bus Powered
MaxPower: 0x32 = 100 mA

===>Interface Descriptor<===
bLength: 0x09
bDescriptorType: 0x04
bInterfaceNumber: 0x00
bAlternateSetting: 0x00
bNumEndpoints: 0x01
bInterfaceClass: 0x03 -> HID Interface Class
bInterfaceSubClass: 0x01
bInterfaceProtocol: 0x02
CAUTION: This may be an invalid bInterfaceProtocol
iInterface: 0x00

===>HID Descriptor<===
bLength: 0x09
bDescriptorType: 0x21
bcdHID: 0x0100
bCountryCode: 0x00
bNumDescriptors: 0x01
bDescriptorType: 0x22
wDescriptorLength: 0x0032

===>Endpoint Descriptor<===
bLength: 0x07
bDescriptorType: 0x05
bEndpointAddress: 0x81 -> Direction: IN - EndpointID: 1
bmAttributes: 0x03 -> Interrupt Transfer Type
wMaxPacketSize: 0x0003 = Invalid bus speed for USB Video Class
bInterval: 0x10
*******

"HID Interface Class" is something the OS handles with its own class
driver. When using that mouse, I just plug it in, and no driver
is needed. That means the USB stack has the software in place to handle
a HID device.

I don't really know how your Alps device is connected logically. It could be
a HID at the lowest layer. The provided driver may be present to "filter" the
information coming from it. Or the provided driver may just be window
dressing. Since the Alps driver has none of the usual stuff I see
in driver packages, that is why I suspect it isn't your usual
low level driver.

Paul

 

[PA Bear [MS MVP]]

<sigh>

Whether this is of any relevance i dont know but i have a hid compliant
mouse showing ..........and also under usb Human interface divice i have a
USB human interface device showing ............should that be (i only have
the one mouse attatched and nothing else

 

[Paul]

<sigh>

If he wasn't reinstalling the OS from scratch, then
telling him to roll back the driver makes sense.
It appears to be too late for that now, so
the experiments continue. At least, I think
that is what he is doing - it's hard to be
sure.

Paul

 

[Zelator]

Right i have digressed .I have corrected the none plug and play fault with
updateing a driver that asked for the XP disc .After puting in the disc the
exclamation mark gone .Moving onto touchpad ,i have the latest driver but
when i uninstal the present driver and try to install the newer one (off
toshiba site ) i am getting a prompt.
SetupDienumDriverinfo code = 0x00000103

googleing this it is common and is reported to be a serice pack 3 issue .

and PA Bear if you are not interested please refrain from thoughs who
helpfully are .

My low and common ways will not be detered from participation in a forum
that is there to help .Not for to take morral high ground and say "well then
you shouldnt have done it in the first place "...........evedidently if you
care to google my issue it is so common people are making programs and
charging money to correct foolish people like you concider me to be .Or is
that the issue here i should be paying for information .

 

[Paul]

Right i have digressed .I have corrected the none plug and play fault with
updateing a driver that asked for the XP disc .After puting in the disc the
exclamation mark gone .Moving onto touchpad ,i have the latest driver but
when i uninstal the present driver and try to install the newer one (off
toshiba site ) i am getting a prompt.
SetupDienumDriverinfo code = 0x00000103

googleing this it is common and is reported to be a serice pack 3 issue .

and PA Bear if you are not interested please refrain from thoughs who
helpfully are .

My low and common ways will not be detered from participation in a forum
that is there to help .Not for to take morral high ground and say "well then
you shouldnt have done it in the first place "...........evedidently if you
care to google my issue it is so common people are making programs and
charging money to correct foolish people like you concider me to be .Or is
that the issue here i should be paying for information .

SetupDiEnumDriverInfo is mentioned here. This seems to have something to do
with the driver side of things, rather than the device itself. Hard to
tell from this article.

http://msdn.microsoft.com/en-us/library/aa906293.aspx

This Linux article confirms that at least some touchpads will
operate as HID devices without a driver. When a driver is
installed, it enhances the operation. Which suggests the
driver is a shim, intercepting data coming from the HID.

http://web.telia.com/~u89404340/touchpad/

So the first question would be, whether the Touchpad does anything,
without the fancy Alps driver installed. I would have expected
to see the Touchpad in Device Manager, before the Alps
software is installed.

So if you click the buttons on the Alps, do they register
as mouse clicks ? What entry do you see in Device Manager
for the Alps.

The Alps is a filter driver, rather than a true driver.

[MouFilter_Inst.HW.AddReg]
HKR,,"UpperFilters",0x00010000,"ApfiltrService"

You would think, if there was a strong correlation between
SP3 and the Alps device, they'd be "dropping like flies".
I didn't find that many hits in a few searches. At least
some people have hardware trouble, such as a loose cable from
the touchpad to the rest of the laptop. One user got a
different response, after shutting down and removing the
battery (presumably removing all power from the touchpad
for a while).

So I'd want to start by at least confirming the device is
there and working.

Paul

 

[Zelator]

Paul i would like to thankyou very much for your patience and time /effort
for concerning yourself with my problem ,but i have to hold my hands up and
say i am limited in the tech department and i have passed my trouble to
someone who knows a lot more than i do .As far as the touchpad not working ,i
might have suspected this if it was a sole problem but it issnt as the
keyboard has problems as well (all after an update that in hind sight was for
vista so confuses me why i was offered this in the first place ....but a
lesson learned ) Also the keyboard works 100% in bios ...........and add to
this fact that one forum says that this is identical to a problem he has
fixed and needs to fix again but cannot find the program anymore of Toshiba
site that was specificaly for reactivating touchpad after downgrading from
Vista (i believe compatability issues resulted in being allowed to downgrade
one time ago).So the touchpad seems to me to be deactivated in some way by
the update i wrongfully installed .

Anyway i'm gonna close this thread now but hey i learned a lot from what you
werte saying and you were correct i was mearly trialing and erroring .

Right i have digressed .I have corrected the none plug and play fault with
updateing a driver that asked for the XP disc .After puting in the disc the
exclamation mark gone .Moving onto touchpad ,i have the latest driver but
when i uninstal the present driver and try to install the newer one (off
toshiba site ) i am getting a prompt.
SetupDienumDriverinfo code = 0x00000103

googleing this it is common and is reported to be a serice pack 3 issue .

and PA Bear if you are not interested please refrain from thoughs who
helpfully are .

My low and common ways will not be detered from participation in a forum
that is there to help .Not for to take morral high ground and say "well then
you shouldnt have done it in the first place "...........evedidently if you
care to google my issue it is so common people are making programs and
charging money to correct foolish people like you concider me to be .Or is
that the issue here i should be paying for information .

SetupDiEnumDriverInfo is mentioned here. This seems to have something to do
with the driver side of things, rather than the device itself. Hard to
tell from this article.

http://msdn.microsoft.com/en-us/library/aa906293.aspx

This Linux article confirms that at least some touchpads will
operate as HID devices without a driver. When a driver is
installed, it enhances the operation. Which suggests the
driver is a shim, intercepting data coming from the HID.

http://web.telia.com/~u89404340/touchpad/

So the first question would be, whether the Touchpad does anything,
without the fancy Alps driver installed. I would have expected
to see the Touchpad in Device Manager, before the Alps
software is installed.

So if you click the buttons on the Alps, do they register
as mouse clicks ? What entry do you see in Device Manager
for the Alps.

The Alps is a filter driver, rather than a true driver.

[MouFilter_Inst.HW.AddReg]
HKR,,"UpperFilters",0x00010000,"ApfiltrService"

You would think, if there was a strong correlation between
SP3 and the Alps device, they'd be "dropping like flies".
I didn't find that many hits in a few searches. At least
some people have hardware trouble, such as a loose cable from
the touchpad to the rest of the laptop. One user got a
different response, after shutting down and removing the
battery (presumably removing all power from the touchpad
for a while).

So I'd want to start by at least confirming the device is
there and working.

Paul