I’m developing an USB device, both driver and firmware.
The installation of that device using an *.inf file is working properly as
long as I only want to run one device at a time, but when I plug in a
second one (or third or …), I get the Windows “Found New Hardware”
Wizard, requesting a second installation of my driver. Having this done
the device is marked as not working properly in the Windows DeviceManager,
claiming “The device is not configured properly. (Code 1)” and the Windows
DeviceManager requires to install the driver again. Doing this doesn’t
change a thing. (This occurs both on Win2k and WinXP.)
Does anybody know this problem or had to deal with some similar problem?
Do I need some special settings / configuration in firmware, driver or
*.inf file?
Try removing the serial number descriptor string from your firmware.
For more details you can see the discussion about unique serial number on
this list in the first days of January.
PaoloC
– Messaggio originale –
Date: Mon, 26 Jan 2004 10:46:00 +0100 (CET)
Subject: [ntdev] Problem when installing second USB device under Windows
From: “Olav” >To: “Windows System Software Devs Interest List” >Reply-To: “Windows System Software Devs Interest List” > > >Hi all, > >I’m developing an USB device, both driver and firmware. > >The installation of that device using an .inf file is working properly as >long as I only want to run one device at a time, but when I plug in a >second one (or third or …), I get the Windows “Found New Hardware” >Wizard, requesting a second installation of my driver. Having this done >the device is marked as not working properly in the Windows DeviceManager, >claiming “The device is not configured properly. (Code 1)” and the Windows >DeviceManager requires to install the driver again. Doing this doesn’t >change a thing. (This occurs both on Win2k and WinXP.) > >Does anybody know this problem or had to deal with some similar problem? > >Do I need some special settings / configuration in firmware, driver or >.inf file? > >I’d appreciate any hint, comment or information! > >Thank you! > >Olav > > >— >Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256 > >You are currently subscribed to ntdev as: xxxxx@tin.it >To unsubscribe send a blank email to xxxxx@lists.osr.com
Why would you suggest to *remove* the serial number descriptor? As long
as the serial number is unique (which is the definition of a serial
number), having a unique serial number provides significant benefits in
many cases.
I would instead suggest that the person validate their serial numbers
are unique on each device.
Of course, the best suggestion is:
Start by looking into the setupapi.log found in your windows directory.
This often contains more useful information about the device
installation, and why a failure occurs/reboot required.
If you can’t figure it out from there, I’d suggest doing the following:
“Uninstall” the two devices from device manager.
Remove both devices from the system.
Delete setupapi.log from the windows directory.
Plug the first device into the system.
Wait for PNP to finish.
Plug the second device into the system.
Wait for PNP to finish.
Put the SETUPAPI.LOG file on a publicly-accesible site (http? ftp?).
Post the location of that log file to this list.
Good luck!
.
-----Original Message-----
From: xxxxx@tin.it [mailto:xxxxx@tin.it]
Sent: Monday, January 26, 2004 3:46 AM
Subject: RE: Problem when installing second USB device under Windows
Try removing the serial number descriptor string from your firmware.
For more details you can see the discussion about unique serial number
on this list in the first days of January.
PaoloC
– Messaggio originale –
Date: Mon, 26 Jan 2004 10:46:00 +0100 (CET)
Subject: [ntdev] Problem when installing second USB device under
Windows
From: “Olav” >To: “Windows System Software Devs Interest List” >Reply-To: “Windows System Software Devs Interest List” > > > >Hi all, > >I’m developing an USB device, both driver and firmware. > >The installation of that device using an .inf file is working properly as >long as I only want to run one device at a time, but when I plug in a >second one (or third or …), I get the Windows “Found New Hardware” >Wizard, requesting a second installation of my driver. Having this done
>the device is marked as not working properly in the Windows >DeviceManager, claiming “The device is not configured properly. (Code >1)” and the Windows DeviceManager requires to install the driver again.
>Doing this doesn’t change a thing. (This occurs both on Win2k and >WinXP.) > >Does anybody know this problem or had to deal with some similar problem? > >Do I need some special settings / configuration in firmware, driver or >.inf file? > >I’d appreciate any hint, comment or information! > >Thank you! > >Olav > > >— >Questions? First check the Kernel Driver FAQ at >http://www.osronline.com/article.cfm?id=256 > >You are currently subscribed to ntdev as: xxxxx@tin.it To unsubscribe >send a blank email to xxxxx@lists.osr.com
I suggested to *remove* the serial number because on devices where the
firmware is loaded by device driver
causing the device re-enumeration (Cypress chip I mean) I dont’ know how can
I have a unique serial number.
Best regards,
PaoloC
----- Original Message -----
From: “Henry Gabryjelski” To: “Windows System Software Devs Interest List” Sent: Tuesday, January 27, 2004 5:37 PM Subject: RE:[ntdev] Problem when installing second USB device under Windows
Why would you suggest to remove the serial number descriptor? As long as the serial number is unique (which is the definition of a serial number), having a unique serial number provides significant benefits in many cases.
I would instead suggest that the person validate their serial numbers are unique on each device.
Of course, the best suggestion is: Start by looking into the setupapi.log found in your windows directory. This often contains more useful information about the device installation, and why a failure occurs/reboot required.
If you can’t figure it out from there, I’d suggest doing the following:
1) “Uninstall” the two devices from device manager. 2) Remove both devices from the system. 3) Delete setupapi.log from the windows directory. 4) Plug the first device into the system. 5) Wait for PNP to finish. 6) Plug the second device into the system. 7) Wait for PNP to finish. 8) Put the SETUPAPI.LOG file on a publicly-accesible site (http? ftp?). 9) Post the location of that log file to this list.
Good luck! .
-----Original Message----- From: xxxxx@tin.it [mailto:xxxxx@tin.it] Sent: Monday, January 26, 2004 3:46 AM Subject: RE: Problem when installing second USB device under Windows
Try removing the serial number descriptor string from your firmware. For more details you can see the discussion about unique serial number on this list in the first days of January.
PaoloC
>– Messaggio originale – >Date: Mon, 26 Jan 2004 10:46:00 +0100 (CET) >Subject: [ntdev] Problem when installing second USB device under >Windows >From: “Olav” >To: “Windows System Software Devs Interest List” >Reply-To: “Windows System Software Devs Interest List” > > > >Hi all, > >I’m developing an USB device, both driver and firmware. > >The installation of that device using an .inf file is working properly as >long as I only want to run one device at a time, but when I plug in a >second one (or third or …), I get the Windows “Found New Hardware” >Wizard, requesting a second installation of my driver. Having this done
>the device is marked as not working properly in the Windows >DeviceManager, claiming “The device is not configured properly. (Code >1)” and the Windows DeviceManager requires to install the driver again.
>Doing this doesn’t change a thing. (This occurs both on Win2k and >WinXP.) > >Does anybody know this problem or had to deal with some similar problem? > >Do I need some special settings / configuration in firmware, driver or >.inf file? > >I’d appreciate any hint, comment or information! > >Thank you! > >Olav > > >— >Questions? First check the Kernel Driver FAQ at >http://www.osronline.com/article.cfm?id=256 > >You are currently subscribed to ntdev as: xxxxx@tin.it To unsubscribe >send a blank email to xxxxx@lists.osr.com
Glad to hear we’re agreed then. This is only a work-around for this
particular type of device. The final hardware should include a serial
number…
.
-----Original Message-----
From: PaoloC [mailto:xxxxx@tin.it]
Sent: Tuesday, January 27, 2004 1:46 PM
Subject: Re: RE:Problem when installing second USB device under Windows
I suggested to *remove* the serial number because on devices where the
firmware is loaded by device driver causing the device re-enumeration
(Cypress chip I mean) I dont’ know how can I have a unique serial
number.
Best regards,
PaoloC
----- Original Message -----
From: “Henry Gabryjelski” To: “Windows System Software Devs Interest List” Sent: Tuesday, January 27, 2004 5:37 PM Subject: RE:[ntdev] Problem when installing second USB device under Windows
Why would you suggest to remove the serial number descriptor? As long as the serial number is unique (which is the definition of a serial number), having a unique serial number provides significant benefits in many cases.
I would instead suggest that the person validate their serial numbers are unique on each device.
Of course, the best suggestion is: Start by looking into the setupapi.log found in your windows directory. This often contains more useful information about the device installation, and why a failure occurs/reboot required.
If you can’t figure it out from there, I’d suggest doing the following:
1) “Uninstall” the two devices from device manager. 2) Remove both devices from the system. 3) Delete setupapi.log from the windows directory. 4) Plug the first device into the system. 5) Wait for PNP to finish. 6) Plug the second device into the system. 7) Wait for PNP to finish. 8) Put the SETUPAPI.LOG file on a publicly-accesible site (http? ftp?). 9) Post the location of that log file to this list.
Good luck! .
-----Original Message----- From: xxxxx@tin.it [mailto:xxxxx@tin.it] Sent: Monday, January 26, 2004 3:46 AM Subject: RE: Problem when installing second USB device under Windows
Try removing the serial number descriptor string from your firmware. For more details you can see the discussion about unique serial number on this list in the first days of January.
PaoloC
>– Messaggio originale – >Date: Mon, 26 Jan 2004 10:46:00 +0100 (CET) >Subject: [ntdev] Problem when installing second USB device under >Windows >From: “Olav” >To: “Windows System Software Devs Interest List” >Reply-To: “Windows System Software Devs Interest List” > > > >Hi all, > >I’m developing an USB device, both driver and firmware. > >The installation of that device using an .inf file is working properly as >long as I only want to run one device at a time, but when I plug in a >second one (or third or …), I get the Windows “Found New Hardware” >Wizard, requesting a second installation of my driver. Having this done
>the device is marked as not working properly in the Windows >DeviceManager, claiming “The device is not configured properly. (Code >1)” and the Windows DeviceManager requires to install the driver again.
>Doing this doesn’t change a thing. (This occurs both on Win2k and >WinXP.) > >Does anybody know this problem or had to deal with some similar problem? > >Do I need some special settings / configuration in firmware, driver or >.inf file? > >I’d appreciate any hint, comment or information! > >Thank you! > >Olav > > >— >Questions? First check the Kernel Driver FAQ at >http://www.osronline.com/article.cfm?id=256 > >You are currently subscribed to ntdev as: xxxxx@tin.it To unsubscribe >send a blank email to xxxxx@lists.osr.com
Greetings mortal, Olav!
You wrote on Mon, 26 Jan 2004 10:46:00 +0100 (CET):
O> The installation of that device using an *.inf file is working
O> properly as long as I only want to run one device at a time, but when
O> I plug in a second one (or third or …), I get the Windows “Found
O> New Hardware”
O> Wizard, requesting a second installation of my driver. Having this
O> done the device is marked as not working properly in the Windows
O> DeviceManager, claiming “The device is not configured properly. (Code
O> 1)” and the Windows
O> DeviceManager requires to install the driver again. Doing this
O> doesn’t change a thing. (This occurs both on Win2k and WinXP.)
In addition to looking in setupapi.log, try to read KB 314743 (HOWTO: Enable
Verbose Debug Tracing in Various Drivers and Subsystems).