@E001.ADF - IBM
Token-Ring Network 16/4 Adapter/A (Tropic based version 2.01!) TRM164.EXE
Drivers/Diagnostic/Option disk v2.0 (includes ADF ver 2.01 and DGS)
188-202 IBM Token-Ring Network 16/4 Adapter/A (Short and Long 16/4) 190-004 IBM Token-Ring Network PS/2 Model P70 386 Adapter/A (4Mbs) (#1598) (#39F9598) 190-090 IBM Token-Ring Network 16/4 Trace and Performance Adapter/A 290-284 IBM Token Ring Network 16/4 Trace and Performance Program bk8r1001.boo LAN Tech Ref Token-Ring Network Shared-RAM Adapters SC30-3588-01 bk8r1000.boo Token-Ring Network Adapter Interface Ver 1, Release 1.0 SC30-3588-00 bk8p7001.boo LAN Tech Ref: 802.2 and NetBIOS APIs (T/R, Broadband, Baseband, Ethernet) SC30-3587-01 96X5767 IBM Token-Ring Network Trace and Performance Program User's Guide 1st Ed (Dec 1987) Understanding Token Ring, by Bret Glass Interactive Token-Ring Network Troubleshooting (my copy) Trace and Performance Program (pages 450-464 of GG24-3291-0) TAP20.ZIP Trace and Performance Program and EPROM images TROPIC chip set 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 Microcode, Even (REEF) DP802515 TROPIC Microcode, Odd (PELE) The DP802514 and DP802515 are the Microcode ROMs for the TROPIC Token-Ring Network Controller. AN-857 An Introduction to Token RingAN-850 TROPIC - A Front End Description AN-816 Layout Guideline for a Token Ring Adapter Using the DP8025 (TROPIC) AN-848 ISA and MicroChannel Host Software and Programmer's Guide for the DP8025 TROPIC Short
16/4 Token Ring Adapter (74F9415 or 74F9321)
53F7748 16F1144 EPROM Change
For Token Ring Adapter H12391 Short
4MB Token Ring Adapter 25F7540
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. o 16/4 megabits-per-second adapter data rate -- program selectable 02G1394ESD
vs. 50G6144ESD W95 will continue to load and the TR works on an 8228. Must be the chipset is close enough to complain about, but also close enough to work. Tokin'
Madness Postulate- The 02G1394ESD
chip is OK, but the 50G6144ESD
had a problem, they issued a new bios for it. They even
tried the bios off the 02G1394ESD.
I don't have a large enough population to derive a high
correlation, but... My wild SWAG is as good as
yours... 16/4 Long Token Ring Adapter 53F7748 / 93F0331
16/4
Long Token Ring Adapter 16F1144
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.
EPROM
Change For Token Ring Adapter H12391 Only PS/2's used as servers operating with non-IBM network software are affected. Workstations which are not used as servers do not require new EPROMs. Replacement EPROMs are FRU P/N 92F9122. o 16/4 megabits-per-second adapter data rate -- program selectable 4MB Token Ring Adapter 25F7540
16KB of RAM 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 Peter sez: David Beem sez: "Texas Instruments (TI) announced
an agreement with IBM to develop a token ring chipset
called the TMS380 based on the IBM token-ring
specification. This chipset had technological and
performance advantages over the IBM chipset that allowed
increased data buffers for data transfer and also
allowed direct memory access (DMA) transfers, in which
an onboard controller managed access to memory. Later,
TI enhanced the TMS380 chipset to accommodate 16Mbps
token-ring networks, resulting in the TMS380C16.
Recently [to when the book was written], TI announced an
advanced token-ring chipset using the TMS380C26 chipset,
which integrates more functionality than the previous
two. While the TI chipset is 100-percent
compatible with the IEEE 802.5 and 802.2 token-ring
specifications, it is not 100-percent compatible with
IBM's LLC protocol implementation. As a result, IBM
developed the Token-Ring Protocol Interface Controller
(TROPIC) chipset for third-party vendor use, ensuring
register-level compatibility for all IBM applications.
Marketed by National Semiconductors under license from
IBM, TROPIC manufacturers include vendors such as Madge
Networks, Proteon, Thomas-Conrad Corp., Cabletron
Systems, and 3Com.....". Registers on Screen? This is new- I got a few lines in the upper left eighth 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... Peter-
Memory It has 64 KB of random access memory (RAM), of which 63.5 KB are available for use by an application program and 512 bytes are reserved. 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 Trace and
Performance Adapter From Peter 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. Then extract the TAP20.BIN ... at
the C:/ Dos-prompt type TAP ... then "Measure Ring
Performance" - enter any file name for storing the
performance data, [ENTER], then select "Start measuring"
from the menu ... and if you did it all right you get a
nice bar graph with the TR network load. Mine never
reaches values over 65% - even when I have all
workstations running and do large copy and backup
jobs. There are other functions as well.
You could build a "traffic matrix": simply spoken "who
talks with whom ?" - the program shows the burn-in
addresses (these 12-digit codes burned in the adapter) -
here it pays to overwrite these internal addresses with
own ones ... my server for example has 4000 0001 CAFE
(hex numbers only). Hmmm....I am not quite sure at the moment if you need any of the DOS LAN support drivers (DXMA0MOD.SYS / DXMC0MOD.SYS / DXMT0MOD.SYS) in your CONFIG.SYS. My P70 has at least the DXMA0MOD.SYS ... but the TAP opens and closes the adapter during operation. 3 files. 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. ADF Settings AdapterID E001h " IBM Token-Ring 16/4 MC Adapter, ver2.01" Primary or Alternate Adapter
Adapter Data Rate ROM Address Range RAM Size and Address Range
Interrupt Level Adapter Media Type Selection
Enable or Disable RPL
|