DEC ApplicationDEC 400xP ApplicationDEC 400xP Service Guide

applicationDEC400xP ServiceGuide

Order Number: EK-PS200-SV. A01

This document provides the information a service technician needs to diagnose and repair the applicationDEC 400xP system. It also describes the features and capabilities of the system.

Digital Equipment Corporation Maynard, Massachusetts

First Printing, April 1992

The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document.

No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation or its afﬁliated companies.

of Digital Equipment Corporation. 1-2-3 is a registered trademark of Lotus Development Corporation. 3Com is a registered

trademark of 3Com Corporation. AT, IBM, OS/2, and PS/2 are registered trademarks of International Business Machines Corporation. Banyan is a registered trademark of Banyan Systems, Inc. Hercules is a registered trademark of Hercules Computer Technology. Intel and 80486 are trademarks of Intel Corporation. Microsoft and MS–DOS are registered trademarks, and Windows is a trademark of Microsoft Corporation. Novell and NetWare are registered trademarks of Novell, Inc. Open Desktop, ODT, and SCO are registered trademarks of The Santa Cruz Operation, Inc. in the USA and other countries. System V is a trademark of the American Telephone and Telegraph Company. SUN is a registered trademark of Sun Microsystems, Inc. UNIX is a registered trademark of UNIX System Laboratories, Inc.

FCC NOTICE: The equipment described in this manual generates, uses, and may emit radio frequency energy. The equipment has been type tested and found to comply with the limits for a Class A computing device pursuant to Subpart J of Part 15 of FCC Rules, which are designed to provide reasonable protection against such radio frequency interference when operated in a commercial environment. Operation of this equipment in a residential area may cause interference, in which case the user at his own expense may be required to take measures to correct the interference.

Dieses Gerät erfüllt in Verbindung mit den hierfür geprüften weiteren Geräten

• Bildschirmgeräte nach — DIN IEC 380/VDE 0806 oder EN 60950 — ZH1/618

• Datensichtgerät — System to be used with GS approved terminals

• Bildschirmtreiberkarte Digital Equipment Corporation

die Anforderungen an Bildschirmarbeitsplätze im Bürobereich.

MA-0347-90-CPG.DG

Contents

Preface ..................................................... xi

1 System Overview

1.1 Features . ........................................... 1–1

1.2 System Cabinet . . . ................................... 1–2

1.2.1 Rear Connectors ................................... 1–4

1.2.2 Internal Layout ................................... 1–6

1.3 System Logic ........................................ 1–8

1.3.1 System Board . . ................................... 1–8

1.3.1.1 Option Module Slots. . ........................... 1–9

1.3.1.2 System Board Jumpers .......................... 1–9

1.3.1.3 Real-Time Clock Chip ........................... 1–9

1.3.2 CPU Module . . . ................................... 1–9

1.3.3 Memory Expansion Module .......................... 1–12

1.4 Power Supply ........................................ 1–12

1.5 Disk Storage and Media Options ......................... 1–12

1.6 Keyboard ........................................... 1–13

1.7 Mouse . . ........................................... 1–13

2 System Troubleshooting

2.1 Introduction ......................................... 2–1

2.2 Diagnostic Tools . . . ................................... 2–1

2.3 Power-On Self-Test. ................................... 2–2

2.3.1 System Board Hardware Tests ........................ 2–2

2.3.2 Peripheral Hardware Tests .......................... 2–3

2.3.3 POST Sequence ................................... 2–3

2.3.4 POST and Boot Messages ........................... 2–5

2.3.5 Beep Codes ....................................... 2–16

2.4 Setup Utility ........................................ 2–18

2.5 Run-Time Error Messages . . . ........................... 2–19

2.6 Troubleshooting . . . ................................... 2–19

iii

3 System Exerciser

3.1 Overview ........................................... 3–1

3.2 Loading the System Exerciser ........................... 3–2

3.3 Running the System Exerciser ........................... 3–3

3.4 Loading Failure . . . ................................... 3–6

3.5 Error Reports ........................................ 3–6

3.6 Test Descriptions . . ................................... 3–8

3.7 Modes. . . ........................................... 3–8

3.8 Flags . . . ........................................... 3–9

3.9 Commands .......................................... 3–10

3.9.1 Block ........................................... 3–11

3.9.2 Cache ........................................... 3–12

3.9.3 Calculate ........................................ 3–12

3.9.4 Conﬁguration . . ................................... 3–14

3.9.5 Ctrl/C ........................................... 3–14

3.9.6 Devices .......................................... 3–14

3.9.7 Display .......................................... 3–16

3.9.8 Examine ......................................... 3–18

3.9.9 Flags ........................................... 3–18

3.9.10 Go ............................................. 3–19

3.9.11 Help . ........................................... 3–19

3.9.12 Istep . ........................................... 3–19

3.9.13 Installation Veriﬁcation Procedure (IVP) ................ 3–19

3.9.14 Log............................................. 3–20

3.9.15 Quit . ........................................... 3–22

3.9.16 Run ............................................ 3–22

3.9.17 Set............................................. 3–22

3.9.18 Show ........................................... 3–24

3.9.19 Status .......................................... 3–24

3.9.20 Time............................................ 3–25

3.9.21 Unblock ......................................... 3–25

4 FRU Removal and Replacement

4.1 FRU Parts List . . . ................................... 4–1

4.2 Required Tools ....................................... 4–3

4.3 Moving the System ................................... 4–3

4.4 Before You Begin . . ................................... 4–4

4.5 Opening the System Cabinet . ........................... 4–5

4.5.1 Removing the Top Cover and Side Panels ............... 4–5

4.5.2 Removing the Card Cage Cover ....................... 4–5

4.5.3 Removing the Bezels ............................... 4–7

4.6 Replacing the CPU Module . . ........................... 4–9

4.7 Replacing the Cache Card . . . ........................... 4–12

4.8 Replacing a SIMM . ................................... 4–14

4.9 Replacing the Memory Expansion Module .................. 4–18

4.10 Replacing Option Modules . . . ........................... 4–20

4.11 Replacing the System Board . ........................... 4–22

4.12 Replacing the Real-Time Clock Chip . . . ................... 4–26

4.13 Replacing the RX23 3.5-Inch Diskette Drive ................ 4–28

4.14 Replacing an Option Drive . . . ........................... 4–31

4.14.1 Option Drive Installation Data ....................... 4–32

4.15 Replacing the Speaker ................................. 4–49

4.16 Replacing the Front Panel Wire Assembly .................. 4–51

4.17 Replacing a Fan . . . ................................... 4–53

4.18 Replacing the Power Supply . ........................... 4–55

4.19 Replacing the DC Switch ............................... 4–58

5 System Conﬁguration

5.1 EISA Architecture . ................................... 5–1

5.2 System Conﬁguration Utility . ........................... 5–1

5.2.1 Diskettes Provided ................................. 5–2

5.2.2 When to Use the SCU . . . ........................... 5–3

5.2.3 Booting the SCU .................................. 5–3

5.2.4 HowtoUsetheSCU ............................... 5–6

5.2.5 SCI Files and CFG Files . ........................... 5–6

5.3 Conﬁguring the Computer System........................ 5–7

5.3.1 Access Password Utility . . ........................... 5–9

5.3.2 Conﬁgure Computer ................................ 5–10

5.3.3 Important EISA Conﬁguration Information .............. 5–10

5.3.4 Adding or Removing Boards.......................... 5–10

5.3.5 View or Edit Details ................................ 5–11

5.3.5.1 System Board Extended Memory ................... 5–16

5.3.5.2 System Base Memory . ........................... 5–16

5.3.5.3 Shadow Off-Board Video BIOS . . ................... 5–16

5.3.5.4 User Deﬁnable Hard Disk Drive ................... 5–16

5.3.5.5 Hard Drive 1 .................................. 5–17

5.3.5.6 Hard Drive 2 .................................. 5–17

5.3.5.7 Parallel Port and Serial Ports . . ................... 5–17

5.3.5.8 CPU Speed . ................................... 5–17

5.3.6 Examine Required Switches .......................... 5–17

5.3.7 Save and Exit. . ................................... 5–18

5.4 Conﬁguring the System with the SCU for ISA Modules........ 5–18

5.4.1 Adding an ISA CFG File . ........................... 5–18

5.5 Conﬁguring the System with EISA Option Modules .......... 5–20

5.6 Automatic Conﬁguration ............................... 5–20

5.7 Viewing Total System Conﬁguration . . . ................... 5–21

5.8 Library Diskette. . . ................................... 5–22

5.9 Advanced System Conﬁguration Utility Feature . . . .......... 5–22

5.9.1 Installing More than One Terminal Multiplexer .......... 5–23

A System Speciﬁcations

A.1 Introduction ......................................... A–1

A.2 System Speciﬁcations .................................. A–1

A.3 Power Supply and Input Power Requirements ............... A–3

A.4 Expansion Slot Current Limitations . . . ................... A–3

A.5 System Component Current Requirements ................. A–4

B System Board Jumpers

B.1 Introduction ......................................... B–1

B.2 Jumper Settings. . . ................................... B–1

C Interface Connectors

C.1 Introduction ......................................... C–1

C.2 External System Connectors . ........................... C–1

C.2.1 Parallel Printer Connector ........................... C–1

C.2.2 Serial Port Connectors . . . ........................... C–2

C.2.3 Keyboard and Mouse Connectors . . . ................... C–3

D Device Mapping

E ISA Option Conﬁguration Files

Index

Figures

1–1 System Cabinet, Front View ......................... 1–3

1–2 System Cabinet, Rear View .......................... 1–5

1–3 System Cabinet, Internal View ....................... 1–7

1–4 System Board . . ................................... 1–11

4–1 System Cover and Side Panel Removal ................. 4–6

4–2 Bezel Removal . ................................... 4–8

4–3 CPU Module Removal . . . ........................... 4–10

4–4 CPU Module Layout ................................ 4–11

4–5 Cache Card Removal ............................... 4–13

4–6 SIMM Removal ................................... 4–15

4–7 SIMM Slots on the System Board . . ................... 4–16

4–8 SIMM Slots on the Memory Module . ................... 4–17

4–9 Memory Expansion Module Removal ................... 4–19

4–10 Option Module Removal . . ........................... 4–21

4–11 System Board Removal . . ........................... 4–24

4–12 RX23 3.5-Inch Diskette Drive Removal (Part 1 of 2) ....... 4–29

4–13 RX23 3.5-Inch Diskette Drive Removal (Part 2 of 2) ....... 4–30

4–14 Option Drive Removal . . . ........................... 4–32

4–15 ID Jumper Code ................................... 4–34

4–16 TZK10-AA ID Jumper Locations . . . ................... 4–35

4–17 RZ24-S Jumper Locations ........................... 4–36

4–18 RZ25-S Jumper Locations ........................... 4–38

4–19 RZ56-E/RZ57-E ID Jumper Locations .................. 4–40

4–20 RZ57-E ID and Conﬁguration Jumpers Location .......... 4–41

4–21 RZ35-E Jumper Locations ........................... 4–42

4–22 RZ58-E Jumper Locations ........................... 4–44

4–23 105 MB IDE Drive Jumper Locations .................. 4–46

4–24 RX33-AS Jumper Locations .......................... 4–48

4–25 Speaker Removal .................................. 4–50

4–26 Front Panel Wire Assembly Removal ................... 4–52

4–27 Fan Removal . . ................................... 4–54

4–28 Power Supply Cable Removal......................... 4–56

4–29 Power Supply Removal . . ........................... 4–57

4–30 DC Switch Removal ................................ 4–59

5–1 SCU Main Menu Options (Part 1 of 2) .................. 5–4

vii

5–2 SCU Main Menu Options (Part 2 of 2) .................. 5–5

B–1 Location of System Board Jumpers . ................... B–2

Tables

1 applicationDEC 400xP Documentation Set .............. xii

1–1 Key for Figure 1–1 ................................. 1–2

1–2 Key for Figure 1–2 ................................. 1–4

1–3 Key for Figure 1–3 ................................. 1–6

1–4 Key for Figure 1–4 ................................. 1–10

2–1 Diagnostic Tools ................................... 2–1

2–2 POST and Boot Messages ........................... 2–5

2–3 Beep Codes for Fatal Errors .......................... 2–16

2–4 Beep Codes for Nonfatal Errors ....................... 2–18

2–5 Run-Time Error Messages ........................... 2–19

2–6 System Troubleshooting . . ........................... 2–20

2–7 Disk Drive Troubleshooting .......................... 2–23

2–8 Monitor Troubleshooting . ........................... 2–24

3–1 System Exerciser Tests . . ........................... 3–8

3–2 System Exerciser Modes . ........................... 3–8

3–3 System Exerciser Flags . . ........................... 3–9

3–4 System Exerciser Commands ......................... 3–10

