| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | PCI hardware ID |
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+* Origin: Bob's Boneyard, Emerson, Iowa (1:2905/3) SEEN-BY: 633/267 270 @PATH: 2905/3 282/0 14/5 153/757 106/1 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™.