mouse problems

Joined
25 Oct 2010
Messages
154
Reaction score
19
Country
United Kingdom
Also strictly speaking a USB hub is not enumerated the same as a proper HID (such as mice, keyboards, gamepads etc) within the WDK.
 
Joined
25 Jan 2010
Messages
4,147
Reaction score
357
Location
Cornwall
Country
United Kingdom
Also strictly speaking a USB hub is not enumerated the same as a proper HID (such as mice, keyboards, gamepads etc) within the WDK.

No, but you get my point. Or you should do by now.

It's almost certainly a corrupted registry, nothing more. USB is designed to 'just work', and so it usually does.

Open up the device manager, go to the view menu and have it show hidden devices, and remove (that is, 'uninstall') any entries for mice or HID devices which you do not have connected. If you can't tell, don't worry, if it turns out to be the mouse you're using you just unplug it and plug it back in.

If that doesn't work it'll require some more drastic cleaning, and I honestly can't remember how (I haven't seen this happen in a long time).
 
Joined
25 Oct 2010
Messages
154
Reaction score
19
Country
United Kingdom
Monkeh

Ok it could well be a corrupted registry entry, Id only expect this when there been some device enumeration that means that windows sees a device classifies it and then stores this information (you are right, within the registry).

No matter what you unplug or uninstall (short of the bus or device driver which would hopefully remove this UUID classification of the device) then ti will always attempt to use the same upon re-insertion.

My point is that this mistaken enumeration is normally due to the bus driver passing on invalid information to "Windows" because the Windows driver does not contain the proprietary add on bit of code that entails it to discover the device properly.

Thus, and I have also seen this, even a full reinstall of windows and therefore a destructive registry, doesn't help.

Ideally you'd research and assure that you have the valid usb bus driver an then also, do as you mention, and remove the "cached" registry entries and let the PnP rediscover the (hopefully now) valid UUID's
 
Joined
25 Jan 2010
Messages
4,147
Reaction score
357
Location
Cornwall
Country
United Kingdom
The odds of the controller not being a bog standard chipset-integrated UHCI or OHCI example are so insane that I really don't see your theory (which, as I said, is precisely why we have OHCI and EHCI, to allow USB to live up to its name) being realistic.

And please, if you work or have worked for a company producing such a device, name and shame. They deserve it.
 
Joined
25 Oct 2010
Messages
154
Reaction score
19
Country
United Kingdom
And such companies do exist, no I don't work for one, however I have coded such "mappings" between "proprietary" and "standards".

And its more prevalent then you'd think.

And I didn't say they were not buffoons , just that I am not naming them in a public forum when my livelihood depends on coding.

Just to highlight, to take my example of *EAP, there is obviously the standards but then there are proprietary methods of this Extensible Protocol. Are these manufacturers buffoons?
 
Joined
25 Jan 2010
Messages
4,147
Reaction score
357
Location
Cornwall
Country
United Kingdom
Just to highlight, to take my example of *EAP, there is obviously the standards but then there are proprietary methods of this Extensible Protocol. Are these manufacturers buffoons?

EAP is not comparable to OHCI. OHCI is a fixed standard. Any additional functionality over OHCI, UHCI, or EHCI should in no way affect normal USB operation.

This is the mobo manual

http://uk.ts.fujitsu.com/rl/service...oards/asus/P5GD1-FM/asus-P5GD1-FM.pdf[/QUOTE]

There you go, it's an ICH6. Bog standard UHCI/EHCI controller. The only thing the Intel 'drivers' do is change the name in the device manager.
 
Joined
25 Oct 2010
Messages
154
Reaction score
19
Country
United Kingdom
Oops, sorry you're right its EHCI/UHCI.

Getting SATA standards mixed up now. I think I need a coffee.
 
Joined
25 Oct 2010
Messages
154
Reaction score
19
Country
United Kingdom
I still don't think the route of a destructive reinstall that Holmslaw was going down is the right option though, either fix the driver if need be (which it would appear not in this case although I might still run one of my debug codings across the driver to see if it really is a true EHCI in this fujitsu siemens case.

Or. remove the "cached" registry entries as to what Windows thinks that device UUID actually is.

Not sure if this information could be incorrect other than via miscommunication, whats your thoughts ?
 
Joined
25 Jan 2010
Messages
4,147
Reaction score
357
Location
Cornwall
Country
United Kingdom
I still don't think the route of a destructive reinstall that Holmslaw was going down is the right option though, either fix the driver if need be (which it would appear not in this case although I might still run one of my debug codings across the driver to see if it really is a true EHCI in this fujitsu siemens case.

Or. remove the "cached" registry entries as to what Windows thinks that device UUID actually is.

Not sure if this information could be incorrect other than via miscommunication, whats your thoughts ?

I agree, a reinstall is not the first choice here. EHCI is, btw, not used unless he has a remarkably fancy mouse.

Cleaning the devices out of the registry is the first thing to try.
 
Joined
25 Jan 2010
Messages
4,147
Reaction score
357
Location
Cornwall
Country
United Kingdom
On a aide, how is EAP(TLS) any different to OHCI?

EAP is a framework. EAP-TLS is a standardised method.

You can use EAP with any method you like, standardised or otherwise. Call it EAP-TLS when it's not, and you're lying. Advertise a USB host controller as OHCI and then not be compatible with OHCI, and you're lying. Say you 'support EAP' and use a proprietary, non-standardised method, and you're merely a dodgy git, but the purchaser is at as much fault as the manufacturer for not checking into the method.
 
Sponsored Links
Top