3–5 Block Command Options . ........................... 3–11

3–6 Calculate Command Qualiﬁers ....................... 3–13

3–7 Calculate Command Radix Symbols. ................... 3–13

3–8 Devices Command Formats .......................... 3–15

3–9 Devices Command State Flags ........................ 3–16

3–10 Display Command Qualiﬁers ......................... 3–17

3–11 Examine Command Qualiﬁers ........................ 3–18

3–12 Log Command Options . . . ........................... 3–20

3–13 System Exerciser Error Log Report, Example . . .......... 3–20

3–14 Set Command State Variables ........................ 3–23

3–15 Show Command Machine States . . . ................... 3–24

3–16 Status Command Options ........................... 3–25

3–17 Unblock Command Options .......................... 3–25

4–1 Field Replaceable Units . . ........................... 4–1

4–2 Key for Figure 4–1 ................................. 4–7

viii

4–3 Key for Figure 4–2 ................................. 4–8

4–4 Key for Figure 4–3 ................................. 4–10

4–5 Key for Figure 4–4 ................................. 4–11

4–6 Cache Size Jumper................................. 4–12

4–7 Key for Figure 4–5 ................................. 4–13

4–8 Key for Figure 4–7 ................................. 4–16

4–9 Key for Figure 4–8 ................................. 4–17

4–10 Memory Expansion Module Jumpers ................... 4–18

4–11 Key for Figure 4–9 ................................. 4–19

4–12 Key for Figure 4–10 ................................ 4–21

4–13 Key for Figure 4–11 ................................ 4–25

4–14 Key for Figure 4–12 ................................ 4–29

4–15 Key for Figure 4–13 ................................ 4–31

4–16 Key for Figure 4–14 ................................ 4–32

4–17 Bay Option Installation Data ......................... 4–33

4–18 Key for Figure 4–16 ................................ 4–35

4–19 Key for Figure 4–17 ................................ 4–37

4–20 Key for Figure 4–18 ................................ 4–39

4–21 Key for Figure 4–19 ................................ 4–40

4–22 Key for Figure 4–20 ................................ 4–41

4–23 Key for Figure 4–21 ................................ 4–43

4–24 Key for Figure 4–22 ................................ 4–45

4–25 Key for Figure 4–23 ................................ 4–47

4–26 Key for Figure 4–24 ................................ 4–49

4–27 Key for Figure 4–25 ................................ 4–51

4–28 Key for Figure 4–26 ................................ 4–53

4–29 Key for Figure 4–27 ................................ 4–55

4–30 Key for Figure 4–28 ................................ 4–56

4–31 Key for Figure 4–29 ................................ 4–57

4–32 Key for Figure 4–30 ................................ 4–59

5–1 SCU Keyboard Function Keys ........................ 5–6

5–2 System Board Setup Options ......................... 5–11

5–3 ISA CFG Files for applicationDEC 400xP ISA Modules . . . . . 5–19

A–1 System Dimensions ................................ A–1

A–2 Environmental Speciﬁcations ......................... A–2

A–3 Acoustics — Declared Values per ISO 9296 and ISO 7779 . . . A–2

A–4 Schallemissionswerte — Vorläuﬁge Werteangaben nach ISO

9296 und ISO 7779/DIN45635-19. . . ................... A–2

A–5 System Power Requirements ......................... A–3

A–6 Computer Component Current and Power Requirements . . . A–4

B–1 System Board Jumper Settings ....................... B–3

C–1 Parallel Printer Connector Pinout . . ................... C–2

C–2 Serial Port Connector Pinout ......................... C–3

C–3 Keyboard and Mouse Connector Pinouts ................ C–3

D–1 Memory Map, Without Options ....................... D–1

D–2 Memory Map, Typical Conﬁguration ................... D–2

D–3 I/O Address Map .................................. D–2

D–4 Interrupt Map . ................................... D–4

D–5 DMAMap ....................................... D–5

E–1 ISA Option Conﬁguration Files ....................... E–1

Intended Audience

This manual is intended for service technicians trained by Digital Equipment Corporation.

Purpose

This manual is designed to help service technicians diagnose and repair the applicationDEC 400xP system. It contains service information for the base system and for options supplied by Digital Equipment Corporation. For information on conﬁguration and installation of options supplied by Digital, refer to the applicationDEC 400xP User Guide.

applicationDEC 400xP Documentation Set

This manual is part of a documentation set shipped with each applicationDEC 400xP system. The manuals in this set are listed in Table 1.

Preface

Table 1 applicationDEC 400xP Documentation Set

Manual Part Number

System Installation Guide Minimum Requirements for Operating Systems Electrostatic Discharge Notice Product Information Request Software Support Notice User Guide EK-PS200-CG SCO UNIX Boot Process Notice

Part of the applicationDEC 400xP Installation Package (EK-PS200-IP)

Conventions

The following conventions are used in this manual:

EK-PS200-IG EK-PS200-AD EK-PS200-ED EK-PS200-CC EK-PS100-SW

EK-PS200-SB

Enter

A key name, such as Enter, is shown enclosed to indicate that you press a key on the keyboard.

Ctrl/X

A two key sequence, such as Ctrl/X, is shown enclosed to indicate that you must hold down the key labeled Ctrl while you simultaneously press another key.

Ctrl/Alt/Delete

A multiple key sequence, such as Ctrl/Alt/Delete, is shown enclosed to indicate that you must hold down the keys labeled Ctrl and Alt

while you simultaneously press another key. boldface text Boldface text is used to represent the name of a command. italic text Italic text is used to indicate SCO UNIX System V ﬁle names.

Notes, Cautions, and Warnings are used throughout this manual to emphasize speciﬁc kinds of information:

Warning

A Warning indicates the presence of a hazard that can cause personal injury.

xii

Caution

A Caution indicates the presence of a hazard that might damage the hardware or currupt the software.

Note

A Note indicates important or explanatory information.

xiii

The applicationDEC 400xP system is a versatile, industry standard computer system suitable for use in any of the following conﬁgurations:

• Multiuser timesharing conﬁgurations running SCO UNIX System V

• Network ﬁle server for Digital PATHWORKS, Novell NetWare, or Banyan

Vines network operating systems

• Single user workstation environments running MS–DOS or Open Desktop

1.1 Features

The applicationDEC 400xP system features include:

• Intel 80486 CPU speeds of 25, 33, or 50 MHz

• Up to 256 KB of cache memory

• Up to 192 MB of system memory

• Support for 2, 4, 8, and 16 MB single in-line memory modules (SIMMs)

System Overview

• Support for IDE and SCSI hard disks

• Up to 4.8 GB of internal SCSI disk storage

• Up to 14 GB of additional external disk storage

• Universal 350 W power supply

• 1.44 MB 3.5-inch diskette drive standard

• Seven half-height storage bays, convertible to three full-height and one

half-height bay

System Overview 1–1

The applicationDEC 400xP system supports:

• SCO UNIX System V

• Open Desktop

• All industry standard SCO UNIX System V applications

• MS–DOS

• Banyan Vines

• Novell NetWare

1.2 System Cabinet

The system cabinet front panel is shown in Figure 1–1. Refer to the ﬁgure key in Table 1–1.

Table 1–1 Key for Figure 1–1

Key Description

A Disk activity LED — indicates activity on the IDE and SCSI bus B Keyboard lock — disables system keyboard and mouse C Reset button — resets the system by emulating a power-off/power-on

D 1.44 MB, 3.5-inch diskette drive E 1.2 MB, 5.25-inch diskette drive (optional) F 525 MB QIC tape drive (optional) G Blank panel H Power indicator — indicates power is applied to the system I Power switch (Standby/On) — applies power to the system J Support feet K Cabinet rear wheels L Diskette eject button

sequence and causes POST to run

1–2 System Overview

Figure 1–1 System Cabinet, Front View

MR-0038-92DG

System Overview 1–3

1.2.1 Rear Connectors

The system cabinet rear panel connectors are shown in Figure 1–2. Refer to the ﬁgure key in Table 1–2. For more information about the rear panel connectors, refer to Appendix C.

Table 1–2 Key for Figure 1–2

Key Description

A Cabinet keylock B Mouse connector — connects mouse used with VGA analog monitor C Keyboard connector — connects keyboard used with VGA analog

D Serial port 1 — RS-232 port for serial printers, UPS control, conﬁgured

E Serial port 2 — RS-232 port for serial printers, UPS control, conﬁgured

F Parallel port — parallel printer port, conﬁgured as LPT1 G VGA monitor connector — connects VGA analog monitor H Option module external connector slots (8) I Auxiliary ac output — unswitched IEC-320 connector J AC input

monitor

as COM1

as COM2

1–4 System Overview

Figure 1–2 System Cabinet, Rear View

1 E

MR-0039-92DG

System Overview 1–5

1.2.2 Internal Layout

Figure 1–3 shows the internal layout of the system when the cabinet is opened. Refer to the ﬁgure key in Table 1–3.

Table 1–3 Key for Figure 1–3

Key Description

A SCSI bus cable B Power cables C Front drive bays D SCSI terminator E Rear drive bays F Diskette drive cable G System board H CPU module I On-board memory SIMMs J Memory expansion module K Power supply L I/O connectors M SCSI host adapter N EISA option module slots (8)

1–6 System Overview

Figure 1–3 System Cabinet, Internal View

MR-0565-91DG

System Overview 1–7

1.3 System Logic

The applicationDEC 400xP system consists of three logic modules (see Figure 1–3):

• System board

• CPU module with optional plug-in cache (25 MHz and 33 MHz CPU) or

attached cache (50 MHz CPU)

• Optional memory expansion module

1.3.1 System Board

The system board, shown in Figure 1–4, contains the following features:

• Slot for CPU module

• Slot for memory expansion module

• 8 EISA slots (6 bus master slots, 2 slave slots)

• On-board VGA with 512K RAM (optional upgrade to 1 MB RAM) and 1024

x 768 resolution

• 4 SIMM sockets (accepts 2, 4, 8, and 16 MB SIMMs for maximum of 64

MB)

• Diskette drive control

• IDE drive control

• 2 9-pin serial ports

• 1 25-pin parallel port

• Keyboard and mouse connections

• VGA monitor connection Refer to the ﬁgure key in Table 1–4.

1–8 System Overview

1.3.1.1 Option Module Slots

Eight extended industry standard architecture (EISA) option slots are available on the system board. The slots are industry standard architecture (ISA) compatible, so both EISA and ISA option modules can be installed.

Six of the EISA slots are EISA master slots. EISA master modules must be installed in EISA master slots. EISA master modules are devices which assume control of the bus for activities such as direct memory access (DMA). ISA modules and EISA slave modules may be installed in any slot.

When you replace the system board, always install the modules in the same slots from which they were removed.

1.3.1.2 System Board Jumpers

System board jumpers allow you to set certain system options. For more information, refer to Appendix B.

1.3.1.3 Real-Time Clock Chip

The real-time clock chip, which contains a lithium battery, provides power for nonvolatile memory when power is removed from the system.

1.3.2 CPU Module

The CPU and all associated speed-dependent components are isolated on a separate CPU module. Upgrading a system is as easy as removing the current CPU module and replacing it with a faster CPU module. The system can be conﬁgured for use with the following Intel 80486 CPU modules.

Note

• 25 MHz Intel 486SX

• 33 MHz Intel 486DX

• 50 MHz Intel 486DX The 25 MHz and 33 MHz CPU modules contain a socket for installation of an

optional 64 or 128 KB cache card. The 50 MHz CPU module comes standard with 256 KB cache installed.

System Overview 1–9

Table 1–4 Key for Figure 1–4

Key Description

A Memory bank 0 B Memory bank 1 C Install ﬁrst SIMM here D Pin 1 of SIMM socket E CPU module slot F Memory module slot G System setup jumpers H SCSI/IDE disk drive activity LED cable connectors J VGA setup jumpers K IDE cable connector L VGA 512K memory upgrade sockets M Power connector (cable from power supply is factory installed) N Diskette cable connector (cable is factory installed) O Real-time clock P Western Digital WD90C30 VGA chip Q EISA slave slots R EISA master slots S Front panel connector (cable is factory installed)

Table B–1 lists the system board jumpers and factory default settings.

On some system boards, J0190 and/or J0491 may not be populated.

1–10 System Overview

Figure 1–4 System Board

MR-0033-92DG

B A

H O

System Overview 1–11

1.3.3 Memory Expansion Module

The memory expansion module:

• Allows for increased memory beyond the 64 MB of memory that can be

installed on the system board

• Is installed in a slot on the system board

• Contains 8 SIMM slots

• Accepts 2, 4, 8, and 16 MB SIMMs If 16 MB SIMMs are installed on the memory expansion module, an additional

128 MB of memory is provided. Combined with the maximum possible 64 MB available on the system board, 192 MB of memory is available.

