From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_0027_01C68F11.6ECCF660
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   64K more than enough?  Maybe for mca which failed.

   As for identifying compatible devices, mca lacks this mechanism.  =
It's entirely a guessing game.  The PCI approach is that the device =
identifies with what it is compatible.

Rich

  "Don Hills"  wrote in message =
news:ci0jEtgaXe+I092yn{at}attglobal.net...
  In article , "Rich"  wrote:
  >    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?

  That's the one. The one that's been working since the 80's. The one =
that,
  like IPv4, proved to have more than enough IDs available for the =
designers'
  foreseeable future.
  And take a look in recent threads in comp.sys.ibm.ps2.hardware by =
UZnal
  regarding the Spock and XGA drivers from Windows 98 to see how =
clueless
  Microsoft were at "identifying compatible devices" for Micro Channel. =
(In
  summary, he's used the DDK to figure out why the drivers have never =
worked
  right, and fixed them.)

  >   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.

  There are many such lists around. I have a printed catalog listing =
over a
  thousand Micro Channel adapters and their manufacturers. Very useful =
when
  you come across an unidentified adapter. (You may dismiss old computer
  hardware as irrelevant, but tinkering with old computers is no =
different
  than, say, tinkering with old cars.)

  --=20
  Don Hills
------=_NextPart_000_0027_01C68F11.6ECCF660
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   64K more than =
enough?  Maybe for=20
mca which failed.
 
   As for
identifying =
compatible devices,=20
mca lacks this mechanism.  It's entirely a guessing
game.  The = PCI=20
approach is that the device identifies with what it is =
compatible.
 
Rich
 

  "Don 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:ci0jEtgaXe+I092yn{at}attg=
lobal.net...In=20
  article <448ed68b$1{at}w3.nls.net>,">mailto:448ed68b$1{at}w3.nls.net">448ed68b$1{at}w3.nls.net>,
=
"Rich"=20
  <{at}> wrote:>   
Do you mean the 16-bit mca =
adapter=20
  IDs though would run out if there>were 64K unique =
devices?  The=20
  one that lacks the mechanisms present in>PCI to identify =
compatible=20
  devices?That's the one. The one that's been working since the =
80's.=20
  The one that,like IPv4, proved to have more than enough IDs =
available for=20
  the designers'foreseeable future.And take a look in recent =
threads in=20
  comp.sys.ibm.ps2.hardware by UZnalregarding the Spock and XGA =
drivers from=20
  Windows 98 to see how cluelessMicrosoft were at "identifying =
compatible=20
  devices" for Micro Channel. (Insummary, he's used the DDK to =
figure out=20
  why the drivers have never workedright, and fixed=20
  them.)>   I did find an
interesting list=20
 
at>>This" target="new">http://www.mcamafia.de/mcapage0/mca.dat.>This
is what =
a mca=20
  enthusiest has come up with.  Sad.There are
many such =
lists=20
  around. I have a printed catalog listing over athousand Micro =
Channel=20
  adapters and their manufacturers. Very useful whenyou come across =
an=20
  unidentified adapter. (You may dismiss old computerhardware as =
irrelevant,=20
  but tinkering with old computers is no differentthan, say, =
tinkering with=20
  old cars.)-- Don =
Hills  

------=_NextPart_000_0027_01C68F11.6ECCF660--

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