USB debugging, some ports work some don't.

  • Thread starter Thread starter NiceGuy999
  • Start date Start date
N

NiceGuy999

Hi,

I am hoping someone might have a suggestion to help me get past a
problem I am having with USB support. I have 8 USB ports in my
system, 2 sets of 2 on the back of the unit and 2 sets of 2 internal on
the motherboard. 6 of the 8 work in all configurations, the first 2
on the back of the unit fail to work with Aladdin USB security keys.

I have tested those 2 ports (USB 0&1) and they work with Mice,
Keyboards, External HD's, and thumb drives. The only device I have
found that will not work is the Aladdin USB dongles. I installed XP
Pro on the system add those 2 ports do work with Aladdin USB dongles
there. That makes me confident the hardware itself works and that I
have some kind of software problem.

I have an image built around the xp pro emulation files from
xpefiles.com (very handy testing tool) and that exhibits the same
behavior where only the first 2 USB ports refuse to detect the Aladdin
USB dongle. It gives the "One of your USB devices has malfunctioned"
message and detects it as an "unknown device". The other 6 ports in
the system detect it and work correctly.

That makes me feel more confident that I am not missing some generic
USB component, though not totally confident as I don't know that much
about USB support in general. There is one other USB related issue
that doesn't affect my current setup but may be somehow related. If my
USB 2.0 support is disabled in the bios and the USB ports are forced
into 1.1 mode, nothing works in those two ports (mice, keyboards,
external drives, ect). The dongle is in 2.0 mode but I find it odd
that those are the "affected" ports in that case as well.

I am at a bit of a loss as to what to try next. This is an ITOX
g4g100n mini-itx motherboard and this is the strangest problem I have
found with it so far. I am going to focus in on what makes those two
ports different and look closer at the 1.1 issue and hope it gives me a
clue. If anyone has any suggestions I would really love to hear them.


Thanks!!

Will Cunningham
 
Here is the info from my setupapi.log file, I figured it might be
useful to anyone who might have a suggestion. The first two sections
are where it works as expected in the working slots. The final section
is where I try it in the slots that aren't working.

Thanks again!

Will


[2006/10/10 23:37:43 1060.3 Driver Install]
#-019 Searching for hardware ID(s):
usb\vid_0529&pid_0001&rev_0216,usb\vid_0529&pid_0001
#-018 Searching for compatible ID(s):
usb\class_ff&subclass_00&prot_00,usb\class_ff&subclass_00,usb\class_ff
#-198 Command line processed: C:\WINDOWS\system32\services.exe
#I022 Found "USB\Vid_0529&Pid_0001" in C:\WINDOWS\inf\oem1.inf; Device:
"Aladdin USB Key"; Driver: "Aladdin USB Key"; Provider: "Aladdin
Knowledge Systems"; Mfg: "Aladdin Knowledge Systems"; Section name:
"aksusb".
#I023 Actual install section: [aksusb.NT]. Rank: 0x00000001. Effective
driver date: 07/27/2005.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [aksusb] in
"c:\windows\inf\oem1.inf".
#I320 Class GUID of device remains:
{36FC9E60-C465-11CF-8056-444553540000}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-166 Device install function: DIF_INSTALLDEVICEFILES.
#I124 Doing copy-only install of "USB\VID_0529&PID_0001\4&BDE6317&0&2".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [aksusb.NT.Interfaces] from
"c:\windows\inf\oem1.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "USB\VID_0529&PID_0001\4&BDE6317&0&2".
#I121 Device install of "USB\VID_0529&PID_0001\4&BDE6317&0&2" finished
successfully.