All of the memory logic is designed for future support of 32 MB SIMMs. When 32 MB SIMMs are available, the total possible memory will be 384 MB.

1.4 Power Supply

In the lower area of the cabinet is the system power supply. The supply provides 350 W to the system cabinet and autosenses input power. This means the cabinet can be connected to 110/120 V or 220/240 V, 50 or 60 Hz, without making any mechanical settings.

1.5 Disk Storage and Media Options

The system board supports IDE drives directly. An IDE drive connector on the board allows connection of up to two 105 MB half-height IDE drives.

By installing a SCSI adapter in an EISA expansion slot, greater expansion is possible. A SCSI bus can have up to seven SCSI devices. The system enclosure has seven half-height expansion bays. These are convertible to full-height bays. Any combination of full- and half-height bays is possible. For maximum storage, three 1.3 GB full-height SCSI drives and one 852 MB half-height drive can be installed for a total of 4.8 GB inside the enclosure.

Three of the seven half-height storage bays are accessible. These bays are directly below the standard 3.5-inch 1.44 MB diskette drive in the front of the enclosure. These bays can be used for the installation of SCSI half-height or full-height tape drives, if desired.

1–12 System Overview

1.6 Keyboard

There are no service procedures for the keyboard other than replacement.

1.7 Mouse

Service procedures for the mouse are limited to cleaning the mouse ball and tracking mechanism. Refer to the documentation supplied with the mouse.

System Overview 1–13

2.1 Introduction

This chapter describes troubleshooting of the applicationDEC 400xP system. It contains the following sections:

• Diagnostic tools

• Power-on self-test

• Setup utility

• Run-time error messages

• Troubleshooting

2.2 Diagnostic Tools

Table 2–1 lists the diagnostic tools required to service the applicationDEC 400xP system.

Table 2–1 Diagnostic Tools

Tool Part Number Description

System Troubleshooting

System Conﬁguration Utility Diskette (APPLICATIONDEC 400 XP SYS 2.0)

Library Diskette (LIBRARY DISK OF ISA CFG FILES)

applicationDEC System Exerciser diagnostics diskette (APPLICATIONDEC SYSX 4.0)

Loopback, 9-pin serial port FD-10164-00 External loopback test

AK-PNHPA-CA This utility is used to

reconﬁgure the system when options are installed.

AK-PLADB-CA Library of ISA conﬁguration

ﬁles used to reconﬁgure the system when ISA options are installed.

AK-PGF7D-CA Standalone system diagnostic

diskette. (See Chapter 3).

connector.

System Troubleshooting 2–1

2.3 Power-On Self-Test

Before the applicationDEC 400xP system can be used, all components must be initialized and tested, and the operating system must be loaded into memory. The BIOS that is stored in ROM controls this sequence of actions. A portion of the BIOS contains a power-on self-test (POST). POST is responsible for initializing and testing system components each time power is applied or when the system boots. The remainder of the BIOS loads the operating system and speciﬁc applications.

Each time you turn on the system, POST displays a numeric countdown (880 to 000) sequence as it tests the system board, Intel 486, system board timers and logic devices, keyboard, memory, and so on. POST countdown numbers 800 through 520 are not displayed on the monitor, but are represented as beep codes (see Section 2.3.5).

The power-on self-tests are divided into two types of tests: system board hardware and peripheral hardware. The following sections describe these tests as well as the POST sequence and POST messages.

2.3.1 System Board Hardware Tests

Post checks the system board hardware ﬁrst. If any of these tests fails, a fatal error condition exists and further testing and initialization is not possible. You are notiﬁed that an error condition exists by an error message displayed on the monitor or by beeps from the system speaker. Refer to Section 2.3.4 for descriptions of the POST messages and Section 2.3.5 for more on the beep codes. The following list of the system hardware tests shows the order of execution:

CPU ROM BIOS (checksum) Programmable interrupt timer (PIT) Base 64 KB DRAM CMOS RAM EISA devices DMA controller Programmable interrupt controller (PIC) Video controller Keyboard controller Real-time clock

2–2 System Troubleshooting

2.3.2 Peripheral Hardware Tests

The ﬁrst peripheral hardware test procedure veriﬁes that the system conﬁguration data stored in CMOS RAM matches the hardware present. Then, the procedures continue to test and initialize other peripheral hardware. This testing includes memory on the system board and, if one is installed, the memory module. A test failure generally results in an error message on the monitor screen. The following list of the peripheral hardware tests shows the order of execution:

ISA CMOS RAM and EISA nonvolatile (FLASH) memory conﬁguration data Serial/parallel interface circuitry Video Keyboard RAM memory above 64 KB Coprocessor Diskette drive controller Hard disk controller Option ROMs, such as SCSI and LAN Intel 486 CPU internal cache memory

2.3.3 POST Sequence

While POST is running, a numeric countdown (800 to 000) is displayed on the monitor.

Note

During the POST memory test, the amount of memory being tested is displayed on the screen. Depending on the amount of extended memory installed, the POST memory test can take several minutes to complete. POST does not check memory after a soft boot.

The POST message displayed may take one of two forms, depending on whether POST detected any conﬁguration errors. Examples follow.

System Troubleshooting 2–3

If POST does not detect any conﬁguration errors, the system beeps once and displays a message similar to the following:

PhoenixBIOS (TM) E486 Version

x.xx.xx.xxx

640K Base Memory 03072K Extended 000

To continue press:.................................SPACEBAR

To configure system press:...............................F1

Note

After the above message appears, you have approximately 10 seconds to press the appropriate function key to display the initial setup screen. If you do not press the appropriate function key within the speciﬁed time, and if POST failed to detect any conﬁguration errors, the system will continue with the boot sequence.

If conﬁguration errors are found, the system beeps more than once and displays a message similar to the following:

PhoenixBIOS (TM) E486 Version

x.xx.xx.xxx

640K Base Memory 03072K Extended 150: Invalid configuration information

To continue press:......................................Esc

To configure system press:...............................F1

It is normal for the above message to appear the ﬁrst time you start the system. Run the system conﬁguration utility (SCU) to create a valid system conﬁguration. If any other error messages appear on the screen, refer to Section 2.3.4 for decriptions and solutions.

2–4 System Troubleshooting

2.3.4 POST and Boot Messages

POST displays messages to alert you to errors in hardware, software, and ﬁrmware. It also displays information about your system.

During POST, the system board speaker beeps to alert you to speciﬁc POST steps. Two beeps signal the start of the time during which you can enter setup. Another beep signals the end of that time, and then a subsequent beep signals that a system boot has begun.

If an error occurs during POST, the countdown is stopped. If an error occurs before the monitor is initialized, speciﬁc beep codes sound to alert you to a problem. If an error occurs after the monitor is initialized, both the POST number and the error message are displayed on the monitor.

Table 2–2 lists POST and boot messages by number.

Table 2–2 POST and Boot Messages

POST No. Error Name Description Solution

880 POST starts 860 Set processor speed for

POST 850 Chipset initialization 2 840 Chipset initialization 3 830 CPU register test 820 8742 initialization 810 Real-time clock RAM

and register test 800 System BIOS checksum

test 790 Initialize programmable

interval timer 780 DMA channel test DMA channel failure Replace the system

770 DMA page register test DMA page register

760 Verify RAM refresh test RAM refresh failure Replace the system

Real-time clock RAM and register test failure

System BIOS checksum failure

Programmable interval timer failure

failure

Replace the realtime clock chip.

Replace the system board.

board. Replace the system

board.

(continued on next page)

System Troubleshooting 2–5

Table 2–2 (Cont.) POST and Boot Messages

POST No. Error Name Description Solution

759 First 64 KB RAM parity

test failure

758 First 64 KB RAM

address line failure

757 First 64 KB RAM

odd/even logic failure

756 First 64 KB RAM chip

or data line failure, multibit

755–740 First 64 KB RAM chip

or data line failure, bit 0–15

730 Initialize stack 710 Initialize keyboard

buffer 700 Chipset initialization 4 Shadow of on-board

BIOS failed

692 Extended CMOS

checksum failure

691 CMOS checksum failure See 690.

Memory has failed. Run SYSEX. Replace any failed SIMM.

See 690.

(continued on next page)

2–6 System Troubleshooting

Table 2–2 (Cont.) POST and Boot Messages

POST No. Error Name Description Solution

690 CMOS checksum test CMOS power failure The conﬁguration

680 Initialize EISA slots 670 Initialize serial ports 660 Initialize parallel ports 655 DMA register test

(slave) 650 DMA register test

(master) 645 Programmable interrupt

controller register test

(master) 640 Programmable interrupt

controller register test

(slave) 620 Initialize interrupt

vector table 610 Enable timer tick

interrupt 600 Initialize keyboard

controller 590 Check video conﬁgura-

tion 580 Search for video ROM 570 Initialize video

controller 560 Using alternate video

controller

DMA register failure (slave)

DMA register failure (master)

Programmable interrupt controller register failure (master)

Programmable interrupt controller register failure (slave)

Keyboard controller failure

Primary display adapter failed, using alternate

information stored in CMOS does not agree with your hardware conﬁguration. Run the SCU to verify conﬁguration. Reboot system.

Replace the system board.

(continued on next page)

System Troubleshooting 2–7

Table 2–2 (Cont.) POST and Boot Messages

POST No. Error Name Description Solution

540 Scan and initialize video

530 Verify video conﬁgura-

520 Initialize console

500 Display sign on message 490 Timer tick interrupt test No timer tick interrupt Replace the system

480 Shutdown test Shutdown failure Replace the system

461 Software port NMI

460 EISA extended devices

450 Chipset initialization 6 441 Unexpected interrupt in

440 Size memory above 64

ROM

tion

redirection

test

board.

failure Fail safe timer NMI

failure

protected mode

Gate A20 failure The computer

Replace the system board.

The computer received an interrupt while in protected mode (probably while testing memory). If the problem persists, replace the system board.

cannot switch into protected mode. Replace the system board.

(continued on next page)

2–8 System Troubleshooting

Table 2–2 (Cont.) POST and Boot Messages

POST No. Error Name Description Solution

430 Interval timer 2 test Timer 2 failure The integrated

390 Initialize keyboard ﬂags 374 Keyboard failure Replace keyboard. 373 Keyboard stuck key

failure

372 Keyboard data line

failure

371 Keyboard clock line

failure

370 Test keyboard Keyboard controller

failure

350 Reinitialize keyboard

controller 330 Initialize auxiliary

device

system peripheral (ISP) chip on the system board might have failed. If the problem persists, replace the system board.

One or more of the keys was pressed. Release the key or keys and try again. If the problem persists, replace the keyboard.

See 371.

The keyboard or the keyboard cable connection has failed. Check the keyboard connection. If the connection is good, the keyboard might have failed. Try another keyboard. If the problem persists, replace the system board.

Replace the system board.

(continued on next page)

System Troubleshooting 2–9

Table 2–2 (Cont.) POST and Boot Messages

POST No. Error Name Description Solution

310 Initialize keyboard

controller output port 300 Initialize gate A20 297 Decreasing available

memory

296 Memory write/read

failure at XXXX–YYYY, read QQQQ expecting ZZZZ

295 Memory address line

failure at XXXX–YYYY, read QQQQ expecting ZZZZ

294 Memory high address

failure at XXXX–0000 to XXXX–FFFF

293 Memory double word

logic failure at XXXX– 0000 to XXXX–FFFF

292 Memory odd/even logic

failure at XXXX–0000 to XXXX–FFFF

This message immediately follows any memory error message informing you that memory modules are failing. Check that all SIMMs are installed correctly.

See 292.

One of the SIMMs or associated circuitry has failed. Run SYSEX to check for failed SIMM and replace if necessary. If the message repeats, replace the system board or memory expansion module, if applicable.

(continued on next page)

2–10 System Troubleshooting

Table 2–2 (Cont.) POST and Boot Messages

POST No. Error Name Description Solution

291 Memory data line

290 Test memory above 64

270 Initialize extended BIOS

data area 250 Chipset initialization 7 230 Enable hardware

interrupts 210 Read keyboard ID 190 Real-time clock test Real-time clock failure The internal

160 Coprocessor test Coprocessor failed The coprocessor

150 Check for invalid

conﬁguration 140 Chipset initialization 8 132 Diskette drive 1 failure See 131.

failure at XXXX–0000 to XXXX–FFFF

Memory parity failure at XXXX–0000 to XXXX– FFFF

See 290.

battery for the clock is probably dead. Replace the real-time clock. If the problem persists, replace the system board.

failed or is missing. Run the SCU.

(continued on next page)

System Troubleshooting 2–11

Table 2–2 (Cont.) POST and Boot Messages

POST No. Error Name Description Solution

131 Diskette drive 0 failure Drive 0 has either

130 Initialize diskette

subsystem

