Type 2 Complex
Reference and Diagnostic Disks
I use a Kingston Turbochip?
ODP vs. ODPR
>1GB Disks as IML Drive
Identify H and L Complexes
In Defense of the
"H" / Upgrade 486SX 25 MHz 92F0079
"L" / Upgrade 486DX2 50/25 92F0161
171 Post Errors on 8595
and 9595 systems
486SX-25 Diskette Data Loss ECA
"L" / Upgrade
486DX2 50/25 92F0161 "H" 92F0079 is similar...
U6 DMA Controller
U8 486 Socket
|U9 487 Socket
Y1 50 MHz
Osc (half can or SMD)
Some Type-2 (92F0079)
suffer from an "incompetent DMA-chip", which is P/N 92F1428 at position
U6/GA-M on the card. Working Type-2s 92F0079 have a DMA-chip P/N 10G7808
at U6/GA-M. If U6/GA-M is 10G7808 a Turbochip should work fine.
The earlier Type-2 use the 92F1428 - which ends
the experiment in odd results (permanent I9990044, 605 FDD errors, permanent
165 errors and inability to read from FDD).
Complex BIOS Needed
for >1GB IML
Type 2 complexes require a BIOS 41G9361 to
handle drives >1GB. You will also need the 92F2244 / 92F2245 SCSI BIOS
on the SCSI adapter to properly address >1GB drives.
The module is available for some Type 1 and Type 2 processor
boards *only*. All other processor boards have previously implemented
The upgrade provides the following additional capabilities:
1. Adapter ROM memory more efficiently utilized to minimize
adapter configuration conflicts.
2. BIOS support for fixed disks up to 3.94 gigabytes per device.
3. Supports "Search IML" from any PUN (Physical Unit Number)
or SCSI ID. The system partition is no longer restricted to
only SCSI ID=6. Each fixed disk ID will be searched for a valid system
4. Allows redundant system partitions (IML).
5. Sharing of SCSI devices. An external SCSI device, such
as the 3511, may be shared between two system units.
The following models are affected:
2. Type 2 processor systems, Model 0HX. ( "X" may
be any character.)
PROCESSOR FRU P/N MODEL
EPROM P/N LOC.
25MHZ SX 92F0079
It was called the "8590/95 Dual Booting Capability EPROM Package"
"8590/95 Dual Booting Capability EPROM Package"
PART NUMBER 61G2835
NOTE: Use the latest refdisk
and diags. See above...
Swapping a 66.667Mhz osc
in for the 50MHz one will result in a 00010200 code in the upper left hand
of the screen and a system hang.
The Y1 Oscillator drives both the data bus and the DMA
controller. 0001 02XX ROM checksum or timer error.
ID H and L Complexes
Both H and L have no L2 cache
socket OR solder pads for one.
H models (92F0079) came with a 486SX-25 in U8 and have
a second socket (U9) for a 487 copro or a 486DX2-50 ODP upgrade chip. They
will accept a Turbochip if the DMA controller is the good one.
L models (92F0161)came with a 486DX2-50 in U8 and
have only solder pads at the U9 location. They will take a ODPR or
(with the good DMA controller) a Turbochip.
Reference and Diagnostics
Disk for Type 2
for Type 2
Min/Max on system board: 8/64MB
RAM: DRAM (PS/2 72-pin SIMM) 70ns parity checked (8 sockets)
The PS/2 486DX2-50 Processor Upgrade
Option supports a maximum of 64MB of parity memory, 16MB of which are addressable
by DMA. The PS/2 486DX2-50 Processor Upgrade Option does not support
85ns memory SIMMs.
Cache: 8kb L1, 0kb L2 (no socket for cache)
* No Level 2 cache socket on complex.
* H models socketed for a 487 copro or a 486DX2-50 MHz upgrade chip.
* High speed 25 MHz DMA - now synchronous with 486; 24 bit DMA.
* Faster bus arbitration (than Base 1) for better busmaster performance.
* Memory controller supports both interleaved
(higher performance –pairs of SIMMs) and non-interleaved memory (allows
* 20 MB per second data transfer support (for MCA bus).
ODP vs. ODPR
The 169 pin is the ODP-version - substitutes a 487SX with the
486SX still in place. Important on boards with soldered CPU or a
The 168 pin is the ODPR-version, where the -R- stands
for "Replace" ... it replaces the 486SX / 486DX respectively and does not
need the "SX-disable" pin therefore.
I Speak for the Humble
Actually Tony Ingenoso said
Austin DID do some LAN server performance modeling along
these lines and determined that there WAS a gain to be had from a dual
386 machine as a 386 file server could become CPU bound. Once a 486DX-33
was fitted, even the heaviest traffic hitting the server wasn't enough
to saturate the DX33 in a pure file server role.
My own casual observations of the lowly (and IMO
brilliant) DX2-50 T2 complex validated Austin's results. With
all NT4 Server's performance monitoring turned on I was never unable to
saturate the stock CPU on a 9595-0LF in a pure file server role.
It might run up to 80%, maybe even peak to 90%, but it never became saturated
at 100%. This was with several other PC hammering it over a 16mb
T/R LAN. Operating within its design purpose, doing what it was sold
to do -- a stock T2 was is a word "sufficient" to the task in all respects,
and remains so even today when run in a pure file server role.
The problem is that TODAY, we are asking these machines
to take on more than they were intended to do initially. Modern
"desktop" usage has a dramatically different use profile than pure file
servers have, and it shows. GUI's are a big drag on performance,
and the 95's placement of the video on the bus hurts quite a bit as well.
171 Post Errors on
8595 and 9595 systems
Symptom: 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 a LANStreamer MC32, MC16 or EtherStreamer MC32
in slot 8.
Fix: Do not install any of the above referenced
adapters in slot 8. Relocate the adapter to one of the other Micro Channel
slots. No further engineering action is planned.
ECA100 - 8590/95,
486-SX-25MHZ DISKETTE DATA LOSS
This problem may allow bad data to be read from or written
to a device WITHOUT any error indications or other evidence of system failure.
This affects any device attached to the floppy controller that is "seen"
as a floppy drive, such as some tape backup devices.
All systems using the 486SX/25MHZ complex FRU P/N92F0079.
The following adapters are no longer supported due to this problem:
5.25 INCH DISKETTE ADAPTER/A (6451007), 4869-001 360KB
External Floppy and 4869-002 1.2MB External Floppy
These adapters use a seperate device driver (not BIOS),
and DMA verify. Updating the system partition will NOT cure the problem.