https://web.archive.org/web/19961219045007/http://www.pc.ibm.com/techlink/f960105a.html

=========================================================================
Date: 96/01/05
Subject: EOS memory reliability and technology advantages

1) EOS does ECC on a byte boundary, so at any given address, EOS is
capable of fixing EIGHT!!! single-bit errors at a time (remember that
for an 8-byte interface, EOS must be used in pairs, hence 8 errors). A
Compaq Prosignia 300/Proliant 1500 does standard ECC on an 8-byte
boundary and can correct only 1 bit per address. A Compaq Proliant
2000/4000 uses "advanced" ECC which is done across 16 bytes. Using this
wide ECC word, they can correct any given bad 4-bit DRAM, or 4 bits/16
bytes (2 bits/8 bytes). In marketing lingo, this translates to EOS being
4X more powerful an ECC scheme!!! How-ever, that is really stretching
things ;-) Note that "advanced" ECC requires SIMMs to be plugged in
sets of 4 instead of set of 2.

2) Performance can be better with EOS. Native ECC has to pay a several
cycle performance hit any time a word less than the bus width (8
bytes/16 bytes) gets written. Much attention can be paid to minimize
this effect with posted-write buffers, but the final impact can range
from near 0% to 20%, depending on the code being run (lots of byte
writes) and the cleverness of the implementation (byte-write gathering
scheme). I have never attempted to see if native ECC running X-2-2-2
with 60ns EDO is better than EOS at 70ns with no byte writes...perhaps
we should call that case a draw.

3) Per the above mentioned presentation, upwards of 95% of all memory
errors are caused by soft errors. A rule of thumb I use is 1 soft error
per month per 256MB of memory. Because of this, one could argue that
having an error reporting scheme is counterproductive. The customer will
see these soft errors periodically and think his memory should be
changed, while in fact the fails are unavoidable (unless you're 50 feet
underground) and should be ignored. Having good error reporting was
actually a major thorn in the side of our S/390 brethren because the
customer could tell whenever a soft error was occurring, but their
competitors did not have good reporting in their boxes, so they seemed
to be better off! I don't know how you argue this one with the
customer...good luck!

4) EOS is a much more flexible solution. If today's mission critical
department server becomes tomorrow's uncritical print server, the EOS
memory can be swapped out for regular parity SIMMs and the ECC function
can be moved to another machine that may not have native ECC. This
flexibility of moving the ECC via EOS to the machines that need it could
be a powerful argument for a smart IS group supporting a large
enterprise with many PCs.

5) EOS is, in a sense, much more highly redundant than native ECC. If
the ECC algorithm in a native ECC memory controller goes bad, then all
of the memory goes bad. If the circuitry in one of the distributed ECC
chips on the EOS SIMMs goes bad, only one byte of one SIMM goes bad, and
the OS has a chance of deallocating that memory and marching forward.

perjantai 31. maaliskuuta 2023 klo 3.11.12 UTC+3 Louis Ohland kirjoitti:
> https://web.archive.org/web/19961219045007/http://www.pc.ibm.com/techlink/f960105a.html
>
> =========================================================================
> Date: 96/01/05
> Subject: EOS memory reliability and technology advantages
>
> 1) EOS does ECC on a byte boundary, so at any given address, EOS is
> capable of fixing EIGHT!!! single-bit errors at a time (remember that
> for an 8-byte interface, EOS must be used in pairs, hence 8 errors). A
> Compaq Prosignia 300/Proliant 1500 does standard ECC on an 8-byte
> boundary and can correct only 1 bit per address. A Compaq Proliant
> 2000/4000 uses "advanced" ECC which is done across 16 bytes. Using this
> wide ECC word, they can correct any given bad 4-bit DRAM, or 4 bits/16
> bytes (2 bits/8 bytes). In marketing lingo, this translates to EOS being
> 4X more powerful an ECC scheme!!! How-ever, that is really stretching
> things ;-) Note that "advanced" ECC requires SIMMs to be plugged in
> sets of 4 instead of set of 2.
>
> 2) Performance can be better with EOS. Native ECC has to pay a several
> cycle performance hit any time a word less than the bus width (8
> bytes/16 bytes) gets written. Much attention can be paid to minimize
> this effect with posted-write buffers, but the final impact can range
> from near 0% to 20%, depending on the code being run (lots of byte
> writes) and the cleverness of the implementation (byte-write gathering
> scheme). I have never attempted to see if native ECC running X-2-2-2
> with 60ns EDO is better than EOS at 70ns with no byte writes...perhaps
> we should call that case a draw.
>
> 3) Per the above mentioned presentation, upwards of 95% of all memory
> errors are caused by soft errors. A rule of thumb I use is 1 soft error
> per month per 256MB of memory. Because of this, one could argue that
> having an error reporting scheme is counterproductive. The customer will
> see these soft errors periodically and think his memory should be
> changed, while in fact the fails are unavoidable (unless you're 50 feet
> underground) and should be ignored. Having good error reporting was
> actually a major thorn in the side of our S/390 brethren because the
> customer could tell whenever a soft error was occurring, but their
> competitors did not have good reporting in their boxes, so they seemed
> to be better off! I don't know how you argue this one with the
> customer...good luck!
>
> 4) EOS is a much more flexible solution. If today's mission critical
> department server becomes tomorrow's uncritical print server, the EOS
> memory can be swapped out for regular parity SIMMs and the ECC function
> can be moved to another machine that may not have native ECC. This
> flexibility of moving the ECC via EOS to the machines that need it could
> be a powerful argument for a smart IS group supporting a large
> enterprise with many PCs.
>
> 5) EOS is, in a sense, much more highly redundant than native ECC. If
> the ECC algorithm in a native ECC memory controller goes bad, then all
> of the memory goes bad. If the circuitry in one of the distributed ECC
> chips on the EOS SIMMs goes bad, only one byte of one SIMM goes bad, and
> the OS has a chance of deallocating that memory and marching forward.
I have two 16 Mb 70ns 5v EOS Simms. Has these any use for PS/2 PCs?
My 9557 accepts only total 16 MB of memory and one simm sice is max 8 MB but how about 8595 or others?

Nice that someone is awake.

Buzzkill, the EOS reports itself as parity, so the system in question
has to support 16MB parity SIMMs.

9585 -X or -K/N

4MB and 8MB EOS are supported by all PS/2s, as their size is supported.

The IBM ECC-on-SIMM (EOS) part numbers are
11H0618 (8MB)
11H0621 (16MB)
11H0624 (32MB)

Lead composition:

11D - Tin
11E - Gold

ECC controller on EOS is 73G6876.
These are a sea of gates, not a specific ASIC

Toshiba TC160G11AT
AMI 6553-013

https://www.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/5/897/ENUS195-075/index.html&request_locale=en

Options by IBM: IBM ECC-on-SIMM Memory Upgrades
Announcement Number: 195-075

Normal Height: 26.4mm
Tall Height: 41.7mm
Wide Width: 14.2mm
Normal Width: 10.1mm

+-------------------------------------------------------------------+
| o SEC high-speed ECC algorithm |
| o 70ns (x36 bits) 72-pin JEDEC standard SIMM |
| o IBM or industry standard presence detects, gold tabs |
| o Fit in standard x36 SIMM socket |
| o No processor changes required |
| |
| o 4MB (Wide) 70ns ECC-on-SIMM Memory Upgrade: |
| - Selected PS/2(R) and IBM PC Server 300 and 320 systems |
| |
| o 8MB (Wide) 70ns ECC-on-SIMM Memory Upgrade: |
| - Selected PS/2 systems |
| |
| o 8MB (Tall), 16MB, and 32MB 70ns ECC-on-SIMM Memory Upgrades: |
| - IBM PC Server 300 and 320 systems |
+-------------------------------------------------------------------+

The following memory options complement the Options by IBM family of
offerings:

4MB 70ns ECC-on-SIMM Memory Upgrade
8MB (Wide) 70ns ECC-on-SIMM Memory Upgrade
8MB (Tall) 70ns ECC-on-SIMM Memory Upgrade
16MB 70ns ECC-on-SIMM Memory Upgrade
32MB 70ns ECC-on-SIMM Memory Upgrade

The IBM ECC-on-SIMM Memory Upgrades offer 4MB, 8MB, 16MB and 32MB of
error-correcting-code (ECC) memory on a SIMM. This upgrade family -- a
plug-compatible, fully retrofittable series of 70ns memory modules --

allows you to upgrade a parity system to a fully functional
single-error-correct (SEC) ECC system. The ECC function is completely
self-contained on the SIMM and provides correction of single-bit errors that

occur in each byte of SIMM data. No processor changes are required to
receive the enhanced reliability this SIMM family offers.

The ECC-on-SIMM Memory Upgrades are organized as x36 bits, support
parity, and are packaged on a 72-pin JEDEC (Joint Electronic Device
Engineering Council) standard SIMM with gold tabs. The 4MB SIMM has IBM

presence detects, while the 8MB (Tall and Wide), 16MB and 32MB SIMMs
have industry standard presence detects.

Use of the ECC-on-SIMM Memory Upgrades is recommended when processing
critical applications on systems without native ECC. Enhanced data
integrity and memory reliability are provided with no system performance

penalty. The upgrades are extremely important in server environments
where single-bit memory errors can impact all users on the network.

Part Availability Unit
Description Number Date Price

4MB 70ns ECC-on-SIMM 75G6500
8MB (Wide) 70ns ECC-on-SIMM 75G6501
8MB (Tall) 70ns ECC-on-SIMM 11H0618
16MB 70ns ECC-on-SIMM 11H0621
32MB 70ns ECC-on-SIMM 11H0624

