Cannot get XP to detect my USB hardware properly - help please !

  • Thread starter Thread starter dave p
  • Start date Start date
D

dave p

hi

Can I point to a thread of mine elsewhere which details my problem:

http://www.kvraudio.com/forum/viewtopic.php?t=218930

My last entry is probably the most important.

So what I need to do is somehow get XP to properly detect these devices &
launch the hardware wizard, not just give a couple of info balloons off the
task bar.

Can anyone help me here ?

thanks
 
dave said:
hi

Can I point to a thread of mine elsewhere which details my problem:

http://www.kvraudio.com/forum/viewtopic.php?t=218930

My last entry is probably the most important.

So what I need to do is somehow get XP to properly detect these devices &
launch the hardware wizard, not just give a couple of info balloons off the
task bar.

Can anyone help me here ?

thanks
Click to expand...
You could just as easily cut and paste the info into this message. I
am not one to click on links provided by people I don't know. A reason
I don't normally get viruses.
 
Big_Al said:
You could just as easily cut and paste the info into this message. I
am not one to click on links provided by people I don't know. A reason
I don't normally get viruses.
Click to expand...

OK - I'll give a brief summary (it's rather complex as I'm a computer
musician)

I use my PC has a DAW (Digital Audio Workstation) and have a number of
soundcards & USB devices.

Recently I had to swap my Asus P5B WiFi Delux motherboard for identical
model replacement.

My original "music" OS partition works fine with this (as expected) except
that my 2 USB Midi controllers (Behringer BCR and BCF2000s) do not show up as
Midi Out devices anymore.

They do show up as Midi In devices and work fine in this respect.

So none of my music software can "talk" to the BCR / BCF - only receive Midi
data from them.

I first thought this was possibly related to a windows 10 midi device
limitation (certainly a known issue with Win98 and 2000 , and some people
report problems wth XP).

So I've tried deleting some of the registry entries related to this problem
(well documented workaround available on various PC audio sites e.g.
http://www.rme-audio.com/english/faq/10entrye.htm ) - didn't work.

So I've tried using the BCR on another PC that's never seen it before.

This time I correctly got the windows hardware installation wizard, and it
installed & worked fine !

What I DON'T get on my main DAW is the installation wizard - just a few
speech bubbles at bottom right of task bar

e.g. first one says "BCR2000", second one "USB Device" or something like that.

One other difference is that with this working installation, one of the
bubbles just before the Hardware Wizard appeared said something like "USB
Composite device".

This doesn't come up on my DAW.

So my guess it that somehow I have to get my DAW to bring up the Hardware
Wizard when connecting the BCR / BCF units - until then it's never going to
work ..

Any ideas as to how I do this ?

I've tried manually deleting the driver files but this hasn't worked -
although as I mentioned before, I know at least one of the registry
references to midi device wdmaud.drv refers to Behringer devices.
 
dave said:
OK - I'll give a brief summary (it's rather complex as I'm a computer
musician)

I use my PC has a DAW (Digital Audio Workstation) and have a number of
soundcards & USB devices.

Recently I had to swap my Asus P5B WiFi Delux motherboard for identical
model replacement.

My original "music" OS partition works fine with this (as expected) except
that my 2 USB Midi controllers (Behringer BCR and BCF2000s) do not show up as
Midi Out devices anymore.

They do show up as Midi In devices and work fine in this respect.

So none of my music software can "talk" to the BCR / BCF - only receive Midi
data from them.

I first thought this was possibly related to a windows 10 midi device
limitation (certainly a known issue with Win98 and 2000 , and some people
report problems wth XP).

