If the usb device has no serial number, the OS cannot uniquely identify
the device. This means that each time it is plugged into a new port, a
new device node is created and installed. For there to be no reinstall
when the device moves around on the machine, the device must be uniquely
identifiable within the system. What you are seeing is by design.
In short, there is no way to solve this problem other then to give your
device a unique serial number.
d
-----Original Message-----
From: Deevi, Srinivasa [mailto:xxxxx@microtune.com]
Sent: Wednesday, January 15, 2003 3:42 PM
To: NT Developers Interest List
Subject: [ntdev] How to stop reloading the driver when the USB device is
plugged i n same slot ?
Hi all,
I have a question about how to stop reloading the same driver in windows
2k/xp environment . The firmware does not send any serial number in its
descriptors . I believe that when the device is not sending any serial
number , the OS should not ask for driver again as if it is a new device
.
what makes OS to think that this is a new device ? Anybody has any idea
how
to solve this problem ?
thanks in advance
sri.
You are currently subscribed to ntdev as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
That isn’t strictly true. It is possible through a coinstaller to copy the
registry info for the device around such that no matter what port it gets
plugged into it will get recognized properly after initial install. I
haven’t done it, but it was reported as doable in the USB presentation at
last years WinHEC.
Bill McKenzie
Compuware Corporation
“Doron Holan” wrote in message
news:xxxxx@ntdev…
If the usb device has no serial number, the OS cannot uniquely identify
the device. This means that each time it is plugged into a new port, a
new device node is created and installed. For there to be no reinstall
when the device moves around on the machine, the device must be uniquely
identifiable within the system. What you are seeing is by design.
In short, there is no way to solve this problem other then to give your
device a unique serial number.
d
-----Original Message-----
From: Deevi, Srinivasa [mailto:xxxxx@microtune.com]
Sent: Wednesday, January 15, 2003 3:42 PM
To: NT Developers Interest List
Subject: [ntdev] How to stop reloading the driver when the USB device is
plugged i n same slot ?
Hi all,
I have a question about how to stop reloading the same driver in windows
2k/xp environment . The firmware does not send any serial number in its
descriptors . I believe that when the device is not sending any serial
number , the OS should not ask for driver again as if it is a new device
.
what makes OS to think that this is a new device ? Anybody has any idea
how
to solve this problem ?
thanks in advance
sri.
—
You are currently subscribed to ntdev as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
Well, the install process has to get far enough to install the
coinstaller no? plus, you are migrating information (so at least you
get the info propagated around) only I think. This actually brings up a
worse scenario b/c now when the device is plugged back into the original
port, any changed settings on the 2nd port are not pushed back to the
original.
d
-----Original Message-----
From: Bill McKenzie [mailto:xxxxx@driver.attbbs.com]
Sent: Wednesday, January 15, 2003 5:11 PM
To: NT Developers Interest List
Subject: [ntdev] Re: How to stop reloading the driver when the USB
device is plugged i n same slot ?
That isn’t strictly true. It is possible through a coinstaller to copy
the
registry info for the device around such that no matter what port it
gets
plugged into it will get recognized properly after initial install. I
haven’t done it, but it was reported as doable in the USB presentation
at
last years WinHEC.
Bill McKenzie
Compuware Corporation
“Doron Holan” wrote in message
news:xxxxx@ntdev…
If the usb device has no serial number, the OS cannot uniquely identify
the device. This means that each time it is plugged into a new port, a
new device node is created and installed. For there to be no reinstall
when the device moves around on the machine, the device must be uniquely
identifiable within the system. What you are seeing is by design.
In short, there is no way to solve this problem other then to give your
device a unique serial number.
d
-----Original Message-----
From: Deevi, Srinivasa [mailto:xxxxx@microtune.com]
Sent: Wednesday, January 15, 2003 3:42 PM
To: NT Developers Interest List
Subject: [ntdev] How to stop reloading the driver when the USB device is
plugged i n same slot ?
Hi all,
I have a question about how to stop reloading the same driver in windows
2k/xp environment . The firmware does not send any serial number in its
descriptors . I believe that when the device is not sending any serial
number , the OS should not ask for driver again as if it is a new device
.
what makes OS to think that this is a new device ? Anybody has any idea
how
to solve this problem ?
thanks in advance
sri.
—
You are currently subscribed to ntdev as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
—
You are currently subscribed to ntdev as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
Maybe I don’t understand. You can’t expect the device to get recognized on
first install anyway right? But, once the coinstaller is invoked on first
install, then the device registry info is migrated around such that the
system effectively sees the device as having been plugged in on every port.
So, moving the device after that will not cause a reprompt for the driver.
As far as not propagating subsequent registry value changes back to all
locations in the registry, who cares? If that truly was an issue for a
given device I suppose you could have the USB device’s driver correct the
problem. Or maybe I am missing some bigger point here.
Bill McKenzie
Compuware Corporation
“Doron Holan” wrote in message
news:xxxxx@ntdev…
Well, the install process has to get far enough to install the
coinstaller no? plus, you are migrating information (so at least you
get the info propagated around) only I think. This actually brings up a
worse scenario b/c now when the device is plugged back into the original
port, any changed settings on the 2nd port are not pushed back to the
original.
d
-----Original Message-----
From: Bill McKenzie [mailto:xxxxx@driver.attbbs.com]
Sent: Wednesday, January 15, 2003 5:11 PM
To: NT Developers Interest List
Subject: [ntdev] Re: How to stop reloading the driver when the USB
device is plugged i n same slot ?
That isn’t strictly true. It is possible through a coinstaller to copy
the
registry info for the device around such that no matter what port it
gets
plugged into it will get recognized properly after initial install. I
haven’t done it, but it was reported as doable in the USB presentation
at
last years WinHEC.
Bill McKenzie
Compuware Corporation
“Doron Holan” wrote in message
news:xxxxx@ntdev…
If the usb device has no serial number, the OS cannot uniquely identify
the device. This means that each time it is plugged into a new port, a
new device node is created and installed. For there to be no reinstall
when the device moves around on the machine, the device must be uniquely
identifiable within the system. What you are seeing is by design.
In short, there is no way to solve this problem other then to give your
device a unique serial number.
d
-----Original Message-----
From: Deevi, Srinivasa [mailto:xxxxx@microtune.com]
Sent: Wednesday, January 15, 2003 3:42 PM
To: NT Developers Interest List
Subject: [ntdev] How to stop reloading the driver when the USB device is
plugged i n same slot ?
Hi all,
I have a question about how to stop reloading the same driver in windows
2k/xp environment . The firmware does not send any serial number in its
descriptors . I believe that when the device is not sending any serial
number , the OS should not ask for driver again as if it is a new device
.
what makes OS to think that this is a new device ? Anybody has any idea
how
to solve this problem ?
thanks in advance
sri.
—
You are currently subscribed to ntdev as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
—
You are currently subscribed to ntdev as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com