Digital PDFs

AA-PK29E-TE

June 1994

40 pages

Original

88.4kB

Document:	MicroVAX Diagnostic Monitor Release Notes
Order Number:	AA-PK29E-TE
Revision:
Pages:	40
Original Filename:	http://manx-docs.org/collections/mds-199909/cd1/vax/pk29ete.pdf

OCR Text

MicroVAX Diagnostic Monitor
Release Notes
Order Number: AA–PK29E–TE

These release notes describe restrictions, undocumented features, and
other essential information about the MicroVAX Diagnostic Monitor (MDM)
Version 5.0, Release 139. These release notes supersede all other MDM
documentation.

June 1994
Digital Equipment Corporation makes no representations that the use of its products in the
manner described in this publication will not infringe on existing or future patent rights, nor do
the descriptions contained in this publication imply the granting of licenses to make, use, or sell
equipment or software in accordance with the description.
Possession, use, or copying of the software described in this publication is authorized only
pursuant to a valid written license from Digital or an authorized sublicensor.
© Digital Equipment Corporation 1994. All Rights Reserved.
The following are trademarks of Digital Equipment Corporation: DEC, DECsystem, Digital,
InfoServer, KDA, MicroVAX, PDP–11, RC25, RCD, RCD50, RRD42, rtVAX, TK, ULTRIX, VAX,
VAX DOCUMENT, VAXELN, VMS, and the DIGITAL logo.
Other trademarks are as follows: OSF/1 is a registered trademark of Open Software Foundation,
Inc.
All other trademarks and registered trademarks are the property of their respective holders.
S2640

This document was prepared using VAX DOCUMENT Version 2.1.

Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

vii

1 Updates
General MDM Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2 MB System Support Restriction . . . . . . . . . . . . . . . . . . . . .
Operating Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Updates to Features and Functionalities . . . . . . . . . . . . . . . . . . .
MDM Network Boot from the InfoServer 100 via
CD–ROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.2
Booting from the TZ30 on the VAX 4000 Models 100, 100A,
and 105 Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.3
Booting MDM from a CD–ROM on the VAX 4000 Models
100, 100A, and 105 Systems . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.4
Booting MDM on VAX 4000 Models 100, 100A, 105, 200, 300,
400, 400A, 500, 500A, 600, 600A, and 700A Systems . . . . . . .
1.2.4.1
Booting from the SHAC on VAX 4000 Models 100, 100A,
105, 200, 300, 400, 400A, 500, 500A, 600, 600A, and
700A Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.4.2
Booting from the SGEC on VAX 4000 Models 100, 100A,
105, 200, 300, 400, 400A, 500, 500A, 600, 600A, and
700A Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.4.3
Booting from the TK50/70 Device on VAX 4000 Models
200, 300, 400, 400A, 500, 500A, 600, 600A, and 700A
Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.4.4
Booting from the KRQ50 Controller on VAX 4000 Models
200, 300, 400, 400A, 500, 500A, 600, 600A, and 700A
Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.4.5
Booting from the TF85 on VAX 4000 Models 200, 300,
400, 400A, 500, 500A, 600, 600A, and 700A Systems . . . .
1.2.4.6
Booting from the DEQNA, DELQA, and DESQA on VAX
4000 Models 100, 100A, 105, 200, 300, 400, 400A, 500,
500A, 600, 600A, and 700A Systems . . . . . . . . . . . . . . . .
1.1
1.1.1
1.1.2
1.2
1.2.1

1–1
1–1
1–1
1–1
1–1
1–2
1–2
1–3

1–3

1–4

1–4
1–4

1–4

iii