So I've tried deleting some of the registry entries related to this problem
(well documented workaround available on various PC audio sites e.g.
http://www.rme-audio.com/english/faq/10entrye.htm ) - didn't work.

So I've tried using the BCR on another PC that's never seen it before.

This time I correctly got the windows hardware installation wizard, and it
installed & worked fine !

What I DON'T get on my main DAW is the installation wizard - just a few
speech bubbles at bottom right of task bar

e.g. first one says "BCR2000", second one "USB Device" or something like that.

One other difference is that with this working installation, one of the
bubbles just before the Hardware Wizard appeared said something like "USB
Composite device".

This doesn't come up on my DAW.

So my guess it that somehow I have to get my DAW to bring up the Hardware
Wizard when connecting the BCR / BCF units - until then it's never going to
work ..

Any ideas as to how I do this ?

I've tried manually deleting the driver files but this hasn't worked -
although as I mentioned before, I know at least one of the registry
references to midi device wdmaud.drv refers to Behringer devices.
Click to expand...

My original comment was to see the details you were linking to. Not so
much that I can solve your problem. I like the brute force approach so
I'm not much help.

I don't know the exact keystroke but there is a way to search for new
devices in Device Manager, I think your hardware wizard comment. Even
maybe the 'update drivers' on the one device you need will start it. If
you have a CD with drivers, if you could point there and exclude all
other sources thus forcing it to pull drivers in that are the right
ones, maybe that would help. I'm just guessing though. I hate to
tell you to do things like this as you are so close to working.

Since you changed boards, have you opened Device Manager and done 'show
hidden devices' to see if any have the yellow ! I've found that my
laptop needed the Intel Mobile Chipset drivers to help explain to XP how
to handle some of the behind the scenes stuff (in layman's terms). It
fixed about 3 of these errors on my laptop. Major devices worked.

Take what I say with a grain of salt. I'm not going to sell myself as
tech support by all means. I've done a lot, but its still not a
science to me yet.
Good Luck.
AL.
 
You are probably not getting the hardware wizard because Windows already has the
..inf files for the devices, from the first time you installed them before changing
the mobo. You would have to delete or rename the .inf files and .pnf files in the
Windows\Inf folder for those devices, and probably also delete the "infcache.1" file
in that folder, reboot, and then connect and detect the devices again.

The .inf and .pnf files for those devices may have names associated with them, or
they may have names like oem2.inf and oem2.pnf

I would sort the folder by date and look for the files added around the time you
first installed the devices. The .inf files can be opened in Notepad to read what
device names they are related to.


This might also help:

1. Click Start> All Programs> Accessories> Command Prompt.

2. At a command prompt, type the following, and press ENTER:

set devmgr_show_nonpresent_devices=1

3. Then type the following command, and press ENTER:

start devmgmt.msc

4. Click View menu> Show hidden devices in Device Manager.

Remove all items listed that in any way relate to your problem devices in all
relevant categories, particularly under Sound, Video and Game Controllers; USB
Controllers; System Devices; Disk Drives; Non-Plug and Play Drivers; Unknown or
Other Devices.

Greyed-out (faded) icons for a device indicates it is a phantom device...that is,
not currently attached to the computer. It will show many USB devices like flash
drives that you have used in the past. Remove all phantom devices.

Close Device Manager and the Command Prompt window.

Reboot to let any attached devices that you removed in Device Manager be
re-detected, then connect your problem devices and see if the hardware wizard now
comes up to reinstall the drivers for them.

Device Manager does not display devices that are not connected to the Windows
XP-based computer:
http://support.microsoft.com/kb/315539
 
glee said:
You are probably not getting the hardware wizard because Windows already has the
..inf files for the devices, from the first time you installed them before changing
the mobo. You would have to delete or rename the .inf files and .pnf files in the
Windows\Inf folder for those devices, and probably also delete the "infcache.1" file
in that folder, reboot, and then connect and detect the devices again.

The .inf and .pnf files for those devices may have names associated with them, or
they may have names like oem2.inf and oem2.pnf

I would sort the folder by date and look for the files added around the time you
first installed the devices. The .inf files can be opened in Notepad to read what
device names they are related to.


This might also help:

1. Click Start> All Programs> Accessories> Command Prompt.

2. At a command prompt, type the following, and press ENTER:

set devmgr_show_nonpresent_devices=1

3. Then type the following command, and press ENTER:

start devmgmt.msc

4. Click View menu> Show hidden devices in Device Manager.

Remove all items listed that in any way relate to your problem devices in all
relevant categories, particularly under Sound, Video and Game Controllers; USB
Controllers; System Devices; Disk Drives; Non-Plug and Play Drivers; Unknown or
Other Devices.

Greyed-out (faded) icons for a device indicates it is a phantom device...that is,
not currently attached to the computer. It will show many USB devices like flash
drives that you have used in the past. Remove all phantom devices.

Close Device Manager and the Command Prompt window.

Reboot to let any attached devices that you removed in Device Manager be
re-detected, then connect your problem devices and see if the hardware wizard now
comes up to reinstall the drivers for them.

Device Manager does not display devices that are not connected to the Windows
XP-based computer:
http://support.microsoft.com/kb/315539
Click to expand...

Many thanks for your detailed reply.

I tried it out and the bloody hardware wizard STILL refused to appear - just
those bubbles again

eg.

when I rebooted and connected the Behringer BCR, a bubble immediately came
up saying "BCR 2000", then "USB Composite Device" then "Your hardware is
installed and ready to use" ... :(

Any further suggestions ?
 
dave p said:
Many thanks for your detailed reply.

I tried it out and the bloody hardware wizard STILL refused to appear - just
those bubbles again

eg.

when I rebooted and connected the Behringer BCR, a bubble immediately came
up saying "BCR 2000", then "USB Composite Device" then "Your hardware is
installed and ready to use" ... :(

Any further suggestions ?
Click to expand...

This is after you deleted the infcache.1 file and the .inf and .pnf files related to
the device?
(Possibly BCR2000.inf and BCR2000.pnf)

About all I can suggest is, have you installed the latest driver or updated it over
your current driver?
http://www.behringer.com/_software/BCFBCR2000v1213.zip

Do you have a MIDI interface to connect to, instead of USB?
 
glee said:
This is after you deleted the infcache.1 file and the .inf and .pnf files related to
the device?
(Possibly BCR2000.inf and BCR2000.pnf)

About all I can suggest is, have you installed the latest driver or updated it over
your current driver?
http://www.behringer.com/_software/BCFBCR2000v1213.zip

Do you have a MIDI interface to connect to, instead of USB?
Click to expand...

thanks again

yes, I do have some other Midi interfaces - but the USB route is by far the
more preferable

is it at all possible that a motherboard fault could be causing this ?

I have tried other bidirectional USB devices (ie ext harddrive) and this
seemed to work fine, in both directions, so I guess the m'board is an
unlikely culprit

the situation is driving me mad !!

actually I think I may have cocked things up further now as I went through
the registry and deleted every single reference to Behringer devices
(including USB keys) - now the PC doesn't react at all when I switch the BCR
/ BCF on

there must be a reason why only the bubbles come up (with recognition of
BCR/BCF ... presumably Windows gets some info regarding the name of the
device directly from the device itself ?)

my whole music studio depends on 2-way communication between the BCR/BCF and
my PC ..... :(
 
dave p said:
:
snip

thanks again

yes, I do have some other Midi interfaces - but the USB route is by far the
more preferable

is it at all possible that a motherboard fault could be causing this ?

I have tried other bidirectional USB devices (ie ext harddrive) and this
seemed to work fine, in both directions, so I guess the m'board is an
unlikely culprit

the situation is driving me mad !!

actually I think I may have cocked things up further now as I went through
the registry and deleted every single reference to Behringer devices
(including USB keys) - now the PC doesn't react at all when I switch the BCR
/ BCF on

there must be a reason why only the bubbles come up (with recognition of
BCR/BCF ... presumably Windows gets some info regarding the name of the
device directly from the device itself ?)

my whole music studio depends on 2-way communication between the BCR/BCF and
my PC ..... :(
Click to expand...

I don't use MIDI devides so I can't think of much more to try. Deleting items from
the Registry without a registry backup is not a good idea. Try System Restore to
restore to the time prior to your deleting binge.
 
hi

Can I point to a thread of mine elsewhere which details my problem:

http://www.kvraudio.com/forum/viewtopic.php?t=218930

My last entry is probably the most important.

So what I need to do is somehow get XP to properly detect these devices &
launch the hardware wizard, not just give a couple of info balloons off the
task bar.

Can anyone help me here ?

thanks
Click to expand...

Are you using Windows XP with Service Pack 3 (SP3) ?

I've got a problem with one, not all, USB device after updating to
SP3. When I reinstalled XP and avoided the SP3 update, the device is
working again.
 
Back
Top