122 Hard drive 0 failure See 120 and 121. 121 Hard drive controller

120 Initialize hard drive

subsystem

110 Chipset initialization 9 101 Shadow of off-board

Diskette drive failure Drive has either

failure

Hard drive conﬁguration error

video BIOS aborted, no video ROM found

failed or is missing. Verify the settings for drive 0 using the BIOS Setup Utility. Make sure drive 0 is present and the diskette is inserted properly. If it is, drive 0 might have failed.

failed or is missing. Verify the drive settings using the BIOS Setup Utility. Make sure drive is present and the diskette is inserted properly. If they are, drive might have failed.

See 120. Check both ends of the controller’s cables. Replace hard drive controller.

Check the system conﬁguration and drive type by running the SCU.

Run the SCU and turn off video BIOS shadow.

(continued on next page)

2–12 System Troubleshooting

Table 2–2 (Cont.) POST and Boot Messages

POST No. Error Name Description Solution

100 Shadow ROMs Shadow of off-board

090 Enable cache Internal cache test

080 Initialize option ROMs XXXX0h optional ROM

070 Set system clock Time of day clock not set Run the SCU. 060 Check for electrical

keylock 043 Invalid EISA conﬁgura-

042 Invalid ISA conﬁgura-

video BIOS failed

failed, cache disabled

bad checksum=YYh

Keyboard is locked, please unlock

tion information

The video controller board might have failed. Check that it is installed correctly. Run the SCU. Also, see 700.

Cache failed. Replace the CPU module.

Expansion board conﬁguration error. Run the SCU.

Unlock the keyboard.

An EISA board has not been properly conﬁgured. Run the SCU and verify all settings. Make sure that an EISA CFG ﬁle has been installed for the module.

An ISA board has not been properly conﬁgured. Run the SCU and check switch and jumper settings. Make sure that an ISA CFG ﬁle has been installed for the module.

(continued on next page)

System Troubleshooting 2–13

Table 2–2 (Cont.) POST and Boot Messages

POST No. Error Name Description Solution

041 ID mismatch error,

040 Report conﬁguration

errors and prompt for

conﬁguration utility 020 Enable parity checking

and NMI 004 No boot sector on hard

slot X

Conﬁguration error, slot X

drive

(A) The board in slot X is bad and returns a bad ID. (B) The board ID does not match the ID that the SCU expects for slot X. The mismatch is due to either the wrong board in the slot or the wrong conﬁguration ﬁle for the board. Run the SCU to conﬁgure slot X, or replace the bad board.

Run the SCU for the board in slot X.

The hard disk drive is not formatted as a bootable disk. Format the drive.

(continued on next page)

2–14 System Troubleshooting

Table 2–2 (Cont.) POST and Boot Messages

POST No. Error Name Description Solution

003 Hard drive read failure The hard disk

002 No boot device available If booting from a

drive has failed. Check the system conﬁguration and drive type by running the SCU. Check both ends of the controller’s cables, and reseat the hard disk controller board. Try another hard disk drive. If the problem persists, replace the hard disk controller.

diskette, it is a nonbootable type or the diskette drive has failed. If booting from a hard disk drive, it might not be formatted or the drive might have failed. The problem might also be the SCSI controller board. Make sure the diskette in drive A contains an operating system. If applicable, make sure the hard disk drive contains an operating system.

(continued on next page)

System Troubleshooting 2–15

Table 2–2 (Cont.) POST and Boot Messages

POST No. Error Name Description Solution

001 Not a bootable diskette The diskette in

000 Boot Diskette read failure No diskette in drive

2.3.5 Beep Codes

If POST ﬁnds an error and cannot display a message, the system board speaker beeps to indicate the error and places a value in I/O port 80h. For example, a failure of bit 3 in the ﬁrst 64 KB of DRAM is indicated by a 2-1-4 beep code (a burst of two beeps, a single beep, and a burst of four beeps).

Tables 2–3 and 2–4 list the beep codes and the values POST writes to I/O port 80h when it encounters an error. Table 2–3 lists fatal errors (errors that lock the computer), and Table 2–4 lists nonfatal errors (errors that do not lock the computer).

One beep code is not listed in either table: a long beep followed by one or more short beeps. This beep code indicates a video controller failure.

drive A is not formatted as a bootable diskette. Replace the diskette with a bootable diskette and try again.

A. Insert a diskette and try again.

Table 2–3 Beep Codes for Fatal Errors

Beep Code Error Message Port 80h

1-1-3 Real-time clock write/read failure 02h 1-1-4 ROM BIOS checksum failure 03h 1-2-1 Programmable interval timer failure 04h 1-2-2 DMA initialization failure 05h 1-2-3 DMA page register write/read failure 06h 1-3-1 DRAM refresh veriﬁcation failure 08h

2–16 System Troubleshooting

(continued on next page)

Table 2–3 (Cont.) Beep Codes for Fatal Errors

Beep Code Error Message Port 80h

1-3-3 1st 64 KB DRAM chip or data line failure 0Ah 1-3-4 1st 64 KB DRAM odd/even logic failure 0Bh 1-4-1 1st 64 KB DRAM address line failure 0Ch 1-4-2 1st 64 KB DRAM parity test in-progress

failure 2-1-1 Bit 0 1st 64 KB DRAM failure 10h 2-1-2 Bit 1 1st 64 KB DRAM failure 11h 2-1-3 Bit 2 1st 64 KB DRAM failure 12h 2-1-4 Bit 3 1st 64 KB DRAM failure 13h 2-2-1 Bit 4 1st 64 KB DRAM failure 14h 2-2-2 Bit 5 1st 64 KB DRAM failure 15h 2-2-3 Bit 6 1st 64 KB DRAM failure 16h 2-2-4 Bit 7 1st 64 KB DRAM failure 17h 2-3-1 Bit 8 1st 64 KB DRAM failure 18h 2-3-2 Bit 9 1st 64 KB DRAM failure 19h 2-3-3 Bit A 1st 64 KB DRAM failure 1Ah 2-3-4 Bit B 1st 64 KB DRAM failure 1Bh 2-4-1 Bit C 1st 64 KB DRAM failure 1Ch 2-4-2 Bit D 1st 64 KB DRAM failure 1Dh 2-4-3 Bit E 1st 64 KB DRAM failure 1Eh 2-4-4 Bit F 1st 64 KB DRAM failure 1Fh 3-1-1 Slave DMA register failure 20h 3-1-2 Master DMA register failure 21h 3-1-3 Master interrupt mask register failure 22h 3-1-4 Slave interrupt mask register failure 23h 3-2-4 Keyboard/mouse controller test failure 27h

0Dh

System Troubleshooting 2–17

Table 2–4 Beep Codes for Nonfatal Errors

Beep Code Error Message Port 80h

3-3-4 Screen memory test failure 2Bh 3-4-1 Screen initialization failure 2Ch 3-4-2 Screen retrace test failure 2Dh

2.4 Setup Utility

The system BIOS also contains a setup utility that enables you to change conﬁguration settings that are stored in CMOS RAM. BIOS setup options are the same as those provided in the "Conﬁgure computer" option of the SCU, with the exception of password. For information on conﬁguring the system with the SCU, refer to Chapter 5.

To run the setup utility, wait for POST to complete. Then, press the appropriate function key to display the following initial setup screen:

Since values specified using the BIOS Setup Utility will be overwritten when the system configuration utility (SCU) is run, it is recommended that the BIOS Setup Utility be used only if you:

o Need to enable your diskette drive o Do not have access to a diskette drive o Have only ISA expansion boards and will not be using the SCU

To exit setup press ESC. To continue setup press F1.

**** NOTE ****

Always use the SCU to conﬁgure the system. Do not use setup to conﬁgure the system. Setup is used primarily to enable the diskette drive.

2–18 System Troubleshooting

Note

2.5 Run-Time Error Messages

Run-time error messages are displayed on the monitor if an error occurs after the system boots. Table 2–5 lists the run-time error messages by number.

Table 2–5 Run-Time Error Messages

POST No. Message Solution

988 Software NMI 987 Bus timeout NMI, slot X 986 Unresolved bus timeout NMI See 985. 985 Fail safe timeout NMI Expansion board malfunction. Replace

984 Expansion board disabled Conﬁguration error or malfunctioning

983 Unresolved I/O expansion board

NMI

982 I/O expansion board NMI, slot X Malfunction or conﬁguration error for

981 Memory parity error at XXXX–

YYYY

980 Unresolved memory parity error Computer DRAM has failed. Replace

971 Unexpected hardware interrupt This could be any hardware-related

970 Unexpected software interrupt There is an error in a software utility.

defective board.

expansion board. Run the SCU and verify settings.

See 982. Slot is unknown.

expansion board in slot X. Run the SCU and verify settings.

See 980.

any failed SIMM.

problem. Check all cables, connections, jumpers, and boards.

Try turning the system off and then on again.

2.6 Troubleshooting

Follow this general procedure to troubleshoot the system.

1. Press the reset button on the front panel. If your system fails to boot, turn

it off, wait 20 seconds, and then turn it back on.

2. Check for non-bootable diskette in A: (drive A).

3. Check for loose cables and connections.

4. Check the system and monitor indicator lights.

System Troubleshooting 2–19

5. Observe any POST messages. Refer to Section 2.3.4, POST and Boot

Messages, take the appropriate steps to correct the problem, and then reset the computer.

6. Run the SCU and make sure the system is conﬁgured correctly for the

installed hardware and software. For information on conﬁguring the system with the SCU, refer to Chapter 5.

7. Run the applicationDEC system exerciser (SYSEX). SYSEX tests each

system unit simultaneously with peripheral and communication transfers to detect interactive errors. For further information on testing the system with SYSEX, refer to Chapter 3.

8. Contact Digital Customer Services for software or hardware problems.

9. Package the failed component in the original container and return it to

Digital for service.

Tables 2–6 through 2–8 help you to identify and solve system, disk drive, and monitor problems.

Table 2–6 System Troubleshooting

Problem Possible Cause Action

No response when the system is turned on

Power is on, but there is no monitor display

System does not boot from an IDE hard disk drive

2–20 System Troubleshooting

System is not pluggedinTurn off the system, plug it in, and

No power at the wall outlet

Monitor brightness and contrast controls are not properly set

Monitor is off Turn on the monitor. Monitor cable is

incorrectly installed Video expansion board

failure Operating system

software is not installed on the IDE hard disk drive

turn it on again.

Use another wall outlet.

Adjust the monitor brightness and contrast controls.

Check all monitor connections.

Make sure the video expansion board is properly installed and ﬁrmly seated.

Install the operating system on the hard disk.

(continued on next page)

Table 2–6 (Cont.) System Troubleshooting

Problem Possible Cause Action

System does not boot from a SCSI hard disk drive

IDE hard disk drive is not properly formatted or the requested partition does not exist

There is no software on the requested partition

IDE hard disk drive jumpers incorrectly set

IDE drive type incorrect

Loose cables Check all cable connections. Operating system

software is not installed on the SCSI hard disk drive

Requested partition does not exist

SCSI hard disk drive jumpers incorrect

SCSI ID conﬂicts Refer to the supplied SCSI hard disk

Terminating resistors not removed from the SCSI hard disk drive

System not conﬁgured for SCSI hard disk operation

IDE drive is conﬁgured in the system

Format the IDE hard disk drive or correctly partition the IDE hard disk drive using the supplied operating system software.

Install software on the requested partition.

Refer to the supplied IDE hard disk drive kit installation instructions.

Run the SCU to identify the correct drive type.

Install the operating system.

Partition the SCSI hard disk drive and then reload the operating system.

Refer to the supplied SCSI hard disk drive kit installation instructions.

drive kit installation instructions on setting SCSI IDs.

Remove terminating resistors. Refer to the supplied kit installation instructions.

Run the SCU to conﬁgure the system for SCSI operation.

Remove the IDE drive or install the boot software on the IDE drive.

(continued on next page)

System Troubleshooting 2–21

Table 2–6 (Cont.) System Troubleshooting

Problem Possible Cause Action

System does not boot from a target diskette drive

System will not boot from system conﬁguration diskette

No response to keyboard commands

Drive ID incorrectly set

Diskette drive not enabled

Diskette does not contain start-up ﬁles

Diskette drive is empty Insert the diskette that contains an

Diskette is worn or damaged

Loose cables Check all cable connections. System conﬁguration

diskette faulty

Keyboard is password protected

Keyboard is not connected

Keyboard is connected to the mouse port

Keyboard is locked Unlock the keyboard.

Make sure the drive ID is correctly set.

Run setup utility to enable diskette drive.

Insert diskette with correct start-up ﬁles.

operating system. Try another diskette.

Use another system conﬁguration diskette.

Run the SCU to enter the keyboard password.

Connect the keyboard.

Connect the keyboard to keyboard port.

2–22 System Troubleshooting

