Text 11495, 198 rader
Skriven 2006-06-10 15:36:16 av Rich (1:379/45)
Kommentar till text 11492 av Robert G Lewis (1:379/45)
Ärende: Re: PCI hardware ID
===========================
From: "Rich" <@>
This is a multi-part message in MIME format.
------=_NextPart_000_03D7_01C68CA3.9CEAF6C0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
This is all keyed off the PCI ID which the hardware provides. Unless =
you are trying to ID ISA devices something like a modem it is the = hardware
that is responsible for identifying both itself and the devices = with which it
is compatible. On Windows XP open the device manager, = select the device of
interest, right click, pick Properties, then select = the Details tab. The
categories of interest here are Hardware Ids and = Compatible Ids. For
example, my video adapter provides the following = hardware IDs
PCI\VEN_10DE&DEV_0322&SUBSYS_043110B0&REV_A1
PCI\VEN_10DE&DEV_0322&SUBSYS_043110B0
PCI\VEN_10DE&DEV_0322&CC_030000
PCI\VEN_10DE&DEV_0322&CC_0300
and the following compatible IDs
PCI\VEN_10DE&DEV_0322&REV_A1
PCI\VEN_10DE&DEV_0322
PCI\VEN_10DE&CC_030000
PCI\VEN_10DE&CC_0300
PCI\VEN_10DE
PCI\CC_030000
PCI\CC_0300
How the device driver is selected from these IDs is explained at =
http://support.microsoft.com/kb/279112. I didn't read through the = article so
I don't know if it points out one gotcha that are = particularly relevant to
OEM devices like nvidia display adapters. The = gotcha is that the OEMs make
changes but forget to change the PCI IDs. = In other words, multiple
incompatible devices claim to be the same or = compatible. I don't have this
issue with any of my current hardware but = I have two friends/family that have
systems with OEM nvidia adapters = that claim to be compatible with the nvidia
drivers but don't work = unless you use customized OEM drivers. This sounds
exactly like the = problem you have only I think both these folks are using
dell systems = not asus systems.
Rich
"Robert G Lewis" <r.g.lewis@comcast.net> wrote in message =
news:448b193f$1@w3.nls.net...
"Rich Gauszka" <gauszka@hotmail.com> wrote in message=20
news:448b1020$1@w3.nls.net...
>
> "Robert G Lewis" <r.g.lewis@comcast.net> wrote in message=20
> news:448b05af$1@w3.nls.net...
>>
>>
>> Optional Hardware update, They are apparently misidentifying some =
of my=20
>> hardware ( for 2+years now). Not something that gives me a log of=20
>> confidence in their hardware identification <g>. Technically its =
not a MS=20
>> Driver ( from NVIDIA ) but they are the ones deciding I may need =
it.
>>
>
> One time I blue screened and hosed my system with an internal modem =
update=20
> WU thought I should have. Stayed away form Microsoft's hardware =
update=20
> recommendations ever since
>
That will teach a lesson <g>. I am concerned that after 2 YEARS it =
still=20
seems to mis identify the hardware. I don't think ASUS is exactly an =
unknown=20
MB maker/
------=_NextPart_000_03D7_01C68CA3.9CEAF6C0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2873" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2> This is all keyed off the =
PCI ID which=20
the hardware provides. Unless you are trying to ID ISA devices =
something=20
like a modem it is the hardware that is responsible for identifying both =
itself=20
and the devices with which it is compatible. On Windows XP open = the
device=20
manager, select the device of interest, right click, pick Properties, = then=20
select the Details tab. The categories of interest here are = Hardware
Ids=20
and Compatible Ids. For example, my video adapter provides the =
following=20
hardware IDs</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
<DIV><FONT face=3DArial=20
=
size=3D2>PCI\VEN_10DE&DEV_0322&SUBSYS_043110B0&REV_A1<BR>PCI\=
VEN_10DE&DEV_0322&SUBSYS_043110B0<BR>PCI\VEN_10DE&DEV_0322&am=
p;CC_030000<BR>PCI\VEN_10DE&DEV_0322&CC_0300</FONT></DIV></BLOCKQ=
UOTE>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>and the following compatible =
IDs</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
<DIV><FONT face=3DArial=20
=
size=3D2>PCI\VEN_10DE&DEV_0322&REV_A1<BR>PCI\VEN_10DE&DEV_032=
2<BR>PCI\VEN_10DE&CC_030000<BR>PCI\VEN_10DE&CC_0300<BR>PCI\VEN_10=
DE<BR>PCI\CC_030000<BR>PCI\CC_0300</FONT></DIV></BLOCKQUOTE>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>How the device driver is selected from =
these IDs is=20
explained at <A=20
href=3D"http://support.microsoft.com/kb/279112">http://support.microsoft.=
com/kb/279112</A>. =20
I didn't read through the article so I don't know if it points out one =
gotcha=20
that are particularly relevant to OEM devices like nvidia display=20
adapters. The gotcha is that the OEMs make changes but forget to =
change=20
the PCI IDs. In other words, multiple incompatible devices claim = to be
the=20
same or compatible. I don't have this issue with any of my current =
hardware but I have two friends/family that have systems with OEM nvidia =
adapters that claim to be compatible with the nvidia drivers but don't =
work=20
unless you use customized OEM drivers. This sounds exactly like = the=20
problem you have only I think both these folks are using dell systems = not
asus=20
systems.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Rich</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Robert G Lewis" <<A=20
href=3D"mailto:r.g.lewis@comcast.net">r.g.lewis@comcast.net</A>> =
wrote in=20
message <A=20
=
href=3D"news:448b193f$1@w3.nls.net">news:448b193f$1@w3.nls.net</A>...</DI=
V><BR>"Rich=20
Gauszka" <<A =
href=3D"mailto:gauszka@hotmail.com">gauszka@hotmail.com</A>>=20
wrote in message <BR><A=20
=
href=3D"news:448b1020$1@w3.nls.net">news:448b1020$1@w3.nls.net</A>...<BR>=
><BR>>=20
"Robert G Lewis" <<A=20
href=3D"mailto:r.g.lewis@comcast.net">r.g.lewis@comcast.net</A>> =
wrote in=20
message <BR>> <A=20
=
href=3D"news:448b05af$1@w3.nls.net">news:448b05af$1@w3.nls.net</A>...<BR>=
>><BR>>><BR>>>=20
Optional Hardware update, They are apparently misidentifying some of =
my=20
<BR>>> hardware ( for 2+years now). Not something that gives me =
a log of=20
<BR>>> confidence in their hardware identification <g>.=20
Technically its not a MS <BR>>> Driver ( from NVIDIA ) but they =
are the=20
ones deciding I may need it.<BR>>><BR>><BR>> One time I =
blue=20
screened and hosed my system with an internal modem update <BR>> WU =
thought=20
I should have. Stayed away form Microsoft's hardware update <BR>>=20
recommendations ever since<BR>><BR><BR>That will teach a lesson =
<g>.=20
I am concerned that after 2 YEARS it still <BR>seems to mis identify =
the=20
hardware. I don't think ASUS is exactly an unknown <BR>MB=20
maker/<BR><BR></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_03D7_01C68CA3.9CEAF6C0--
--- BBBS/NT v4.01 Flag-5
* Origin: Barktopia BBS Site http://HarborWebs.com:8081 (1:379/45)
|