Booting MDM from a CD–ROM on the VAX 4000 Models
500A, 600A, and 700A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.6
Booting MDM on the DECsystem 5500 System . . . . . . . . . . .
1.2.6.1
Booting from the SGEC on the DECsystem 5500
System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.6.2
Booting from the DEQNA, DELQA, and DESQA on the
DECsystem 5500 System . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.6.3
Booting MDM from a CD–ROM on the DECsystem 5500
System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3
Enhanced Booting from TK50/TK70/TF85 . . . . . . . . . . . . . . . . . .
1.3.1
Standard Boot from TK50/70—for Systems with More than 5
MB of Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.2
Standard Boot from TF85—for Systems with More than 5
MB of memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.3
Solicitation Boot from TK50/TK70 . . . . . . . . . . . . . . . . . . . . .
1.3.4
Device Diagnostic Support . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.5
MDM System Notes and Updates . . . . . . . . . . . . . . . . . . . . .
1.3.6
TK50 Load Times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.7
Order Number Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.8
Automatic Distribution of Diagnostics . . . . . . . . . . . . . . . . . .
1.3.9
Debugging Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.10
MDM Boot Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4
MDM Diagnostic Notes and Updates . . . . . . . . . . . . . . . . . . . . . .
1.2.5

1–5
1–6
1–6
1–6
1–6
1–7
1–7
1–7
1–7
1–8
1–13
1–13
1–15
1–17
1–18
1–18
1–18

2 Problems and Corrections
2.1
Monitor Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.1
MDM Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.1.1
MDM Programmer’s Guide: Update on
DSL$GET_ENVIRONMENT Call . . . . . . . . . . . . . . . . . .
2.1.1.2
MDM Hard Disk User’s Guide: Update on Booting from
a SHAC Attached to a DSSI Controller . . . . . . . . . . . . . .
2.1.1.3
MDM Programmer’s Guide: Clarification in
DSL$Disable_Controller Description . . . . . . . . . . . . . . . .
2.1.2
Unsupported Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.3
Unsupported DSSI/KFQSA Test Configuration . . . . . . . . . . .
2.1.4
RF Boot Off DSSI Hangs After Reset Config/Config
Commands Issued . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Ctrl/C>> Stops the VCB02 . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.5
2.1.6
MDM Intermittently Configures the DFA01 as a DZQ11 . . .
2.1.7
uVDOS V4.0 Banner Does Not Appear on VAX 4000 Models
100 and 100A Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2
Diagnostic Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2–1
2–1
2–1
2–2
2–2
2–2
2–2
2–3
2–3
2–3
2–3
2–4

2.2.1
2.2.2
2.2.3
2.2.4
2.2.5
2.2.6
2.2.7
2.2.8
2.2.9
2.2.10
2.2.11
2.2.12
2.2.13
2.2.14
2.2.15
2.2.16

2.2.17

2.2.18
2.2.19
2.2.20

DSSI—Verify Test 4 Fails When the Drive Is Off Line . . . . . .
MIRA—Out of Range Input Causes Wait . . . . . . . . . . . . . . . .
RC25—nakdal—Functional Tests Can Give Fatal
Bugcheck . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DTQNA/nazqaa—Cumulative Pass Count as Printed is
Confusing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DZV11/nadzaf—Fails Exerciser Test 1 with DTQNA in
Config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ADV11D–A—Gets Fatal Bugcheck with Utility Tests 5 and
6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
KDA—Diagnostic Produces Fatal Bugcheck During Config if
Nonexistent CSR Is Used . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NALAA—LPS40 Fails Utility Test 2 . . . . . . . . . . . . . . . . . . .
NALAA—LPS40 Fails Utility Test 4 . . . . . . . . . . . . . . . . . . .
CXF32—Fails Utility Test 1 on MicroVAX 3500/3600
Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
VS550—Diagnostic Fails When Exercised with the TK70 . . .
DSIA—Diagnostic Prints Nonstandard "CR" Message When
Prompting User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
KDA50—Diagnostic Errors When Run for Extended Period
on rtVAX Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RQX05—Diagnostic Fails Intermittently in Service/Exerciser
Mode on MicroVAX II Systems . . . . . . . . . . . . . . . . . . . . . . . .
NASCAB—Diagnostic Errors When Run with RRD40 and
RRD42 on DECsystem 5500 Systems . . . . . . . . . . . . . . . . . . .
AXV11–CA—Diagnostic Fails to Set Individual CSR Bit
Correctly During Functional Test on VAX 4000 Models 400
and 500 Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
VCB02/DFA0/TK70—Produces a "Hang" During MDM Boot
with the VCB02 as a Console on VAX 4000 Model 500
Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
KFQSA—Produces Error During Functional Test on
MicroVAX 3800/3900 Systems . . . . . . . . . . . . . . . . . . . . . . . .
KXJ11—Diagnostic Fails During Functional Test on VAX
4000 Model 500 Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DPV11—Diagnostic Reports "Passed" Message During
Exerciser Test on VAX 4000 Model 400 Systems . . . . . . . . . .

