@8FA0.ADF - IBM LANStreamer MC 32 Adapter
W95 Configurable Settings
LanStreamer Not Seen Under NT4
TRMLS322.EXE Diagnostics and Option Diskette v2.0 (requires a 720k diskette, not 1.44M)
TRMLS321.EXE  Drivers v3.0

LanStreamer SCO Unix file 2 of 2
LanStreamer SCO Unix file 1 of 2

IBM LANStreamer MC 32 Adapter

Adapter Data Rate:  This Token-Ring Network Adapter can operate at two different data rates:  4 Mbps or 16 Mbps. The adapter data rate MUST be set to the rate of the Token-Ring Network LAN segment to which you are connecting the adapter.

Media Type Selection:  This Token-Ring Network Adapter supports two media types,  STP and UTP. The media type selected MUST be cable connected to the token ring. If not the adapter will exhibit a LOBE MEDIA FAILURE. (STP is the IBM cabling).

Interrupt Level This Token-Ring Network Adapter can operate on one of four interrupt levels:  2, 3, 10 or 11. The preferred interrupt level is 3, but the adapter can operate on any of the four levels if necessary.

Parity Enable/Monitor Feedback This Token-Ring Adapter provides the capability of generating and checking data and address parity.  This adapter also provides the capability of monitoring slave device's Selected Feedback Return Exception signals during DMA operations.

Remote Program Load This Token-Ring Network adapter Remote Program Load (RPL) ROM is relocatable within Micro Channel memory space. The adapter RPL ROM may be located on any 16K boundary from hex 000C 000 to 000D C000.

Fairness/Streaming Data This Token-Ring Network Adapter can operate with or without arbitration fairness and with or without Data Streaming.

Lalali lalala .. its a "no go" unless you have SP3 or the revised NDIS.SYS (122.224 bytes) from Micro$haft. 

There is a document from IBM - RMIE-3ACDGC "Servers - Streamers not working under Windows NT v4.0", which references Q156324 "MCAFINDBUS fails to enumerate net cards / Device Manager Message with MCA Network Adapter" (NT looked at MCA slots starting with 0, not 1)

Non-MCA buses are not affected by this problem. The following MCA network adapters are known to be affected: 3Com 3C527 Etherlink MC/32, IBM Streamer adapters, Cabletron F30xx FDDI, NCR Starlan TR, NCR Wavelan and SysKonnect FDDI

The M$ Knowlegde Base has the Articles Q157815 "Service Control Manager Event 7003 and 7024 (2105)" / Netbios Interface missing (install or bind Netbios), Q131351 "IBM Lan Streamer Error" / data integrity problems with L-S card FRU 92F8941 available for further problem analysis if that failed. (Contact IBM for replacement of the card...)

The Ndis.sys device driver in Service Pack 2 fails to detect any network cards installed in MCA slots 8 or higher. Network cards installed in slots 1 through 7 are detected by Windows NT and function normally. 

Failure to Obtain IP Address Via DHCP on Token Ring w/ SP2 Q163383
   When you run Windows NT version 4.0, with Service Pack 2 applied, in a source routed Token Ring environment and configured as a DHCP client, you may receive the following message when you start:  The DHCP client could not obtain an IP address.  If you want to see DHCP messages in the future, choose YES, otherwise choose NO. 
Fix Change the ArpAlwaysSourceRoute value to 1. If this value is not present, click on Edit, Add Value, and enter the following settings: Value Type: REG_DWORD - Boolean Valid Range: 0,1 (False or True) Default: 0 (False) 

Slot 8 Incompatability in 8595 and  9595
A 00017100 (171) error occurs on POST (Power-On System Test). This problem may occur on 8595/9595 models xLx or xHx systems during the installation of any of the following adapters in micro channel slot 8:
- IBM LANStreamer MC 32 / 16 
- IBM EtherStreamer MC 32 
- IBM Auto / Dual LANStreamer MC 32
- IBM Dual EtherStreamer MC 32
Fix (Pretty wild, eh?)
Do not install any of the affected adapters in slot 8. Relocate any of the affected adapters to one of the other microchannel slots.