[2006/10/10 23:37:47 1060.7 Driver Install]
#-019 Searching for hardware ID(s): usb\hasp
#-018 Searching for compatible ID(s): usb\hasp
#-198 Command line processed: C:\WINDOWS\system32\services.exe
#I022 Found "USB\Hasp" in C:\WINDOWS\inf\oem0.inf; Device: "Aladdin
HASP Key"; Driver: "Aladdin HASP Key"; Provider: "Aladdin Knowledge
Systems"; Mfg: "Aladdin Knowledge Systems"; Section name: "akshasp".
#I023 Actual install section: [akshasp.NT]. Rank: 0x00000000. Effective
driver date: 07/27/2005.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [akshasp] in
"c:\windows\inf\oem0.inf".
#I320 Class GUID of device remains:
{36FC9E60-C465-11CF-8056-444553540000}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-166 Device install function: DIF_INSTALLDEVICEFILES.
#I124 Doing copy-only install of "USB\HASP\5&142CDEBF&0&00".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [akshasp.NT.Interfaces] from
"c:\windows\inf\oem0.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "USB\HASP\5&142CDEBF&0&00".
#I121 Device install of "USB\HASP\5&142CDEBF&0&00" finished
successfully.


[2006/10/10 23:41:41 1060.3 Driver Install]
#-019 Searching for hardware ID(s): usb\unknown
#-018 Searching for compatible ID(s): usb\unknown
#-198 Command line processed: C:\WINDOWS\system32\services.exe
#I022 Found "USB\UNKNOWN" in C:\WINDOWS\inf\usb.inf; Device: "Unknown
Device"; Driver: "Unknown Device"; Provider: "Microsoft"; Mfg:
"(Standard USB Host Controller)"; Section name: "BADDEVICE.Dev".
#I023 Actual install section: [BADDEVICE.Dev.NT]. Rank: 0x00000000.
Effective driver date: 07/01/2001.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [BADDEVICE.Dev] in
"c:\windows\inf\usb.inf".
#I320 Class GUID of device remains:
{36FC9E60-C465-11CF-8056-444553540000}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-166 Device install function: DIF_INSTALLDEVICEFILES.
#I124 Doing copy-only install of
"USB\VID_0000&PID_0000\4&2125D824&0&1".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [BADDEVICE.Dev.NT.Interfaces] from
"c:\windows\inf\usb.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "USB\VID_0000&PID_0000\4&2125D824&0&1".
#I121 Device install of "USB\VID_0000&PID_0000\4&2125D824&0&1" finished
successfully.
 
I would bet that either there is a different .inf file or a registry
difference on the two systems that is causing it.

On the working system, search the Windows INF folder for files
containing "Aladdin" or "USB" .
You will need to copy one of the .inf files, and any other files that
the inf references that are not already present.


Also, In the registry there are a number of keys relating to the USB
services, you may find clues there as well (driver file names, etc)

HKLM\System\CurrentControlSet\Services\usbhub
...\usbohci
...\usbprint
...\usbstor

Also, when the device is plugged in the plug and play will add a new
entry under
[HKLM\System\CurrentControlSet\Enum\USB] that is specific to the serial
number of the device.

Comparing these entries will probably allow you to figure out what you
need.

Then, you can take the INF and associated files and create a component
for the Aladdin keys.

Good Luck!
SteveS
stevesATeyeDASHimagingDOTcom.
 
Will,

You are missing Alladin's driver(s) in your image.
You can download it here (HASP, right?) and get it componentized or even install at run time, depending on if you got Windows
Installer component included with all the driver's and driver installer's dependencies. Worth to try:
http://www.aladdin.com/support/hasp/vendor.asp#latestDD,
ftp://ftp.aladdin.com/pub/hasp/hl/windows/installed/Samples/Driver_Install/HASP_HL_driver_msi.zip

Or command line installation (likely less fat than the above):
ftp://ftp.aladdin.com/pub/hasp/hl/windows/installed/redistribute/drivers/HASP_HL_driver_cmdline.zip

IIRC, Alladin's drivers got certified by WDHC pretty recently and they didn't get to XPe database when it was created long time ago.

The XPProEmulation image does not include platform support as it is documented in the tool Readme. It is only a set of all software
components from the database.

--
=========
Regards,
KM


Here is the info from my setupapi.log file, I figured it might be
useful to anyone who might have a suggestion. The first two sections
are where it works as expected in the working slots. The final section
is where I try it in the slots that aren't working.

Thanks again!

Will


