Hi,
I found some posts on the list dealing with the same
issue but didnt see a conclusion to any of those to
answer my question.
I have this virtual display device driver which is
installed and works fine. However when i run dxdiag
the display 2 tab shows the manufacturer string as
n/a. Now I went to the registry and checked out
HKLM\System\CCS\Enum\Root\DISPLAY\xxxx\Mfg entry which
was a valid string, non-zero length, no Microsoft in
there. So i checked out the
Services\CompanyName\Enum\0 key which pointed rightly
to Root\DISPLAY\xxxx.
Next I ran dxdiag with a registry spy running. Now the
spy detected dxdiag accessing the keys in
Services\CompanyName\Device0 such as
HardwareInformation.ChipType and
HardwareInformation.DacType but it was neither going
to Services\CompanyName\Enum\0 nor to the path it
specified(Root\DISPLAY\xxxx).
However for the principal display driver on my PC (an
ATI rage driver) it dislayed the manufacturer string
from HKLM\System\CCS\Enum\PCI\VENDORID\PARTID\Msg key
even though it just like for the VDD has not found the
path from Services\atirage3\Enum\0. So does that mean
it enumerates the devices it actually physically
detects and only their
HKLM\System\CCS\Enum\PCI\VENDORID\PARTID\Msg keys are
accessed or am I seriously flawed here?
Any help most appreciated,
Zeeshan
Yahoo! Mail - PC Magazine Editors’ Choice 2005
http://mail.yahoo.com