From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_0015_01C68E0D.D7EB5100
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   I doubt anyone is deliberately having the hardware return incorrect =
IDs.  If I had to guess they hardware was designed to be compatible and =
then found not to be.  Why whatever changes the OEMs have to do to their =
drivers can't be supported in the nvidia drivers I do not know.  I = expect
any such changes to be small.  That though is a business decision = between
nvida and its oems.

   The data isn't garbage.  It is how PCI devices are identified.

Rich

  "Frank Haber"  wrote in message =
news:448da34d$1{at}w3.nls.net...
  >   That would deny them to the bulk of the users which have good =
hardware.

  I think I'm going to challenge that.

  o Given that, what, 60% of the machines out there are Dell, HP and a =
couple of=20
  others (guessing)....

  o and that Dell and HP, at least, have a history of buying =
cost-reduced OEM=20
  hardware, or subtly different variants "just because" (? to be =
different?  ?to=20
  retain update control?), and affixing ?deliberately sketchy/generic =
PCI=20
  IDs....

  o then doesn't it make sense for MS to give up this irritating and =
Quixotic=20
  scheme, which bases machine-munging updates on garbage data?


  ....the above advice is offered sans strings under the Who Cares =
licensing=20
  program, which I have just invented, named and forgotten practically =
in one=20
  breath.  Use or discard at will, but breathe free, if you still can.=20

------=_NextPart_000_0015_01C68E0D.D7EB5100
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   I doubt anyone is =
deliberately having=20
the hardware return incorrect IDs.  If I had to guess they hardware = was=20
designed to be compatible and then found not to be.  Why whatever
= changes=20
the OEMs have to do to their drivers can't be supported in the nvidia = drivers I=20
do not know.  I expect any such changes to be small. 
That = though is a=20
business decision between nvida and its oems.
 
   The data isn't =
garbage.  It is=20
how PCI devices are identified.
 
Rich
 

  "Frank Haber" <frhaber{at}N0SPMrcn.com>">mailto:frhaber{at}N0SPMrcn.com">frhaber{at}N0SPMrcn.com>
=
wrote in=20
  message news:448da34d$1{at}w3.nls.net...>  =20
  That would deny them to the bulk of the users which have good=20
  hardware.I think I'm going to challenge
that.o Given =
that,=20
  what, 60% of the machines out there are Dell, HP and a couple of =
others=20
  (guessing)....o and that Dell and HP, at least, have
a history =
of=20
  buying cost-reduced OEM hardware, or subtly different variants =
"just=20
  because" (? to be different?  ?to retain update
control?), =
and=20
  affixing ?deliberately sketchy/generic PCI
IDs....o then =
doesn't=20
  it make sense for MS to give up this irritating and Quixotic =
scheme, which=20
  bases machine-munging updates on garbage
data?....the =
above advice=20
  is offered sans strings under the Who Cares licensing program, =
which I=20
  have just invented, named and forgotten practically in one =
breath. =20
  Use or discard at will, but breathe free, if you still can.=20


------=_NextPart_000_0015_01C68E0D.D7EB5100--

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