2–4
2–4
2–4
2–5
2–5
2–5
2–6
2–7
2–7
2–7
2–7
2–7
2–8
2–8
2–8

2–9

2–9
2–9
2–10
2–10

Tables
1–1
1–2
1–3
1–4
1–5

Device Diagnostic Support . . . . . . . . . . . . . . . . . . . . . . . . . . .
TK Load Times (in minutes) . . . . . . . . . . . . . . . . . . . . . . . . .
Order Number Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Area Contacts for Diagnostic Distribution . . . . . . . . . . . . . . .
MDM Boot Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1–8
1–14
1–15
1–17
1–18

Preface
These release notes describe update information, enhancements, new features,
and bug fixes for the MicroVAX Diagnostic Monitor (MDM) Version 5.0, Release
139.

Intended Audience
These release notes are intended for the following people:
•

System managers who are installing MDM

•

Individuals responsible for maintaining MicroVAX systems

•

Diagnostic developers

Document Structure
These notes are organized as follows:
•

Chapter 1 lists updates.

•

Chapter 2 lists known problems and corrections.

Associated Documents
The following MDM documents are available:
•

MicroVAX Diagnostic Monitor Programmer’s Guide

•

MicroVAX Diagnostic Monitor Development Kit Installation Guide

•

MicroVAX Diagnostic Monitor User’s Guide

•

MicroVAX Diagnostic Monitor Ethernet Server User’s Guide

vii

viii

•

MicroVAX Diagnostic Monitor Hard Disk User’s Guide

•

MicroVAX Diagnostic Monitor Reference Card

•

MicroVAX Diagnostic Monitor Customer CD–ROM Booklet

•

MicroVAX Diagnostic Monitor Maintenance CD–ROM Booklet

1
Updates
This chapter updates information necessary to run the MicroVAX Diagnostic
Monitor (MDM) software.

1.1 General MDM Updates
This section updates hardware and installation requirements.

1.1.1 2 MB System Support Restriction
MDM Release 139 requires at least 2 megabytes (MB) of memory. The monitor
uses about 1.5 MB. If the memory requirements exceed the available memory,
MDM does not run.

1.1.2 Operating Environment
Users of the MDM Development Kit must install VAXELN Version 4.0 for use
with MDM Release 139.

1.2 Updates to Features and Functionalities
This section provides information on new MDM features and functionalities
that were added in recent releases.

1.2.1 MDM Network Boot from the InfoServer 100 via CD–ROM
The existing Customer and Maintenance Compact Discs can now be used to
boot MDM from the InfoServer 100. A ‘‘bundled’’ image, MDMNET.SYS, on the
existing compact discs can be used to accomplish this. It contains the MDM
CD–ROM bootable image and all the MDM diagnostics.
At least 5 MB of memory are required to boot MDM from the InfoServer 100.

Updates 1–1

Updates
1.2 Updates to Features and Functionalities
To downline load MDM from the InfoServer 100, take the following steps:
1. Load the MDM CD–ROM into the appropriate drive on the InfoServer 100.
2. Set up the InfoServer 100 to downline load:
•

