Drivers/Diagnostic/Option disk v2.0
@E001.ADF - IBM Token-Ring Network 16/4 Adapter/A (Tropic based)
There are a few differences between cards that I haven't a explanaition for. If you have a better answer (or just an answer) send it to ME.
Short 16/4 Token Ring Adapter
(74F9415 or 74F9321)
Short 16/4 Token Ring Adapter (74F9415 or 74F9321)
Most short 16/4 have the RPL-code integrated in the ROM-code - the 4Mb/s and the long 16/4 adapters have a separate ROM for it - and the chip needed to be purchased separately.
02G1394ESD vs. 50G6144ESD
16/4 Long Token Ring Adapter 53F7748
ZM13 Mitsubishi M5M5256BP-10L
ZM15 Mitsubishi M5M5256BP-10L
Differences between the 53F and 16F adapters are the addition of a 64D7274ESD and different ROM (25F9532 and 25F9531). They are basically the same - however the one with the 64D7274 at ZM3 is the later revision. This chip contains the output drivers and some "corporate logic", which was the 2 14-pin ICs on the elder version (ZM1 & ZM4).
The P/N for the RPL-ROM is 25F8923 by the way.
4MB Token Ring Adapter 25F7540
With the infamous Tropic chipset
ZM5 Mitsubishi M5M5179P-55
ZM7 Mitsubishi M5M5179P-55
ZM9 25F9158, Even
ZM10 25F9157, Odd
ZM11 BIOS (RPL)
Identifying the Tropic Chipset
Hi Louis !
>Is the 51F1439ESD and 25F7355 the Tropic chipset?
If the card-ID = E001 (or E000 for the 4Mb/s) then - Yes. This chipset is also used by all E000 / E001 compatible cards from Madge, Compex, Hypertech, Kingston etc. pp. ... some cards use different card-ID however.
IBM came "out of the TROPICs" for MCA with the LanStreamers (MC16 - 8FA4/ MC32 - 8FA0 & 8FA2). The TR Server Busmaster adapter (8FC8) bases mainly on the Tropic architecture as far as I know.
OEM TROPIC chipset list
Listed below is the TROPIC chip set that IBM licensed from National Semiconductor.
DP8025 Token Ring Interface Controller
DP802511 TROPIC RAM Relocation Register Decoder
DP802512 Upper Memory Decoder
DP802513 Memory MEMCS-16 Signal Decoder
DP802514 TROPIC REEF
DP802515 TROPIC PELE
The DP802514 and DP802515 are Microcode ROMs for the TROPIC Token-Ring Network Controllers and they feature an interface that is compatible to DP8025 Interface Controller to allow direct interfacing without the use of GLUE logic.
Registers on Screen?
This is new- I got a few lines in the upper left eigth of the screen. They were registers- AX, BX... They didn't change... There was a top line with an ET that actually counted the seconds... Up to 26 by the time I gave up on rebooting...
or Alternate Adapter
Adapter Data Rate
RAM Size and Address Range
Adapter fails to insert on ring
A Token-Ring adapter may fail to insert on the ring due to adapter congestion. Adapters entering the ring send a request to the Ring Parameter Server (RPS) address to learn ring parameters, such as ring number. If the RPS exists on this ring, which is usually the case only if the ring is bridged to another segment, this RPS request frame returns to the originating station with the Address Recognized Indicator (ARI) set; ARI set informs the inserting station that the RPS exists on this ring and that the station should wait for the RPS response before completing its insertion on the ring. The RPS returns its response to the inserting station as a normal Token-Ring frame. If the inserting station's adapter has begun to experience significant congestion by this time, it may not be able to process the frame. The adapter driver then will stop the adapter's insertion because the adapter was unable to process the RPS response.
This problem is more likely to occur on multistation access units (MAUs) with electronic relays that do not disturb the ring during an adapter insertion; the adapter may have to wait seven seconds to participate in the neighbor notification process. In units without electronic relays, the relay disturbance causes the active monitor to start a new neighbor notification process and the adapter does not have to wait as long to insert. The longer insertion time increases the probability that the adapter will become congested.
The 802.5 Standards Committee recommends that the RPS send two frames to the adapter: one normal frame and one frame with the express, buffer-bits set. The inserting adapter will then copy the express frame into its express buffer. This information is documented in the errata sheets from the 802.5 Standards meeting V.
Promiscuous Copy and Promiscuous Mode
NOT supported on the 16/4 Token-Ring Network Adapter/A with RPL, 16/4 Token-Ring Network Adapter/A or the Token-Ring Network Adapter/A
You need the two .BIN files for burning two Eproms. These replace
the two Eproms on the 16/4 card. The "analyzer" machine needs to run a
generic DOS with the modified adapter installed.
I tried them with the "long" 16/4 and the two short ones (with and w.o. RPL). Currently they are running with a 93F0179 - which is the short 16/4 with RPL.
Feelin' like TAP Dancing?
NOTE: The 5-digit error code begin with 166 if you are testing the PRIMARY adapter or 167 if you are testing an ALTERNATE adapter.
16x80 Invalid testing mode