Table 2–7 Disk Drive Troubleshooting

Problem Possible Cause Action

IDE/SCSI hard disk drive cannot read or write information

Target diskette drive cannot read or write information

Incorrect jumper settings

Loose or incorrectly installed cables

IDE/SCSI hard disk drive is not properly formatted or partitioned

IDE drive type incorrect

System not conﬁgured for SCSI hard disk operation

Diskette is not formatted

Diskette is worn or damaged

Diskette is writeprotected

Diskette drive is empty Insert a diskette.

Refer to the supplied kit installation instructions.

Make sure all cables are correctly installed.

Format and partition as required using the supplied operating system.

Run the SCU to identify the correct drive type.

Run the SCU to conﬁgure the system for SCSI operation.

Format the diskette.

Try another diskette.

Slide the write-protect switch so the hole is not visible (3.5-inch diskette) or uncover the write-protect notch (5.25-inch diskette).

System Troubleshooting 2–23

Table 2–8 Monitor Troubleshooting

Problem Possible Cause Action

Monitor power indicator is not on

No monitor display Conﬁguration error Check video board cabling and jumper

Distorted, rolling, or ﬂickering screen display, or wrong/uneven color

Color monitor displaying monochrome

Monitor is turned off Turn on the monitor.

Power cord is not connected

No power at wall outlet

Power indicator is defective

Monitor brightness and contrast controls are not properly set

Monitor incorrectly adjusted

Monitor signal cable incorrectly installed

System was turned on before the monitor was turned on

Connect the power cord to the system.

Use another outlet.

Replace monitor.

settings. Adjust the monitor brightness and

contrast controls.

Adjust accordingly.

Straighten any bent connector pins and then reseat.

Turn off the system and monitor, turn on the monitor, and then turn the system on.

2–24 System Troubleshooting

3.1 Overview

The applicationDEC system exerciser (SYSEX) is a standalone, diskettebased diagnostic that detects and isolates hardware problems to the ﬁeld replaceable unit (FRU) level. SYSEX tests each system unit simultaneously with peripheral and communication transfers to detect interactive errors.

Version 4.0 or higher of the applicationDEC System Exerciser is required for use with the applicationDEC 400xP system.

SYSEX veriﬁes the following:

• System motherboard logic

• Memory expansion module

• Serial port (COM1, COM2) logic

System Exerciser

Note

• Parallel port (LPT1) logic

• Terminal multiplexer module

• EtherWORKS Turbo Ethernet controller

• 3.5-inch diskette drive

• 5.25-inch diskette drive

• 2.2 GB helical 8 mm tape drive (TKZ08)

• 320/525 MB QIC tape drive (TZK10)

System Exerciser 3–1

• Digital hard disk drives:

209 MB disk drive (RZ24) 426 MB disk drive (RZ25) 665 MB disk drive (RZ56) 852 MB disk drive (RZ35)

1.0 GB disk drive (RZ57)

1.3 GB disk drive (RZ58)

You can run the system exerciser two ways:

• The installation veriﬁcation procedure (IVP) performs a 15-minute (default

time) test session that returns the system status.

• The run command executes the system exerciser tests continuously. Press The SYSEX commands let you run, halt, and block tests. In addition, you

can display the following information:

• System conﬁguration

• Data at speciﬁed locations

• Status of tests and devices

• Error reports You can dedicate CPU resources to speciﬁed tests by blocking unwanted tests.

Section 3.9.1 provides information on how to block tests.

Ctrl/C

to halt SYSEX at any time.

3.2 Loading the System Exerciser

Load the system exerciser as follows:

1. Insert the system exerciser diskette into the 3.5-inch diskette drive.

2. Boot the system from the diskette in either of the following ways:

• Turn the system power off and then on again.

• Press the reset switch on the front panel.

If a bad checksum message is displayed, see Section 3.4.

3–2 System Exerciser

3.3 Running the System Exerciser

Note

Before you run SYSEX, verify the system conﬁguration with the system conﬁguration utility (SCU). For information on conﬁguring the system with the SCU, refer to Chapter 5.

When the system exerciser has been booted, system conﬁguration information is displayed on the screen:

03/12/92 15:00:08 applicationDEC System Exerciser Rev 4.0 400xP 0000:00:00

Unpublished-rights reserved under the copyright laws of the United States. Verifying program loaded correctly System Configuration:

Slot Type ==== ==== 0 33MHz Viceroy Motherboard 0 0 KB Secondary Cache 0 16MB Memory

EISA slot configuration: Slot IRQ Ports Type ==== === ===== ==== 0 6 3F0-3F7 Floppy controller 0 7 378-37B Parallel port, LPT1 0 4 3F8-3FF Serial port, COM1 0 3 2F8-2FF Serial port, COM2 0 Video Adapter (80x25 color) 1 10 D0000 8x4 Mux 3 11 330-332 Adaptec 1540B, firmware rev = 05 2 5 300-30C DE200 Ethernet, Node addr = 08-00-2B-27-73-31

Load scratch media into all drives to be tested in write-read mode Hit any key to continue

applicationDEC System Exerciser Rev 4.0 03/01/92

After you load the drives to be tested, press displayed.

Is a printer connected to COM1 (Y/N)?

Enter your response by pressingYorN. The following message is displayed:

Sizing devices (please wait - up to 5 min.) ...

Enter

. The following message is

System Exerciser 3–3

Then you are prompted to select destructive (write/read) or nondestructive (read only) testing for each device:

Test mode selection. Use keyboard to make selections. Space key selects write/read testing. ENTER key protects media.

The screen should resemble the following display during and after test mode selections:

BUS Configuration: Slot ID LUN Device Type Rev Selection 0 0 * Disk RX23/1.44M Protected 0 1 * Disk RX33/1.2M Read only 3 0 0 Disk RZ25 (C) DEC 0700 Read only 3 1 0 Disk RZ24 (C) DEC 211B Read only

Next, you are prompted to enable or disable external loopback testing:

Loopback Selection. Hit SPACE to enable external loopback, ENTER to disable. 1 D0000 8x4 Mux A-C disabled B-D disabled

00 COMM1 disabled 00 COMM2 disabled 00 LPT1 disabled

Note

If you selected destructive (write/read) testing for any device, the following message is also displayed:

******************************************

* WARNING! Destructive testing enabled. *

* Data will be lost when testing begins! *

******************************************

If loopback testing is enabled, loopback connectors must be installed on the enabled ports (8x4 mux, serial port 1, serial port 2, parallel port) or the related tests will fail.

The next display shows the tests that the system exerciser will run. The display is based on the selections you made and the recognized system conﬁguration.

3–4 System Exerciser

Scheduled tests: Test Name Rev

==== ==== ===

1. Memory 1

2. Memory Retention 1

3. Numeric 0

4. Serial Line (COM1) 2

5. Serial Line (COM2) 2

6. Motherboard [Slot 0] 2

7. Parallel Port (LPT1) 1

8. Console 1

9. SCSI Disk 3:0:0 1

10. SCSI Disk 3:1:0 1

11. Floppy Disk 0:0 1

12. Floppy Disk 0:1 1

13. 8x4 Mux [Slot 11] 2

14. Ethernet/2 (DE200) 0 Type "HELP" for information, "RUN" or "IVP" to begin testing

HLT>

When the HLT> prompt is displayed, you can run the 15-minute installation veriﬁcation procedure (IVP). Type the ivp command and press

HLT> ivp

Enter

You can run the IVP for less than the full 15 minutes by specifying a number of minutes in the ivp command. The following command speciﬁes 5 minutes:

HLT> ivp 5

Enter

When the IVP is running, the following message is displayed:

Installation Verification Procedure Running

Also, the HLT> prompt will change to RUN>. After 15 minutes (default time), a success message is displayed, indicating that

the system is functional. Then the HLT> prompt is reissued:

Installation Verification Procedure Complete: No Errors Detected HLT>

If an error is detected, an error report is displayed immediately and the IVP is aborted. See Section 3.5 for details on how to interpret the error report.

If you wish to rerun the IVP, you must reboot the system exerciser. You cannot rerun the IVP by typing ivp again. By typing the run command, you can run the same tests without rebooting the system, but the tests run continuously (without the 15-minute timeout).

Type status to see error summaries. Press

Ctrl/C

to stop the tests. Type quit

to reboot.

System Exerciser 3–5

3.4 Loading Failure

After you load SYSEX, one or two messages appear on the console monitor. If the only message is the following, loading was successful:

Verifying program loaded correctly

If the error report ‘‘Checksum error detected at load time’’ follows the above message, the loading failed. Take the following action:

1. Reload the diskette.

2. Reboot. If this fails to correct the loading failure, try a different SYSEX

diskette in case the ﬁrst diskette is bad.

3. If this load also fails, check for failed memory or a bad load path. A bad

load path occurs when either the diskette drive itself is bad or the cable to the diskette drive is bad. Section 4.9 provides information on replacing memory modules.

4. Run the POST tests again for possible further information.

3.5 Error Reports

If SYSEX detects an error condition or a failed FRU, an error report is displayed on the monitor and written to the error log. By default, SYSEX stops execution when an error is detected. (Information in the error log can be displayed using the log command.)

Each error report calls out a FRU. Because there may be more than one of any type of FRU in the system, additional information is provided to identify which of the multiple units has failed:

• For modules, the slot number indicates the module which has failed.

• For SIMM failures, the socket number of the failed SIMM is indicated.

• For SCSI storage devices, the bus ID and logical unit number of the device

is indicated. Also, the slot number of the associated adapter is identiﬁed. SCSI devices controlled by an ISA SCSI adapter or an EISA SCSI adapter are identiﬁed by the slot number of the adapter.

3–6 System Exerciser

The following SYSEX error report shows that the loopback plug was found missing during external loopback testing of serial port 1 (COM1):

applicationDEC System Exerciser Rev: 4.0 03/01/92 (400xP)

Current time = 03/12/92 15:50:06 Elapsed time = 2:41:58 Test # 4 Serial Line (COM1) 2 Subtest # 3 Passes 1828 Errors 1 Task # 3 Processor # 0 Slot: 0

FRU = slot 0 Serial Port, loopback plug Registers at time of error:

eax = 44E924FE ebx = 44E9245F ecx = 0000FF04 edx = 000003F8 esi = 00001000 edi = 0000005F Error address = 33F Current UART registers: LCR = 3B MCR = 18 LSR = 60 MSR = 8A DL = 11F

Test: External loopback (xmit -> rcvr)

Interrupt wait elapsed, outstanding interrupts = 9.

Transmit string, length = 9. CC AC 7E 78 75 0C 38 C2 29

Receive string, length = 0.

After an error, continued testing is dependent on the state of the halt ﬂag:

Halt ﬂag on = suspend test execution (until the run command is reissued) Halt ﬂag off = continue test execution (immediately after completion of error report)

Before replacing a FRU identiﬁed by SYSEX:

1. Make sure that the module in the designated slot is the correct module for

the slot.

2. Make sure that all switches and jumpers are set correctly on the module.

3. Check any cable connections.

4. Reseat modules installed in the EISA bus slots. Now, rerun SYSEX. If the same FRU is called out again, replace the FRU.

System Exerciser 3–7

3.6 Test Descriptions

Table 3–1 describes the system exerciser tests.

Table 3–1 System Exerciser Tests

Name Description

Memory Write/read main memory. Memory retention Memory refresh circuitry. Numeric CPU ﬂoating point. Motherboard System motherboard logic. Console Writes test patterns to the console for visual veriﬁcation. Terminal multiplexer Internal/external data loopback and registers. Serial port (COM1, COM2) Internal/external data loopback and registers. Parallel port (LPT1) Internal/external data loopback and registers. Floppy Write/read (destructive) or read-only (nondestructive)

Ethernet Send, receive, and verify messages internally and with

SCSI disk Write/read (destructive) or read-only (nondestructive)

SCSI tape Write/read veriﬁcation. Requires that tape cartridge be

veriﬁcation. User selectable. Requires that diskette be installed in device.

other network nodes.

veriﬁcation. User selectable.

installed in device.

3.7 Modes

The system exerciser has two modes. The modes are described in Table 3–2.

Table 3–2 System Exerciser Modes

Mode Prompt Meaning

Halt HLT> Tests have not begun or testing is suspended. Run RUN> Tests are running.

You can run most SYSEX commands in either mode. The exceptions are the ivp command, which is valid only in the halt mode, and the istep command, which is valid only at a breakpoint.

3–8 System Exerciser

You can place SYSEX in the halt mode at any time by pressing no tests are running when SYSEX is in the halt mode, response to commands is immediate. When SYSEX is in the run mode and tests are running, the keys you press are echoed to the screen as they are typed, but the commands are not executed until the completion of the current test pass. This can sometimes cause a short delay.

3.8 Flags

You can set ﬂags to control whether:

