Hello,
Now in my .inf file I no longer specify what the
underlying bus driver is (before I had something like
“root\xyz”). Now in the .inf file I changed to “*xyz”
because I could not load the driver programmatically
with “root\xyz”.
Question: with “*xyz” in my .inf file, what is the
underlying bus driver now??
Regards, Vasili
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
Any bus driver.
These IDs are not tied to a particular bus.
Max
----- Original Message -----
From: “Galchin Vasili”
To: “NT Developers Interest List”
Sent: Saturday, May 10, 2003 12:08 AM
Subject: [ntdev] Bus driver question …
> Hello,
>
> Now in my .inf file I no longer specify what the
> underlying bus driver is (before I had something like
> “root\xyz”). Now in the .inf file I changed to “*xyz”
> because I could not load the driver programmatically
> with “root\xyz”.
>
> Question: with “*xyz” in my .inf file, what is the
> underlying bus driver now??
>
> Regards, Vasili
>
> __________________________________
> Do you Yahoo!?
> The New Yahoo! Search - Faster. Easier. Bingo.
> http://search.yahoo.com
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@storagecraft.com
> To unsubscribe send a blank email to
xxxxx@lists.osr.com
root
–
Bill McKenzie
Compuware Corporation
Watch your IRPs/IRBs/URBs/NDIS pkts with our free WDMSniffer tool:
http://frontline.compuware.com/nashua/patches/utility.htm
“Galchin Vasili” wrote in message news:xxxxx@ntdev…
>
> Hello,
>
> Now in my .inf file I no longer specify what the
> underlying bus driver is (before I had something like
> “root\xyz”). Now in the .inf file I changed to “*xyz”
> because I could not load the driver programmatically
> with “root\xyz”.
>
> Question: with “*xyz” in my .inf file, what is the
> underlying bus driver now??
>
> Regards, Vasili
>
> __________________________________
> Do you Yahoo!?
> The New Yahoo! Search - Faster. Easier. Bingo.
> http://search.yahoo.com
>
>
>
Hello,
Thank you for answer. The reason I am asking is
that for
IRP_MN_QUERY_DEVICE_RELATIONS
IRP_MN_QUERY_QUERY_RELATIONS
IRP_MN_QUERY_CHARACTERISTICS
I am just passing down to the underlying bus driver.
I.e. I don’t do anything with these IRPs in my
function driver. Now I am trying run HCT (WHQL) and I
am getting failure on “device path test”. The test log
doesn’t help at all. Some I am thinking maybe I am not
handling these IRPs correctly, i.e. I should not only
pass to bus driver, but also do something in my
driver.
In driver books it doesn’t say much about these IRPs.
I “deregistered” my DeviceIoControl dispatch function
to narrow done problem … that is why I suspect a PnP
IRP problem.
BTW, I find WHQL very frustrating because logs do not
help,
Regards, Vasili
— Bill McKenzie wrote:
> root
>
> –
> Bill McKenzie
> Compuware Corporation
> Watch your IRPs/IRBs/URBs/NDIS pkts with our free
> WDMSniffer tool:
>
http://frontline.compuware.com/nashua/patches/utility.htm
>
>
> “Galchin Vasili” wrote in
> message news:xxxxx@ntdev…
> >
> > Hello,
> >
> > Now in my .inf file I no longer specify what
> the
> > underlying bus driver is (before I had something
> like
> > “root\xyz”). Now in the .inf file I changed to
> “*xyz”
> > because I could not load the driver
> programmatically
> > with “root\xyz”.
> >
> > Question: with “*xyz” in my .inf file, what is
> the
> > underlying bus driver now??
> >
> > Regards, Vasili
> >
> >
> > Do you Yahoo!?
> > The New Yahoo! Search - Faster. Easier. Bingo.
> > http://search.yahoo.com
> >
> >
> >
>
>
>
> —
> You are currently subscribed to ntdev as:
> xxxxx@yahoo.com
> To unsubscribe send a blank email to
xxxxx@lists.osr.com
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
So when I attach my function driver to driver stack
the underlying bus driver will be a random one???
Regards, Bill
— “Maxim S. Shatskih”
wrote:
> Any bus driver.
> These IDs are not tied to a particular bus.
>
> Max
>
> ----- Original Message -----
> From: “Galchin Vasili”
> To: “NT Developers Interest List”
>
> Sent: Saturday, May 10, 2003 12:08 AM
> Subject: [ntdev] Bus driver question …
>
>
> > Hello,
> >
> > Now in my .inf file I no longer specify what
> the
> > underlying bus driver is (before I had something
> like
> > “root\xyz”). Now in the .inf file I changed to
> “*xyz”
> > because I could not load the driver
> programmatically
> > with “root\xyz”.
> >
> > Question: with “*xyz” in my .inf file, what is
> the
> > underlying bus driver now??
> >
> > Regards, Vasili
> >
> >
> > Do you Yahoo!?
> > The New Yahoo! Search - Faster. Easier. Bingo.
> > http://search.yahoo.com
> >
> >
> > —
> > You are currently subscribed to ntdev as:
> xxxxx@storagecraft.com
> > To unsubscribe send a blank email to
> xxxxx@lists.osr.com
>
>
>
> —
> You are currently subscribed to ntdev as:
> xxxxx@yahoo.com
> To unsubscribe send a blank email to
xxxxx@lists.osr.com
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
Yes, such a device is attacheable to several kinds of buses.
And to what kind of bus will your device be attached?
Max
----- Original Message -----
From: “Galchin Vasili”
To: “NT Developers Interest List”
Cc:
Sent: Saturday, May 10, 2003 1:45 AM
Subject: [ntdev] Re: Bus driver question …
>
> So when I attach my function driver to driver stack
> the underlying bus driver will be a random one???
>
> Regards, Bill
>
> — “Maxim S. Shatskih”
> wrote:
> > Any bus driver.
> > These IDs are not tied to a particular bus.
> >
> > Max
> >
> > ----- Original Message -----
> > From: “Galchin Vasili”
> > To: “NT Developers Interest List”
> >
> > Sent: Saturday, May 10, 2003 12:08 AM
> > Subject: [ntdev] Bus driver question …
> >
> >
> > > Hello,
> > >
> > > Now in my .inf file I no longer specify what
> > the
> > > underlying bus driver is (before I had something
> > like
> > > “root\xyz”). Now in the .inf file I changed to
> > “*xyz”
> > > because I could not load the driver
> > programmatically
> > > with “root\xyz”.
> > >
> > > Question: with “*xyz” in my .inf file, what is
> > the
> > > underlying bus driver now??
> > >
> > > Regards, Vasili
> > >
> > >
> > > Do you Yahoo!?
> > > The New Yahoo! Search - Faster. Easier. Bingo.
> > > http://search.yahoo.com
> > >
> > >
> > > —
> > > You are currently subscribed to ntdev as:
> > xxxxx@storagecraft.com
> > > To unsubscribe send a blank email to
> > xxxxx@lists.osr.com
> >
> >
> >
> > —
> > You are currently subscribed to ntdev as:
> > xxxxx@yahoo.com
> > To unsubscribe send a blank email to
> xxxxx@lists.osr.com
>
>
>
> Do you Yahoo!?
> The New Yahoo! Search - Faster. Easier. Bingo.
> http://search.yahoo.com
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@storagecraft.com
> To unsubscribe send a blank email to
xxxxx@lists.osr.com
What?? WHQL logs not helpful? I am shocked 
I am sure that will all be
solved in the LDK.
Not familiar with some of the IRPs you mention. Have you tried running this
driver with Driver Verifier active on it? Verifier will often help you
catch this sort of thing.
If you have used Verifier then I would suggest you post the code you use to
send the IRPs down. Perhaps others can see what you are missing. Also,
post some useful info like the error statements in the logs or something.
–
Bill McKenzie
Compuware Corporation
Watch your IRPs/IRBs/URBs/NDIS pkts with our free WDMSniffer tool:
http://frontline.compuware.com/nashua/patches/utility.htm
“Galchin Vasili” wrote in message news:xxxxx@ntdev…
>
> Hello,
>
> Thank you for answer. The reason I am asking is
> that for
>
> IRP_MN_QUERY_DEVICE_RELATIONS
>
> IRP_MN_QUERY_QUERY_RELATIONS
>
> IRP_MN_QUERY_CHARACTERISTICS
>
> I am just passing down to the underlying bus driver.
> I.e. I don’t do anything with these IRPs in my
> function driver. Now I am trying run HCT (WHQL) and I
> am getting failure on “device path test”. The test log
> doesn’t help at all. Some I am thinking maybe I am not
> handling these IRPs correctly, i.e. I should not only
> pass to bus driver, but also do something in my
> driver.
> In driver books it doesn’t say much about these IRPs.
> I “deregistered” my DeviceIoControl dispatch function
> to narrow done problem … that is why I suspect a PnP
> IRP problem.
>
> BTW, I find WHQL very frustrating because logs do not
> help,
> Regards, Vasili
> — Bill McKenzie wrote:
> > root
> >
> > –
> > Bill McKenzie
> > Compuware Corporation
> > Watch your IRPs/IRBs/URBs/NDIS pkts with our free
> > WDMSniffer tool:
> >
> http://frontline.compuware.com/nashua/patches/utility.htm
> >
> >
> > “Galchin Vasili” wrote in
> > message news:xxxxx@ntdev…
> > >
> > > Hello,
> > >
> > > Now in my .inf file I no longer specify what
> > the
> > > underlying bus driver is (before I had something
> > like
> > > “root\xyz”). Now in the .inf file I changed to
> > “*xyz”
> > > because I could not load the driver
> > programmatically
> > > with “root\xyz”.
> > >
> > > Question: with “*xyz” in my .inf file, what is
> > the
> > > underlying bus driver now??
> > >
> > > Regards, Vasili
> > >
> > >
> > > Do you Yahoo!?
> > > The New Yahoo! Search - Faster. Easier. Bingo.
> > > http://search.yahoo.com
> > >
> > >
> > >
> >
> >
> >
> > —
> > You are currently subscribed to ntdev as:
> > xxxxx@yahoo.com
> > To unsubscribe send a blank email to
> xxxxx@lists.osr.com
>
>
>
> Do you Yahoo!?
> The New Yahoo! Search - Faster. Easier. Bingo.
> http://search.yahoo.com
>
>
>
Please see below.
— “Maxim S. Shatskih”
wrote:
> Yes, such a device is attacheable to several kinds
> of buses.
>
> And to what kind of bus will your device be
> attached?
^^ that was my original question. In the .inf file
I no longer specify the bus driver (before I
explicitly specified “root bus driver”).
Regards, Vasili
>
> Max
>
> ----- Original Message -----
> From: “Galchin Vasili”
> To: “NT Developers Interest List”
>
> Cc:
> Sent: Saturday, May 10, 2003 1:45 AM
> Subject: [ntdev] Re: Bus driver question …
>
>
> >
> > So when I attach my function driver to driver
> stack
> > the underlying bus driver will be a random one???
> >
> > Regards, Bill
> >
> > — “Maxim S. Shatskih”
> > wrote:
> > > Any bus driver.
> > > These IDs are not tied to a particular bus.
> > >
> > > Max
> > >
> > > ----- Original Message -----
> > > From: “Galchin Vasili”
> > > To: “NT Developers Interest List”
> > >
> > > Sent: Saturday, May 10, 2003 12:08 AM
> > > Subject: [ntdev] Bus driver question …
> > >
> > >
> > > > Hello,
> > > >
> > > > Now in my .inf file I no longer specify
> what
> > > the
> > > > underlying bus driver is (before I had
> something
> > > like
> > > > “root\xyz”). Now in the .inf file I changed to
> > > “*xyz”
> > > > because I could not load the driver
> > > programmatically
> > > > with “root\xyz”.
> > > >
> > > > Question: with “*xyz” in my .inf file, what
> is
> > > the
> > > > underlying bus driver now??
> > > >
> > > > Regards, Vasili
> > > >
> > > >
> > > > Do you Yahoo!?
> > > > The New Yahoo! Search - Faster. Easier. Bingo.
> > > > http://search.yahoo.com
> > > >
> > > >
> > > > —
> > > > You are currently subscribed to ntdev as:
> > > xxxxx@storagecraft.com
> > > > To unsubscribe send a blank email to
> > > xxxxx@lists.osr.com
> > >
> > >
> > >
> > > —
> > > You are currently subscribed to ntdev as:
> > > xxxxx@yahoo.com
> > > To unsubscribe send a blank email to
> > xxxxx@lists.osr.com
> >
> >
> >
> > Do you Yahoo!?
> > The New Yahoo! Search - Faster. Easier. Bingo.
> > http://search.yahoo.com
> >
> >
> > —
> > You are currently subscribed to ntdev as:
> xxxxx@storagecraft.com
> > To unsubscribe send a blank email to
> xxxxx@lists.osr.com
>
>
>
> —
> You are currently subscribed to ntdev as:
> xxxxx@yahoo.com
> To unsubscribe send a blank email to
xxxxx@lists.osr.com
__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
From the DDK:
hw-id
Specifies a vendor-defined hardware ID string that identifies a device,
which the PnP Manager uses to find an INF-file match for this device. Such a
hardware ID has one of the following formats:
enumerator\enumerator-specific-device-id
Is the typical format for individual PnP devices reported to the PnP
Manager by a single enumerator. For example, USB\VID_045E&PID_00B identifies
the Microsoft HID keyboard device on a USB bus. Depending on the enumerator,
such a specification can even include the device’s hardware revision number
as, for example, PCI\VEN_1011&DEV_002&SUBSYS_00000000&REV_02.
*enumerator-specific-device-id
Indicates with the asterisk (*) that the device is supported by more than
one enumerator. For example, *PNP0F01 identifies the Microsoft serial mouse,
which also has a compatible-id specification of SERENUM\PNP0F01
What it doesn’t seem to explain, and perhaps I have missed it, is if you
don’t explicitly specify an enumerator then you are implicitly specifying
the root bus as the enumerator for your device, and this includes using * in
your case.
–
Bill McKenzie
Compuware Corporation
Watch your IRPs/IRBs/URBs/NDIS pkts with our free WDMSniffer tool:
http://frontline.compuware.com/nashua/patches/utility.htm
“Galchin Vasili” wrote in message news:xxxxx@ntdev…
>
> Please see below.
>
> — “Maxim S. Shatskih”
> wrote:
> > Yes, such a device is attacheable to several kinds
> > of buses.
> >
> > And to what kind of bus will your device be
> > attached?
> ^^ that was my original question. In the .inf file
> I no longer specify the bus driver (before I
> explicitly specified “root bus driver”).
>
> Regards, Vasili
>
> >
> > Max
> >
> > ----- Original Message -----
> > From: “Galchin Vasili”
> > To: “NT Developers Interest List”
> >
> > Cc:
> > Sent: Saturday, May 10, 2003 1:45 AM
> > Subject: [ntdev] Re: Bus driver question …
> >
> >
> > >
> > > So when I attach my function driver to driver
> > stack
> > > the underlying bus driver will be a random one???
> > >
> > > Regards, Bill
> > >
> > > — “Maxim S. Shatskih”
> > > wrote:
> > > > Any bus driver.
> > > > These IDs are not tied to a particular bus.
> > > >
> > > > Max
> > > >
> > > > ----- Original Message -----
> > > > From: “Galchin Vasili”
> > > > To: “NT Developers Interest List”
> > > >
> > > > Sent: Saturday, May 10, 2003 12:08 AM
> > > > Subject: [ntdev] Bus driver question …
> > > >
> > > >
> > > > > Hello,
> > > > >
> > > > > Now in my .inf file I no longer specify
> > what
> > > > the
> > > > > underlying bus driver is (before I had
> > something
> > > > like
> > > > > “root\xyz”). Now in the .inf file I changed to
> > > > “*xyz”
> > > > > because I could not load the driver
> > > > programmatically
> > > > > with “root\xyz”.
> > > > >
> > > > > Question: with “*xyz” in my .inf file, what
> > is
> > > > the
> > > > > underlying bus driver now??
> > > > >
> > > > > Regards, Vasili
> > > > >
> > > > >
> > > > > Do you Yahoo!?
> > > > > The New Yahoo! Search - Faster. Easier. Bingo.
> > > > > http://search.yahoo.com
> > > > >
> > > > >
> > > > > —
> > > > > You are currently subscribed to ntdev as:
> > > > xxxxx@storagecraft.com
> > > > > To unsubscribe send a blank email to
> > > > xxxxx@lists.osr.com
> > > >
> > > >
> > > >
> > > > —
> > > > You are currently subscribed to ntdev as:
> > > > xxxxx@yahoo.com
> > > > To unsubscribe send a blank email to
> > > xxxxx@lists.osr.com
> > >
> > >
> > >
> > > Do you Yahoo!?
> > > The New Yahoo! Search - Faster. Easier. Bingo.
> > > http://search.yahoo.com
> > >
> > >
> > > —
> > > You are currently subscribed to ntdev as:
> > xxxxx@storagecraft.com
> > > To unsubscribe send a blank email to
> > xxxxx@lists.osr.com
> >
> >
> >
> > —
> > You are currently subscribed to ntdev as:
> > xxxxx@yahoo.com
> > To unsubscribe send a blank email to
> xxxxx@lists.osr.com
>
>
> __________________________________
> Do you Yahoo!?
> The New Yahoo! Search - Faster. Easier. Bingo.
> http://search.yahoo.com
>
>
>
If I am not mistaken, his id with no enumerator implies no bus attachment.
The IRPs mentioned are IRP that a bus driver processes to inform PnP what
devices are attached to the bus, and reports their associated PDO’s,
relationships, etc. Thus, he either needs to write his own bus driver, much
like the toaster sample, or enumerate his device to a defined bus.
“Bill McKenzie” wrote in message
news:xxxxx@ntdev…
>
> From the DDK:
>
> hw-id
> Specifies a vendor-defined hardware ID string that identifies a device,
> which the PnP Manager uses to find an INF-file match for this device. Such
a
> hardware ID has one of the following formats:
> enumerator\enumerator-specific-device-id
> Is the typical format for individual PnP devices reported to the PnP
> Manager by a single enumerator. For example, USB\VID_045E&PID_00B
identifies
> the Microsoft HID keyboard device on a USB bus. Depending on the
enumerator,
> such a specification can even include the device’s hardware revision
number
> as, for example, PCI\VEN_1011&DEV_002&SUBSYS_00000000&REV_02.
> enumerator-specific-device-id
> Indicates with the asterisk () that the device is supported by more
than
> one enumerator. For example, *PNP0F01 identifies the Microsoft serial
mouse,
> which also has a compatible-id specification of SERENUM\PNP0F01
>
>
> What it doesn’t seem to explain, and perhaps I have missed it, is if you
> don’t explicitly specify an enumerator then you are implicitly specifying
> the root bus as the enumerator for your device, and this includes using *
in
> your case.
>
> –
> Bill McKenzie
> Compuware Corporation
> Watch your IRPs/IRBs/URBs/NDIS pkts with our free WDMSniffer tool:
> http://frontline.compuware.com/nashua/patches/utility.htm
>
>
> “Galchin Vasili” wrote in message
news:xxxxx@ntdev…
> >
> > Please see below.
> >
> > — “Maxim S. Shatskih”
> > wrote:
> > > Yes, such a device is attacheable to several kinds
> > > of buses.
> > >
> > > And to what kind of bus will your device be
> > > attached?
> > ^^ that was my original question. In the .inf file
> > I no longer specify the bus driver (before I
> > explicitly specified “root bus driver”).
> >
> > Regards, Vasili
> >
> > >
> > > Max
> > >
> > > ----- Original Message -----
> > > From: “Galchin Vasili”
> > > To: “NT Developers Interest List”
> > >
> > > Cc:
> > > Sent: Saturday, May 10, 2003 1:45 AM
> > > Subject: [ntdev] Re: Bus driver question …
> > >
> > >
> > > >
> > > > So when I attach my function driver to driver
> > > stack
> > > > the underlying bus driver will be a random one???
> > > >
> > > > Regards, Bill
> > > >
> > > > — “Maxim S. Shatskih”
> > > > wrote:
> > > > > Any bus driver.
> > > > > These IDs are not tied to a particular bus.
> > > > >
> > > > > Max
> > > > >
> > > > > ----- Original Message -----
> > > > > From: “Galchin Vasili”
> > > > > To: “NT Developers Interest List”
> > > > >
> > > > > Sent: Saturday, May 10, 2003 12:08 AM
> > > > > Subject: [ntdev] Bus driver question …
> > > > >
> > > > >
> > > > > > Hello,
> > > > > >
> > > > > > Now in my .inf file I no longer specify
> > > what
> > > > > the
> > > > > > underlying bus driver is (before I had
> > > something
> > > > > like
> > > > > > “root\xyz”). Now in the .inf file I changed to
> > > > > “*xyz”
> > > > > > because I could not load the driver
> > > > > programmatically
> > > > > > with “root\xyz”.
> > > > > >
> > > > > > Question: with “*xyz” in my .inf file, what
> > > is
> > > > > the
> > > > > > underlying bus driver now??
> > > > > >
> > > > > > Regards, Vasili
> > > > > >
> > > > > >
> > > > > > Do you Yahoo!?
> > > > > > The New Yahoo! Search - Faster. Easier. Bingo.
> > > > > > http://search.yahoo.com
> > > > > >
> > > > > >
> > > > > > —
> > > > > > You are currently subscribed to ntdev as:
> > > > > xxxxx@storagecraft.com
> > > > > > To unsubscribe send a blank email to
> > > > > xxxxx@lists.osr.com
> > > > >
> > > > >
> > > > >
> > > > > —
> > > > > You are currently subscribed to ntdev as:
> > > > > xxxxx@yahoo.com
> > > > > To unsubscribe send a blank email to
> > > > xxxxx@lists.osr.com
> > > >
> > > >
> > > >
> > > > Do you Yahoo!?
> > > > The New Yahoo! Search - Faster. Easier. Bingo.
> > > > http://search.yahoo.com
> > > >
> > > >
> > > > —
> > > > You are currently subscribed to ntdev as:
> > > xxxxx@storagecraft.com
> > > > To unsubscribe send a blank email to
> > > xxxxx@lists.osr.com
> > >
> > >
> > >
> > > —
> > > You are currently subscribed to ntdev as:
> > > xxxxx@yahoo.com
> > > To unsubscribe send a blank email to
> > xxxxx@lists.osr.com
> >
> >
> > __________________________________
> > Do you Yahoo!?
> > The New Yahoo! Search - Faster. Easier. Bingo.
> > http://search.yahoo.com
> >
> >
> >
>
>
>
>
No, his device will be enumerated by the ROOT bus if he attempts an install
with an INF containing an ID as he specified.
I just installed a WDM driver controlling no hardware with an INF containing
the following ID line:
%Blah_DeviceDesc%=Blah_DDI, *Blah
I ended up with a registry key:
\HKLM\SYSTEM\CurrentControlSet\Enum\Root\BLAH\0000
Now I should have clarified that the PnP manager won’t pick up on this
device automagically, rather he will have to use device manager or DEVCON to
instantiate an install. But, any device not handled by some other bus will
be handled by the ROOT bus, at least that is my understanding.
–
Bill McKenzie
Compuware Corporation
Watch your IRPs/IRBs/URBs/NDIS pkts with our free WDMSniffer tool:
http://frontline.compuware.com/nashua/patches/utility.htm
“Del Fredricks” wrote in message
news:xxxxx@ntdev…
>
> If I am not mistaken, his id with no enumerator implies no bus attachment.
> The IRPs mentioned are IRP that a bus driver processes to inform PnP what
> devices are attached to the bus, and reports their associated PDO’s,
> relationships, etc. Thus, he either needs to write his own bus driver,
much
> like the toaster sample, or enumerate his device to a defined bus.
>
> “Bill McKenzie” wrote in message
> news:xxxxx@ntdev…
> >
> > From the DDK:
> >
> > hw-id
> > Specifies a vendor-defined hardware ID string that identifies a device,
> > which the PnP Manager uses to find an INF-file match for this device.
Such
> a
> > hardware ID has one of the following formats:
> > enumerator\enumerator-specific-device-id
> > Is the typical format for individual PnP devices reported to the PnP
> > Manager by a single enumerator. For example, USB\VID_045E&PID_00B
> identifies
> > the Microsoft HID keyboard device on a USB bus. Depending on the
> enumerator,
> > such a specification can even include the device’s hardware revision
> number
> > as, for example, PCI\VEN_1011&DEV_002&SUBSYS_00000000&REV_02.
> > enumerator-specific-device-id
> > Indicates with the asterisk () that the device is supported by more
> than
> > one enumerator. For example, PNP0F01 identifies the Microsoft serial
> mouse,
> > which also has a compatible-id specification of SERENUM\PNP0F01
> >
> >
> > What it doesn’t seem to explain, and perhaps I have missed it, is if you
> > don’t explicitly specify an enumerator then you are implicitly
specifying
> > the root bus as the enumerator for your device, and this includes using
> in
> > your case.
> >
> > –
> > Bill McKenzie
> > Compuware Corporation
> > Watch your IRPs/IRBs/URBs/NDIS pkts with our free WDMSniffer tool:
> > http://frontline.compuware.com/nashua/patches/utility.htm
> >
> >
> > “Galchin Vasili” wrote in message
> news:xxxxx@ntdev…
> > >
> > > Please see below.
> > >
> > > — “Maxim S. Shatskih”
> > > wrote:
> > > > Yes, such a device is attacheable to several kinds
> > > > of buses.
> > > >
> > > > And to what kind of bus will your device be
> > > > attached?
> > > ^^ that was my original question. In the .inf file
> > > I no longer specify the bus driver (before I
> > > explicitly specified “root bus driver”).
> > >
> > > Regards, Vasili
> > >
> > > >
> > > > Max
> > > >
> > > > ----- Original Message -----
> > > > From: “Galchin Vasili”
> > > > To: “NT Developers Interest List”
> > > >
> > > > Cc:
> > > > Sent: Saturday, May 10, 2003 1:45 AM
> > > > Subject: [ntdev] Re: Bus driver question …
> > > >
> > > >
> > > > >
> > > > > So when I attach my function driver to driver
> > > > stack
> > > > > the underlying bus driver will be a random one???
> > > > >
> > > > > Regards, Bill
> > > > >
> > > > > — “Maxim S. Shatskih”
> > > > > wrote:
> > > > > > Any bus driver.
> > > > > > These IDs are not tied to a particular bus.
> > > > > >
> > > > > > Max
> > > > > >
> > > > > > ----- Original Message -----
> > > > > > From: “Galchin Vasili”
> > > > > > To: “NT Developers Interest List”
> > > > > >
> > > > > > Sent: Saturday, May 10, 2003 12:08 AM
> > > > > > Subject: [ntdev] Bus driver question …
> > > > > >
> > > > > >
> > > > > > > Hello,
> > > > > > >
> > > > > > > Now in my .inf file I no longer specify
> > > > what
> > > > > > the
> > > > > > > underlying bus driver is (before I had
> > > > something
> > > > > > like
> > > > > > > “root\xyz”). Now in the .inf file I changed to
> > > > > > “*xyz”
> > > > > > > because I could not load the driver
> > > > > > programmatically
> > > > > > > with “root\xyz”.
> > > > > > >
> > > > > > > Question: with “*xyz” in my .inf file, what
> > > > is
> > > > > > the
> > > > > > > underlying bus driver now??
> > > > > > >
> > > > > > > Regards, Vasili
> > > > > > >
> > > > > > >
> > > > > > > Do you Yahoo!?
> > > > > > > The New Yahoo! Search - Faster. Easier. Bingo.
> > > > > > > http://search.yahoo.com
> > > > > > >
> > > > > > >
> > > > > > > —
> > > > > > > You are currently subscribed to ntdev as:
> > > > > > xxxxx@storagecraft.com
> > > > > > > To unsubscribe send a blank email to
> > > > > > xxxxx@lists.osr.com
> > > > > >
> > > > > >
> > > > > >
> > > > > > —
> > > > > > You are currently subscribed to ntdev as:
> > > > > > xxxxx@yahoo.com
> > > > > > To unsubscribe send a blank email to
> > > > > xxxxx@lists.osr.com
> > > > >
> > > > >
> > > > >
> > > > > Do you Yahoo!?
> > > > > The New Yahoo! Search - Faster. Easier. Bingo.
> > > > > http://search.yahoo.com
> > > > >
> > > > >
> > > > > —
> > > > > You are currently subscribed to ntdev as:
> > > > xxxxx@storagecraft.com
> > > > > To unsubscribe send a blank email to
> > > > xxxxx@lists.osr.com
> > > >
> > > >
> > > >
> > > > —
> > > > You are currently subscribed to ntdev as:
> > > > xxxxx@yahoo.com
> > > > To unsubscribe send a blank email to
> > > xxxxx@lists.osr.com
> > >
> > >
> > > __________________________________
> > > Do you Yahoo!?
> > > The New Yahoo! Search - Faster. Easier. Bingo.
> > > http://search.yahoo.com
> > >
> > >
> > >
> >
> >
> >
> >
>
>
>
>