[2006/10/10 23:37:43 1060.3 Driver Install]
#-019 Searching for hardware ID(s):
usb\vid_0529&pid_0001&rev_0216,usb\vid_0529&pid_0001
#-018 Searching for compatible ID(s):
usb\class_ff&subclass_00&prot_00,usb\class_ff&subclass_00,usb\class_ff
#-198 Command line processed: C:\WINDOWS\system32\services.exe
#I022 Found "USB\Vid_0529&Pid_0001" in C:\WINDOWS\inf\oem1.inf; Device:
"Aladdin USB Key"; Driver: "Aladdin USB Key"; Provider: "Aladdin
Knowledge Systems"; Mfg: "Aladdin Knowledge Systems"; Section name:
"aksusb".
#I023 Actual install section: [aksusb.NT]. Rank: 0x00000001. Effective
driver date: 07/27/2005.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [aksusb] in
"c:\windows\inf\oem1.inf".
#I320 Class GUID of device remains:
{36FC9E60-C465-11CF-8056-444553540000}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-166 Device install function: DIF_INSTALLDEVICEFILES.
#I124 Doing copy-only install of "USB\VID_0529&PID_0001\4&BDE6317&0&2".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [aksusb.NT.Interfaces] from
"c:\windows\inf\oem1.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "USB\VID_0529&PID_0001\4&BDE6317&0&2".
#I121 Device install of "USB\VID_0529&PID_0001\4&BDE6317&0&2" finished
successfully.


[2006/10/10 23:37:47 1060.7 Driver Install]
#-019 Searching for hardware ID(s): usb\hasp
#-018 Searching for compatible ID(s): usb\hasp
#-198 Command line processed: C:\WINDOWS\system32\services.exe
#I022 Found "USB\Hasp" in C:\WINDOWS\inf\oem0.inf; Device: "Aladdin
HASP Key"; Driver: "Aladdin HASP Key"; Provider: "Aladdin Knowledge
Systems"; Mfg: "Aladdin Knowledge Systems"; Section name: "akshasp".
#I023 Actual install section: [akshasp.NT]. Rank: 0x00000000. Effective
driver date: 07/27/2005.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [akshasp] in
"c:\windows\inf\oem0.inf".
#I320 Class GUID of device remains:
{36FC9E60-C465-11CF-8056-444553540000}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-166 Device install function: DIF_INSTALLDEVICEFILES.
#I124 Doing copy-only install of "USB\HASP\5&142CDEBF&0&00".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [akshasp.NT.Interfaces] from
"c:\windows\inf\oem0.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "USB\HASP\5&142CDEBF&0&00".
#I121 Device install of "USB\HASP\5&142CDEBF&0&00" finished
successfully.


[2006/10/10 23:41:41 1060.3 Driver Install]
#-019 Searching for hardware ID(s): usb\unknown
#-018 Searching for compatible ID(s): usb\unknown
#-198 Command line processed: C:\WINDOWS\system32\services.exe
#I022 Found "USB\UNKNOWN" in C:\WINDOWS\inf\usb.inf; Device: "Unknown
Device"; Driver: "Unknown Device"; Provider: "Microsoft"; Mfg:
"(Standard USB Host Controller)"; Section name: "BADDEVICE.Dev".
#I023 Actual install section: [BADDEVICE.Dev.NT]. Rank: 0x00000000.
Effective driver date: 07/01/2001.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [BADDEVICE.Dev] in
"c:\windows\inf\usb.inf".
#I320 Class GUID of device remains:
{36FC9E60-C465-11CF-8056-444553540000}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-166 Device install function: DIF_INSTALLDEVICEFILES.
#I124 Doing copy-only install of
"USB\VID_0000&PID_0000\4&2125D824&0&1".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [BADDEVICE.Dev.NT.Interfaces] from
"c:\windows\inf\usb.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "USB\VID_0000&PID_0000\4&2125D824&0&1".
#I121 Device install of "USB\VID_0000&PID_0000\4&2125D824&0&1" finished
successfully.
Click to expand...
 
