Hi,
Can someone explaing how are the registry entries set
for display drivers. I know that the following entries
are set using VideoPortSetRegistryParameters function
HKLM\SYSTEM\CurrentControlSet\Control\Video\PART_GUID\ID\HardwareInformation.ChipType
HKLM\SYSTEM\CurrentControlSet\Control\Video\PART_GUID\ID\HardwareInformation.DACType
HKLM\SYSTEM\CurrentControlSet\Control\Video\PART_GUID\ID\HardwareInformation.DACType
HKLM\SYSTEM\CurrentControlSet\Control\Video\PART_GUID\ID\HardwareInformation.DACType
What I don’t understand is how are these entries set.
HKLM\SYSTEM\CurrentControlSet\Enum\PCI\VENDORID\PARTID\Mfg
HKLM\SYSTEM\CurrentControlSet\Enum\PCI\VENDORID\PARTID\DeviceDesc
Are they set through the inf file. And where should
the vendow ID and PartId be specified so that their
corresponding keys are generated.
Thanks in advance
Mudeem
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
mudeem siddiqui wrote:
Can someone explaing how are the registry entries set
for display drivers. …
What I don’t understand is how are these entries set.
HKLM\SYSTEM\CurrentControlSet\Enum\PCI\VENDORID\PARTID\Mfg
HKLM\SYSTEM\CurrentControlSet\Enum\PCI\VENDORID\PARTID\DeviceDesc
Are they set through the inf file. And where should
the vendow ID and PartId be specified so that their
corresponding keys are generated.
Yes, those values come straight from the INF file.
I’m not sure I understand your second question. Every PCI device has a
vendor and device ID in its PCI configuration space. The PnP system
reads those values at enumerationg time, and uses them to figure out
which Enum registry key to use, and to search through the INF files to
find the one that includes the driver information.
If you can try asking your second question in a different way, maybe you
can get your meaning through my thick skull.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
Let me tell you my exact problem. I am working on a
virtual display driver. There is no display adapter.
My display driver fools the OS that there is a display
driver present. Now the problem is I am running
display compatibility test kit on that driver to get
it signed from Microsoft. The driver fails the
registry validation test as the test app finds the
manufacturer name (szManufacturer) null in
HKLM\SYSTEM\CurrentControlSet\Enum\PCI\VENDORID\PARTID\Mfg
Interestingly the test app finds the correct device
description (szDescription) from somewhere. Although
the WHQL test specificatoin says that it looks for the
device description in
HKLM\SYSTEM\CurrentControlSet\Enum\PCI\VENDORID\PARTID\DeviceDesc
Now as there is no physical adapter, how can I
generate a key in PCI\VENDORID\PARTID? or if there is
anyother way around this.
Mudeem
— Tim Roberts wrote:
> mudeem siddiqui wrote:
>
> >Can someone explaing how are the registry entries
> set
> >for display drivers. …
> >
> >What I don’t understand is how are these entries
> set.
>
>HKLM\SYSTEM\CurrentControlSet\Enum\PCI\VENDORID\PARTID\Mfg
>
>HKLM\SYSTEM\CurrentControlSet\Enum\PCI\VENDORID\PARTID\DeviceDesc
> >
> >Are they set through the inf file. And where should
> >the vendow ID and PartId be specified so that their
> >corresponding keys are generated.
> >
> >
>
> Yes, those values come straight from the INF file.
>
> I’m not sure I understand your second question.
> Every PCI device has a
> vendor and device ID in its PCI configuration space.
> The PnP system
> reads those values at enumerationg time, and uses
> them to figure out
> which Enum registry key to use, and to search
> through the INF files to
> find the one that includes the driver information.
>
> If you can try asking your second question in a
> different way, maybe you
> can get your meaning through my thick skull.
>
> –
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as:
> xxxxx@yahoo.com
> To unsubscribe send a blank email to
> xxxxx@lists.osr.com
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
mudeem siddiqui wrote:
Let me tell you my exact problem. I am working on a
virtual display driver. There is no display adapter.
My display driver fools the OS that there is a display
driver present.
How does it do that? The CurrentControlSet\Enum tree is supposed to
identify where the device physically exists in the device hierarchy. If
you aren’t a PCI device, then you have no business living in the
Enum\PCI tree. You should be in the Root tree, or perhaps in some
custom tree. That, of course, requires a bit of PnP activity somewhere,
to report a device relation that makes your device appear.
Now the problem is I am running
display compatibility test kit on that driver to get
it signed from Microsoft. The driver fails the
registry validation test as the test app finds the
manufacturer name (szManufacturer) null in
HKLM\SYSTEM\CurrentControlSet\Enum\PCI\VENDORID\PARTID\Mfg
How did it know to look in CCS\Enum\PCI to begin with? Does your
miniport’s Services key point back there?
Interestingly the test app finds the correct device
description (szDescription) from somewhere.
Probably from the CCS\Services key.
Now as there is no physical adapter, how can I
generate a key in PCI\VENDORID\PARTID? or if there is
anyother way around this.
You won’t appear in Enun\PCI. You’ll appear in Enum\Root or in
Enum\VirtualVideo or some other key.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
— Tim Roberts wrote:
> mudeem siddiqui wrote:
>
> >Let me tell you my exact problem. I am working on a
> >virtual display driver. There is no display
> adapter.
> >My display driver fools the OS that there is a
> display
> >driver present.
> >
>
> How does it do that? The CurrentControlSet\Enum
> tree is supposed to
> identify where the device physically exists in the
> device hierarchy. If
> you aren’t a PCI device, then you have no business
> living in the
> Enum\PCI tree. You should be in the Root tree, or
> perhaps in some
> custom tree. That, of course, requires a bit of PnP
> activity somewhere,
> to report a device relation that makes your device
> appear.
Yes the driver is present in Enum\Root\Display.
>
> >Now the problem is I am running
> >display compatibility test kit on that driver to
> get
> >it signed from Microsoft. The driver fails the
> >registry validation test as the test app finds the
> >manufacturer name (szManufacturer) null in
> >
>
>HKLM\SYSTEM\CurrentControlSet\Enum\PCI\VENDORID\PARTID\Mfg
> >
> >
>
> How did it know to look in CCS\Enum\PCI to begin
> with? Does your
> miniport’s Services key point back there?
>
The WHQL test specification says that it should look
there. But it is definitly not getting the DeviceDesc
from over there as there is nothing related to my
driver present at that location
> >Interestingly the test app finds the correct device
> >description (szDescription) from somewhere.
> >
>
> Probably from the CCS\Services key.
>
In Enum\Root\Display there is Mfg key as well for the
manufacturer. But somehow the test finds it null. Do
you think it could be looking somewhere else?
> >Now as there is no physical adapter, how can I
> >generate a key in PCI\VENDORID\PARTID? or if there
> is
> >anyother way around this.
> >
> >
>
> You won’t appear in Enun\PCI. You’ll appear in
> Enum\Root or in
> Enum\VirtualVideo or some other key.
>
Yes thats what I thought as well. There is no point
being in Enum\PCI.
> –
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as:
> xxxxx@yahoo.com
> To unsubscribe send a blank email to
> xxxxx@lists.osr.com
>
__________________________________
Yahoo! Mail - PC Magazine Editors’ Choice 2005
http://mail.yahoo.com
mudeem siddiqui wrote:
Yes the driver is present in Enum\Root\Display.
…
The WHQL test specification says that it should look
there. But it is definitly not getting the DeviceDesc
from over there as there is nothing related to my
driver present at that location
Ah, I think I see. That’s just an example, because 99.44% of all
display drivers are either PCI or AGP, and will thus appear in the
Enum\PCI tree. The Enum\Root\Display key is the one you need to worry
about. In your Services key, in the Enum subkey for your service, does
the “0” entry point to Root\Display\Something? That’s the link to the
Enum tree.
In Enum\Root\Display there is Mfg key as well for the
manufacturer. But somehow the test finds it null. Do
you think it could be looking somewhere else?
This I do not know. Make sure that Services\Xxxx\Enum\0 points to
exactly the right place.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
— Tim Roberts wrote:
> mudeem siddiqui wrote:
>
> >Yes the driver is present in Enum\Root\Display.
> >
> >…
> >
> >The WHQL test specification says that it should
> look
> >there. But it is definitly not getting the
> DeviceDesc
> >from over there as there is nothing related to my
> >driver present at that location
> >
> >
>
> In your Services key, in the Enum subkey for
> your service, does
> the “0” entry point to Root\Display\Something?
> That’s the link to the
> Enum tree.
>
Yes the Enum subkey in services point to Root\Display.
So that is correct
> >In Enum\Root\Display there is Mfg key as well for
> the
> >manufacturer. But somehow the test finds it null.
> Do
> >you think it could be looking somewhere else?
> >
>
> This I do not know. Make sure that
> Services\Xxxx\Enum\0 points to
> exactly the right place.
>
I think I’ll have to consult someone from MS DCT help
forum regarding this Issue. Thanks alot for your help.
> –
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as:
> xxxxx@yahoo.com
> To unsubscribe send a blank email to
> xxxxx@lists.osr.com
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com