SET SERVER STATE ON

•

SET SERVER MOP ENABLED

For more information, refer to the InfoServer System Operations Guide.
To boot MDM on the target system, use the solicitation boot request,
BOOT/100, for your appropriate Ethernet device (XQA0, ESA0, or EZA0), and
supply the file name MDMNET at the system prompt. For example:
>>> BOOT/100 EZA0
2...
Bootfile: MDMNET

1.2.2 Booting from the TZ30 on the VAX 4000 Models 100, 100A, and
105 Systems
The existing MDM TK50 Maintenance Kit supports booting from a TZ30
connected to the onboard SCSI. The boot command is as follows:
>>> BOOT MKAnnn
where nnn is the TZ30 port number. Enter the SHOW SCSI command to
display the port number.

1.2.3 Booting MDM from a CD–ROM on the VAX 4000 Models 100,
100A, and 105 Systems
MDM supports booting from an RRD42 connected to an onboard SCSI bus on
the VAX 4000 Model 100. A maintenance compact disc has been provided for
this purpose.
The boot command is as follows:
>>> BOOT/100 DKAnnn
where nnn is the boot number of the RRD42. (Enter the SHOW SCSI command
at the console prompt (>>>) to display the boot number.)
When the system requests the name of the bootfile, supply the name
[SYS0.SYSEXE]MDMCD.SYS, as in the following example:
Bootfile: [SYS0.SYSEXE]MDMCD.SYS

1–2 Updates

Updates
1.2 Updates to Features and Functionalities

1.2.4 Booting MDM on VAX 4000 Models 100, 100A, 105, 200, 300, 400,
400A, 500, 500A, 600, 600A, and 700A Systems
You can boot MDM on VAX 4000 Models 100, 100A, 105, 200, 300, 400, 400A,
500, 500A, 600, 600A, and 700A systems from either the Second Generation
Ethernet Controller (SGEC), from the Single Host Adapter Chip (SHAC), from
TK50/70, KRQ50, and TF85 devices, and over the network from the DEQNA,
DELQA, and DESQA.
Note
The SHAC is optional on the VAX 4000 Model 100 system.

1.2.4.1 Booting from the SHAC on VAX 4000 Models 100, 100A, 105, 200, 300, 400,
400A, 500, 500A, 600, 600A, and 700A Systems
You can boot MDM from an RF drive connected to the VAX 4000 Single Host
Adapter Chip (SHAC). You must first install the MDM Hard Disk Kit on device
DIA0: and use the MDMSHA.SYS bootable image. The boot command is as
follows:
>>> BOOT/100 DIAn
where n is the boot number of the SHAC drive.
Supply [SYS0.SYSEXE]MDMSHA.SYS when the system requests the bootfile
name, as in the following example:
Bootfile: [SYS0.SYSEXE]MDMSHA.SYS
1.2.4.2 Booting from the SGEC on VAX 4000 Models 100, 100A, 105, 200, 300, 400,
400A, 500, 500A, 600, 600A, and 700A Systems
You can boot MDM over a network by means of the Second Generation
Ethernet Controller (SGEC) with the H3604 cover panel. You must first
install the MDM Ethernet Maintenance Kit and use the NA18AW.SYS bootable
image. The boot command is as follows:
>>> BOOT EZA0

Updates 1–3

