Text 11711, 245 rader
Skriven 2006-06-21 11:52:34 av Rich (1:379/45)
Kommentar till text 11710 av Robert Comer (1:379/45)
Ärende: Re: PCI hardware ID
===========================
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" <bobcomer@mindspring.com> wrote in message =
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=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@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" <bobcomer@mindspring.com> wrote in message=20
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=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" <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=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
<!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> 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.</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:4499947b@w3.nls.net">news:4499947b@w3.nls.net</A>...</DIV>&g=
t; =20
Must be an issue with the NICs you buy.<BR><BR>Nope, the only one I've =
ever=20
seen it identify correctly is the Intel/Dec <BR>11240 type. (older =
than the=20
hills in other words)<BR><BR>>I have never had a problem. In =
any=20
case, any problem is with the hardware. <BR>>The >hardware =
identifies=20
itself to the OS and anyone else. Unless the <BR>>hardware=20
>provides a bad ID there is no problem.<BR><BR>Or the OS has in=20
incomplete/incorrect list 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=20
problem. In <BR>any case, any problem is with the =
hardware. The=20
hardware identifies itself <BR>to the OS and anyone else. Unless =
the=20
hardware provides a bad ID there is <BR>no =
problem.<BR><BR>Rich<BR><BR> =20
"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> -- <BR> Bob =
Comer<BR><BR><BR> "Rich" <@> 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 =
the=20
<BR>shelf<BR> adapter that is plugged in. I do not expect =
that all=20
drivers will be<BR> automatically available but that is a =
distinct issue=20
from recognizing the<BR> hardware. If I have a device =
without a=20
driver Windows can still tell me<BR> exactly what that device =
is. =20
Windows will offer to automatically search <BR>for<BR> the =
driver if it=20
is not available and for me often finds those drivers. =
<BR>If<BR> the=20
hardware vendors choose they can have their drivers made available=20
<BR>that<BR> way.<BR><BR> Rich<BR><BR> =
"Don=20
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 =
expect a=20
mainframe to automatically detect any off the<BR> =
>shelf=20
adapter that is plugged in. The PC could go back to the dark=20
<BR>ages<BR> >too as this is how things used to =
be when=20
the PC first came to be.<BR><BR> You don't expect a =
PC to=20
automatically detect any off the shelf adapter<BR> =20
that<BR> is plugged in, either. A device driver has =
to be=20
present that will<BR> recognise<BR> the =
adapter's ID=20
or that the adapter is plug compatible with another.=20
<BR>OS/2<BR> and Windows 9x have device drivers that =
recognise plug compatible<BR> adapters.<BR> =
The=20
c.s.i.p.h folks are currently running tests using the Windows 9x=20
<BR>Spock<BR> SCSI driver for the dozen or so plug=20
compatible Micro Channel SCSI<BR> adapters<BR> =
from=20
various manufacturers that are known to =
exist.<BR><BR> --=20
<BR> Don =
Hills<BR><BR><BR></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_0209_01C69529.2EF5DB60--
--- BBBS/NT v4.01 Flag-5
* Origin: Barktopia BBS Site http://HarborWebs.com:8081 (1:379/45)
|