Text 11713, 306 rader
Skriven 2006-06-21 11:59:34 av Rich (1:379/45)
Kommentar till text 11712 av Robert Comer (1:379/45)
Ärende: Re: PCI hardware ID
===========================
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" <bobcomer@mindspring.com> wrote in message =
news:4499965e$1@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@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" <bobcomer@mindspring.com> wrote in message=20
news:4499947b@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@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" <bobcomer@mindspring.com> wrote in message
news:44973abc$1@w3.nls.net...
WinXP *rarely* gets a PCI NIC right...
--=20
Bob Comer
"Rich" <@> wrote in message news:44971e38@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" <black.hole.4.spam@gmail.com> wrote in message
news:zY5kEtgaX2wD092yn@attglobal.net...
In article <4493558b$1@w3.nls.net>, "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
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2912" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2> 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.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Rich</FONT></DIV>
<DIV> </DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Robert Comer" <<A=20
=
href=3D"mailto:bobcomer@mindspring.com">bobcomer@mindspring.com</A>> = wrote
in=20
message <A=20
=
href=3D"news:4499965e$1@w3.nls.net">news:4499965e$1@w3.nls.net</A>...</DI=
V>No,=20
the only time I have a problem with it is when Windows update installs =
<BR>the=20
wrong driver... (I've seen it with NIC's, audio and video=20
cards...)<BR><BR>-- <BR>Bob Comer<BR><BR><BR><BR><BR><BR>"Rich" =
<@>=20
wrote in message <A=20
=
href=3D"news:449995a9@w3.nls.net">news:449995a9@w3.nls.net</A>...<BR>&nbs=
p; =20
Incomplete, absolutely. Only devices with drivers available have =
IDs=20
<BR>known. An ID that is unknown is still one that is =
identified. =20
Are you just <BR>complaining that Windows and/or Windows Update do not =
have=20
drivers for all <BR>devices that exist in the world? Of course =
they=20
don't.<BR><BR>Rich<BR><BR> "Robert Comer" <<A=20
=
href=3D"mailto:bobcomer@mindspring.com">bobcomer@mindspring.com</A>> = wrote
in=20
message <BR><A=20
=
href=3D"news:4499947b@w3.nls.net">news:4499947b@w3.nls.net</A>...<BR>&nbs=
p;=20
> Must be an issue with the NICs you buy.<BR><BR> =
Nope,=20
the only one I've ever seen it identify correctly is the =
Intel/Dec<BR> =20
11240 type. (older than the hills in other words)<BR><BR> >I =
have=20
never had a problem. In any case, any problem is with the=20
<BR>hardware.<BR> >The >hardware identifies itself to the =
OS and=20
anyone else. Unless the<BR> >hardware >provides a =
bad ID=20
there is no problem.<BR><BR> Or the OS has in =
incomplete/incorrect list=20
to match up to...<BR><BR> -- <BR> Bob=20
Comer<BR><BR><BR><BR><BR><BR> "Rich" <@> wrote in message =
<A=20
=
href=3D"news:44999326$1@w3.nls.net">news:44999326$1@w3.nls.net</A>...<BR>=
=20
Must be an issue with the NICs you buy. I have never had a =
problem.=20
<BR>In<BR> any case, any problem is with the hardware. The =
hardware identifies <BR>itself<BR> to the OS and anyone =
else. =20
Unless the hardware provides a bad ID there is<BR> no=20
problem.<BR><BR> Rich<BR><BR> "Robert Comer" =
<<A=20
=
href=3D"mailto:bobcomer@mindspring.com">bobcomer@mindspring.com</A>> = wrote
in=20
message<BR> <A=20
=
href=3D"news:44973abc$1@w3.nls.net">news:44973abc$1@w3.nls.net</A>...<BR>=
=20
WinXP *rarely* gets a PCI NIC right...<BR><BR> --=20
<BR> Bob Comer<BR><BR><BR> "Rich"=20
<@> wrote in message <A=20
=
href=3D"news:44971e38@w3.nls.net">news:44971e38@w3.nls.net</A>...<BR>&nbs=
p; =20
Not correct. I do expect a PC to automatically detect any off=20
the<BR> shelf<BR> adapter that is plugged =
in. I=20
do not expect that all drivers will be<BR> =
automatically=20
available but that is a distinct issue from recognizing=20
<BR>the<BR> hardware. If I have a device =
without a=20
driver Windows can still tell me<BR> exactly what =
that=20
device is. Windows will offer to automatically search<BR> =20
for<BR> the driver if it is not available and for me =
often=20
finds those drivers.<BR> If<BR> the hardware =
vendors=20
choose they can have their drivers made available<BR> =20
that<BR> way.<BR><BR> =20
Rich<BR><BR> "Don Hills" <<A=20
=
href=3D"mailto:black.hole.4.spam@gmail.com">black.hole.4.spam@gmail.com</=
A>>=20
wrote in message<BR> <A=20
=
href=3D"news:zY5kEtgaX2wD092yn@attglobal.net">news:zY5kEtgaX2wD092yn@attg=
lobal.net</A>...<BR> =20
In article <<A=20
href=3D"mailto:4493558b$1@w3.nls.net">4493558b$1@w3.nls.net</A>>, =
"Rich"=20
<@> wrote:<BR> > =
You don't=20
expect a mainframe to automatically detect any off=20
the<BR> >shelf adapter that is =
plugged=20
in. The PC could go back to the dark<BR> =20
ages<BR> >too as this is how things =
used to=20
be when the PC first came to be.<BR><BR> =
You=20
don't expect a PC to automatically detect any off the shelf=20
<BR>adapter<BR> =
that<BR> is=20
plugged in, either. A device driver has to be present that=20
will<BR> recognise<BR> =
the=20
adapter's ID or that the adapter is plug compatible with =
another.<BR> =20
OS/2<BR> and Windows 9x have device =
drivers that=20
recognise plug compatible<BR> =20
adapters.<BR> The c.s.i.p.h folks are =
currently=20
running tests using the Windows 9x<BR> =20
Spock<BR> SCSI driver for the dozen or =
so plug=20
compatible Micro Channel SCSI<BR> =20
adapters<BR> from various manufacturers =
that are=20
known to exist.<BR><BR> --=20
<BR> Don=20
Hills<BR><BR><BR><BR></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_0213_01C6952A.29C92150--
--- BBBS/NT v4.01 Flag-5
* Origin: Barktopia BBS Site http://HarborWebs.com:8081 (1:379/45)
|