Updates
1.2 Updates to Features and Functionalities
1.2.4.3 Booting from the TK50/70 Device on VAX 4000 Models 200, 300, 400, 400A,
500, 500A, 600, 600A, and 700A Systems
The existing MDM TK50 Maintenance Kit supports booting from a TK50/70
device. The boot command is as follows:
>>> BOOT MUA0
There is no support for booting MDM from a TK50/70 on VAX 4000 Models
100, 100A, and 105 systems.
1.2.4.4 Booting from the KRQ50 Controller on VAX 4000 Models 200, 300, 400, 400A,
500, 500A, 600, 600A, and 700A Systems
To boot MDM from the KRQ50 controller, refer to the MicroVAX Diagnostic
Monitor Maintenance CD–ROM Booklet for instructions on handling and setup
procedures for your system. The boot command is as follows:
>>> BOOT/100 DUxn
2...
Bootfile: [SYS0.SYSEXE]MDMCD.SYS
where x is the drive controller port letter, and n is the drive controller unit
number.
1.2.4.5 Booting from the TF85 on VAX 4000 Models 200, 300, 400, 400A, 500, 500A,
600, 600A, and 700A Systems
You can boot MDM, load diagnostics from the TF85 on the SHAC, and run
them on VAX 4000 Models 200, 300, 400, 400A, 500, 500A, 600, 600A, and
700A systems by using the existing TK50/70 kit.
The command to boot MDM from a TF85 drive on the SHAC is as follows:
>>> BOOT MIAn
where n is the TF85 controller port number.
1.2.4.6 Booting from the DEQNA, DELQA, and DESQA on VAX 4000 Models 100,
100A, 105, 200, 300, 400, 400A, 500, 500A, 600, 600A, and 700A Systems
The MDM kits that support the DEQNA, DELQA, and DESQA bootable images
are distributed as part of the Ethernet Server Kit. The bootable images are
NA06AW.SYS and NA07AW.SYS. NA07AW.SYS tests the load device. The boot
command is as follows:
>>> BOOT XQA0

1–4 Updates

Updates
1.2 Updates to Features and Functionalities

1.2.5 Booting MDM from a CD–ROM on the VAX 4000 Models 500A,
600A, and 700A
MDM supports booting from an RRD40/42 connected to an onboard Small
Computer Systems Interface (SCSI) bus on the VAX 4000 Models 500A, 600A,
and 700A systems. A maintenance compact disc has been provided for this
purpose.
The boot command is as follows:
>>> BOOT DKAnnn
where nnn is the boot number of the RRD40/42. (Enter the SHOW DEVICE
command at the console prompt (>>>) to display the boot number.)

Updates 1–5

Updates
1.2 Updates to Features and Functionalities

1.2.6 Booting MDM on the DECsystem 5500 System
You may boot MDM from the network from the SGEC, the DEQNA, DELQA,
and DESQA, and a CD–ROM.
1.2.6.1 Booting from the SGEC on the DECsystem 5500 System
The MDM kit that supports the SGEC bootable images is distributed as
part of the Ethernet Server Kit. You must first install the MDM Ethernet
Maintenance Kit and then use the NAU07AW.SYS bootable image.
The boot command is as follows:
>>> BOOT EZA0
1.2.6.2 Booting from the DEQNA, DELQA, and DESQA on the DECsystem 5500
System
The MDM kits that support the DEQNA, DELQA, and DESQA bootable images
are distributed as part of the Ethernet Server Kit. The bootable images are
NA06AW.SYS and NA07AW.SYS. NA07AW.SYS tests the load device.
The boot command is as follows:
>>> BOOT XQA0
1.2.6.3 Booting MDM from a CD–ROM on the DECsystem 5500 System
MDM supports booting from an RRD4x connected to an onboard Small
Computer Systems Interface (SCSI) bus on a DECsystem 5500. A maintenance
compact disc has been provided for this purpose.
The boot command is as follows:
>>> BOOT/100 DIAn
where n is the boot number of the RRD4x. (Enter the SHOW SCSI command
at the console prompt (>>>) to display the boot number.)
When the system requests the name of the bootfile, supply the name
[SYS0.SYSEXE]MDMCD.SYS, as in the following example:
Bootfile: [SYS0.SYSEXE]MDMCD.SYS

1–6 Updates

Updates
1.3 Enhanced Booting from TK50/TK70/TF85