Thanks, I really appreciate the input. I think the driver is installed
correctly, I tried both the graphical install and the command line
install. The key is detected (and works) in 6 of the 8 USB slots so
the drivers are definately in the system. I know the slots physically
function because if I test them under full XP pro all 8 slots.

I used filemon and regmon over on XP pro to see what files and registry
entries were updated when installing the key and used the diff to make
a componenetized version of the aladdin drivers. I ended up with the
same results, it worked for all but two USB slots.

I am still at a bit of a loss to explain why all the USB slots execept
the first two detect the key and install the drivers with no problem.
The hardware and bios settings are the same between the XP Pro and XPe
installs so the difference will eventually boil down to software
somehow. I tried this on a second machine and got the same behavior so
I think I have ruled out something specific to my particular
motherboard.

If it is not the Aladdin drivers, not the hardware, not the bios, I am
thinking it has to be some generic USB component, conficting system
resource, or registry setting that is causing my problems.

The machine detects that something is pluged into the USB slot, and it
looks like when it tries to read the device's ID's it is not getting
good data, the setupapi.log showed the ID's to be zero, which is
probably not correct. If I can figure out why that is I might have a
shot at nailing down the root cause.
 
Will,

You're right. I didn't carefully check the log you showed earlier.
The driver is indeed installed correctly. The problem seems to be around the back ports there.

Did you get the right USB Host Controller components in your image?
Basically you'd know which host controller driver required for Aladdin to work if you look under Device Manager (or setupapi.log) on
XP Pro installation.
Also, make sure required USB Hub components are in your image (I'd add both Generic USB Hub and Standard USB Hub)
 
Howdy,

Thanks for the tip! I did not have Standard USB in my image so I am
definately going to add that. I will also double check my usb drivers
vs XP pro. I am glad you suggested checking xp pro's setupapi.log. I
had not thought of that. I think I have a few imiages to build and
install. lol.

Thanks again!!

Will
 
This has turned out to be an interesting issue to try and resolve. I
was frustrated by the fact that it worked fine under XP Pro and that it
worked in all the other slots implying that I was not missing any major
USB components.

I ran a test. I installed XP Pro, installed the HASP drivers and got
the Aladdin Key working in all the USB slots. I ran TAP and got a
device.pmq file that included the Aladdin stuff. I compared that with
my original PMQ file and while nothing really jumped out at me, there
were some differences. There were entries for composite USB device
and Aladdin in particular, but other than that it was pretty close to
the same.

I continued the experiment by importing the new PMQ file, adding the
minium stuff to get it up an running. The resulting image ended up
working in all the USB slots under XPe. There must have been
something corrupt or missing in my original PMQ and import that is
preventing this from working.

I think I will have this problem licked by figuring out what in the new
PMQ file is making it work. I am really glad I hung onto my original
PMQ file now. I am also glad that I made a macro component based on
the original PMQ import, it should make it easier to correct the issue
in my main configuration.

Thanks again for all the suggestions and help with this!

Take Care,

Will
 
Hello Everyone,

I just called SanDisc at 1-866-248-4498 and they told me I was the FIRST
person to call about the problem with the USB not being recodgnized! They
had no idea there was such a HUGE problem and they want to fix it.

I was offered this temporary solution:

1. Go to Sandisc.com and download the UNINSTALLER.
2. Your Thumb Drive must be plugged into a WORKING system that recognizes it
for the software to be removed from the thumb drive. Do it on a friends
computer, at work, what-ever.
3. After you run the uninstall it will work on ANY computer. It is the
software on the thumb drive that is not compatiable with Windows.

I would recommend you all make that call. I talked with Elizabeth and she
seemed concerned that all those U3 Sandisc's out there were not working. She
is passing this info onto their R&D for a solution.

The more calls they get, the more serious they will be to find a quick
answer. Elizabeth told me it may take a while. The more calls they get, the
more motivated they will be to find a cure.

Floyd (e-mail address removed)
 
See my post for instructions on fixing your problem. It worked for me. Look
for 'USB FIXED! in the subject line.

Floyd
 
Back
Top