IBM 4MB 70NS ECC-ON-SIMM MEMORY UPGRADE (#1500, 75G6500)

The 4MB 70ns ECC-on-SIMM Memory Upgrade module is organized as 1M x 36,
supports parity, and is packaged on a 72-pin JEDEC standard SIMM with
gold tabs and IBM presence detects.

Technical Information

Physical Specifications

Dimensions:
Height: 26.4 mm (1.04 in.)
Width: 108 mm (4.25 in.)
Depth: 10.1 mm (0.4 in.)
Weight: .025kg (0.055 lb)

Operating Environment

Temperature: 0(degs)C to 65(degs)C (32(degs)F to 149(degs)F)
Relative humidity: 8% to 80%
Wet bulb: 23(degs)C (73(degs)F)
Electrical power: 1620 mA max

Hardware Requirements: The 4BM 70ns ECC-on-SIMM Memory Upgrade (#1500,
75G6500) is supported on the following IBM platforms:

Machine
Description Type Model

PS/2 8525 K00, K01, L02
8535 040, 043, 050, 055,
14X, 24X
8540 040, 043, 045
8556 043, 045, 055, 059,
14X, 15X, 24X, 25X
8557 045, 049, 055, 059,
05F, 259
8590(1) 0J5, 0J9, 0JD, 0JF,
0K9, 0KD, 0KF, 0GF,
0G5, 0G9, 0HF, 0H5, 0H9,
0L9, 0LF
8595(1) 0J9, 0JD, 0JF, 0KD,
0KF, 0G5, 0G9, 0GF,
0H5, 0H9, 0HF, 0L9,
0LF, 0X6, 0XA, 0XF,
0XG
9553 0B7, 0BB, 1BX, 2BX
9556 DBA, DB6, DEB, DED,
DE9, KBA, KB6, QBA,
QB6, 0BA, 0B6, 1EX, 2EX
9557 DBA, DBG, DB6, DEB,
DED, DEG, DE9, KBA,
KBG, KB6, QBA, QB6,
0BA, 0B6, 1BA, 2BA,
6EB, 6EG, 7EB, 7EG
9576 DUA,DU6, KUA, KU6,
QUA, QU6, 0UA, 0U6
9577 DNA, DNG, DUA, DUG,
KNA, KNG, KUA, KUG
QBA, QB6, QNA, QUA,
0NA, 0NF, 0UA, 0UF,
1NA, 1UA,
9585(1) 0X6, 0XA, 0XF, 0XG,
0KG, 0KT, 0NG, 0NT
9590(1) DLA, 0LA, QLA, KLA,
0LF, DLG, KLG
9595(1) 0LF, 0LG

PC Server 8640(1) 0N0, 0NJ, 0P0, 0PT,
0Y0, 0YT, 1Y0, 1YT

(1) These systems must be upgraded with sets of two 75G6500
upgrades.

Limitations

Parity memory cannot coexist with the 4MB 70ns ECC-on-SIMM Memory
Upgrade in the same system.
8590, 8595, 9590, and 9595 models with native ECC (xMx,1Nx, xPx,
xQx, xTx, xVx) are not supported.

IBM 8MB (WIDE) 70NS ECC-ON-SIMM MEMORY UPGRADE (#6501, 675G6501)

The 8MB (Wide) 70ns ECC-on-SIMM Memory Upgrade module is organized as 2M
x 36, supports parity, and is packaged on a 72-pin JEDEC standard SIMM
with gold tabs and industry standard presence detects.

Technical Information

Physical Specifications

Dimensions:
Height: 26.4 mm (1.04 in.)
Width: 108 mm (4.25 in.)
Depth: 14.2 mm (0.56 in.)
Weight: .041 kg (0.09 lb)

Operating Environment

Temperature: 0(degs)C to 65(degs)C (32(degs)F to 149(degs)F)
Relative humidity: 8% to 80%
Wet bulb: 23(degs)C (73(degs)F)
Electrical power: 1656 mA max

Hardware Requirements: The 8MB (Wide) 70ns ECC-on-SIMM Memory Upgrade
(#6501, 675G6501) is supported on the following IBM platforms:

Machine
Description Type Model

PS/2 8556 043, 045, 055, 059,
14X, 15X, 24X, 25X
8557 045, 049, 055, 059,
05F, 259
8590(1) 0J5, 0J9, 0JD, 0JF,
0K9, 0KD, 0KF, 0G5,
0G9, 0GF, 0H5, 0H9,
0HF, 0L9, 0LF
8595(1) 0J9, 0JD, 0JF, 0KD,
0KF, 0G5, 0G9, 0GF,
0H5, 0H9, 0HF, 0L9,
0LF, 0X6, 0XA, 0XF,
0XG
9556 DBA, DB6, DEB, DED,
DE9, KBA, KB6, QBA,
QB6, 0BA, 0B6, 1EX,
2EX
9557 DBA, DBG, DB6, DEB,
DED, DEG, DE9, KBA,
KBG, KB6, QBA, QB6,
0BA, 0B6, 1BA, 2BA,
6EB, 6EG, 7EB, 7EG
9576 DUA, DU6, KUA, KU6,
QUA, QU6, 0UA, 0U6
9577 DNA, DNG, DUA, DUG,
KNA, KNG, KUA, KUG,
QBA, QB6, QNA, QUA,
0NA, 0NF,0UA, 0UF,
1NA, 1UA
9585(1) 0X6, 0XA, 0XF, 0XG,
0KG, 0KT, 0NG, 0NT
9590(1) DLA, 0LA, QLA, KLA,
0LF, DLG, KLG
9595(1) 0LF, 0LG

Lacuna also supports 16MB parity.

Louis Ohland wrote:
> Nice that someone is awake.
>
> Buzzkill, the EOS reports itself as parity, so the system in question
> has to support 16MB parity SIMMs.
>
> 9585 -X or -K/N
>
> 4MB and 8MB EOS are supported by all PS/2s, as their size is supported.
>
> The IBM ECC-on-SIMM (EOS) part numbers are
> 11H0618 (8MB)
> 11H0621 (16MB)
> 11H0624 (32MB)
>
> Lead composition:
>
> 11D - Tin
> 11E - Gold
>
> ECC controller on EOS is 73G6876.
>   These are a sea of gates, not a specific ASIC
>
> Toshiba TC160G11AT
> AMI 6553-013
>
> https://www.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/5/897/ENUS195-075/index.html&request_locale=en
>
>
>
> Options by IBM: IBM ECC-on-SIMM Memory Upgrades
> Announcement Number: 195-075
>
> Normal Height: 26.4mm
> Tall Height: 41.7mm
> Wide Width: 14.2mm
> Normal Width: 10.1mm
>
> +-------------------------------------------------------------------+
> | o  SEC high-speed ECC algorithm                                   |
> | o  70ns (x36 bits) 72-pin JEDEC standard SIMM                     |
> | o  IBM or industry standard presence detects, gold tabs           |
> | o  Fit in standard x36 SIMM socket                                |
> | o  No processor changes required                                  |
> |                                                                   |
> | o  4MB (Wide) 70ns ECC-on-SIMM Memory Upgrade:                    |
> |    -  Selected PS/2(R) and IBM PC Server 300 and 320 systems      |
> |                                                                   |
> | o  8MB (Wide) 70ns ECC-on-SIMM Memory Upgrade:                    |
> |    -  Selected PS/2 systems                                       |
> |                                                                   |
> | o  8MB (Tall), 16MB, and 32MB 70ns ECC-on-SIMM Memory Upgrades:   |
> |    -  IBM PC Server 300 and 320 systems                           |
> +-------------------------------------------------------------------+
>
> The following memory options complement the Options by IBM family of
> offerings:
>
>     4MB 70ns ECC-on-SIMM Memory Upgrade
>     8MB (Wide) 70ns ECC-on-SIMM Memory Upgrade
>     8MB (Tall) 70ns ECC-on-SIMM Memory Upgrade
>     16MB 70ns ECC-on-SIMM Memory Upgrade
>     32MB 70ns ECC-on-SIMM Memory Upgrade
>
> The IBM ECC-on-SIMM Memory Upgrades offer 4MB, 8MB, 16MB and 32MB of
> error-correcting-code (ECC) memory on a SIMM. This upgrade family -- a
> plug-compatible, fully retrofittable series of 70ns memory modules --
>
> allows you to upgrade a parity system to a fully functional
> single-error-correct (SEC) ECC system. The ECC function is completely
> self-contained on the SIMM and provides correction of single-bit errors
> that
>
> occur in each byte of SIMM data. No processor changes are required to
> receive the enhanced reliability this SIMM family offers.
>
> The ECC-on-SIMM Memory Upgrades are organized as x36 bits, support
> parity, and are packaged on a 72-pin JEDEC (Joint Electronic Device
> Engineering Council) standard SIMM with gold tabs. The 4MB SIMM has IBM
>
> presence detects, while the 8MB (Tall and Wide), 16MB and 32MB SIMMs
> have industry standard presence detects.
>
> Use of the ECC-on-SIMM Memory Upgrades is recommended when processing
> critical applications on systems without native ECC. Enhanced data
> integrity and memory reliability are provided with no system performance
>
> penalty. The upgrades are extremely important in server environments
> where single-bit memory errors can impact all users on the network.
>
>                               Part         Availability      Unit
> Description                   Number       Date              Price
>
>
> 4MB 70ns ECC-on-SIMM        75G6500
> 8MB (Wide) 70ns ECC-on-SIMM    75G6501
> 8MB (Tall) 70ns ECC-on-SIMM    11H0618
> 16MB 70ns ECC-on-SIMM        11H0621
> 32MB 70ns ECC-on-SIMM        11H0624
>
>
>
> IBM 4MB 70NS ECC-ON-SIMM MEMORY UPGRADE (#1500, 75G6500)
>
>
> The 4MB 70ns ECC-on-SIMM Memory Upgrade module is organized as 1M x 36,
> supports parity, and is packaged on a 72-pin JEDEC standard SIMM with
> gold tabs and IBM presence detects.
>
> Technical Information
>
> Physical Specifications
>
>     Dimensions:
>         Height: 26.4 mm (1.04 in.)
>         Width: 108 mm (4.25 in.)
>         Depth: 10.1 mm (0.4 in.)
>         Weight: .025kg (0.055 lb)
>
> Operating Environment
>
>     Temperature: 0(degs)C to 65(degs)C (32(degs)F to 149(degs)F)
>     Relative humidity: 8% to 80%
>     Wet bulb: 23(degs)C (73(degs)F)
>     Electrical power: 1620 mA max
>
> Hardware Requirements: The 4BM 70ns ECC-on-SIMM Memory Upgrade (#1500,
> 75G6500) is supported on the following IBM platforms:
>
>                     Machine
> Description         Type           Model
>
>
> PS/2                8525           K00, K01, L02
>                     8535           040, 043, 050, 055,
>                                    14X, 24X
>                     8540           040, 043, 045
>                     8556           043, 045, 055, 059,
>                                    14X, 15X, 24X, 25X
>                     8557           045, 049, 055, 059,
>                                    05F, 259
>                     8590(1)        0J5, 0J9, 0JD, 0JF,
>                                    0K9, 0KD, 0KF, 0GF,
>                                    0G5, 0G9, 0HF, 0H5, 0H9,
>                                    0L9, 0LF
>                     8595(1)        0J9, 0JD, 0JF, 0KD,
>                                    0KF, 0G5, 0G9, 0GF,
>                                    0H5, 0H9, 0HF, 0L9,
>                                    0LF, 0X6, 0XA, 0XF,
>                                    0XG
>                     9553           0B7, 0BB, 1BX, 2BX
>                     9556           DBA, DB6, DEB, DED,
>                                    DE9, KBA, KB6, QBA,
>                                    QB6, 0BA, 0B6, 1EX, 2EX
>                     9557           DBA, DBG, DB6, DEB,
>                                    DED, DEG, DE9, KBA,
>                                    KBG, KB6, QBA, QB6,
>                                    0BA, 0B6, 1BA, 2BA,
>                                    6EB, 6EG, 7EB, 7EG
>                     9576           DUA,DU6, KUA, KU6,
>                                    QUA, QU6, 0UA, 0U6
>                     9577           DNA, DNG, DUA, DUG,
>                                    KNA, KNG, KUA, KUG
>                                    QBA, QB6, QNA, QUA,
>                                    0NA, 0NF, 0UA, 0UF,
>                                    1NA, 1UA,
>                     9585(1)        0X6, 0XA, 0XF, 0XG,
>                                    0KG, 0KT, 0NG, 0NT
>                     9590(1)        DLA, 0LA, QLA, KLA,
>                                    0LF, DLG, KLG
>                     9595(1)        0LF, 0LG
>
>
> PC Server           8640(1)        0N0, 0NJ, 0P0, 0PT,
>                                    0Y0, 0YT, 1Y0, 1YT
>
> (1)   These systems must be upgraded with sets of two 75G6500
>       upgrades.
>
> Limitations
>
>     Parity memory cannot coexist with the 4MB 70ns ECC-on-SIMM Memory
> Upgrade in the same system.
>     8590, 8595, 9590, and 9595 models with native ECC (xMx,1Nx, xPx,
> xQx, xTx, xVx) are not supported.
>
>
> IBM 8MB (WIDE) 70NS ECC-ON-SIMM MEMORY UPGRADE (#6501, 675G6501)
>
> The 8MB (Wide) 70ns ECC-on-SIMM Memory Upgrade module is organized as 2M
> x 36, supports parity, and is packaged on a 72-pin JEDEC standard SIMM
> with gold tabs and industry standard presence detects.
>
> Technical Information
>
> Physical Specifications
>
>     Dimensions:
>         Height: 26.4 mm (1.04 in.)
>         Width: 108 mm (4.25 in.)
>         Depth: 14.2 mm (0.56 in.)
>         Weight: .041 kg (0.09 lb)
>
> Operating Environment
>
>     Temperature: 0(degs)C to 65(degs)C (32(degs)F to 149(degs)F)
>     Relative humidity: 8% to 80%
>     Wet bulb: 23(degs)C (73(degs)F)
>     Electrical power: 1656 mA max
>
>
> Hardware Requirements: The 8MB (Wide) 70ns ECC-on-SIMM Memory Upgrade
> (#6501, 675G6501) is supported on the following IBM platforms:
>
>                          Machine
> Description              Type                Model
>
>
> PS/2                     8556                043, 045, 055, 059,
>                                              14X, 15X, 24X, 25X
>                          8557                045, 049, 055, 059,
>                                              05F, 259
>                          8590(1)             0J5, 0J9, 0JD, 0JF,
>                                              0K9, 0KD, 0KF, 0G5,
>                                              0G9, 0GF, 0H5, 0H9,
>                                              0HF, 0L9, 0LF
>                          8595(1)             0J9, 0JD, 0JF, 0KD,
>                                              0KF, 0G5, 0G9, 0GF,
>                                              0H5, 0H9, 0HF, 0L9,
>                                              0LF, 0X6, 0XA, 0XF,
>                                              0XG
>                          9556                DBA, DB6, DEB, DED,
>                                              DE9, KBA, KB6, QBA,
>                                              QB6, 0BA, 0B6, 1EX,
>                                              2EX
>                          9557                DBA, DBG, DB6, DEB,
>                                              DED, DEG, DE9, KBA,
>                                              KBG, KB6, QBA, QB6,
>                                              0BA, 0B6, 1BA, 2BA,
>                                              6EB, 6EG, 7EB, 7EG
>                          9576                DUA, DU6, KUA, KU6,
>                                              QUA, QU6, 0UA, 0U6
>                          9577                DNA, DNG, DUA, DUG,
>                                              KNA, KNG, KUA, KUG,
>                                              QBA, QB6, QNA, QUA,
>                                              0NA, 0NF,0UA, 0UF,
>                                              1NA, 1UA
>                          9585(1)             0X6, 0XA, 0XF, 0XG,
>                                              0KG, 0KT, 0NG, 0NT
>                          9590(1)             DLA, 0LA, QLA, KLA,
>                                              0LF, DLG, KLG
>                          9595(1)             0LF, 0LG
>
> (1)   These systems must be upgraded with sets of two 75G6501 upgrades.
>
> Limitations
>
>     Parity SIMMs cannot coexist with the IBM 8MB (Wide) 70ns
> ECC-on-SIMM Memory Upgrade in the same system.
>     8590, 8595, 9590, and 9595 models with native ECC (xMx, 1Nx, xPx,
> xQx, xTx, xVx) are not supported.
>     Maximum system memory is not attainable on 8556, 8557, 9556, 9557,
> 9576, and 9577 models due to physical constraints:
>         Two 8MB (Wide) ECC-on-SIMM Memory Upgrades cannot be installed
> in adjacent SIMM sockets.
>         Models with three SIMM sockets have a maximum of two 8MB (Wide)
> and one 4MB ECC-on-SIMM Memory Upgrades.
>         Models with four SIMM sockets have a maximum of two 8MB (Wide)
> and two 4MB ECC-on-SIMM Memory Upgrades.
>
>
>
> IBM 8MB (TALL) 70NS ECC-ON-SIMM MEMORY UPGRADE (#1681, 11H0618)
>
> The 8MB (Tall) 70ns ECC-on-SIMM Memory Upgrade module is organized as 2M
> x 36, supports parity, and is packaged on a 72-pin JEDEC standard SIMM
> with gold tabs and industry standard presence detects.
>
> Technical Information
>
> Physical Specifications
>
>     Dimensions:
>         Height: 41.7 mm (1.64 in.)
>         Width: 108 mm (4.25 in.)
>         Depth: 10.1 mm (0.40 in.)
>         Weight: .039 kg (0.09 lb)
>
> Operating Environment
>
>     Temperature: 0(degs)C to 65(degs)C (32(degs)F to 149(degs)F)
>     Relative humidity: 8% to 80%
>     Wet bulb: 23(degs)C (73(degs)F)
>     Electrical power: 1656 mA max
>
>
> Hardware Requirements: The 8MB (Tall) 70ns ECC-on-SIMM Memory Upgrade is
> supported on the following IBM platforms:
>
>                     Machine
> Description         Type           Model
>
>
> PC Server           8640(1)        0N0, ONJ, 0P0, 0PT, 0Y0,
>                                    0YT, 1Y0, 1YT
>
> (1)   These systems must be upgraded with sets of two 11H0618
>       upgrades.
>
> Limitations: Parity SIMMs cannot coexist with the 8MB (Tall) 70ns
> ECC-on-SIMM Memory Upgrade in the same system.
>
>
> IBM 16MB 70NS ECC-ON-SIMM MEMORY UPGRADE (#1621, 11H0621)
>
>
> The 16MB 70ns ECC-on-SIMM Memory Upgrade module is organized as 4M x 36,
> supports parity, and is packaged on a 72-pin JEDEC standard SIMM with
> gold tabs and industry standard presence detects.
>
>
> Physical Specifications
>
>     Dimensions:
>         Height: 26.4 mm (1.04 in.)
>         Width: 108 mm (4.25 in.)
>         Depth: 10.1 mm (0.40 in.)
>         Weight: .025 kg (0.06 lb)
>
> Operating Environment
>
>     Temperature: 0(degs)C to 65(degs)C (32(degs)F to 149(degs)F)
>     Relative humidity: 8% to 80%
>     Wet bulb: 23(degs)C (73(degs)F)
>     Electrical power: 1440 mA max
>
> Hardware Requirements: The 16MB 70ns ECC-on-SIMM Memory Upgrade  is
> supported on the following IBM platforms:
>
>                     Machine
> Description         Type           Model
>
>
> PC Server           8640(1)        0N0, ONJ, 0P0, 0PT, 0Y0,
>                                    0YT, 1Y0, 1YT
>
> (1)   These systems must be upgraded with sets of two 11H0621 upgrades.
>
> Limitations: Parity SIMMs cannot coexist with the 16MB 70ns ECC-on-SIMM
> Memory Upgrade in the same system.
>
>
>
> IBM 32MB 70NS ECC-ON-SIMM MEMORY UPGRADE (#1624, 11H0624)
>
> The 32MB 70ns ECC-on-SIMM Memory Upgrade module is organized as 8M x 36,
> supports parity, and is packaged on a 72-pin JEDEC standard SIMM with
> gold tabs and industry standard presence detects.
>
> Technical Information
>
> Physical Specifications
>
>     Width: 108 mm (4.25 in.)
>     Depth: 10.1 mm (0.40 in.)
>     Length: 41.7 mm (1.64 in.)
>     Weight: .039 kg (0.09 lb)
>
> Operating Environment
>
>     Temperature: 0(degs)C to 65(degs)C (32(degs)F to 149(degs)F)
>     Relative humidity: 8% to 80%
>     Wet bulb: 23(degs)C (73(degs)F)
>     Electrical power: 1464 mA max
>
>
> Hardware Requirements: The 32MB 70ns ECC-on-SIMM Memory Upgrade  is
> supported on the following IBM platforms:
>
>                     Machine
> Description         Type           Model
>
>
> PC Server           8640(1)        0N0, ONJ, 0P0, 0PT, 0Y0,
>                                    0YT, 1Y0, 1YT
>
> (1)   These systems must be upgraded with sets of two 11H0624 upgrades.
>
> Limitations: Parity SIMMs cannot coexist with the 32MB 70ns ECC-on-SIMM
> Memory Upgrade in the same system.
>

perjantai 31. maaliskuuta 2023 klo 13.23.31 UTC+3 Louis Ohland kirjoitti:
> Nice that someone is awake.
>
> Buzzkill, the EOS reports itself as parity, so the system in question
> has to support 16MB parity SIMMs.
>
> 9585 -X or -K/N
>
> 4MB and 8MB EOS are supported by all PS/2s, as their size is supported.
>
> The IBM ECC-on-SIMM (EOS) part numbers are
> 11H0618 (8MB)
> 11H0621 (16MB)
> 11H0624 (32MB)
>
> Lead composition:
>
> 11D - Tin
> 11E - Gold
>
> ECC controller on EOS is 73G6876.
> These are a sea of gates, not a specific ASIC
>
> Toshiba TC160G11AT
> AMI 6553-013
>
> https://www.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/5/897/ENUS195-075/index.html&request_locale=en
>
>
> Options by IBM: IBM ECC-on-SIMM Memory Upgrades
> Announcement Number: 195-075
>
> Normal Height: 26.4mm
> Tall Height: 41.7mm
> Wide Width: 14.2mm
> Normal Width: 10.1mm
>
> +-------------------------------------------------------------------+
> | o SEC high-speed ECC algorithm |
> | o 70ns (x36 bits) 72-pin JEDEC standard SIMM |
> | o IBM or industry standard presence detects, gold tabs |
> | o Fit in standard x36 SIMM socket |
> | o No processor changes required |
> | |
> | o 4MB (Wide) 70ns ECC-on-SIMM Memory Upgrade: |
> | - Selected PS/2(R) and IBM PC Server 300 and 320 systems |
> | |
> | o 8MB (Wide) 70ns ECC-on-SIMM Memory Upgrade: |
> | - Selected PS/2 systems |
> | |
> | o 8MB (Tall), 16MB, and 32MB 70ns ECC-on-SIMM Memory Upgrades: |
> | - IBM PC Server 300 and 320 systems |
> +-------------------------------------------------------------------+
>
> The following memory options complement the Options by IBM family of
> offerings:
>
> 4MB 70ns ECC-on-SIMM Memory Upgrade
> 8MB (Wide) 70ns ECC-on-SIMM Memory Upgrade
> 8MB (Tall) 70ns ECC-on-SIMM Memory Upgrade
> 16MB 70ns ECC-on-SIMM Memory Upgrade
> 32MB 70ns ECC-on-SIMM Memory Upgrade
>
> The IBM ECC-on-SIMM Memory Upgrades offer 4MB, 8MB, 16MB and 32MB of
> error-correcting-code (ECC) memory on a SIMM. This upgrade family -- a
> plug-compatible, fully retrofittable series of 70ns memory modules --
>
> allows you to upgrade a parity system to a fully functional
> single-error-correct (SEC) ECC system. The ECC function is completely
> self-contained on the SIMM and provides correction of single-bit errors that
>
> occur in each byte of SIMM data. No processor changes are required to
> receive the enhanced reliability this SIMM family offers.
>
> The ECC-on-SIMM Memory Upgrades are organized as x36 bits, support
> parity, and are packaged on a 72-pin JEDEC (Joint Electronic Device
> Engineering Council) standard SIMM with gold tabs. The 4MB SIMM has IBM
>
> presence detects, while the 8MB (Tall and Wide), 16MB and 32MB SIMMs
> have industry standard presence detects.
>
> Use of the ECC-on-SIMM Memory Upgrades is recommended when processing
> critical applications on systems without native ECC. Enhanced data
> integrity and memory reliability are provided with no system performance
>
> penalty. The upgrades are extremely important in server environments
> where single-bit memory errors can impact all users on the network.
>
> Part Availability Unit
> Description Number Date Price
>
>
> 4MB 70ns ECC-on-SIMM 75G6500
> 8MB (Wide) 70ns ECC-on-SIMM 75G6501
> 8MB (Tall) 70ns ECC-on-SIMM 11H0618
> 16MB 70ns ECC-on-SIMM 11H0621
> 32MB 70ns ECC-on-SIMM 11H0624
>
>
>
> IBM 4MB 70NS ECC-ON-SIMM MEMORY UPGRADE (#1500, 75G6500)
>
>
> The 4MB 70ns ECC-on-SIMM Memory Upgrade module is organized as 1M x 36,
> supports parity, and is packaged on a 72-pin JEDEC standard SIMM with
> gold tabs and IBM presence detects.
>
> Technical Information
>
> Physical Specifications
>
> Dimensions:
> Height: 26.4 mm (1.04 in.)
> Width: 108 mm (4.25 in.)
> Depth: 10.1 mm (0.4 in.)
> Weight: .025kg (0.055 lb)
>
> Operating Environment
>
> Temperature: 0(degs)C to 65(degs)C (32(degs)F to 149(degs)F)
> Relative humidity: 8% to 80%
> Wet bulb: 23(degs)C (73(degs)F)
> Electrical power: 1620 mA max
>
> Hardware Requirements: The 4BM 70ns ECC-on-SIMM Memory Upgrade (#1500,
> 75G6500) is supported on the following IBM platforms:
>
> Machine
> Description Type Model
>
>
> PS/2 8525 K00, K01, L02
> 8535 040, 043, 050, 055,
> 14X, 24X
> 8540 040, 043, 045
> 8556 043, 045, 055, 059,
> 14X, 15X, 24X, 25X
> 8557 045, 049, 055, 059,
> 05F, 259
> 8590(1) 0J5, 0J9, 0JD, 0JF,
> 0K9, 0KD, 0KF, 0GF,
> 0G5, 0G9, 0HF, 0H5, 0H9,
> 0L9, 0LF
> 8595(1) 0J9, 0JD, 0JF, 0KD,
> 0KF, 0G5, 0G9, 0GF,
> 0H5, 0H9, 0HF, 0L9,
> 0LF, 0X6, 0XA, 0XF,
> 0XG
> 9553 0B7, 0BB, 1BX, 2BX
> 9556 DBA, DB6, DEB, DED,
> DE9, KBA, KB6, QBA,
> QB6, 0BA, 0B6, 1EX, 2EX
> 9557 DBA, DBG, DB6, DEB,
> DED, DEG, DE9, KBA,
> KBG, KB6, QBA, QB6,
> 0BA, 0B6, 1BA, 2BA,
> 6EB, 6EG, 7EB, 7EG
> 9576 DUA,DU6, KUA, KU6,
> QUA, QU6, 0UA, 0U6
> 9577 DNA, DNG, DUA, DUG,
> KNA, KNG, KUA, KUG
> QBA, QB6, QNA, QUA,
> 0NA, 0NF, 0UA, 0UF,
> 1NA, 1UA,
> 9585(1) 0X6, 0XA, 0XF, 0XG,
> 0KG, 0KT, 0NG, 0NT
> 9590(1) DLA, 0LA, QLA, KLA,
> 0LF, DLG, KLG
> 9595(1) 0LF, 0LG
>
>
> PC Server 8640(1) 0N0, 0NJ, 0P0, 0PT,
> 0Y0, 0YT, 1Y0, 1YT
>
> (1) These systems must be upgraded with sets of two 75G6500
> upgrades.
>
> Limitations
>
> Parity memory cannot coexist with the 4MB 70ns ECC-on-SIMM Memory
> Upgrade in the same system.
> 8590, 8595, 9590, and 9595 models with native ECC (xMx,1Nx, xPx,
> xQx, xTx, xVx) are not supported.
>
>
> IBM 8MB (WIDE) 70NS ECC-ON-SIMM MEMORY UPGRADE (#6501, 675G6501)
>
> The 8MB (Wide) 70ns ECC-on-SIMM Memory Upgrade module is organized as 2M
> x 36, supports parity, and is packaged on a 72-pin JEDEC standard SIMM
> with gold tabs and industry standard presence detects.
>
> Technical Information
>
> Physical Specifications
>
> Dimensions:
> Height: 26.4 mm (1.04 in.)
> Width: 108 mm (4.25 in.)
> Depth: 14.2 mm (0.56 in.)
> Weight: .041 kg (0.09 lb)
>
> Operating Environment
>
> Temperature: 0(degs)C to 65(degs)C (32(degs)F to 149(degs)F)
> Relative humidity: 8% to 80%
> Wet bulb: 23(degs)C (73(degs)F)
> Electrical power: 1656 mA max
>
>
> Hardware Requirements: The 8MB (Wide) 70ns ECC-on-SIMM Memory Upgrade
> (#6501, 675G6501) is supported on the following IBM platforms:
>
> Machine
> Description Type Model
>
>
> PS/2 8556 043, 045, 055, 059,
> 14X, 15X, 24X, 25X
> 8557 045, 049, 055, 059,
> 05F, 259
> 8590(1) 0J5, 0J9, 0JD, 0JF,
> 0K9, 0KD, 0KF, 0G5,
> 0G9, 0GF, 0H5, 0H9,
> 0HF, 0L9, 0LF
> 8595(1) 0J9, 0JD, 0JF, 0KD,
> 0KF, 0G5, 0G9, 0GF,
> 0H5, 0H9, 0HF, 0L9,
> 0LF, 0X6, 0XA, 0XF,
> 0XG
> 9556 DBA, DB6, DEB, DED,
> DE9, KBA, KB6, QBA,
> QB6, 0BA, 0B6, 1EX,
> 2EX
> 9557 DBA, DBG, DB6, DEB,
> DED, DEG, DE9, KBA,
> KBG, KB6, QBA, QB6,
> 0BA, 0B6, 1BA, 2BA,
> 6EB, 6EG, 7EB, 7EG
> 9576 DUA, DU6, KUA, KU6,
> QUA, QU6, 0UA, 0U6
> 9577 DNA, DNG, DUA, DUG,
> KNA, KNG, KUA, KUG,
> QBA, QB6, QNA, QUA,
> 0NA, 0NF,0UA, 0UF,
> 1NA, 1UA
> 9585(1) 0X6, 0XA, 0XF, 0XG,
> 0KG, 0KT, 0NG, 0NT
> 9590(1) DLA, 0LA, QLA, KLA,
> 0LF, DLG, KLG
> 9595(1) 0LF, 0LG
>
> (1) These systems must be upgraded with sets of two 75G6501 upgrades.
>
> Limitations
>
> Parity SIMMs cannot coexist with the IBM 8MB (Wide) 70ns
> ECC-on-SIMM Memory Upgrade in the same system.
> 8590, 8595, 9590, and 9595 models with native ECC (xMx, 1Nx, xPx,
> xQx, xTx, xVx) are not supported.
> Maximum system memory is not attainable on 8556, 8557, 9556, 9557,
> 9576, and 9577 models due to physical constraints:
> Two 8MB (Wide) ECC-on-SIMM Memory Upgrades cannot be installed
> in adjacent SIMM sockets.
> Models with three SIMM sockets have a maximum of two 8MB (Wide)
> and one 4MB ECC-on-SIMM Memory Upgrades.
> Models with four SIMM sockets have a maximum of two 8MB (Wide)
> and two 4MB ECC-on-SIMM Memory Upgrades.
>
>
>
> IBM 8MB (TALL) 70NS ECC-ON-SIMM MEMORY UPGRADE (#1681, 11H0618)
>
> The 8MB (Tall) 70ns ECC-on-SIMM Memory Upgrade module is organized as 2M
> x 36, supports parity, and is packaged on a 72-pin JEDEC standard SIMM
> with gold tabs and industry standard presence detects.
>
> Technical Information
>
> Physical Specifications
>
> Dimensions:
> Height: 41.7 mm (1.64 in.)
> Width: 108 mm (4.25 in.)
> Depth: 10.1 mm (0.40 in.)
> Weight: .039 kg (0.09 lb)
>
> Operating Environment
>
> Temperature: 0(degs)C to 65(degs)C (32(degs)F to 149(degs)F)
> Relative humidity: 8% to 80%
> Wet bulb: 23(degs)C (73(degs)F)
> Electrical power: 1656 mA max
>
>
> Hardware Requirements: The 8MB (Tall) 70ns ECC-on-SIMM Memory Upgrade is
> supported on the following IBM platforms:
>
> Machine
> Description Type Model
>
>
> PC Server 8640(1) 0N0, ONJ, 0P0, 0PT, 0Y0,
> 0YT, 1Y0, 1YT
>
> (1) These systems must be upgraded with sets of two 11H0618
> upgrades.
>
> Limitations: Parity SIMMs cannot coexist with the 8MB (Tall) 70ns
> ECC-on-SIMM Memory Upgrade in the same system.
>
>
> IBM 16MB 70NS ECC-ON-SIMM MEMORY UPGRADE (#1621, 11H0621)
>
>
> The 16MB 70ns ECC-on-SIMM Memory Upgrade module is organized as 4M x 36,
> supports parity, and is packaged on a 72-pin JEDEC standard SIMM with
> gold tabs and industry standard presence detects.
>
>
> Physical Specifications
>
> Dimensions:
> Height: 26.4 mm (1.04 in.)
> Width: 108 mm (4.25 in.)
> Depth: 10.1 mm (0.40 in.)
> Weight: .025 kg (0.06 lb)
>
> Operating Environment
>
> Temperature: 0(degs)C to 65(degs)C (32(degs)F to 149(degs)F)
> Relative humidity: 8% to 80%
> Wet bulb: 23(degs)C (73(degs)F)
> Electrical power: 1440 mA max
>
> Hardware Requirements: The 16MB 70ns ECC-on-SIMM Memory Upgrade is
> supported on the following IBM platforms:
>
> Machine
> Description Type Model
>
>
> PC Server 8640(1) 0N0, ONJ, 0P0, 0PT, 0Y0,
> 0YT, 1Y0, 1YT
>
> (1) These systems must be upgraded with sets of two 11H0621 upgrades.
>
> Limitations: Parity SIMMs cannot coexist with the 16MB 70ns ECC-on-SIMM
> Memory Upgrade in the same system.
>
>
>
> IBM 32MB 70NS ECC-ON-SIMM MEMORY UPGRADE (#1624, 11H0624)
>
> The 32MB 70ns ECC-on-SIMM Memory Upgrade module is organized as 8M x 36,
> supports parity, and is packaged on a 72-pin JEDEC standard SIMM with
> gold tabs and industry standard presence detects.
>
> Technical Information
>
> Physical Specifications
>
> Width: 108 mm (4.25 in.)
> Depth: 10.1 mm (0.40 in.)
> Length: 41.7 mm (1.64 in.)
> Weight: .039 kg (0.09 lb)
>
> Operating Environment
>
> Temperature: 0(degs)C to 65(degs)C (32(degs)F to 149(degs)F)
> Relative humidity: 8% to 80%
> Wet bulb: 23(degs)C (73(degs)F)
> Electrical power: 1464 mA max
>
>
> Hardware Requirements: The 32MB 70ns ECC-on-SIMM Memory Upgrade is
> supported on the following IBM platforms:
>
> Machine
> Description Type Model
>
>
> PC Server 8640(1) 0N0, ONJ, 0P0, 0PT, 0Y0,
> 0YT, 1Y0, 1YT
>
> (1) These systems must be upgraded with sets of two 11H0624 upgrades.
>
> Limitations: Parity SIMMs cannot coexist with the 32MB 70ns ECC-on-SIMM
> Memory Upgrade in the same system.
So mine two 11H0621 has only use in PC Server 8640 that I don´t have.

The size is the issue. Most PS/2s do not support 16MB FPM.

9585-xXx, 9585-K/N, Lacuna

Pertti Helander wrote:
> So mine two 11H0621 has only use in PC Server 8640 that I don´t have.

On Friday, March 31, 2023 at 6:23:31 AM UTC-4, Louis Ohland wrote:
> Nice that someone is awake.
>
> Buzzkill, the EOS reports itself as parity, so the system in question
> has to support 16MB parity SIMMs.
>
> 9585 -X or -K/N
>
> 4MB and 8MB EOS are supported by all PS/2s, as their size is supported.
>
> The IBM ECC-on-SIMM (EOS) part numbers are
> 11H0618 (8MB)
> 11H0621 (16MB)
> 11H0624 (32MB)
>
> Lead composition:
>
> 11D - Tin
> 11E - Gold
>
> ECC controller on EOS is 73G6876.
> These are a sea of gates, not a specific ASIC
>
> Toshiba TC160G11AT
> AMI 6553-013
>
> https://www.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/5/897/ENUS195-075/index.html&request_locale=en
>
>
> Options by IBM: IBM ECC-on-SIMM Memory Upgrades
> Announcement Number: 195-075
>
> Normal Height: 26.4mm
> Tall Height: 41.7mm
> Wide Width: 14.2mm
> Normal Width: 10.1mm
>
> +-------------------------------------------------------------------+
> | o SEC high-speed ECC algorithm |
> | o 70ns (x36 bits) 72-pin JEDEC standard SIMM |
> | o IBM or industry standard presence detects, gold tabs |
> | o Fit in standard x36 SIMM socket |
> | o No processor changes required |
> | |
> | o 4MB (Wide) 70ns ECC-on-SIMM Memory Upgrade: |
> | - Selected PS/2(R) and IBM PC Server 300 and 320 systems |
> | |
> | o 8MB (Wide) 70ns ECC-on-SIMM Memory Upgrade: |
> | - Selected PS/2 systems |
> | |
> | o 8MB (Tall), 16MB, and 32MB 70ns ECC-on-SIMM Memory Upgrades: |
> | - IBM PC Server 300 and 320 systems |
> +-------------------------------------------------------------------+
>
> The following memory options complement the Options by IBM family of
> offerings:
>
> 4MB 70ns ECC-on-SIMM Memory Upgrade
> 8MB (Wide) 70ns ECC-on-SIMM Memory Upgrade
> 8MB (Tall) 70ns ECC-on-SIMM Memory Upgrade
> 16MB 70ns ECC-on-SIMM Memory Upgrade
> 32MB 70ns ECC-on-SIMM Memory Upgrade
>
> The IBM ECC-on-SIMM Memory Upgrades offer 4MB, 8MB, 16MB and 32MB of
> error-correcting-code (ECC) memory on a SIMM. This upgrade family -- a
> plug-compatible, fully retrofittable series of 70ns memory modules --
>
> allows you to upgrade a parity system to a fully functional
> single-error-correct (SEC) ECC system. The ECC function is completely
> self-contained on the SIMM and provides correction of single-bit errors that
>
> occur in each byte of SIMM data. No processor changes are required to
> receive the enhanced reliability this SIMM family offers.
>
> The ECC-on-SIMM Memory Upgrades are organized as x36 bits, support
> parity, and are packaged on a 72-pin JEDEC (Joint Electronic Device
> Engineering Council) standard SIMM with gold tabs. The 4MB SIMM has IBM
>
> presence detects, while the 8MB (Tall and Wide), 16MB and 32MB SIMMs
> have industry standard presence detects.
>
> Use of the ECC-on-SIMM Memory Upgrades is recommended when processing
> critical applications on systems without native ECC. Enhanced data
> integrity and memory reliability are provided with no system performance
>
> penalty. The upgrades are extremely important in server environments
> where single-bit memory errors can impact all users on the network.
>
> Part Availability Unit
> Description Number Date Price
>
>
> 4MB 70ns ECC-on-SIMM 75G6500
> 8MB (Wide) 70ns ECC-on-SIMM 75G6501
> 8MB (Tall) 70ns ECC-on-SIMM 11H0618
> 16MB 70ns ECC-on-SIMM 11H0621
> 32MB 70ns ECC-on-SIMM 11H0624
>
>
>
> IBM 4MB 70NS ECC-ON-SIMM MEMORY UPGRADE (#1500, 75G6500)
>
>
> The 4MB 70ns ECC-on-SIMM Memory Upgrade module is organized as 1M x 36,
> supports parity, and is packaged on a 72-pin JEDEC standard SIMM with
> gold tabs and IBM presence detects.
>
> Technical Information
>
> Physical Specifications
>
> Dimensions:
> Height: 26.4 mm (1.04 in.)
> Width: 108 mm (4.25 in.)
> Depth: 10.1 mm (0.4 in.)
> Weight: .025kg (0.055 lb)
>
> Operating Environment
>
> Temperature: 0(degs)C to 65(degs)C (32(degs)F to 149(degs)F)
> Relative humidity: 8% to 80%
> Wet bulb: 23(degs)C (73(degs)F)
> Electrical power: 1620 mA max
>
> Hardware Requirements: The 4BM 70ns ECC-on-SIMM Memory Upgrade (#1500,
> 75G6500) is supported on the following IBM platforms:
>
> Machine
> Description Type Model
>
>
> PS/2 8525 K00, K01, L02
> 8535 040, 043, 050, 055,
> 14X, 24X
> 8540 040, 043, 045
> 8556 043, 045, 055, 059,
> 14X, 15X, 24X, 25X
> 8557 045, 049, 055, 059,
> 05F, 259
> 8590(1) 0J5, 0J9, 0JD, 0JF,
> 0K9, 0KD, 0KF, 0GF,
> 0G5, 0G9, 0HF, 0H5, 0H9,
> 0L9, 0LF
> 8595(1) 0J9, 0JD, 0JF, 0KD,
> 0KF, 0G5, 0G9, 0GF,
> 0H5, 0H9, 0HF, 0L9,
> 0LF, 0X6, 0XA, 0XF,
> 0XG
> 9553 0B7, 0BB, 1BX, 2BX
> 9556 DBA, DB6, DEB, DED,
> DE9, KBA, KB6, QBA,
> QB6, 0BA, 0B6, 1EX, 2EX
> 9557 DBA, DBG, DB6, DEB,
> DED, DEG, DE9, KBA,
> KBG, KB6, QBA, QB6,
> 0BA, 0B6, 1BA, 2BA,
> 6EB, 6EG, 7EB, 7EG
> 9576 DUA,DU6, KUA, KU6,
> QUA, QU6, 0UA, 0U6
> 9577 DNA, DNG, DUA, DUG,
> KNA, KNG, KUA, KUG
> QBA, QB6, QNA, QUA,
> 0NA, 0NF, 0UA, 0UF,
> 1NA, 1UA,
> 9585(1) 0X6, 0XA, 0XF, 0XG,
> 0KG, 0KT, 0NG, 0NT
> 9590(1) DLA, 0LA, QLA, KLA,
> 0LF, DLG, KLG
> 9595(1) 0LF, 0LG
>
>
> PC Server 8640(1) 0N0, 0NJ, 0P0, 0PT,
> 0Y0, 0YT, 1Y0, 1YT
>
> (1) These systems must be upgraded with sets of two 75G6500
> upgrades.
>
> Limitations
>
> Parity memory cannot coexist with the 4MB 70ns ECC-on-SIMM Memory
> Upgrade in the same system.
> 8590, 8595, 9590, and 9595 models with native ECC (xMx,1Nx, xPx,
> xQx, xTx, xVx) are not supported.
>
>
> IBM 8MB (WIDE) 70NS ECC-ON-SIMM MEMORY UPGRADE (#6501, 675G6501)
>
> The 8MB (Wide) 70ns ECC-on-SIMM Memory Upgrade module is organized as 2M
> x 36, supports parity, and is packaged on a 72-pin JEDEC standard SIMM
> with gold tabs and industry standard presence detects.
>
> Technical Information
>
> Physical Specifications
>
> Dimensions:
> Height: 26.4 mm (1.04 in.)
> Width: 108 mm (4.25 in.)
> Depth: 14.2 mm (0.56 in.)
> Weight: .041 kg (0.09 lb)
>
> Operating Environment
>
> Temperature: 0(degs)C to 65(degs)C (32(degs)F to 149(degs)F)
> Relative humidity: 8% to 80%
> Wet bulb: 23(degs)C (73(degs)F)
> Electrical power: 1656 mA max
>
>
> Hardware Requirements: The 8MB (Wide) 70ns ECC-on-SIMM Memory Upgrade
> (#6501, 675G6501) is supported on the following IBM platforms:
>
> Machine
> Description Type Model
>
>
> PS/2 8556 043, 045, 055, 059,
> 14X, 15X, 24X, 25X
> 8557 045, 049, 055, 059,
> 05F, 259
> 8590(1) 0J5, 0J9, 0JD, 0JF,
> 0K9, 0KD, 0KF, 0G5,
> 0G9, 0GF, 0H5, 0H9,
> 0HF, 0L9, 0LF
> 8595(1) 0J9, 0JD, 0JF, 0KD,
> 0KF, 0G5, 0G9, 0GF,
> 0H5, 0H9, 0HF, 0L9,
> 0LF, 0X6, 0XA, 0XF,
> 0XG
> 9556 DBA, DB6, DEB, DED,
> DE9, KBA, KB6, QBA,
> QB6, 0BA, 0B6, 1EX,
> 2EX
> 9557 DBA, DBG, DB6, DEB,
> DED, DEG, DE9, KBA,
> KBG, KB6, QBA, QB6,
> 0BA, 0B6, 1BA, 2BA,
> 6EB, 6EG, 7EB, 7EG
> 9576 DUA, DU6, KUA, KU6,
> QUA, QU6, 0UA, 0U6
> 9577 DNA, DNG, DUA, DUG,
> KNA, KNG, KUA, KUG,
> QBA, QB6, QNA, QUA,
> 0NA, 0NF,0UA, 0UF,
> 1NA, 1UA
> 9585(1) 0X6, 0XA, 0XF, 0XG,
> 0KG, 0KT, 0NG, 0NT
> 9590(1) DLA, 0LA, QLA, KLA,
> 0LF, DLG, KLG
> 9595(1) 0LF, 0LG
>
> (1) These systems must be upgraded with sets of two 75G6501 upgrades.
>
> Limitations
>
> Parity SIMMs cannot coexist with the IBM 8MB (Wide) 70ns
> ECC-on-SIMM Memory Upgrade in the same system.
> 8590, 8595, 9590, and 9595 models with native ECC (xMx, 1Nx, xPx,
> xQx, xTx, xVx) are not supported.
> Maximum system memory is not attainable on 8556, 8557, 9556, 9557,
> 9576, and 9577 models due to physical constraints:
> Two 8MB (Wide) ECC-on-SIMM Memory Upgrades cannot be installed
> in adjacent SIMM sockets.
> Models with three SIMM sockets have a maximum of two 8MB (Wide)
> and one 4MB ECC-on-SIMM Memory Upgrades.
> Models with four SIMM sockets have a maximum of two 8MB (Wide)
> and two 4MB ECC-on-SIMM Memory Upgrades.
>
>
>
> IBM 8MB (TALL) 70NS ECC-ON-SIMM MEMORY UPGRADE (#1681, 11H0618)
>
> The 8MB (Tall) 70ns ECC-on-SIMM Memory Upgrade module is organized as 2M
> x 36, supports parity, and is packaged on a 72-pin JEDEC standard SIMM
> with gold tabs and industry standard presence detects.
>
> Technical Information
>
> Physical Specifications
>
> Dimensions:
> Height: 41.7 mm (1.64 in.)
> Width: 108 mm (4.25 in.)
> Depth: 10.1 mm (0.40 in.)
> Weight: .039 kg (0.09 lb)
>
> Operating Environment
>
> Temperature: 0(degs)C to 65(degs)C (32(degs)F to 149(degs)F)
> Relative humidity: 8% to 80%
> Wet bulb: 23(degs)C (73(degs)F)
> Electrical power: 1656 mA max
>
>
> Hardware Requirements: The 8MB (Tall) 70ns ECC-on-SIMM Memory Upgrade is
> supported on the following IBM platforms:
>
> Machine
> Description Type Model
>
>
> PC Server 8640(1) 0N0, ONJ, 0P0, 0PT, 0Y0,
> 0YT, 1Y0, 1YT
>
> (1) These systems must be upgraded with sets of two 11H0618
> upgrades.
>
> Limitations: Parity SIMMs cannot coexist with the 8MB (Tall) 70ns
> ECC-on-SIMM Memory Upgrade in the same system.
>
>
> IBM 16MB 70NS ECC-ON-SIMM MEMORY UPGRADE (#1621, 11H0621)
>
>
> The 16MB 70ns ECC-on-SIMM Memory Upgrade module is organized as 4M x 36,
> supports parity, and is packaged on a 72-pin JEDEC standard SIMM with
> gold tabs and industry standard presence detects.
>
>
> Physical Specifications
>
> Dimensions:
> Height: 26.4 mm (1.04 in.)
> Width: 108 mm (4.25 in.)
> Depth: 10.1 mm (0.40 in.)
> Weight: .025 kg (0.06 lb)
>
> Operating Environment
>
> Temperature: 0(degs)C to 65(degs)C (32(degs)F to 149(degs)F)
> Relative humidity: 8% to 80%
> Wet bulb: 23(degs)C (73(degs)F)
> Electrical power: 1440 mA max
>
> Hardware Requirements: The 16MB 70ns ECC-on-SIMM Memory Upgrade is
> supported on the following IBM platforms:
>
> Machine
> Description Type Model
>
>
> PC Server 8640(1) 0N0, ONJ, 0P0, 0PT, 0Y0,
> 0YT, 1Y0, 1YT
>
> (1) These systems must be upgraded with sets of two 11H0621 upgrades.
>
> Limitations: Parity SIMMs cannot coexist with the 16MB 70ns ECC-on-SIMM
> Memory Upgrade in the same system.
>
>
>
> IBM 32MB 70NS ECC-ON-SIMM MEMORY UPGRADE (#1624, 11H0624)
>
> The 32MB 70ns ECC-on-SIMM Memory Upgrade module is organized as 8M x 36,
> supports parity, and is packaged on a 72-pin JEDEC standard SIMM with
> gold tabs and industry standard presence detects.
>
> Technical Information
>
> Physical Specifications
>
> Width: 108 mm (4.25 in.)
> Depth: 10.1 mm (0.40 in.)
> Length: 41.7 mm (1.64 in.)
> Weight: .039 kg (0.09 lb)
>
> Operating Environment
>
> Temperature: 0(degs)C to 65(degs)C (32(degs)F to 149(degs)F)
> Relative humidity: 8% to 80%
> Wet bulb: 23(degs)C (73(degs)F)
> Electrical power: 1464 mA max
>
>
> Hardware Requirements: The 32MB 70ns ECC-on-SIMM Memory Upgrade is
> supported on the following IBM platforms:
>
> Machine
> Description Type Model
>
>
> PC Server 8640(1) 0N0, ONJ, 0P0, 0PT, 0Y0,
> 0YT, 1Y0, 1YT
>
> (1) These systems must be upgraded with sets of two 11H0624 upgrades.
>
> Limitations: Parity SIMMs cannot coexist with the 32MB 70ns ECC-on-SIMM
> Memory Upgrade in the same system.

Click here to read the complete article

The quiet ones are the dangerous ones.

Don't want to be TOO quiet...

James Hall wrote:
> I'm awake. Just being quiet.

On Friday, March 31, 2023 at 9:33:38 AM UTC-4, Louis Ohland wrote:
> The quiet ones are the dangerous ones.
>
> Don't want to be TOO quiet...
> James Hall wrote:
> > I'm awake. Just being quiet.
Any reason why 11H0621/11H0622 would hang in a Reply TurboProcessor 80? The system boots but eventually hangs.

No idea. Does the system boot normally with FPM?

lharr...@gmail.com wrote:
> Any reason why 11H0621/11H0622 would hang in a Reply TurboProcessor 80? The system boots but eventually hangs.

PC Server 8640(1) 0N0, ONJ, 0P0, 0PT, 0Y0,
0YT, 1Y0, 1YT

(1) These systems must be upgraded with sets of two 11H0621 upgrades.

Limitations: Parity SIMMs cannot coexist with the 16MB 70ns ECC-on-SIMM
Memory Upgrade in the same system.

OK, coffee injection to War Power settings... rammed the throttle
through the seals....

The 4MB and 8MB EoS are marketed for the PS/2. the 16MB are not. Why?
Dunno. Only the Lacuna, 85X and 85K can handle 16MB FPM, and therefore,
the 16MB EoS.

Standard 4MB of RAM, expandable to 128MB

Reply offers 2MB, 4MB, 8MB, and 16MB memory module option kits. You must
install the modules in pairs (two modules for each bank). Modules in
different banks do not need to be of the same density, however, ECC and
Parity memory modules cannot be installed on the same Reply system
board. Memory modules are not required to be installed in any specific
bank order.

4MB on-board | 128MB = Maximum
Type 2, 4, 8, 16MB memory modules types are supported:
“Industry standard" x 36 parity, 72-pin SIMMs
“IBM Proprietary" x 36 parity, 72-pin SIMMs
“Industry standard" x 40 ECC, 72-pin SIMMs
(For maximum performance, 70nS recommended)

ECC looks odd, typo? PS/2 ECC x39. RS/6000 x40.

https://www.ardent-tool.com/Reply/Turbo_60_80_Manual.pdf

Physical page 39. Reply has two SIMM sockets next to each other as a
"Bank", while IBM had arrangements where [at least on the 95] "A" bank
and "B" bank are grouped together.

Whatever, Reply has "Bank 1", analogous to A1/B1, "Bank 2" analogous to
A2/B2, usw...

If you are wandting to try EoS, fill one bank with a matched pair of
EoS. EoS CANNOT be used in the same bank as FPM because you need two EoS
to generate the ECC.

Now as to the next question, I dunno. Can EoS banks and FPM banks exist
in the same system?

Try it, I will trumpet your success or commiserate with your failure...

lharr...@gmail.com wrote:
> On Friday, March 31, 2023 at 9:33:38 AM UTC-4, Louis Ohland wrote:
>> The quiet ones are the dangerous ones.
>>
>> Don't want to be TOO quiet...
>> James Hall wrote:
>>> I'm awake. Just being quiet.
> Any reason why 11H0621/11H0622 would hang in a Reply TurboProcessor 80? The system boots but eventually hangs.
>

On Friday, March 31, 2023 at 9:33:38 AM UTC-4, Louis Ohland wrote:
> The quiet ones are the dangerous ones.
>
> Don't want to be TOO quiet...
> James Hall wrote:
> > I'm awake. Just being quiet.
Any reason why 11H0621/11H0622 would hang in a Reply TurboProcessor 80? The system boots but eventually hangs.
. X-Received: by 2002:a05:622a:294:b0:3ef:3204:5159 with SMTP id z20-20020a05622a029400b003ef32045159mr771792qtw.7.1682021120814;
Thu, 20 Apr 2023 13:05:20 -0700 (PDT)
X-Received: by 2002:a05:6870:a10:b0:187:e1d0:ea18 with SMTP id
bf16-20020a0568700a1000b00187e1d0ea18mr826723oac.9.1682021120493; Thu, 20 Apr
2023 13:05:20 -0700 (PDT)
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!1.us.feeder.erje.net!3.us.feeder.erje.net!feeder.erje.net!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.sys.ibm.ps2.hardware
Date: Thu, 20 Apr 2023 13:05:20 -0700 (PDT)
In-Reply-To: <u1rhmv$1ekd$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
Injection-Info: google-groups.googlegroups.com; posting-host!7.89.119.238; posting-account=MSoytgoAAAB840_pyx2nqfEwBbRVpagI
NNTP-Posting-Host: 217.89.119.238
References: <u1m9sb$bmf$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
<u1mck8$dpi$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
<u1mdo3$eit$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
<u1mdqs$eit$2@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
<u1mf2t$fhl$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
<u1mj21$ibq$2@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
<u1mnqs$lum$2@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
<u1n9qu$13lj$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
<ea6af368-5770-420c-afbc-4706658a4423n@googlegroups.com> <u1pgeo$2pnu$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
<92d7cb5b-c3e2-4441-ac2d-df825c4b7618n@googlegroups.com> <u1pluu$2trq$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
<u1q3io$8c7$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com> <u1rhmv$1ekd$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <16c57455-2354-4fdd-80c8-5541ad68b3fan@googlegroups.com>
Subject: Re: A miss is as good as a mile Re: Did you READ it? Re: IBM Single
Chip SCSI Subsystem page
From: schimmi <stefan.lemanski@gmail.com>
Injection-Date: Thu, 20 Apr 2023 20:05:20 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 3051
Xref: retrobbs comp.sys.ibm.ps2.hardware:4171

Guess there was only one CPU made for this - the DX50. On my old 486/VLB setup I always had problems even with 40MHz/VLB using more than just the graphics adapter. On a 3-slot VLB Board you had one busmastering and accordingly 2 secondary slots you had to address using more than one card, especially with a SCSI/IO-Cards. With all three VLB slots filled, it was some kind of a gamble if the system was stable, even with 40MHz :-/ VLB was very card-dependant.

Tomas Slavotinek schrieb am Donnerstag, 20. April 2023 um 16:20:17 UTC+2:
> On 20.04.2023 3:13, Louis Ohland wrote:
> > The number of slots also decreases with increased speed. IIRC, you could
> > only use one slot at 50MHz.
> >
> > Tomas Slavotinek wrote:
> >> hence the limitation to 3 or less slots).
> That's correct. At 50 MHz you were lucky if it even worked in the
> single-slot configuration. The CPU bus was never designed for something
> like this...
. Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!csiph.com!.POSTED.071-087-128-099.res.spectrum.com!not-for-mail
From: Louis Ohland <ohland@charter.net>
Newsgroups: comp.sys.ibm.ps2.hardware
Subject: Parallel realities
Date: Mon, 24 Apr 2023 11:57:52 -0500
Organization: csiph.com Internet News Service
Message-ID: <u26cdd$lec$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Mon, 24 Apr 2023 16:57:17 -0000 (UTC)
Injection-Info: 842ffb22-07e1-11e5-a459-00266cf00584.csiph.com; posting-host="071-087-128-099.res.spectrum.com:71.87.128.99";
logging-data="21964"; mail-complaints-to="admin@kev009.com"
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:91.0) Gecko/20100101
Firefox/91.0 SeaMonkey/2.53.16
X-Mozilla-News-Host: news://csiph.com:119
Xref: retrobbs comp.sys.ibm.ps2.hardware:4171

Foundt a few parallel port patents

More l8ter. The same presentation style as with the SCS page.
. Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!csiph.com!.POSTED.071-087-128-099.res.spectrum.com!not-for-mail
From: Louis Ohland <ohland@charter.net>
Newsgroups: comp.sys.ibm.ps2.hardware
Subject: Little Boy Blue! Report!
Date: Wed, 26 Apr 2023 22:00:47 -0500
Organization: csiph.com Internet News Service
Message-ID: <u2cofn$2j3i$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Thu, 27 Apr 2023 03:00:07 -0000 (UTC)
Injection-Info: 842ffb22-07e1-11e5-a459-00266cf00584.csiph.com; posting-host="071-087-128-099.res.spectrum.com:71.87.128.99";
logging-data="85106"; mail-complaints-to="admin@kev009.com"
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:91.0) Gecko/20100101
Firefox/91.0 SeaMonkey/2.53.16
X-Mozilla-News-Host: news://csiph.com:119
Xref: retrobbs comp.sys.ibm.ps2.hardware:4171

Ryan, update us on Azure SCSI.
. Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!csiph.com!.POSTED.071-087-128-099.res.spectrum.com!not-for-mail
From: Louis Ohland <ohland@charter.net>
Newsgroups: comp.sys.ibm.ps2.hardware
Subject: Re: Using Jaz Traveller with non-Iomega drives
Date: Fri, 28 Apr 2023 23:03:59 -0500
Organization: csiph.com Internet News Service
Message-ID: <u2i4u1$k1h$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
References: <u2dp8s$b6r$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
<o7krhj-h0p42.ln1@HPmini-i3.gateway>
<u2gipb$2fab$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
<27auhj-7otb2.ln1@HPmini-i3.gateway>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Sat, 29 Apr 2023 04:03:13 -0000 (UTC)
Injection-Info: 842ffb22-07e1-11e5-a459-00266cf00584.csiph.com; posting-host="071-087-128-099.res.spectrum.com:71.87.128.99";
logging-data="20529"; mail-complaints-to="admin@kev009.com"
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:91.0) Gecko/20100101
Firefox/91.0 SeaMonkey/2.53.16
In-Reply-To: <27auhj-7otb2.ln1@HPmini-i3.gateway>
Xref: retrobbs comp.sys.ibm.ps2.hardware:4171

Don't need the traveller function, I'd like to use a SD card reader on it.

> SCSI to Parallel is what you have ATM with the traveller
>
> SCSI to IDE
> SCSI to SATA
> SCSI to USB ??
>
> anyway , you get the point, you be eliminating the traveller function.
>
. Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!tncsrv06.tnetconsulting.net!csiph.com!.POSTED.159.196.95.10!HPmini-i3.gateway!not-for-mail
From: moussa <devol95@hotmail.com>
Newsgroups: comp.sys.ibm.ps2.hardware
Subject: Re: Using Jaz Traveller with non-Iomega drives
Date: Tue, 2 May 2023 11:39:25 +0800
Organization: PS2moussa
Message-ID: <d8d6ij-hqv.ln1@HPmini-i3.gateway>
References: <u2dp8s$b6r$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
<o7krhj-h0p42.ln1@HPmini-i3.gateway>
<u2gipb$2fab$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
<27auhj-7otb2.ln1@HPmini-i3.gateway>
<u2i4u1$k1h$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
Reply-To: devol95@hotmail.com
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Info: 842ffb22-07e1-11e5-a459-00266cf00584.csiph.com; posting-host="159.196.95.10";
logging-data="20749"; mail-complaints-to="admin@kev009.com"
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
Thunderbird/102.10.0
Content-Language: en-AU
In-Reply-To: <u2i4u1$k1h$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
Xref: retrobbs comp.sys.ibm.ps2.hardware:4171

On 29/4/23 12:03, Louis Ohland wrote:
> Don't need the traveller function, I'd like to use a SD card reader on it.
>
>> SCSI to Parallel is what you have ATM with the traveller
>>
>> SCSI to IDE
>> SCSI to SATA
>> SCSI to USB ??
>>
>> anyway , you get the point, you be eliminating the traveller function.
>>
3rd time the charm

You are better of with CF media/devices, the common ASIC used has a poor
transfer rate in those SD adaptors coming from the east.

No idea. Does the system boot normally with FPM?

lharr...@gmail.com wrote:
> Any reason why 11H0621/11H0622 would hang in a Reply TurboProcessor 80? The system boots but eventually hangs.
. X-Received: by 2002:ac8:5a84:0:b0:3ef:337b:4fce with SMTP id c4-20020ac85a84000000b003ef337b4fcemr989081qtc.6.1682026259729;
Thu, 20 Apr 2023 14:30:59 -0700 (PDT)
X-Received: by 2002:a9d:51ca:0:b0:6a5:f8b6:ccc9 with SMTP id
d10-20020a9d51ca000000b006a5f8b6ccc9mr798069oth.4.1682026259427; Thu, 20 Apr
2023 14:30:59 -0700 (PDT)
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.sys.ibm.ps2.hardware
Date: Thu, 20 Apr 2023 14:30:59 -0700 (PDT)
In-Reply-To: <16c57455-2354-4fdd-80c8-5541ad68b3fan@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=217.89.119.238; posting-account=MSoytgoAAAB840_pyx2nqfEwBbRVpagI
NNTP-Posting-Host: 217.89.119.238
References: <u1m9sb$bmf$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
<u1mck8$dpi$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
<u1mdo3$eit$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
<u1mdqs$eit$2@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
<u1mf2t$fhl$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
<u1mj21$ibq$2@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
<u1mnqs$lum$2@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
<u1n9qu$13lj$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
<ea6af368-5770-420c-afbc-4706658a4423n@googlegroups.com> <u1pgeo$2pnu$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
<92d7cb5b-c3e2-4441-ac2d-df825c4b7618n@googlegroups.com> <u1pluu$2trq$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
<u1q3io$8c7$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
<u1rhmv$1ekd$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com> <16c57455-2354-4fdd-80c8-5541ad68b3fan@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <6398d445-7440-45b1-ac57-c99fb733eff9n@googlegroups.com>
Subject: Re: A miss is as good as a mile Re: Did you READ it? Re: IBM Single
Chip SCSI Subsystem page
From: schimmi <stefan.lemanski@gmail.com>
Injection-Date: Thu, 20 Apr 2023 21:30:59 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 3500
Xref: retrobbs comp.sys.ibm.ps2.hardware:4172

I'm a bit off here, sorry. The question I now have in mind is: is SCSI betw=
een CPU and MCA better than SCSI on MCA, nicely packed between all other MC=
A-devices, on one bus? I mean, local bus operations should impact MCA trans=
actions and vice versa, probably affecting the overall performance Oo

schimmi schrieb am Donnerstag, 20. April 2023 um 22:05:21 UTC+2:
> Guess there was only one CPU made for this - the DX50. On my old 486/VLB =
setup I always had problems even with 40MHz/VLB using more than just the gr=
aphics adapter. On a 3-slot VLB Board you had one busmastering and accordin=
gly 2 secondary slots you had to address using more than one card, especial=
ly with a SCSI/IO-Cards. With all three VLB slots filled, it was some kind =
of a gamble if the system was stable, even with 40MHz :-/ VLB was very card=
-dependant.
> Tomas Slavotinek schrieb am Donnerstag, 20. April 2023 um 16:20:17 UTC+2:=
=20
> > On 20.04.2023 3:13, Louis Ohland wrote:=20
> > > The number of slots also decreases with increased speed. IIRC, you co=
uld=20
> > > only use one slot at 50MHz.=20
> > >=20
> > > Tomas Slavotinek wrote:=20
> > >> hence the limitation to 3 or less slots).=20
> > That's correct. At 50 MHz you were lucky if it even worked in the=20
> > single-slot configuration. The CPU bus was never designed for something=
=20
> > like this...
. X-Received: by 2002:ac8:5808:0:b0:3f0:a9a0:45e3 with SMTP id g8-20020ac85808000000b003f0a9a045e3mr515313qtg.12.1682361434904;
Mon, 24 Apr 2023 11:37:14 -0700 (PDT)
X-Received: by 2002:a9d:4c10:0:b0:6a5:ceab:55c with SMTP id
l16-20020a9d4c10000000b006a5ceab055cmr4790344otf.3.1682361434545; Mon, 24 Apr
2023 11:37:14 -0700 (PDT)
Path: i2pn2.org!rocksolid2!i2pn.org!weretis.net!feeder8.news.weretis.net!proxad.net!feeder1-2.proxad.net!209.85.160.216.MISMATCH!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.sys.ibm.ps2.hardware
Date: Mon, 24 Apr 2023 11:37:14 -0700 (PDT)
In-Reply-To: <bca38c38-2c60-4873-b3f8-6960c677172an@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=208.48.51.22; posting-account=hY9MKgoAAADq7zYYpSn9YyDsmniHDGMe
NNTP-Posting-Host: 208.48.51.22
References: <3ed8acfd-2404-46f0-b673-954f1ba56e96n@googlegroups.com>
<4d563c0b-dbe6-4a42-9468-33c44c34ca4dn@googlegroups.com> <bca38c38-2c60-4873-b3f8-6960c677172an@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <b65b7abb-e8da-43e2-971a-f3b09117d625n@googlegroups.com>
Subject: Re: Looking for MCA Sound card to buy
From: Ryan Alswede <ryanalswede@gmail.com>
Injection-Date: Mon, 24 Apr 2023 18:37:14 +0000
Content-Type: text/plain; charset="UTF-8"
Xref: retrobbs comp.sys.ibm.ps2.hardware:4172

What are the ratings on the reproduction sound cards? Like my understanding is the Resound New Wave reproduction card on eBay is only rated for 8 bit mono stereo or something.

Ultimedia 7-6 was 16 bit which I got working under NT years ago...

I have M-ACPA that worked in Windows 98SE which I believe is a 16 bit card?

Ryan

.
X-Received: by 2002:a05:6214:902:b0:5ef:7245:33e9 with SMTP id dj2-20020a056214090200b005ef724533e9mr106460qvb.0.1682582312285;
Thu, 27 Apr 2023 00:58:32 -0700 (PDT)
X-Received: by 2002:a05:6870:6b88:b0:17e:1970:e5d9 with SMTP id
ms8-20020a0568706b8800b0017e1970e5d9mr326897oab.4.1682582311944; Thu, 27 Apr
2023 00:58:31 -0700 (PDT)
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.sys.ibm.ps2.hardware
Date: Thu, 27 Apr 2023 00:58:31 -0700 (PDT)
In-Reply-To: <u2co76$2ita$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
Injection-Info: google-groups.googlegroups.com; posting-host=83.94.209.108; posting-account=nEZJJAoAAAAvns0QLa8_nOOrE1P9nnbq
NNTP-Posting-Host: 83.94.209.108
References: <0d3090e6-f00d-4475-ab4c-80b9f9e300a4n@googlegroups.com> <u2co76$2ita$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <5147344a-d69b-4d80-a68f-167be7daee77n@googlegroups.com>
Subject: Re: Running Man Re: Buying a IBM PS/2 Model 9595-AHA - SN:55-1A9Z6
From: Carsten Lyng <askevej37a@gmail.com>
Injection-Date: Thu, 27 Apr 2023 07:58:32 +0000
Content-Type: text/plain; charset="UTF-8"
X-Received-Bytes: 2017
Xref: retrobbs comp.sys.ibm.ps2.hardware:4172

torsdag den 27. april 2023 kl. 04.55.36 UTC+2 skrev Louis Ohland:
> What flavor of OS will you be looking at installing on this 95?

Hi Louis and Pertti,

Thanks for all the info on the machine, I can see that there are some things I have to checkout
before "maybe" making a purchase :-)

I will get some more details about he machine from the seller
I have only got this picrure off the machine... you can see it here.: https://drive.google.com/drive/folders/1dBXmlRLZ_GIJYHU9oYTAwM-BDjwcsVcz?usp=sharing

The seller writes.: It is very heavy, and is not going to be shipped - you have to make a local picup :-)
The machine was working, when it was put in storage some years ago - it can be tested upon purchase.
but you have to carry it up to my flat first :-))

.
X-Received: by 2002:a05:622a:143:b0:3e4:e5bf:a24f with SMTP id v3-20020a05622a014300b003e4e5bfa24fmr2737010qtw.7.1682756393487;
Sat, 29 Apr 2023 01:19:53 -0700 (PDT)
X-Received: by 2002:a9d:64c1:0:b0:6a5:d944:f1d9 with SMTP id
n1-20020a9d64c1000000b006a5d944f1d9mr2003855otl.7.1682756392881; Sat, 29 Apr
2023 01:19:52 -0700 (PDT)
Path: i2pn2.org!i2pn.org!news.niel.me!glou.org!news.glou.org!usenet-fr.net!proxad.net!feeder1-2.proxad.net!209.85.160.216.MISMATCH!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.sys.ibm.ps2.hardware
Date: Sat, 29 Apr 2023 01:19:52 -0700 (PDT)
In-Reply-To: <u2h0e8$2pkk$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
Injection-Info: google-groups.googlegroups.com; posting-host=83.94.209.108; posting-account=nEZJJAoAAAAvns0QLa8_nOOrE1P9nnbq
NNTP-Posting-Host: 83.94.209.108
References: <0d3090e6-f00d-4475-ab4c-80b9f9e300a4n@googlegroups.com>
<u2co76$2ita$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
<5147344a-d69b-4d80-a68f-167be7daee77n@googlegroups.com> <u2dmru$9f9$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
<u2doi9$and$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
<u2douc$b1b$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
<06774042-8b6c-4785-a783-2e6dfd64fe00n@googlegroups.com> <u2gc3p$2aep$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
<u2ghfr$2efd$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
<6b77eb14-e72c-4228-93d7-9609a3e8ef7cn@googlegroups.com> <u2h0e8$2pkk$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <c410f187-8ede-4b7a-b18a-78b44ea38731n@googlegroups.com>
Subject: Re: Installed parts
From: Carsten Lyng <askevej37a@gmail.com>
Injection-Date: Sat, 29 Apr 2023 08:19:53 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Xref: retrobbs comp.sys.ibm.ps2.hardware:4172

PC Server 8640(1) 0N0, ONJ, 0P0, 0PT, 0Y0,
0YT, 1Y0, 1YT

(1) These systems must be upgraded with sets of two 11H0621 upgrades.

Limitations: Parity SIMMs cannot coexist with the 16MB 70ns ECC-on-SIMM
Memory Upgrade in the same system.

OK, coffee injection to War Power settings... rammed the throttle
through the seals....

The 4MB and 8MB EoS are marketed for the PS/2. the 16MB are not. Why?
Dunno. Only the Lacuna, 85X and 85K can handle 16MB FPM, and therefore,
the 16MB EoS.

Standard 4MB of RAM, expandable to 128MB

Reply offers 2MB, 4MB, 8MB, and 16MB memory module option kits. You must
install the modules in pairs (two modules for each bank). Modules in
different banks do not need to be of the same density, however, ECC and
Parity memory modules cannot be installed on the same Reply system
board. Memory modules are not required to be installed in any specific
bank order.

4MB on-board | 128MB = Maximum
Type 2, 4, 8, 16MB memory modules types are supported:
“Industry standard" x 36 parity, 72-pin SIMMs
“IBM Proprietary" x 36 parity, 72-pin SIMMs
“Industry standard" x 40 ECC, 72-pin SIMMs
(For maximum performance, 70nS recommended)

ECC looks odd, typo? PS/2 ECC x39. RS/6000 x40.

https://www.ardent-tool.com/Reply/Turbo_60_80_Manual.pdf

Physical page 39. Reply has two SIMM sockets next to each other as a
"Bank", while IBM had arrangements where [at least on the 95] "A" bank
and "B" bank are grouped together.

Whatever, Reply has "Bank 1", analogous to A1/B1, "Bank 2" analogous to
A2/B2, usw...

If you are wandting to try EoS, fill one bank with a matched pair of
EoS. EoS CANNOT be used in the same bank as FPM because you need two EoS
to generate the ECC.

Now as to the next question, I dunno. Can EoS banks and FPM banks exist
in the same system?

Try it, I will trumpet your success or commiserate with your failure...

lharr...@gmail.com wrote:
> On Friday, March 31, 2023 at 9:33:38 AM UTC-4, Louis Ohland wrote:
>> The quiet ones are the dangerous ones.
>>
>> Don't want to be TOO quiet...
>> James Hall wrote:
>>> I'm awake. Just being quiet.
> Any reason why 11H0621/11H0622 would hang in a Reply TurboProcessor 80? The system boots but eventually hangs.
>
. Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!csiph.com!.POSTED.071-087-128-099.res.spectrum.com!not-for-mail
From: Louis Ohland <ohland@charter.net>
Newsgroups: comp.sys.ibm.ps2.hardware
Subject: All that Schimmis is not gold.
Date: Thu, 20 Apr 2023 17:37:13 -0500
Organization: csiph.com Internet News Service
Message-ID: <u1seq0$24sd$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
References: <u1m9sb$bmf$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
<u1mck8$dpi$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
<u1mdo3$eit$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
<u1mdqs$eit$2@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
<u1mf2t$fhl$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
<u1mj21$ibq$2@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
<u1mnqs$lum$2@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
<u1n9qu$13lj$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
<ea6af368-5770-420c-afbc-4706658a4423n@googlegroups.com>
<u1pgeo$2pnu$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
<92d7cb5b-c3e2-4441-ac2d-df825c4b7618n@googlegroups.com>
<u1pluu$2trq$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
<u1q3io$8c7$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
<u1rhmv$1ekd$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
<16c57455-2354-4fdd-80c8-5541ad68b3fan@googlegroups.com>
<6398d445-7440-45b1-ac57-c99fb733eff9n@googlegroups.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Thu, 20 Apr 2023 22:36:49 -0000 (UTC)
Injection-Info: 842ffb22-07e1-11e5-a459-00266cf00584.csiph.com; posting-host="071-087-128-099.res.spectrum.com:71.87.128.99";
logging-data="70541"; mail-complaints-to="admin@kev009.com"
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:91.0) Gecko/20100101
Firefox/91.0 SeaMonkey/2.53.16
In-Reply-To: <6398d445-7440-45b1-ac57-c99fb733eff9n@googlegroups.com>
Xref: retrobbs comp.sys.ibm.ps2.hardware:4173

Sorry, we don't have a full busmaster local bus implementation to
compare to. The 56 SCS is a cost reduced implementation, at some point,
the CPU has to step in to emulate the missing functionality.

So trying to compare a true SCSI busmaster, that can perform all SCSI
control tasks without CPU involvement, to a cost reduced single SCSI
chip, is unwarranted.

So, IBM chose to have a reduced functionality SCSI Control Chip on the
CPU local bus, as long as the system isn't heavily multi-tasked, you
probably wouldn't notice the difference.

schimmi wrote:
> I'm a bit off here, sorry. The question I now have in mind is: is SCSI between CPU and MCA better than SCSI on MCA, nicely packed between all other MCA-devices, on one bus? I mean, local bus operations should impact MCA transactions and vice versa, probably affecting the overall performance Oo
>
> schimmi schrieb am Donnerstag, 20. April 2023 um 22:05:21 UTC+2:
>> Guess there was only one CPU made for this - the DX50. On my old 486/VLB setup I always had problems even with 40MHz/VLB using more than just the graphics adapter. On a 3-slot VLB Board you had one busmastering and accordingly 2 secondary slots you had to address using more than one card, especially with a SCSI/IO-Cards. With all three VLB slots filled, it was some kind of a gamble if the system was stable, even with 40MHz :-/ VLB was very card-dependant.
>> Tomas Slavotinek schrieb am Donnerstag, 20. April 2023 um 16:20:17 UTC+2:
>>> On 20.04.2023 3:13, Louis Ohland wrote:
>>>> The number of slots also decreases with increased speed. IIRC, you could
>>>> only use one slot at 50MHz.
>>>>
>>>> Tomas Slavotinek wrote:
>>>>> hence the limitation to 3 or less slots).
>>> That's correct. At 50 MHz you were lucky if it even worked in the
>>> single-slot configuration. The CPU bus was never designed for something
>>> like this...
. Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!csiph.com!.POSTED.071-087-128-099.res.spectrum.com!not-for-mail
From: Louis Ohland <ohland@charter.net>
Newsgroups: comp.sys.ibm.ps2.hardware
Subject: NCC-8570A crashes? Re: Scotty! We need LESS power NOW! [20MHz
8570-Axx?]
Date: Sun, 23 Apr 2023 07:34:27 -0500
Organization: csiph.com Internet News Service
Message-ID: <u238jj$1amq$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
References: <u237i4$19t8$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Sun, 23 Apr 2023 12:33:55 -0000 (UTC)
Injection-Info: 842ffb22-07e1-11e5-a459-00266cf00584.csiph.com; posting-host="071-087-128-099.res.spectrum.com:71.87.128.99";
logging-data="43738"; mail-complaints-to="admin@kev009.com"
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:91.0) Gecko/20100101
Firefox/91.0 SeaMonkey/2.53.16
In-Reply-To: <u237i4$19t8$1@842ffb22-07e1-11e5-a459-00266cf00584.csiph.com>
Xref: retrobbs comp.sys.ibm.ps2.hardware:4173

Caffeine injection system must be lagging.

85nS for 20MHz CPU
80nS for 25MHz CPU

8570A is hard coded to 2MB 80nS SIMMs.

MAJ Tom, will we damage the Dilithium crystals in the NCC-8570A by
down-clocking the 386 Power Platform to 20MHz? System is plodding around
at 20MHz, will it be able to use the faster memory successfully? If we
stoke up the boilers with 80nS, the BIOS will accept it, but will the
memory controller be able to give us warp power with a clock 20% slower?

Too fast to live, too young to die...

Louis Ohland wrote:
> https://www.ardent-tool.com/8570/Planar_T3-4.html
>
> In an odd shift, maybe the 8570-Axx can be throttled down to a 20.0000
> MHz osc on the 386 Power Platform, giving us a system somewhat
> comparable to the Model 90 T0.
>
> Ramming the caffeine throttle through the stops to full war power...
>
> 8590-T0 supports DBA-ESDI.
> 8570-Axx supports DBA-ESDI.
>
> 8590-T0 has a 386DX-20 w/64KB of screaming L2 cache..
> 8570-Axx has a 386DX-25 w/64KB of screaming L2 cache..
>
> 8590-T0 supports 4x 2MB 85nS FPM.
> 8570-Axx supports 4x 2MB 80nS FPM.
>
> Snippet from T0 complex BIOS
>
> https://www.ardent-tool.com/trouble/badmem.html
>
> The -X- in the error-code can be any number, -S- marks the position of
> the memory socket, -Y- determines the module type, size and access-speed
>
> 00021100 Configuration Mismatch
> 00021110 J11/J1 0 - Parity, 4MB???, 80nS
> 00021120 J11/J2
> 00021130 J11/J3
> 00021140 J11/J4
> 00021150 J14/J1
> 00021160 J14/J2
> 00021170 J14/J3
> 00021180 J14/J4
>
> Houston, we have a problem. Empirical evidence says 2MB works, and
> that's it.
>
.
Click here to read the complete article

> Here it is, I misplaced my copy...
Good stuff!!! has a C example of DMA transfer on MCA.

Whatever the server is, it has a red power switch and some sort of a
tape drive. Probably floppy, my SWAG is this box has MFM drives.

See the pile of tapes in the alcove in the desk?

Tomas Slavotinek wrote:
> https://youtu.be/zI0zfIiYKO0
>
> Wow, time capsule indeed! A couple of 25s and a 60 (or 80?) as a server...

Louis Ohland schrieb am Sonntag, 12. November 2023 um 04:59:21 UTC+1:
> Whatever the server is, it has a red power switch and some sort of a
> tape drive. Probably floppy, my SWAG is this box has MFM drives.
>
> See the pile of tapes in the alcove in the desk?
> Tomas Slavotinek wrote:
> > https://youtu.be/zI0zfIiYKO0
> >
> > Wow, time capsule indeed! A couple of 25s and a 60 (or 80?) as a server...
Looks a bit too expensive for a small business like this. PS/2 Workstations, a PS/2-Server an Novell Netware Oo
But interesting to see such a capsule, indeed, Tomas :)

On Saturday, November 11, 2023 at 10:59:21 PM UTC-5, Louis Ohland wrote:
> Whatever the server is, it has a red power switch and some sort of a
> tape drive. Probably floppy, my SWAG is this box has MFM drives.
>
> See the pile of tapes in the alcove in the desk?

Yes, QIC (Quarter Inch Cartridge) tapes, probably low density where you'd get 40-60MB on each tape depending on how much compression is involved in the backup. There were a number of 16-bit Microchannel QIC adapters on the market. I would have liked to see which model of Tek scope was on the floor.. I'm guessing that the 8525s only had the floppy drive to keep the system cost "reasonable".

Rick