1.3 Enhanced Booting from TK50/TK70/TF85
MDM has enhanced booting from the TK50/TK70/TF85 by using the bundled
image NA21Cx (for the Customer kit) and NA22Cx (for the Maintenance kit)
as the primary boot image, where x is the revision letter of the image.
This requires a minimum of 5 MB of memory as the bundled image is
approximately 7,500 blocks. The enhancement is virtually transparent as no
additional setup procedure is required. However, if you boot from TF85 you
cannot use the solicitation boot request. The following sections describe which
boot request to use depending on your boot device and the memory capacity of
your system.

1.3.1 Standard Boot from TK50/70—for Systems with More than 5 MB
of Memory
To perform a standard MDM boot from a TK50/70, issue the standard boot
command:
>>> BOOT MUA0
This uses the bundled image NA21Cx (for the Customer kit) and NA22Cx
(for the Maintenance kit) as the boot image. This is particularly useful for
those systems with more than 5 MB as it significantly reduces load times for
diagnostics.

1.3.2 Standard Boot from TF85—for Systems with More than 5 MB of
memory
To perform a standard MDM boot from TF85, issue the standard boot
command:
>>> BOOT MIAn
where n is the TF85 controller port number.
This uses the same files as the TK50/TK70 boot. It is particularly useful for
those systems with more than 5 MB as it significantly reduces load times for
diagnostics.

1.3.3 Solicitation Boot from TK50/TK70
For those systems with less than 5 MB, use the solicitation boot request:
>>> BOOT/100 MUA0

Updates 1–7

Updates
1.3 Enhanced Booting from TK50/TK70/TF85
Supply MDM.SYS when the system requests the bootfile name, as in the
following example:
Bootfile: MDM.SYS
This procedure uses NA04Cx.SYS as the boot image, where x is the revision
letter of the file.
Loading and configuring diagnostics is much slower in this procedure.

1.3.4 Device Diagnostic Support
Table 1–1 provides updates on device support.
Table 1–1 Device Diagnostic Support
Controller

Device

Revision

File Name

CPU

KA620

NAKAA

MS220

NAMSC

MS630

NAMSA

MS650

NAMTA

MS670

KA630
KA640
KA650
KA655
KA670
KA675
KA680
KA681
KA690
KA691
KA692
KN210
KN220
KA52
MEMORY

NAMSB
(continued on next page)

1–8 Updates

Updates
1.3 Enhanced Booting from TK50/TK70/TF85
Table 1–1 (Cont.) Device Diagnostic Support
Controller

Device

Revision

File Name

NALPA

NARXA

NAKDA

MS690
LPV11 & LPV11SA

LP25
LP26
LP27
LG01
LG02

RQDX2 & RQDX3

RX50
RD32
RX33
RD52
RD53
RD54

KDA50–Q & KLESI

RA60
RA70
RA81
RA82
RA90

KLESI

RC25

TQK50

TK50

NATKA

TQK70

TK70

NATKA

DEQNA

–

NAXQA

DELQA

–

NAXQA

DESQA

–

NAXQA

DLV11

–

NADLA

DZQ11 & DZV11

–

NADZA

DRV11–WA

–

NADRA

DRV11–J

–

NADRB

DPV11

–

NADPA

DMV11

–

NADMA
(continued on next page)

Updates 1–9

Updates
1.3 Enhanced Booting from TK50/TK70/TF85
Table 1–1 (Cont.) Device Diagnostic Support
Controller

Device

Revision

File Name

KRQ50

RRD40

NARRA

RRD50
KMV11A (KMV1A)

–

NAKMA

KMV11B (KMV1B)

–

NAKMB

IEQ11

–

NAIEA

NADHA

NADFA

DHQ11
CXY08

–

CXA16

–

CXB16

–

CXF32

–

DHF11

–

DHV11

–

DFA01

–

VCB01

–

NAVCA

ADV11–DA

–

NAADA

AAV11–DA

–

NAAAA

AAV11–C

–

NAAAC