• Information sent to the console monitor and the error log should include

• Information is sent to the console monitor in one-screen segments.

• Testing should continue when an error is encountered.

• Console output should be echoed to a serial printer on the COM1 port.

• Failing tests should automatically block themselves. Flags are set with the ﬂag command. Table 3–3 describes the SYSEX ﬂags.

Table 3–3 System Exerciser Flags

Flag Default Description

Ctrl/C

. Because

data about memory allocation, task swapping, and segment descriptors.

Halt On Stop testing when error is reported; return to halt mode prompt.

Long Off Include test environment information in the error report. This

More Off Displays information on the console in one-screen segments.

Print Off Allows the console output to be echoed to a serial printer on the

Threshold On Automatically blocks any test that reaches the error threshold.

If off, continue testing after an error is reported.

information describes the machine state during the most recent task swaps, segment descriptor data, and the memory allocation table. If off, generate an abbreviated error report that contains only the header block and text.

Enter

Press

Spacebar

to stop displaying information. If off, any information containing more than 23 lines will have some lines that scroll off the console monitor.

COM1 port. The print ﬂag is ignored if the startup ‘‘ Is a printer connected to COM1 (Y/N)?’’ question is not answered with Y.

The threshold is ten failed passes in a row. If off, allows the failing test to keep running and reporting failures.

to display the next line of information. Press

to display the next screen of information. Press

System Exerciser 3–9

Use the ﬂag command to change the status of a ﬂag. For example, to set the long ﬂag, enter the following:

HLT> flag on long

If you boot the system, the SYSEX ﬂags return to the default settings.

3.9 Commands

Table 3–4 lists the system exerciser commands. The commands are not case sensitive and may be abbreviated.

Table 3–4 System Exerciser Commands

Command Description

B[lock] Prevent speciﬁed tests from running. B[lock] {no argument} Display all tests that are currently blocked from running. Cac[he] Set internal processor cache state (enabled or disabled). Cac[he] {no argument} Display current state (enabled or disabled) of the internal

Cal[culate] Make a calculation in one of three radices: decimal, octal, or

Co[nﬁguration] Display the conﬁguration of the system.

Ctrl/C

De[vices] Display or modify the ﬂag state of devices under test. De[vices] {no argument} Display a list of the supported devices. Di[splay] Display the data at speciﬁed locations in memory. E[xamine] Examine the data at a speciﬁed location in memory. You

F[lags] Modify the ﬂag settings. F[lags] {no argument} Display the state of all ﬂags (on or off). G[o] Set and run until a breakpoint. H[elp] Obtain information on any command. H[elp] {no argument} Display a list of all system exerciser commands. Is[tep] Execute individual instruction(s) while in debug mode. Ivp Run the installation veriﬁcation procedure.

Enter

processor cache.

hexadecimal. Hexadecimal is the default radix.

Halt testing; return to the halt mode prompt.

can also deposit data at the speciﬁed location in memory.

(continued on next page)

3–10 System Exerciser

Table 3–4 (Cont.) System Exerciser Commands

Command Description

L[og] Play back or delete previous error reports or write error

Q[uit] or R[un] Begin or resume testing (change from halt mode to run

Se[t] Set or display the values of state variables. Se[t] {no argument} Display a list of all state variables. Sh[ow] Show a machine state. Sh[ow] {no argument} Display a list of all available machine states that can be

St[atus] or

Ctrl/T

T[ime] Display current date and time and elapsed test time. U[nblock] Allow tests that have been blocked to resume running. U[nblock] {no argument} Display all tests that are currently unblocked.

3.9.1 Block

Use the block command to prevent one or more tests from running. This might be helpful if you want to focus CPU time on one test. For example, you might want to eliminate a test from which you have already gathered sufﬁcient error information, or you might want to eliminate constantly scrolling error reports from a failing test.

Ctrl/Alt/Delete

reports to a DOS diskette. Stop all tests and reboot the system.

mode).

shown. Display which tests are running, whether they are blocked,

and how many test passes have been made.

Format: BLOCK [option_argument] Table 3–5 describes the options that you can use with the block command.

Table 3–5 Block Command Options

Command Description

B[lock] Display all tests that are currently blocked. B[lock] t Block the speciﬁed test. B[lock] t-t Block a range of tests that begins with the ﬁrst test number speciﬁed

and ends with the second test number speciﬁed.

System Exerciser 3–11

For example, to block test 1:

RUN> block 1

If you look at the test status, the display indicates that test 1 is blocked by placing the letter B next to the number of the test.

To block test 1 and test 3, use either of the following:

RUN> block 1 3 RUN> block 1,3

To block test 1, test 2, and test 3:

RUN> block 1-3

3.9.2 Cache

The cache command lets you set or display the state (enabled or disabled) of the internal cache.

Format: CACHE [enable,disable] If no argument is given, the cache command displays the current state of the

cache.

RUN> cache disable

3.9.3 Calculate

The calculate command lets you make calculations and includes functions similar to a pocket calculator, such as addition, subtraction, multiplication, and division.

Enter

Format: CALCULATE[/radix] argument_list The calculate command provides support for the following three radices:

• Octal

• Decimal

• Hexadecimal (default) The result of the calculation is displayed in all three radices in the order octal,

decimal, hexadecimal. The calculate command is a convenient way to convert radices. Table 3–6 describes the qualiﬁers that you use to set the default radix for all

numbers in a calculation.

3–12 System Exerciser

Table 3–6 Calculate Command Qualiﬁers

Command Description

Cal[culate]/o Calculate using the octal radix. Cal[culate]/d Calculate using the decimal radix. Cal[culate]/h Calculate using the hexadecimal radix.

Hexadecimal is the default radix. If you set the default radix to decimal or octal, the system immediately defaults back to hexadecimal when the calculation is ﬁnished.

To convert the value of 100 octal to hexadecimal or decimal, use the following command:

HLT> caculate/o 100

Enter

100, 64, 40

To convert the value of 100 decimal to octal or hexadecimal, use the following command:

HLT> calculate/d 100

Enter

144, 100, 64

To see the value of 100 hexadecimal in the three radices, use the following command:

HLT> calculate 100

Enter

400, 256, 100

Note that because hexadecimal is the default, you do not have to specify /h when calculating in hexadecimal.

If you use more than one radix in a calculation, use the symbols shown in Table 3–7 to specify the radix of an individual number.

Table 3–7 Calculate Command Radix Symbols

Radix Symbol Example

Decimal . 10. Hexadecimal h 10h Octal o 10o

For example, in the equation that follows, the number 13 is hexadecimal, 59 is decimal, and 100 is octal:

HLT> calculate 13 + 59. + 100o

Enter

216, 142, 8e

System Exerciser 3–13

You can use the following functions with the calculate command:

• Add ( +)

• Subtract ( -)

• Multiply (*)

• Divide ( /)

• Exponentiation (^) The order of precedence is:

• Exponentiation (highest precedence)

• Multiply or divide

• Add or subtract (lowest precedence) Use parentheses to change the order.

3.9.4 Conﬁguration

The conﬁguration command lets you display the same system and EISA bus conﬁguration information that was displayed during initial SYSEX startup.

Format: CONFIGURATION

RUN> configuration

3.9.5 Ctrl/C

Press

Ctrl/C

at any time to suspend testing and enter halt mode.

Enter

Note that although testing is stopped when suspended, the clock that measures elapsed test time continues to operate. The clock will always reﬂect the elapsed time since you started testing. If you suspend testing, the clock does not reﬂect the actual test time.

3.9.6 Devices

The devices command lets you display or modify the ﬂag state of devices under test.

