USB Device INCORRECTLY identified as DVB-T USB Device

[Guest]

I have a custom developed USB device that suddenly no long works. Before,
when plugging into a new machine it would properly ask for drivers which
include a firmware loader and then controller driver.

Well I have a new machine - asus p5b with a fresh copy of XP with all
updates applied installed. I install the custom usb device and the OS
detects it as a DVB-T USB BDA device (loads firmware loader and receiver
drivers). Well, this is not a television receive, it's a lab device and now
I can't even tell it to use different drivers... HELP!!!

 

[Chuck]

Sounds like the ID of the device was duplicated by another type of device.
Someone did not register things as they should.
You will need to uninstall the incorrect drivers. You may be able to do a
manual install of the correct drivers if you have them.

 

[Guest]

....you can try to update all the USB device drivers in Device Manager with
the device installed with the Windows XP installation cd in the cdrom drive .

 

[Guest]

I have been researching this problem for several days now. I still don't
have a good solution for this. The only way to deal with it is to delete
the OEMxx.inf files and then manually installing the driver. But this is
not a good thing for customers (as you can probably imagine).

I have even tried DPInst from the DDK to get around this and that doesn’t
work either. For some reason it still thinks the DVB-T device driver is
still a better driver no matter what I specify in the DPInst configuration.

I just wish I knew where this other driver is coming from... I cannot find
an inf for it, a cat for it or anything. Any clues???

As a reminder for everyone, the Device Description for the bad driver is
"DVB-T USB BDA firmware loader" with a Hardware ID of
USB\Vid_04b4&Pid_8613.. The Driver it loads is CDBDALDR.sys and the
provider name is C&E, Inc.

Thanks for the help!

 

[sibi]

USB\Vid_04b4&Pid_8613 is Cypress EZUSB FX2 USB controllers hard wired VID/PID

Several developers use that ID for custom devices for inhouse use.

How could that ID be hijacked as belonging to DVB-T that too in a clean OS install.

What does cypress have to say about it.
This will render using their developement kits un-usable in future version of Windows. This situation needs to be corrected.

EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com

 

[paulgc3]

USB\Vid_04b4&Pid_8613 is Cypress EZUSB FX2 USB controllers hard wired VID/PID

What does cypress have to say about it.
This will render using their development kits unusable in future version of Windows. This situation needs to be corrected.

Cypress hands out incomplete instructions for trying to remove the old
device. Their first advice is to roll back all the Microsoft windows
updates until the device enumerates correctly. This is so patently
ridiculous that I wouldn't even consider it.

Their next bit of advice is to remove the vid/pid from the registry.
This sounds better, but for my box, I can remove the registry entry for
the device, but it just goes ahead and finds the DVB-T BDA USB Receiver
again. Whoever those pinheads are that stole Cypresses vid/pid and
shipped a product.... I wanna.....

Anyway if anybody knows a bit more about where I can make windows
forget about this bad device and let me force it to use the new
device... It would be much appreciated.

(e-mail address removed)