From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_0209_01C69529.2EF5DB60
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   Incomplete, absolutely.  Only devices with drivers available have IDs =
known.  An ID that is unknown is still one that is identified.  Are you =
just complaining that Windows and/or Windows Update do not have drivers =
for all devices that exist in the world?  Of course they don't.

Rich

  "Robert Comer"  wrote in message =
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=20
  11240 type. (older than the hills in other words)

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

  Rich

    "Robert Comer"  wrote in message=20
  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=20
  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 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=20
  for
    the driver if it is not available and for me often finds those =
drivers.=20
  If
    the hardware vendors choose they can have their drivers made =
available=20
  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=20
  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 =
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.=20
  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=20
  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_0209_01C69529.2EF5DB60
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   Incomplete, =
absolutely.  Only=20
devices with drivers available have IDs known.  An ID that is =
unknown is=20
still one that is identified.  Are you just complaining that =
Windows and/or=20
Windows Update do not have drivers for all devices that exist in the=20
world?  Of course they 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...&g=
t;  =20
  Must be an issue with the NICs you buy.Nope, the only
one I've =
ever=20
  seen it identify correctly is the Intel/Dec 11240 type. (older =
than the=20
  hills in other words)>I have never had a
problem.  In =
any=20
  case, any problem is with the hardware. >The >hardware =
identifies=20
  itself to the OS and anyone else.  Unless the
>hardware=20
  >provides a bad ID there is no problem.Or the
OS has in=20
  incomplete/incorrect list 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=20
  problem.  In any case, any problem is with the =
hardware.  The=20
  hardware identifies itself to the OS and anyone else.  Unless =
the=20
  hardware provides a bad ID there is no =
problem.Rich =20
  "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...  --
  Bob =

  Comer  "Rich"
<{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 =
the=20
  shelf  adapter that is plugged in. 
I do not expect =
that all=20
  drivers will be  automatically available but that is a =
distinct issue=20
  from recognizing the  hardware.  If I have a device =
without a=20
  driver Windows can still tell me  exactly what that device =
is. =20
  Windows will offer to automatically search for  the =
driver if it=20
  is not available and for me often finds those drivers. =
If  the=20
  hardware vendors choose they can have their drivers made available=20
  that  way. 
Rich    =
"Don=20
  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 =
expect a=20
  mainframe to automatically detect any off
the    =
>shelf=20
  adapter that is plugged in.  The PC could go back to the dark=20
  ages    >too as
this is how things used to =
be when=20
  the PC first came to
be.    You don't expect a =
PC to=20
  automatically detect any off the shelf adapter =20
  that    is plugged in, either. A
device driver has =
to be=20
  present that will 
recognise    the =
adapter's ID=20
  or that the adapter is plug compatible with another.=20
  OS/2    and Windows 9x
have device drivers that =

  recognise plug compatible 
adapters.    =
The=20
  c.s.i.p.h folks are currently running tests using the Windows 9x=20
  Spock    SCSI driver for
the dozen or so plug=20
  compatible Micro Channel SCSI 
adapters    =
from=20
  various manufacturers that are known to =
exist.    --=20
      Don =
Hills

------=_NextPart_000_0209_01C69529.2EF5DB60--

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