From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_00AD_01C6916F.CEA2F020
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   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.

Rich

   wrote in message =
news:108423.cf2a91{at}harborwebs.com...
  Replying to a message of Don Hills to Rich:

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

   DH> That wasn't allowed. The device driver had to recognise the =
adapter
   DH> ID. This ensured that the device driver had actually been tested =
with
   DH> the adapter and proven to work reliably. Mainframe mindset.

  That 'mainframe mindset' has worked well for over half a century.  I =
have never
  heard of an IBM mainframe OS crashing absent some hardware failure.  =
We did
  manage to occasionally crash a Honeywell OS thirty years ago, though, =
but our
  particular version of the OS was heavily patched and thus =
'nonstandard'.

  --- FleetStreet 1.19+
------=_NextPart_000_00AD_01C6916F.CEA2F020
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   You don't expect =
a mainframe=20
to automatically detect any off the shelf adapter that is plugged =
in.  The=20
PC could go back to the dark ages too as this is how things used to be = when the=20
PC first came to be.
 
Rich
 

  <Bob.Ackley{at}harborwebs.com&g=">mailto:Bob.Ackley{at}harborwebs.com">Bob.Ackley{at}harborwebs.com&g=
t;=20
  wrote in message news:108423.cf2a91{at}harborwebs.=
com...Replying=20
  to a message of Don Hills to
Rich: >>   =
As for=20
  identifying compatible devices, mca lacks this mechanism.=20
  It's >> entirely a guessing
game.  The PCI =
approach is=20
  that the device >> identifies with what it is=20
  compatible. DH> That wasn't allowed.
The device driver =
had to=20
  recognise the adapter DH> ID. This ensured that
the device =
driver=20
  had actually been tested with DH> the adapter
and proven =
to work=20
  reliably. Mainframe mindset.That 'mainframe mindset' has =
worked well=20
  for over half a century.  I have neverheard of an IBM =
mainframe OS=20
  crashing absent some hardware failure.  We didmanage to =
occasionally=20
  crash a Honeywell OS thirty years ago, though, but ourparticular =
version=20
  of the OS was heavily patched and thus 'nonstandard'.--- =
FleetStreet=20
(1:2905/3)

------=_NextPart_000_00AD_01C6916F.CEA2F020--

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