MicroChannel Reference Database
  Home  |  Main  |  What's new  |  Credits  |  Participate  |  Updated  |  About

MicroChannel Adapters by Adapter-ID and Company
PageID RangePageID Range
 --0000 - FFFF  
 19000 - FFFF 66200 - 64FF
 28000 - 8FFF 76000 - 61FF
 37000 - 7FFF 85800 - 5FFF
 46B00 - 6FFF 95000 - 57FF
 56500 - 6AFF100000 - 4FFF
IBMIBM Corp.CBLTCabletron
INTELIntel Corp.CMPTComputone

MicroChannel Adapters by Class

 TRToken-Ring SERSerial Port
 ETEthernet PARParallel Port
STO Mass Storage MPTMulti-Protocol
 SCSISCSI 32703270 Connection
 FLDDiskette DrivesIOIOInput/Output Boards
 CDRCD-ROM Drives DAQData Acquisition
 TAPTape DrivesDEVDEVDevices
PRCPRCProcessors PRTPrinter Adapters
 CPUCPU Complexes SCNScanner
MEMMEMMemory SECSecurity Options
 MFMultifunction Boards PENLight Pen
VIDVIDVideo JSTGame/Joystick
SNDAUDAudio NLSNational Language
 VOIVoice Adapters TRMTerminal Emulation

IBM Microchannel Adapter ID Assigments

The MicroChannel Adapter Design Guidelines in the IBM Technical Reference specify adapter ID assigments for the different classes of adapters. However, this recommendation has not been followed or implemented strictly.

The following table shows the recommended ID values for vendors according to the adapter function. ID values 8200 to FFFE are assigned for IBM products only.

ID ValuesClass or Function
0000Device Not Ready
0001 - 0FFFBusmaster Devices
5000 - 5FFFDMA Devices
6000 - 6FFFDirect Program Control (incl. Memory Mapped I/O)
7000 - 7FFFStorage (incl. Multifunction Adapters containing storage)
7DB8 - 7DBFReserved for Prototypes
8000 - 81FFVideo
8200 - FFFEIBM Products Only
FFFFDevice Not Attached

The adapter IDs hex 7DB8 through 7DBF are reserved for the prototyping, developing, and testing of adapters and adapter designs and for adapters used in the testing of system design. These IDs should not be used for purposes other than the local development of adapters or systems.

How to participate and contribute

You are invited to author adapter pages, send adapter images, ADFs, links to drivers and adapter related resources, in short, any information you consider useful and worth sharing.

If you maintain your own web site where you provide specific information about adapters, you may send the links to your adapter pages along with a complementary information.

Send your contributions to unalz-at-mail333-dot-com. Contributions will be acknowledged and credited. Contributors are logged in the Credits page and subsequently linked to it.


Colored text entries denote hyperlinks. In the rare cases of misplaced entries, please suggest changes to unalz-at-mail333-dot-com or post a message to comp.sys.ibm.ps2.hardware.

Individual adapter pages have been statically

The implication is that you might eventually get out of focus if you choose to follow the adapter page links. Use the browser navigation controls as an additional navigation aid.


The MCA Adapter Database started in Jan 2006 with entries for 1170 adapters and 622 Adapter Description Files (ADF). The source of these first 622 ADFs was the EPRM ADF collection, ADF contents were extracted and converted first to HTML files with the INF2HTML utility (INF2HTML V0.91, Copyright © 1997-98 Ulrich Möller), and then to plain ADFs with the macros of the DOS version of the AEDIT-86 Text Editor (Aedit V2.2 Copyright 1983-85 Intel Corp.).

The obtained ADFs were merged with the already existing ID-Range pages, based on the existing QUMC adapter list. Adapter classes were defined and individual adapter classification performed manually whereas origin categorization was performed fully automatically with Aedit macros. Separation of adapters into class and origin (company) pages was again done with Aedit macros, also the final generation of the individual adapter pages. This final, in the context of Aedit macros, computationally complex step required carefully synchronized advanced Aedit macros.

An adapter page is automatically generated from one of the two templates (ADF or not-ADF) by substituting predefined parameters in the template with values taken from the table-row (<TR>) entry for the adapter where row cells (<TD>) are tagged with HTML comments to designate columns and simulate keys for database records. A tagged HTML table description is thus seen and treated as a "database table" (which it is implicitly anyway) in this simple model.

Credit for the quick production of the MCA Adapter Database deserves solely Aedit. I am greatly indebted to this powerful and yet minimalistic text processing machine, in fact, a micro[text]processor embodied in mere 76,895 bytes of software. (UZ)

 Legal  |  Copyrighttop  
  Contents © 2006