ADV11–C

–

NAADC

AXV11–C

–

NAAXA

VCB02

–

NAVCB

DSV11

–

NADSA

VSV11

VSV21–AA

NAVVA

NADQA

VSV21–CA
VSV90
DRQ11–C

–

LNV11

–

NALAA

LNV11–A

–

NALNA

KLESI

TU81

NATUA

TU81E
(continued on next page)

1–10 Updates

Updates
1.3 Enhanced Booting from TK50/TK70/TF85
Table 1–1 (Cont.) Device Diagnostic Support
Controller

Device

Revision

File Name

TSV05

TS05

NATSA

DRQ3B

–

NAQBA

IBQ01

–

NAIBA

IAV11–A

–

NAIAA

IAV11–B

–

NAIAB

IDV11–A

–

NAIDA

IDV11–B

–

NAIDB

IDV11–C

–

NAIDC

IDV11–D

–

NAIDD

MIRA

–

NAMIA

KXJ11

–

NAKXA

ADQ32

–

NAAQA

KLESI

RV20

NARVA

DESNA

–

NACQA

DTC–04

–

NADTA

DTC–05

–

NADTB

IGQ11

–

NAIGA

KWV11–C

–

NAKWA

KWV11–W

–

NAKWB

POLARSTAR

–

NAQCA

GS03–WD–DHV11

–

NAGSA

GS03–WD–DQZ11

–

NAGSB

GS03–WD–CXY08

–

NAGSC

LANCE

–

NALAN

SGEC

–

NASGA

DSSI

RF30

NADSI

RF71
TF85
SHAC

RF30

NASHA
(continued on next page)

Updates 1–11

Updates
1.3 Enhanced Booting from TK50/TK70/TF85
Table 1–1 (Cont.) Device Diagnostic Support
Controller

Device

Revision

File Name

–

NAVSA

RF30

NAKFA

RF31
RF35
RF36
RF71
RF72
RF73
RF74
TF85
TF857
EF51
EF52
EF53
VS550
KFQSA

RF31
RF35
RF36
RF71
RF72
RF73
RF74
DIV32

NADIA

KWV32

NAKWC

DELIX1

–

NADXA

RQX05

–

NARQA

KZQSA

RRD40

NAKZA

RRD42
1 Indicates diagnostics that are included on the media, but are not supported in the auto-

configuration information. To use these diagnostics, you must use the custom configuration
commands.

(continued on next page)

1–12 Updates

Updates
1.3 Enhanced Booting from TK50/TK70/TF85
Table 1–1 (Cont.) Device Diagnostic Support
Controller

Device

Revision

File Name

NASCA

TLZ04
TLZ06
TSZ07
RWZ01
TKZ60
SCSI

RRD40
TLZ04
RZ22
RZ23
RZ24
RZ55
RZ56
RZ57
RZ58

DTQNA

–

NAZQA

DWQVA

–

NADWQ

DEQRA

–

NAQRA

DEFQA

–

NADFQ

1.3.5 MDM System Notes and Updates
A Software Performance Report (SPR) form is in each kit. SPRs inform
software developers as soon as possible about problems found in the product,
and provide users a way to offer suggestions based on actual use of the product.

1.3.6 TK50 Load Times
Table 1–2 is a chart of TK50 and TK70 load times for MDM releases 114
through 131. Load times, in any configuration, are not available for MDM
Release 139. Load time is how long a system needs to load and configure the
diagnostics for the individual devices in the system. The listed times do not
include the length of time needed for the monitor to load initially (the elapsed
time from the boot command to the display of the disclaimer).

Updates 1–13

Updates
1.3 Enhanced Booting from TK50/TK70/TF85
Table 1–2 TK Load Times (in minutes)
Release

TK50

TK70

TK50

(Config 1 )

TK70

TK50

(Config 2 )

TK70
(Config 3 )

TK50

TK70

(Config 4 )

114