Updated: 24-SEP-2003 (Use your browsers' Reload button to ensure you're viewing the most recent version)
VAXTTDR02_061 VAX TTDRIVER ECO Summary
Copyright (c) Digital Equipment Corporation 1994, 1995. All rights
reserved.
OP/SYS: OpenVMS VAX
COMPONENT: TTDRIVER
SOURCE: Digital Equipment Corporation
ECO INFORMATION:
ECO Kit Name: VAXTTDR02_061
ECO Kits Superseded by This ECO Kit: VAXTTDR01_061 (CSCPAT_1103)
VAXTTDR01_060
ECO Kit Approximate Size: Saveset A - 72 Blocks
Saveset B - 90 Blocks
Saveset C - 90 Blocks
Total of n files - 252 Blocks
NOTE: This ECO kit may cause printout corruption on DEClaser printers.
Using 'SET TERMINAL / PASTHRU' will resolve the issue.
ECO KIT SUMMARY:
An ECO kit exists for TTDRIVER on OpenVMS VAX V6.0 through V6.1. This kit
addresses the following problems:
o Move IRPW_BCNT going negative fix to include more code
Problem Description:
Users are unable to use the third party package IRIS. This
3rd party code is a mid-driver, meaning it is between the
terminal class driver and the port driver. The driver uses
the IRP$W_BCNT field which is negative (FFFx), causing a fatal
bugcheck (SSRVEXCEPT).
Problem Analysis:
This problem was fixed V6.1 for the terminal driver, but a 3rd
party is looking at the byte count before the field is
cleared. The problem is caused by a noisy line and a bad
escape sequence termination.
PROBLEMS ADDRESSED IN VAXTTDR01_061 KIT
o Fix terminal display wrap problem on some escape sequences.
Problem Description:
When using the DCL command SEARCH, with the default /highlight
switch, the line does not wrap at the correct position on the
terminal screen.
Problem Analysis:
The problem was with the way the TTdriver handled escape
sequences. Before this fix, if an escape sequence was in the
output stream, the cursor position would be zeroed.
PROBLEMS ADDRESSED IN VAXTTDR01_060 KIT
o System crashes if IRP$W_BCNT goes negative.
Problem Description:
The user will see a FATAL bugcheck (SSRVEXCEPT) in routine
IO_POST (in MOVBUF), because the IRP$W_BCNT field is negative
(FFFx) and tries to copy 64k of buffer space.
Problem Analysis:
If all of the following occur:
- A port has the characteristics /EDITING, and /ESC
- A process issues a READ with prompt and the prompt length = zero
to that port
- The recall buffer has a CTRL character, like a CTRL I (tab), in it.
- The data inputted has an escape sequence that is terminated with a
CTRL B (command recall).
- The process can except a READ of length 64k bytes.
then, the process will crash trying to copy the buffer.
o 6.2 System crash in CTRLAST because of corrupted AST list.
Problem Description:
The user will see a FATAL bugcheck (SSRVEXCEPT) in routine
CTRLAST (in module TTYFDT.MAR), because the CTRL list pointed
to by R7 has been emptied while inserting an entry. This
occurs because the call to COM$SETATTNAST was done at IPL 2
and an interrupt occurred.
Problem Analysis:
This problem occurs because the device lock was not taken out
when calling COM$SETATTNAST. The fix is simply to take out
the device lock before calling COM$SETATTNAS.
o Change TEST_PRIVS to use physical UCB.
Problem Description:
The user may see the following error message when setting
terminal characteristics, even though there is really no
error:
-SYSTEM-F-NOLOG_IO, operation requires LOG_IO privilege
The problem is that the logical UCB is used instead of the
physical UCB when comparing the baud rate.
This problem can only occur when virtual terminals are enabled
and the port is set to /DISCONNECT and /NOSET_SPEED.
Problem Analysis:
The virtual UCB is used instead of the physical UCB.
The fix is to use the physical UCB instead of the virtual UCB.
If there is no physical UCB, then the request of the baud rate
is disregarded. Also the FORK lock is acquired to make sure
the logical UCB is not being disconnected from the physical
UCB during this check.
RELATED ARTICLES:
Detailed articles describing the problems listed above may exist
in the OpenVMS database. To view these articles, open the
appropriate product database and perform a query using either of
the following search strings: 'VAXTTDR02_061' or 'VAXTTDR'.
ECO KIT ORDERING INSTRUCTIONS:
If after an evaluation you wish to obtain this kit, request it
electronically using the appropriate Advanced Electronic Services (AES)
Service Tool. If you are not familiar with how to request kits
electronically, open the DIA, WIS or DSNLINK database and review the
article entitled:
[AES] How To Electronically Request ECO Kits Using Service Tools
INSTALLATION NOTES:
In order for the corrections in this kit to take effect, the system
must be rebooted. If the system is a member of a VAXcluster, the entire
cluster should be rebooted.
==========================================================================
Table of Kit Image Information |
|
