| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Re: PCI hardware ID |
From: "Rich"
This is a multi-part message in MIME format.
------=_NextPart_000_006C_01C68EC1.682ED5D0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Do you mean the 16-bit mca adapter IDs though would run out if there =
were 64K unique devices? The one that lacks the mechanisms present in =
PCI to identify compatible devices?
I did find an interesting list at =
http://www.mcamafia.de/mcapage0/mca.dat. This is what a mca enthusiest =
has come up with. Sad.
Rich
"Don Hills" wrote in message =
news:O5mjEtgaXGgP092yn{at}attglobal.net...
In article , "Rich" wrote:
>
> The data isn't garbage. It is how PCI devices are identified.
All these years, and the industry has yet to better the Micro Channel =
device
ID scheme....
--=20
Don Hills
------=_NextPart_000_006C_01C68EC1.682ED5D0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Do you mean the =
16-bit mca=20
adapter IDs though would run out if there were 64K unique
devices? = The one=20
that lacks the mechanisms present in PCI to identify compatible=20
devices?
I did
find an interesting =
list at http://www.mcamafia.de/m" target="new">http://www.mcamafia.de/m=">http://www.mcamafia.de/mcapage0/mca.dat">http://www.mcamafia.de/m=
capage0/mca.dat. =20
This is what a mca enthusiest has come up with.
Sad.
Rich
* Origin: Barktopia BBS Site http://HarborWebs.com:8081 (1:379/45)SEEN-BY: 633/267 270 @PATH: 379/45 1 106/2000 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.