From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_0213_01C6952A.29C92150
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   I've only seen it with Nvidia adapters.  Never with NICs and never =
with audio.  You should buy better NICs if you are seeing this problem.

Rich

  "Robert Comer"  wrote in message =
news:4499965e$1{at}w3.nls.net...
  No, the only time I have a problem with it is when Windows update =
installs=20
  the wrong driver...  (I've seen it with NIC's, audio and video =
cards...)

  --=20
  Bob Comer





  "Rich"  wrote in message news:449995a9{at}w3.nls.net...
     Incomplete, absolutely.  Only devices with drivers available have =
IDs=20
  known.  An ID that is unknown is still one that is identified.  Are =
you just=20
  complaining that Windows and/or Windows Update do not have drivers for =
all=20
  devices that exist in the world?  Of course they don't.

  Rich

    "Robert Comer"  wrote in message=20
  news:4499947b{at}w3.nls.net...
    >   Must be an issue with the NICs you buy.

    Nope, the only one I've ever seen it identify correctly is the =
Intel/Dec
    11240 type. (older than the hills in other words)

    >I have never had a problem.  In any case, any problem is with the=20
  hardware.
    >The >hardware identifies itself to the OS and anyone else.  Unless =
the
    >hardware >provides a bad ID there is no problem.

    Or the OS has in incomplete/incorrect list to match up to...

    --=20
    Bob Comer





    "Rich"  wrote in message news:44999326$1{at}w3.nls.net...
       Must be an issue with the NICs you buy.  I have never had a =
problem.=20
  In
    any case, any problem is with the hardware.  The hardware identifies =

  itself
    to the OS and anyone else.  Unless the hardware provides a bad ID =
there is
    no problem.

    Rich

      "Robert Comer"  wrote in message
    news:44973abc$1{at}w3.nls.net...
      WinXP *rarely* gets a PCI NIC right...

      --=20
      Bob Comer


      "Rich"  wrote in message news:44971e38{at}w3.nls.net...
         Not correct.  I do expect a PC to automatically detect any off =
the
    shelf
      adapter that is plugged in.  I do not expect that all drivers will =
be
      automatically available but that is a distinct issue from =
recognizing=20
  the
      hardware.  If I have a device without a driver Windows can still =
tell me
      exactly what that device is.  Windows will offer to automatically =
search
    for
      the driver if it is not available and for me often finds those =
drivers.
    If
      the hardware vendors choose they can have their drivers made =
available
    that
      way.

      Rich

        "Don Hills"  wrote in message
      news:zY5kEtgaX2wD092yn{at}attglobal.net...
        In article , "Rich"  wrote:
        >   You don't expect a mainframe to automatically detect any off =
the
        >shelf adapter that is plugged in.  The PC could go back to the =
dark
    ages
        >too as this is how things used to be when the PC first came to =
be.

        You don't expect a PC to automatically detect any off the shelf=20
  adapter
      that
        is plugged in, either. A device driver has to be present that =
will
      recognise
        the adapter's ID or that the adapter is plug compatible with =
another.
    OS/2
        and Windows 9x have device drivers that recognise plug =
compatible
      adapters.
        The c.s.i.p.h folks are currently running tests using the =
Windows 9x
    Spock
        SCSI driver for the dozen or so plug compatible Micro Channel =
SCSI
      adapters
        from various manufacturers that are known to exist.

        --=20
        Don Hills




------=_NextPart_000_0213_01C6952A.29C92150
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   I've only
seen it with =
Nvidia=20
adapters.  Never with NICs and never with audio.  You
should = buy=20
better NICs if you are seeing this problem.
 
Rich
 

  "Robert Comer" <bobcomer{at}mindspring.com>">mailto:bobcomer{at}mindspring.com">bobcomer{at}mindspring.com>
= wrote in=20
  message news:4499965e$1{at}w3.nls.net...No,=20
  the only time I have a problem with it is when Windows update installs =
the=20
  wrong driver...  (I've seen it with NIC's, audio and video=20
  cards...)-- Bob
