USB problems... (Just WinXPe or ?? )

[Thomas Johansen]

Hi

I have seen the following with USB devices (USB keys and USB Keyboard)

In some cases (not often, but it happens), when I insert an USB key or
keyboard nothing happens (No detection). I then re-insert the device or
reboot the PC and then the USB device is enumerated and working.

I have included the following componets to my image:

USB Human Interface Device
USB Root Hub
USB User Interface
Generic USB Composite Device
Generic USB Hub
Generic USB Input Device Support (Macro)
HID Keyboard Device
HID-compliant consumer control device
VIA Rev 5 or later USB Universal Host Controller


Is this an known problem with WinXPe ? Is it a general Win2k/XP/XPe thing ?

Is it a device driver bug ? (Low level / high level )

Is there any solution ?

I seems to remember that my Win2k machine sometimes does the same.. !!!

Thomas

 

[Tom Barclay]

Is the keyboard plugged directly into one of the computer's USB sockets, or
is it plugged into a hub? Try plugging it directly into the computer if it's
not already there. Also, check to see if there's a setting to turn on USB
emulation in your BIOS. If the system is fairly old (more than 2 or 3
years), you may want to check with the computer manufacturer (or motherboard
website if it's home built) to see if there's a BIOS update which
specifically addresses this problem.

 

[Thomas Johansen]

Is the keyboard plugged directly into one of the computer's USB sockets,
or

is it plugged into a hub? Try plugging it directly into the computer if

it's

Direct pluged. Do not use HUB

not already there. Also, check to see if there's a setting to turn on USB
emulation in your BIOS. If the system is fairly old (more than 2 or 3
years), you may want to check with the computer manufacturer (or motherboard
website if it's home built) to see if there's a BIOS update which
specifically addresses this problem.

Its not an BIOS problem. Itøs not just keuboard but allso USB keys.
The USB keyboard is working great in BIOS screen.
IT allso works the must of the time but time to time it does not when pluged
into the USB

 

[Richard Urban]

Label the computer port when you "first" plug in and use the device.
Whenever you use the device, make certain you plug it into the SAME port. If
you don't, the system will have to re-initialize itself for the new port.
This is also why many people end up with 15 entries for a single device
(i.e.: a scanner). Each time you plug it into a different port it is seen as
NEW.

--
Regards:

Richard Urban

aka Crusty (-: Old B@stard

 

[Mario Dambauer]

Hi Thomas...

I have noticed the same problem...

I also have the usb devices direct plugged on.

The problem occures rarely but it is there.
In my case it was also keyboard und USB WLAN Adapters...


I hope someone could throw some light on this topic!
Mario

 

[Mario Dambauer]

Hi Richard, you are right that it is better to plug in a devie always on the
same port.
But it should also work if you use another port!

By the way, this has nothing to do, that sometimes the usb device is not
recogniced from the system.

At my tests, the problem occured also on the same port!
Mario

 

[Thomas Johansen]

Label the computer port when you "first" plug in and use the device.

Whenever you use the device, make certain you plug it into the SAME port. If
you don't, the system will have to re-initialize itself for the new port.
This is also why many people end up with 15 entries for a single device
(i.e.: a scanner). Each time you plug it into a different port it is seen as
NEW.

It's allways in the same port. It's actally in the port when the PC boots.
But sometime the keyboard og USB key isn't working in WInXPe until I
re-insert it...

 

[Slobodan Brcin \(eMVP\)]

If device has serial number then it should not matter which port you choose.
Also there are LL registry switches that will enable you to port based
enumeration instead or serial number enum.

Regards,
Slobodan

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Have an opinion on the effectiveness of Microsoft Embedded newsgroups? Tell
Microsoft!
https://www.windowsembeddedeval.com/community/newsgroups
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 

[Slobodan Brcin \(eMVP\)]

In my opinion USB stack is the worst driver stack I have seen in XP
operating system up till today. There are just too many issues and fixing
one creates another.

Try using Q823025. Also try not using Q823025.
I can't use Q823025 drivers since I got some specific problems.

Regards,
Slobodan

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Have an opinion on the effectiveness of Microsoft Embedded newsgroups? Tell
Microsoft!
https://www.windowsembeddedeval.com/community/newsgroups
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 

[Mario Dambauer]

Hi Slobodan

I can't image that this QFE has any effect to my system...
I am NOT using EWF.

any other ideas?
Thanks
Mario

 

[Slobodan Brcin \(eMVP\)]

I have shifted one line in my notes :$
You are absolutely right that EWF has nothing to do with this problem.

Security Update for Windows XP Embedded with SP1 (822603)
QFE: request for XPE componentization of Q822603 - Availability of the
Windows XP SP1 USB 1.1 and 2.0 Update

I had to go so I just typed without actually rechecking, sorry.

Regards,
Slobodan

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Have an opinion on the effectiveness of Microsoft Embedded newsgroups? Tell
Microsoft!
https://www.windowsembeddedeval.com/community/newsgroups
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 

[Mario Dambauer]

I have checked my notes, and it seemes that this problem is caused by
someting else and not 822603 (in my case).
At the master which is currently on the market, I havent applied this QFE to
the system....

We have currently also problems with our USB Elo Touch Screens...
From time to time the touch screen is not reacting vor 2s to 2min...

I think there are really some problems at the USB driver stack...


Has MS noticed this problem?
Are they doing anything on this problem?

Mario

 

[Mario Dambauer]

My post has gone away.. so I post once more...

It seemes that this problem is caused by someting else and not 822603 (in my
case).
At the master which is currently on the market, I have'nt applied this QFE
to
the system....

We have currently also problems with our USB Elo Touch Screens...
From time to time the touch screen is not reacting vor 2s to 2min...
(perhaps has something to do with the usb problems..)

I think there are really some problems at the USB driver stack...


Has MS noticed the USB problems?
Are they doing anything on this problem?

Mario

 

[Slobodan Brcin \(eMVP\)]

Hi Mario,

I have no idea what MS is doing about improving USB drivers for XPe. (Maybe
for Longhorn they are writing something new).
There are 6-7 undocumented registry values in USB drivers that can be used
for some tweaking. (I guess that they are there for testing purposes or
solving some issues).

Few of these values can be found searching the news groups, others can't be
found anywhere.

http://groups.google.com/groups?q=Andy+USB+group:microsoft.public.windowsxp.
embedded.*&hl=en&lr=&ie=UTF-8&oe=UTF-8&group=microsoft.public.windowsxp.embe
dded.*&scoring=d&selm=%23xV4ai6BEHA.3360%40TK2MSFTNGP11.phx.gbl&rnum=1

Has MS noticed the USB problems?
Are they doing anything on this problem?

Well you have new QFE available it solves some problems and introduces new
problems so you should try it, for you it will probably bring some
improvements.

Regards,
Slobodan

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Have an opinion on the effectiveness of Microsoft Embedded newsgroups? Tell
Microsoft!
https://www.windowsembeddedeval.com/community/newsgroups
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 

[Mario Dambauer]

Thanks Slobodan...

I will see if I can find out more...

Mario