From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_041E_01C68CB3.31CFBB90
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   When in doubt check the PCI IDs.  Messages such as =
http://forums.nvidia.com/lofiversion/index.php?t14339.html suggest that =
the nvidia device is a realtek device of vice versa.  It sounds like =
another example of incompatible hardware using the same PCI ID.

Rich

  "Robert G Lewis"  wrote in message =
news:448b5a1e$1{at}w3.nls.net...
  In this case Windows XP does identify it correctly in Device Manager =
as a RealTek 97 audio , I do not recall any problems when I installed XP =
but that was a long time ago. I do see some entries in the registry =
relating to NVIDIA for sound in and out but that may be related to the =
one time I allowed the driver to be 'updated'. After removing it I had = no
further problems with audio or system (KB 833846).=20

  Windows Update wants to give me "NVIDIA(R) nForce(TM) Audio Codec =
Interface"for it. I misspoke when I said device driver .The MB does
have = NVIDIA components just not the audio hardware and this file WILL
cause = my system to be unstable.

  Not a big deal. just enough for me to not trust Windows Update fully. =
Given the variations possible in hardware and software configurations I =
consider this to be understandable.
    "Rich"  wrote in message news:448b497b$1{at}w3.nls.net...
       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"  wrote in message =
news:448b193f$1{at}w3.nls.net...

      "Rich Gauszka"  wrote in message=20
      news:448b1020$1{at}w3.nls.net...
      >
      > "Robert G Lewis"  wrote
in message=20
      > news:448b05af$1{at}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 . 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 . 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_041E_01C68CB3.31CFBB90
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   When in
doubt check the =
PCI IDs. =20
Messages such as http:=">http://forums.nvidia.com/lofiversion/index.php?t14339.html">http:=
//forums.nvidia.com/lofiversion/index.php?t14339.html suggest=20
that the nvidia device is a realtek device of vice versa.  It =
sounds like=20
another example of incompatible hardware using the same PCI =
ID.
 
Rich
 

  "Robert G Lewis" <r.g.lewis{at}comcast.net>">mailto:r.g.lewis{at}comcast.net">r.g.lewis{at}comcast.net>
=
wrote in=20
  message news:448b5a1e$1{at}w3.nls.net...
  In this case Windows XP does identify it
correctly =
in Device=20
  Manager as a RealTek 97 audio , I do not recall any problems when I =
installed=20
  XP but that was a long time ago. I do see some entries in the registry =

  relating to NVIDIA for sound in and out but that may be related to the =
one=20
  time I allowed the driver to be 'updated'. After removing it I had no =
further=20
  problems with audio or system (KB 833846). =

   
  Windows Update wants to give me "NVIDIA(R) =
nForce(TM) Audio=20
  Codec Interface"for it. I misspoke when I said device driver .The MB =
does have=20
  NVIDIA components just not the audio hardware and this file WILL cause =
my=20
  system to be unstable.
   
  Not a big deal. just enough for me to not trust =
Windows=20
  Update fully. Given the variations possible in hardware and software=20
  configurations I consider this to be understandable.
  

    "Rich" <{at}> wrote in message news:448b497b$1{at}w3.nls.net...
       This
is all keyed off =
the PCI ID=20
    which the hardware provides.  Unless you are trying to ID ISA =
devices=20
    something like a modem it is the hardware that is responsible for=20
    identifying both itself and the devices with which it is =
compatible. =20
    On Windows XP open the device manager, select the device of =
interest, right=20
    click, pick Properties, then select the Details tab.  The =
categories of=20
    interest here are Hardware Ids and Compatible Ids.  For =
example, my=20
    video adapter provides the following hardware IDs
     
    
      PCI\VEN_10DE&DEV_0322&SUBSYS_043110B0&REV_A1PCI\=
VEN_10DE&DEV_0322&SUBSYS_043110B0PCI\VEN_10DE&DEV_0322&am=
p;CC_030000PCI\VEN_10DE&DEV_0322&CC_0300
     
    and the following compatible =
IDs
     
    
      PCI\VEN_10DE&DEV_0322&REV_A1PCI\VEN_10DE&DEV_032=
2PCI\VEN_10DE&CC_030000PCI\VEN_10DE&CC_0300PCI\VEN_10=
DEPCI\CC_030000PCI\CC_0300
     
    How the device driver is selected =
from these=20
    IDs is explained at http://support.microsoft" target="new">http://support.microsoft.=">http://support.microsoft.com/kb/279112">http://support.microsoft.=
com/kb/279112. =20
    I didn't read through the article so I don't know if it points out =
one=20
    gotcha that are particularly relevant to OEM devices like nvidia =
display=20
    adapters.  The gotcha is that the OEMs make changes but forget =
to=20
    change the PCI IDs.  In other words, multiple incompatible =
devices=20
    claim to be the same or compatible.  I don't have this issue =
with any=20
    of my current hardware but I have two friends/family that have =
systems with=20
    OEM nvidia adapters that claim to be compatible with the nvidia =
drivers but=20
    don't work unless you use customized OEM drivers.  This sounds =
exactly=20
    like the problem you have only I think both these folks are using =
dell=20
    systems not asus systems.
     
    Rich
     
     
    
      "Robert G Lewis" <r.g.lewis{at}comcast.net>">mailto:r.g.lewis{at}comcast.net">r.g.lewis{at}comcast.net>
= wrote in=20
      message news:448b193f$1{at}w3.nls.net..."Rich=20
      Gauszka" <gauszka{at}hotmail.com>">mailto:gauszka{at}hotmail.com">gauszka{at}hotmail.com>
=
wrote in=20
      message news:448b1020$1{at}w3.nls.net...=
>>=20
      "Robert G Lewis" <r.g.lewis{at}comcast.net>">mailto:r.g.lewis{at}comcast.net">r.g.lewis{at}comcast.net>
= wrote in=20
      message > news:448b05af$1{at}w3.nls.net...=
>>>>>>=20
      Optional Hardware update, They are apparently misidentifying some =
of my=20
      >> hardware ( for 2+years now). Not something
that gives =
me a=20
      log of >> confidence in their hardware identification =
<g>.=20
      Technically its not a MS >> Driver ( from
NVIDIA ) but =
they are=20
      the ones deciding I may need
it.>>>> One =
time I=20
      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=20
      lesson <g>. I am concerned that after 2 YEARS it still =
seems to=20
      mis identify the hardware. I don't think ASUS is exactly an =
unknown MB=20
      =
maker/

------=_NextPart_000_041E_01C68CB3.31CFBB90--

--- BBBS/NT v4.01 Flag-5