From: "Geo" 

This is a multi-part message in MIME format.

------=_NextPart_000_009E_01C69ADE.4BD3B260
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I have Intel adapters. Several vintages.

Geo.
  "Rich"  wrote in message news:44a2e5f8{at}w3.nls.net...
     Do you have Intel adapters or adapters made with Intel chipsets?  I =
have never had a problem with Intel adapters.  The proset drivers = whether
from Intel or Windows Update have always worked for me.

  Rich

    "Geo"  wrote in message =
news:449d5720$1{at}w3.nls.net...
    I have 2 intel pro 100 cards, they use different drivers, even the =
intel
    install routine can't tell them apart so I have to just try one =
driver then
    the other to figure out which one is required. The one that works is =
the
    right one. I have a third intel pro 100 that is built into a dell =
server, it
    has to have the dell driver or the machine doesn't reboot without a =
hard
    power off. So that one isn't even Intel's fault.

    Geo.


    "Frank Haber"  wrote in message
    news:449d3b07$1{at}w3.nls.net...
    > > it's the people writing the drivers and making the hardware that =
I blame
    >
    > For sure, but I can't see continuing to offer a toxic update =
facility.
    Let's
    > consider the bright side: things are getting better, but it's not =
from
    better
    > vendor diligence.  It's from chipset monopoly.  Hmm, speaking of
    monoculture -
    > there are probably some nice holes in EFI/Aptio - let's just wake =
up the
    NIC,
    > come out of S3, and PAR-TEE!
    >


------=_NextPart_000_009E_01C69ADE.4BD3B260
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








I have Intel adapters. Several=20
vintages.
 
Geo.

  "Rich" <{at}> wrote in message news:44a2e5f8{at}w3.nls.net...
     Do you
have Intel =
adapters or=20
  adapters made with Intel chipsets?  I have never had a problem =
with Intel=20
  adapters.  The proset drivers whether from Intel or Windows =
Update have=20
  always worked for me.
   
  Rich
   
  
    "Geo" <georger{at}nls.net>=20">mailto:georger{at}nls.net">georger{at}nls.net>=20
    wrote in message news:449d5720$1{at}w3.nls.net...I=20
    have 2 intel pro 100 cards, they use different drivers, even the=20
    intelinstall routine can't tell them apart so I have to just try =
one=20
    driver thenthe other to figure out which one is required. The =
one that=20
    works is theright one. I have a third intel pro 100 that is =
built into a=20
    dell server, ithas to have the dell driver or the machine =
doesn't reboot=20
    without a hardpower off. So that one isn't even Intel's=20
    fault.Geo."Frank
Haber" <frhaber{at}N0SPMrcn.com>">mailto:frhaber{at}N0SPMrcn.com">frhaber{at}N0SPMrcn.com>
=
wrote in=20
    messagenews:449d3b07$1{at}w3.nls.net...=
>=20
    > it's the people writing the drivers and making the hardware =
that I=20
    blame>> For sure, but I can't see
continuing to offer =
a toxic=20
    update facility.Let's> consider the bright
side: things =
are=20
    getting better, but it's not frombetter> vendor =
diligence. =20
    It's from chipset monopoly.  Hmm, speaking ofmonoculture =
->=20
    there are probably some nice holes in EFI/Aptio - let's just wake up =

    theNIC,> come out of S3, and=20
PAR-TEE!>

------=_NextPart_000_009E_01C69ADE.4BD3B260--

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