Comer"Rich"
=
<{at}>=20
  wrote in message news:449995a9{at}w3.nls.net...&nbs=
p; =20
  Incomplete, absolutely.  Only devices with drivers available have =
IDs=20
  known.  An ID that is unknown is still one that is =
identified. =20
  Are you just complaining that Windows and/or Windows Update do not =
have=20
  drivers for all devices that exist in the world?  Of course =
they=20
  don't.Rich  "Robert
Comer" <bobcomer{at}mindspring.com>">mailto:bobcomer{at}mindspring.com">bobcomer{at}mindspring.com>
= wrote in=20
  message news:4499947b{at}w3.nls.net...&nbs=
p;=20
  >   Must be an issue with the NICs you
buy.  =
Nope,=20
  the only one I've ever seen it identify correctly is the =
Intel/Dec =20
  11240 type. (older than the hills in other
words)  >I =
have=20
  never had a problem.  In any case, any problem is with the=20
  hardware.  >The >hardware
identifies itself to the =
OS and=20
  anyone else.  Unless the  >hardware
>provides a =
bad ID=20
  there is no problem.  Or the OS has in =
incomplete/incorrect list=20
  to match up to...  --   Bob=20
 
Comer 
"Rich" <{at}> wrote in message =
news:44999326$1{at}w3.nls.net...=
    =20
  Must be an issue with the NICs you buy.  I have never had a =
problem.=20
  In  any case, any problem is with the
hardware.  The =

  hardware identifies itself  to the OS and anyone =
else. =20
  Unless the hardware provides a bad ID there is  no=20
  problem. 
Rich    "Robert
Comer" =
<bobcomer{at}mindspring.com>">mailto:bobcomer{at}mindspring.com">bobcomer{at}mindspring.com>
= wrote in=20
  message  news:44973abc$1{at}w3.nls.net...=
   =20
  WinXP *rarely* gets a PCI NIC
right...    --=20
      Bob
Comer   
"Rich"=20
  <{at}> wrote in message news:44971e38{at}w3.nls.net...&nbs=
p;     =20
  Not correct.  I do expect a PC to automatically detect any off=20
  the  shelf   
adapter that is plugged =
in.  I=20
  do not expect that all drivers will be    =
automatically=20
  available but that is a distinct issue from recognizing=20
  the    hardware. 
If I have a device =
without a=20
  driver Windows can still tell me   
exactly what =
that=20
  device is.  Windows will offer to automatically
search =20
  for    the driver if it is not
available and for me =
often=20
  finds those drivers. 
If    the hardware =
vendors=20
  choose they can have their drivers made available =20
  that   
way.   =20
 
Rich     
"Don Hills" <black.hole.4.spam{at}gmail.commailto:black.hole.4.spam{at}gmail.com">black.hole.4.spam{at}gmail.com
A>>=20
  wrote in message    news:zY5kEtgaX2wD092yn{at}attg=
lobal.net...     =20
  In article <4493558b$1{at}w3.nls.net>,">mailto:4493558b$1{at}w3.nls.net">4493558b$1{at}w3.nls.net>,
=
"Rich"=20
  <{at}>
wrote:     
>   =
You don't=20
  expect a mainframe to automatically detect any off=20
  the     
>shelf adapter that is =
plugged=20
  in.  The PC could go back to the dark =20
  ages     
>too as this is how things =
used to=20
  be when the PC first came to
be.      =
You=20
  don't expect a PC to automatically detect any off the shelf=20
  adapter    =
that      is=20
  plugged in, either. A device driver has to be present that=20
  will   
recognise      =
the=20
  adapter's ID or that the adapter is plug compatible with =
another. =20
  OS/2      and
Windows 9x have device =
drivers that=20
  recognise plug compatible   =20
  adapters.      The
c.s.i.p.h folks are =
currently=20
  running tests using the Windows 9x =20
  Spock      SCSI
driver for the dozen or =
so plug=20
  compatible Micro Channel SCSI   =20
  adapters      from
various manufacturers =
that are=20
  known to
exist.     
--=20
        Don=20
Hills

------=_NextPart_000_0213_01C6952A.29C92150--

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