Format: DEVICES [device[/n] [ﬂag_list] The devices command is extremely useful for changing the test state of

devices that were set up incorrectly at the start. Without this command, you would have to reboot SYSEX to set up the device tests differently.

3–14 System Exerciser

For example, if you select destructive (write/read) testing for a disk that really should be write protected, then you can use this command to change to nondestructive (read only) testing for the disk. Or, if you set up a COM or LPT for external loopback testing and ﬁnd that loopback plugs are not installed, then you can use the devices command to reconﬁgure the COM or LPT for internal loopback testing only.

The ﬁrst argument must be the name of the requested device. The /n modiﬁer can be used to request a speciﬁc device of the type given. The following example speciﬁes COM2 and no other COM devices:

RUN> devices com/2

Enter

The format of the /n modiﬁer depends on the device type. Table 3–8 shows the format for each device type.

Table 3–8 Devices Command Formats

Device Type(s) Format Description

COM LPT

Disk x:y[:z] x = disk adapter slot number

Ethernet nn= device slot number

nn= device port number

y = SCSI ID address z = logical unit number (hard disk drives only)

If the /n modiﬁer is not provided, then all devices of the given type will be affected.

A ﬂag list can be included in the command line, which will cause the speciﬁed device ﬂag(s) to be set to the requested state. When a ﬂag list is not included, the current state of the speciﬁed device(s) is displayed. A ﬂag list has the format (enable/disable) ﬂag1, ﬂag2, ..., ﬂagn. You must specify the state followed by a list of all ﬂags that should be set to that state.

The /n modiﬁer for the disk device type has the format x:y[:z], where x:y:z speciﬁes the disk whose ﬂag state should be displayed or modiﬁed. The disk number can be found in the test list. For example, dev disk/0:0 speciﬁes the RX23 diskette drive, and dev disk/3:1:0 speciﬁes a disk on the SCSI bus.

Table 3–9 shows the available state ﬂags for supported devices.

System Exerciser 3–15

Table 3–9 Devices Command State Flags

Device Flag(s) Description(s)

COM Lpbk External loopback Disk Protect Data protect ﬂag Ethernet

Auto_census Census Int_lpbk Network

Automatic census every ‘‘time x’’ minutes Issue census command Internal loopback

Network testing LPT Lpbk External loopback MUX AClpbk, BDlpbk A->C and B->D loopback ﬂags

Enabled runs test as read only.

Ethernet devices support two additional command qualiﬁers: add and remove. You use these qualiﬁers to add node addresses to the network partners table or to remove nodes from test. The remove qualiﬁer leaves the entry in the table, but sets the status to ‘‘not testing’’. Following the qualiﬁer verb is the node address in the form xx-xx-xx-xx-xx-xx, which is the 48-bit LAN address. An example is dev ether add 08-00-2B-5E-1C-5A.

Automatic census can be disabled for network devices to prevent periodic census commands from being issued. The time interval can also be set to zero in order to disable the automatic census feature. To set the time, enter the command dev ethernet/n enable auto x, where x is the time in munutes.

Versus external loopback.

Versus internal or external loopback testing. If network testing is enabled, test packets are sent to other nodes on the network. If network testing is disabled, then either internal or external loopback testing is performed, based on the state of the int_lpbk ﬂag.

3.9.7 Display

The display command lets you display data at speciﬁed locations in memory. Format: DISPLAY[/mode] [address] Data can be displayed in the following modes:

• Byte (default)

• Word

• Doubleword

• ASCII To choose a display mode, use one of the display command qualiﬁers shown in

Table 3–10.

3–16 System Exerciser

Table 3–10 Display Command Qualiﬁers

Command Display Mode

D[isplay]/b Byte (default) D[isplay]/w Word D[isplay]/d Doubleword D[isplay]/a ASCII

If you do not designate an address, the system defaults to the last address selected for display or to address 0 if no previous display command was executed.

Addresses have the format task:seg:offset. The task:seg ﬁelds are optional, but are always displayed by the system. The offset ﬁeld is required and is the address offset within the segment. For example, to display the data in the byte display mode (default) at address location 32F (hex) in segment 8 (default), use either of the following:

HLT> display 32f

Enter

0:8:32F 53 HLT> display 0:8:32f

Enter

0:8:32F 53

You can also specify an argument list to display an address range. The range can be any size from one unit or more and can be in ascending or descending order. The range is speciﬁed as addr addr (starting address, ending address) or as addr length value (starting address, length qualiﬁer, length value in display mode units).

In addr addr mode, the ending address is another offset within the segment. If the ending offset (address) is greater than the starting offset, then memory is displayed in order of ascending addresses. If the ending offset is less than the starting offset, data is displayed in descending order.

In addr length value mode, the length value speciﬁes how many units (byte, word, and so on) of data to display beginning with the starting address. If the length is a positive number, data is displayed in ascending addresses. A negative length displays addresses in descending order. For example, to display eight doublewords of data beginning at location 32FH in segment 8 (default), use the following:

HLT> display/dword 32f length 8

Enter

0:8:32F F000FF53 F000FF53 F105ED41 F000FF53 0:8:33F F000FF53 F000EDF2 F0008C8C F000FF53

System Exerciser 3–17

3.9.8 Examine

The examine command lets you analyze and modify data at a speciﬁed location in memory.

Format: EXAMINE[/mode] [address] When data is displayed, the system cursor remains in place and waits for

you to input new data. To modify the data at the current location, input the new data and then use the",#,or without data modiﬁcation, the"key examines data at the previous location in memory. The#key examines data at the next location in memory. The key exits examine mode.

ESC

The new data was typed in or not.

You can examine the contents of memory as bytes, words, doublewords, or as ASCII by using the examine command qualiﬁers shown in Table 3–11.

Table 3–11 Examine Command Qualiﬁers

Command Display Type

E[xamine]/b Byte (default) E[xamine]/w Word E[xamine]/d Doubleword E[xamine]/a ASCII

Enter

keys to store the new data. With or

Enter

key exits examine mode, but will not modify the location whether

If you do not designate an address, the system defaults to the last address selected for examination or to address 0 if no previous examine command was executed.

3.9.9 Flags

The ﬂags command lets you display or modify ﬂags. Format: FLAGS [ﬂags_list] See Section 3.8, Flags.

3–18 System Exerciser

3.9.10 Go

The go command lets you set and run until a breakpoint. Format: GO[/n] [(instruction,write,access,task,forever) (byte,word dword) addr] The go command is an advanced feature of the system exerciser debugger and

is reserved for use by Digital Equipment Corporation development personnel. Debug operations at the lowest hardware levels are extremely complex and can result in unexpected consequences.

3.9.11 Help

The help command lets you view on-line help information. Format: HELP [command]

RUN> help display

3.9.12 Istep

The istep command lets you execute individual instruction(s) while in debug mode. The istep command can be issued only from a breakpoint.

Format: ISTEP [n] The istep command is an advanced feature of the system exerciser debugger

and is reserved for use by Digital Equipment Corporation development personnel. Debug operations at the lowest hardware levels are extremely complex and can result in unexpected consequences.

Enter

3.9.13 Installation Veriﬁcation Procedure (IVP)

The ivp command lets you verify system functionality within 15 minutes (default time) of testing.

Format: IVP [test_time_in_minutes]

HLT> ivp

When the IVP starts, the system displays the following message:

After 15 minutes (default time) of error-free operation, a success message is displayed, indicating that the system is functional. Then the HLT> prompt is reissued:

Installation Verification Procedure Complete: No Errors Detected HLT>

If an error is detected, an error report is displayed and the IVP is aborted. See Section 3.5 for details on how to interpret the error report.

Enter

Installation Verification Procedure Running

System Exerciser 3–19

If you wish to rerun the IVP, you must reboot the system exerciser or type run to continue running SYSEX tests, but without the 15-minute (default time) timeout.

3.9.14 Log

The log command lets you write error reports to a DOS diskette, play back error reports that have been logged, and remove reports from the log.

Format: LOG[/error, /recovered] [<PLAY,CLEAR> entry_number, last] or Format: LOG ARCHIVE ﬁlename.ext

Table 3–12 describes options that can be used with the log command.

Table 3–12 Log Command Options

Command Description

L[og] Display error log summary. L[og] archive ﬁlename.ext Write all error reports to a DOS diskette. L[og] clear entry-number Remove speciﬁc error reports. L[og] clear Remove all error reports. L[og] play entry-number Play back speciﬁc error reports. L[og] play Play back all error reports.

RUN> log

Enter

Table 3–13 illustrates a typical log summary report.

Table 3–13 System Exerciser Error Log Report, Example

Entry Error Test Log Address

0 1 9 28316 1 2 6 27FFA 2 3 15 27AB2

The Entry column denotes which entry from the error log is being described. The Error column denotes whether this is the ﬁrst, second, third, or nth encounter of an error in the test run. The Test column denotes which of the SYSEX tests reported the error. The Log Address column describes where the report is logged in memory.

3–20 System Exerciser

To review an error report from the log, use the log play command and specify the entry number of the error. For example, to review entry 0 from the sample report in Table 3–13:

RUN> log play 0

Enter

You can specify one entry number to review a single error report or a range of entry numbers to review several error reports. However, you cannot enter both single numbers and a range of numbers on the same command line.

Memory space for error reports is limited, but there should be space available for at least 50 error reports.

Note

When the error log is full, new error reports are not included in the error log. Errors must be cleared before new error reports can be included.

To remove an error report from the log, use the log clear command and specify an entry number obtained from the error summary report. For example, to remove entry 0 from the sample report in Table 3–13:

RUN> log clear 0

Enter

Note

Error reports that have been removed from the error log are permanently deleted; they cannot be restored.

You can specify one entry number to remove a single error report or a range of entry numbers to remove several error reports. However, you cannot enter both single numbers and a range of numbers on the same command line.

System Exerciser 3–21

3.9.15 Quit

You can use the quit command to end a test run and reboot the system. Format: QUIT You can also use the key sequence

3.9.16 Run

The run command lets you run SYSEX tests continuously. Format: RUN [test_time_in_minutes] To start or resume testing, enter run or r at the HLT> prompt as follows:

HLT> run RUN>

All unblocked tests begin executing immediately. Devices are tested concurrently. Testing continues until you press encountered while the halt ﬂag is on. Section 3.8 provides information on how to use SYSEX ﬂags.

While the tests run, you can execute the status command at the RUN> prompt to obtain information about SYSEX tests.

3.9.17 Set

The set command lets you set or display state variables. Format: SET [variable [value]] Table 3–14 describes the available state variables that you can set or display.

Enter

Ctrl/Alt/Delete

to duplicate the quit command.

Ctrl/C

or until an error is

3–22 System Exerciser

Table 3–14 Set Command State Variables

State Variable Value(s) Description

Baud 2400

4800 9600

Status n Auto status display. Automatically displays test status every n

Baud rate of the line printer on the COM1 port. This variable is valid only if there is a printer available on the COM1 port.

• Viewing or setting the baud variable is illegal if the startup ‘‘ Is a printer connected to COM1 (Y/N)?’’ question is not answered with Y.

• Specifying an incorrect baud value is ﬂagged as illegal and the current baud rate is not changed.

minutes when n is set to a value greater than zero. When the value of n is zero, automatic test status displays are disabled.

• Auto status display lets you see a recent test status in the event that the system gets into a hung state. This feature is useful on systems that are monitored at infrequent intervals.

• Auto status display does not occur if SYSEX is in halt mode or is at the MORE prompt when status is ready to be displayed.

If you do not specify a state variable, a list of all available state variables is displayed:

HLT> set

Enter

Avaliable state to be set:

BAUD STATUS

If you specify a state variable without providing a new value, the current value of that variable is displayed:

HLT> set status

Enter

Status auto display time = 8

To set a state variable, specify the variable and the new value. The following example sets the baud rate state to 9600 baud:

HLT> set baud 9600

Enter

System Exerciser 3–23

3.9.18 Show

The show command lets you examine the machine state. Table 3–15 describes the available machine states that you can examine.

Format: SHOW [machine_state]

Table 3–15 Show Command Machine States

Machine State Description

Breakpoints Active breakpoints GDT Global descriptor table entries IDT Interrupt descriptor table entries Physical Physical address of speciﬁed logical address Task Task state segments for each task TSS Individual task state segment

3.9.19 Status

The status command (or The command also lets you display the status of all devices that are under test.

Format: STATUS [option] The test statistics that you can display are:

Ctrl/T

) lets you display the test statistics for all tests.

• Test number and description

• The letter B to the left of the test name, if a test is blocked

• Test module revision level

• Total number of test passes made

• Total number of errors detected in each test

• Total number of page faults encountered in each test For example, to obtain the status of all SYSEX tests, enter status or st at the

prompt:

RUN> status

3–24 System Exerciser

Enter

Table 3–16 lists the options for the status command.

Table 3–16 Status Command Options

Command Description

St[atus] Display status of all tests. St[atus] COM[/n] Display status of COMM port(s) under test. St[atus] devices Display status of currently running devices. St[atus] Ethernet/n St[atus] network/n St[atus] t Display status of speciﬁed test. St[atus] t-t Display a range of tests that begins with the ﬁrst test

Device slot number.

3.9.20 Time

The time command lets you display the current date and time and also the elapsed time since the start of testing.

Format: TIME

RUN> time 03/01/92 15:00:08 applicationDEC System Exerciser Rev 4.0 400xP 0000:07:32

Enter

Display status of an Ethernet device. Display network table for an Ethernet device.

number speciﬁed and ends with the second test number speciﬁed.

3.9.21 Unblock

The unblock command lets you resume a test that was prevented from running by the block command.

Format: UNBLOCK [argument_list] Table 3–17 describes the options that can be used with the unblock

command.

Table 3–17 Unblock Command Options

Command Description

U[nblock] Display tests that are currently unblocked. U[nblock] t Unblock the speciﬁed test. U[nblock] t-t Unblock a range of tests that begins with the ﬁrst test number

speciﬁed and ends with the second test number speciﬁed.

System Exerciser 3–25

For example, to unblock test 1:

RUN> unblock 1

Enter

To unblock test 1 and test 3:

RUN> unblock 1 3 RUN> unblock 1,3

Enter

To unblock test 1, test 2, and test 3:

RUN> unblock 1-3

Enter

If you use the unblock command without an argument, a list of all unblocked tests is displayed on the screen.

3–26 System Exerciser

FRU Removal and Replacement

This chapter contains a list of ﬁeld replaceable units (FRUs) and special diagnostics tools. It also contains information regarding electric shock and electrostatic discharge (ESD) that you should read before beginning any FRU removal and replacement procedure.

4.1 FRU Parts List

Table 4–1 lists the available FRUs for the applicationDEC 400xP system. Many FRU replacement procedures require you to run the system conﬁguration

utility (SCU) to conﬁgure the system. For information on conﬁguring the system with the SCU, refer to Chapter 5.

Table 4–1 Field Replaceable Units

Part Number FRU Order Number

30-37794-01 System board (EISA, 8-slot) 54-21819-01 486/25 MHz CPU module (SX25) PS2XK-AA 54-21821-01 486/33 MHz CPU module (DX33) PS2XK-BA 54-21823-01 486/50 MHz CPU module (DX50) PS2XK-CA

Power supply (350 W) H7882-AA US 101-key keyboard PCXAL-AA 3 button mouse (Logitech) PCXAS-AA

17-00083-39 US power cord (125 V) BN26J-1K

14-inch color monitor (1024 x 768, 60 Hz) VRT13-DA

RX23-AA RX23 3.5-inch diskette drive (grey bezel)

Base System Major Components

(continued on next page)

FRU Removal and Replacement 4–1

Table 4–1 (Cont.) Field Replaceable Units

Part Number FRU Order Number

Options

International 102-key keyboard PCXAL-xx 19-32971-01 64 KB cache card (for DX25, DX33) PSWXM-AA 19-32971-02 128 KB cache card (for DX25, DX33) PSWXM-AB

512 KB video RAM kit PSWXM-BA

4 MB SIMM kit (2 x 2 MB, 80 ns) PS2XM-AA

8 MB SIMM kit (2 x 4 MB, 80 ns) PS2XM-AB

16 MB SIMM kit (2 x 8 MB, 80 ns) PS2XM-AC

32 MB SIMM kit (2 x 16 MB, 70 ns) PS2XM-AD

Memory expansion module PS2XM-AE

Terminal multiplexer kit PC4XD-DA 29-28309-01 8-port terminal concentrator PC4XD-DB

EtherWORKS Turbo DE200-AC 30-37789-01 Adaptec 1520 SCSI adapter PSXAZ-AA 29-29052-01 Adaptec 1540B 16-bit SCSI adapter PSXAZ-CA 30-37790-01 Adaptec 1740A SCSI adapter PSXAZ-BA 30-24962-01 RX33 5.25-inch diskette drive PS20R-FA

105 MB IDE 3.5-inch hard disk drive PC4XR-EB

RZ24-S 209 MB SCSI 3.5-inch hard disk drive PS20R-AA

RZ25-S 426 MB SCSI 3.5-inch hard disk drive PS20R-BA

RZ35-E 852 MB SCSI 3.5-inch hard disk drive PS20R-GA

RZ56-E 665 MB SCSI 5.25-inch hard disk drive PS20R-CA

RZ57-E 1.0 GB SCSI 5.25-inch hard disk drive PS20R-DA

RZ58-E 1.38 GB SCSI 5.25-inch hard disk drive PS20R-HA TKZ08-AA TKZ08 2.2 GB SCSI helical tape drive

TZK10-AA 320/525 MB SCSI QIC tape drive PS20R-EA 30-34761-01 16-inch color monitor (1280 x 1024, multisync) VRC16-DA

70-28293-01 Wire assembly, front panel 70-28294-01 Wire assembly, DC switch 12-22355-12 DC switch, DPST (on-none-off) 12-23609-11 4.5-inch fan, tube axial 12-17119-01 Cabinet key 29-26246-01 Field engineer ESD kit 12-36175-01 Disposable ESD strap

The DC switch (12-22355-12) is part of the DC switch wire assembly (70-28294-01), but can be

ordered and replaced separately. The switch is plastic and is connected with push-on terminals.

4–2 FRU Removal and Replacement

Miscellaneous

(continued on next page)

Table 4–1 (Cont.) Field Replaceable Units

Part Number FRU Order Number

74-43107-01 Shielding, driver 70-28286-01 Stand assembly, plastic stabilizer 74-43105-01 Opening insert, plastic 74-43772-01 RX23 insert, plastic 74-43102-01 Lower rear bezel, plastic 74-42776-01 Upper rear bezel, plastic 74-42785-01 Upper front bezel, plastic 70-28259-01 Lower front bezel, plastic 17-02985-02 Diskette drive internal cable assembly 29-27912-01 IDE internal cable assembly (part of PC4XR-EB) 70-28301-01 System power cable 70-28273-02 SCSI internal cable assembly (includes 12-33816-01,

SCSI terminator) 21-32423-01 Real-time clock chip (Dallas Semiconductor DS1287)

4.2 Required Tools

The following tools are required to service the applicationDEC 400xP system:

• Phillips screwdriver

• Flat-blade screwdriver

Miscellaneous

PSXAZ-DA

• Antistatic wrist strap

• Needlenose pliers (for real-time clock disposal)

• Insulating tape (for real-time clock disposal)

4.3 Moving the System

To move the system, grasp the handle inside the front bezel (near the top of the system cabinet) and lift the front of the cabinet slightly. The system can then be moved by wheeling it on the rear wheels.

FRU Removal and Replacement 4–3

4.4 Before You Begin

Before you open the system cabinet, shut the system down and remove power:

Risk of electrical shock. Failure to disconnect the source of power before opening the system can result in personal injury.

Do not touch any logic component unless you are grounded. Grounding can be established by wearing a grounded wrist strap or by touching an exposed metal part of the system chassis. A static discharge from your ﬁngers can result in permanent damage to logic components.

1. If the SCO UNIX System V operating system is being used, type

shutdown on the system console. This command closes all open ﬁles and prepares hard disk drives and other hardware for loss of power.

2. Remove any diskettes from the diskette drives. (If you leave a diskette in

the drive, the system will try to boot from the diskette drive when power is reapplied to the system.)

Warning

Caution

3. Turn the power switch to the Standby position.

4. Unplug the power cord from the wall socket.

You must unplug the power cord from the wall socket to ensure there is no electricity in the system.

4–4 FRU Removal and Replacement

Warning

4.5 Opening the System Cabinet

This section describes how to open the applicationDEC 400xP system cabinet to gain access to the internal components. Refer to Figure 4–1 and Table 4–2.

4.5.1 Removing the Top Cover and Side Panels

1. Shut the system down and unplug the power cord (Section 4.4).

2. Unlock the top cover by inserting the cabinet key and turning it fully to the

left. This will pull the top cover toward the rear of the cabinet. Remove the cabinet key.

3. Push the cover toward the rear to free the front locking tabs. Remove the

top cover by lifting it straight up.

4. Remove the side panels by lifting them up and away from the cabinet. The

two side panels are identical.

Reverse the above procedure to replace the top cover and side panels.

Note

An arrow on the underside of the top cover points to the front.

4.5.2 Removing the Card Cage Cover

1. Shut the system down and unplug the power cord (Section 4.4).

2. Remove the top cover and left side panel using the procedure in

Section 4.5.1.

3. Loosen the two screws on the right side of the card cage cover. Do not

remove the screws.

4. Slide the cover to the right to clear the keyhole and remove the cover. Reverse the above procedure to replace the card cage cover.

FRU Removal and Replacement 4–5

Figure 4–1 System Cover and Side Panel Removal

4–6 FRU Removal and Replacement

MR-0191-91DG

Table 4–2 Key for Figure 4–1

Key Description

A Cabinet key B Top cover C Front locking tabs D Left side panel E Cover retaining screw F Card cage cover G Rear locking tabs

4.5.3 Removing the Bezels

The front (upper and lower) and rear (upper and lower) bezels are removed the same way. Each bezel has four ﬂexible, wedge-shaped locking tabs that snap into matching cutouts on the system cabinet. There are no retaining screws.

The following steps describe the removal procedure for a bezel. See Figure 4–2 and Table 4–3.

1. Shut the system down and unplug the power cord (Section 4.4).

2. Remove the top cover and both side panels using the procedure in

Section 4.5.1.

3. Reach behind the bezel and press the top two locking tabs to release them.

While pressing the tabs, pull the top of the bezel away from the system chassis.

4. Similarly, reach behind the bezel and release the bottom two locking tabs.

Remove the bezel.

Note

You may need to use a tool, such as a ﬂat-blade screwdriver, to release some bezel locking tabs.

To replace a bezel, hold it in position against the system cabinet and push until it locks into place. Alignment pins on the bezel help to guide it into position.

FRU Removal and Replacement 4–7

Figure 4–2 Bezel Removal

Table 4–3 Key for Figure 4–2

Key Description

A Locking tab (1 of 4) B Guide pin (1 of 2)

4–8 FRU Removal and Replacement

MR-0024-92DG

4.6 Replacing the CPU Module

The following steps describe the removal procedure for the CPU module. Refer to Figure 4–3 and Table 4–4 during the procedure.

1. Shut down the system and unplug the power cord (Section 4.4).

2. Remove the cabinet top cover, left side panel, and card cage cover using the

procedures in Section 4.5.

3. Remove the screw on the left end of the CPU module retaining bar and

slide the bar out of the slot on the right side. Save this screw.

4. Pull the CPU module from its slot and slide the module out of the card

cage.

5. Place the module on an antistatic package, antistatic foam pad, or a

grounded workstation surface.

6. Remove the replacement CPU module from its antistatic package and

place it on an an antistatic package, antistatic foam pad, or a grounded workstation surface.

7. If you are replacing a 25 MHz (SX25) or 33 MHz (DX33) CPU module and

an optional cache card is installed on the failed module: a. Remove the cache card and install it on the replacement CPU module

using the procedure in Section 4.7.

b. Ensure that the cache size jumper (J3) on the replacement module

matches the position of the jumper on the failed module. Jumper J2 on the module is not used. Refer to Figure 4–4 and Table 4–5. Table 4–6 describes the jumper J3 positions.

8. Place the failed CPU module in an antistatic package. Reverse the above procedure to install the replacement CPU module.

FRU Removal and Replacement 4–9

Figure 4–3 CPU Module Removal

Table 4–4 Key for Figure 4–3

Key Description

A Retaining bar B CPU module

4–10 FRU Removal and Replacement

MR-0002-92DG

Figure 4–4 CPU Module Layout

123 123

Table 4–5 Key for Figure 4–4

Key Description

MR-0027-92DG

A CPU B Cache socket C Guide pin D 25 MHz or 33 MHz CPU module E 50 MHz CPU module

FRU Removal and Replacement 4–11

Table 4–6 Cache Size Jumper

Cache Size Jumper J3 Position

128 KB 1–2 64 KB 2–3 No cache installed Either position is okay.

4.7 Replacing the Cache Card

The following steps describe the removal and replacement of the cache card. Refer to Figure 4–5 and Table 4–7 during the procedure.

1. Use the procedure in Section 4.6 to remove the CPU module.

2. Place the CPU module on an antistatic package, antistatic foam pad, or a

grounded workstation surface.

3. Use a ﬂat-blade screwdriver to lift the cache card and remove it from from

the CPU module. Refer to Figure 4–4 and Table 4–5.

4. Remove the replacement cache card from its antistatic package. Do not

touch any pins.

5. Position the cache card over the CPU module with the guide pin over the

corresponding pin socket.

6. Gently insert the pins on the cache card in the socket on the CPU module.

7. Push the cache card down evenly on the CPU module. Do not bend the

pins.

8. Install the CPU module.

4–12 FRU Removal and Replacement

Figure 4–5 Cache Card Removal

Table 4–7 Key for Figure 4–5

Key Description

A Guide pin

MR-0001-92DG

FRU Removal and Replacement 4–13

4.8 Replacing a SIMM

SIMMs are removed from their slots at oblique angles, as shown in Figure 4–6. Therefore, any SIMMs installed above a failed SIMM must be removed ﬁrst:

• On the system board, remove SIMMs in order from slots J0651, J0650,

J0551, and J0550 (see Figure 4–7 and Table 4–8).

• On the memory expansion module, remove SIMMs in order from slots J1 or

J5, J2 or J6, J3 or J7, and J4 or J8. (see Figure 4–8 and Table 4–9).

The following steps describe the removal procedure for a SIMM.

1. Shut down the system and unplug the power cord (Section 4.4).

2. Remove the cabinet top cover, left side panel, and card cage cover using the

procedure in Section 4.5.

3. If the failed SIMM is on the memory expansion module, remove the

memory module using the procedure in Section 4.9.

4. If the failed SIMM is on the system board:

a. Remove the CPU module using the procedure in Section 4.6. b. If a memory expansion module is installed, remove it using the

procedure in Section 4.9.

5. Clips on each end of the memory slot hold the SIMM in place. Use your

ﬁnger or a small ﬂat-blade screwdriver to press these clips outward.

6. Tip the SIMM toward the top edge of the board or module and pull the

SIMM out of its slot.

Reverse the above procedure to install the SIMM.

4–14 FRU Removal and Replacement

Figure 4–6 SIMM Removal

MR-0567-91DG

FRU Removal and Replacement 4–15

Figure 4–7 SIMM Slots on the System Board

J0651 J0650 J0551 J0550

MR-0028-92DG

Table 4–8 Key for Figure 4–7

Key Description

A Pin 1 of SIMM slot

4–16 FRU Removal and Replacement

Figure 4–8 SIMM Slots on the Memory Module

J1 J2 J3 J4

W2 W3

Table 4–9 Key for Figure 4–8

Key Description

A Pin 1 of SIMM slot B Memory bank jumpers (4), one for each bank

J5 J6 J7 J8

MR-0029-92DG

FRU Removal and Replacement 4–17

4.9 Replacing the Memory Expansion Module

The following steps describe the removal procedure for the memory expansion module. Refer to Figure 4–9 and Table 4–11 during the procedure.

1. Shut down the system and unplug the power cord (Section 4.4).

2. Remove the cabinet top cover, left side panel, and card cage cover using the procedure in Section 4.5.

3. Remove the screw on the left end of the memory expansion module retaining bar and slide the bar to the left. Save this screw.

4. Pull the memory module from its slot and slide the module out of the card cage.

5. Place the module on an antistatic package, antistatic foam pad, or a grounded workstation surface.

6. Remove all of the SIMMs from the failed module using the procedure in Section 4.8.

7. Remove the replacement memory module from its antistatic package and place it on an antistatic package, antistatic foam pad, or a grounded workstation surface.

8. Install the SIMMs that you removed from the failed module into the same memory slots on the replacement module.

9. Ensure that the jumpers on the replacement module match the positions of the jumpers on the failed module. Figure 4–8 shows the jumper locations on the memory expansion module. Table 4–10 shows the correct jumper positions.

10. Place the failed memory module in an antistatic package.

Reverse the above procedure to install the memory module.

Table 4–10 Memory Expansion Module Jumpers

SIMM Size (MB) W1/W2/W3/W4 Jumper Position

2, 4, 8 1–2 16, 32 2–3

4–18 FRU Removal and Replacement

Figure 4–9 Memory Expansion Module Removal

Table 4–11 Key for Figure 4–9

Key Description

A Retaining bar B Memory expansion module

MR-0003-92DG

FRU Removal and Replacement 4–19

4.10 Replacing Option Modules

The following steps describe the removal procedure for option modules. Refer to Figure 4–10 and Table 4–12 during the procedure.

1. Shut down the system and unplug the power cord (Section 4.4).

2. Remove the cabinet top cover, left side panel, and card cage cover using the procedure in Section 4.5.

3. Disconnect any external cables attached to the option module I/O connections at the back of the system.

4. Disconnect any internal cables from the option module.

5. Remove the screw that secures the module. Save this screw.

6. Pull the failed option module from its slot and slide the module out of the card cage.

7. Place the module on top of an antistatic package, antistatic foam pad, or a grounded workstation surface.

8. Remove the replacement module from its antistatic package and place it on an antistatic package, antistatic foam pad, or a grounded workstation surface.

9. Ensure that the jumpers on the replacement module match the positions of the jumpers on the failed module.

10. Place the failed memory module in an antistatic package.

Install the replacement module into the same slot from which you removed the failed module. Reverse the above procedure to install the module.

4–20 FRU Removal and Replacement

DEC ApplicationDEC 400xP ApplicationDEC 400xP Service Guide

Specifications and Main Features

Frequently Asked Questions

User Manual