Updated: 24-SEP-2003 (Use your browsers' Reload button to ensure you're viewing the most recent version)
VAXTTDR09_U2055 Terminal Driver V5.5-5.5-2H4 ECO Summary
Copyright (c) Digital Equipment Corporation 1994. All rights reserved.
OP/SYS: OpenVMS VAX
COMPONENTS: Terminal Driver (TTDRIVER.EXE)
SOURCE: Digital Equipment Corporation
ECO INFORMATION:
ECO Kit Name: VAXTTDR09_U2055
ECO Kits Superseded by This ECO Kit: VAXTTDR08_U2055
VAXTTDR07_U2055
VAXTTDR05_U2055
TTDRV$01_U2055
ECO Kit Approximate Size: 108 Blocks
Kit Applies To: OpenVMS VAX V5.5, V5.5-1, V5.5-2, V5.5-2H4
System Reboot Necessary: Yes
NOTE: OpenVMS VAX V5.5-2H4 is a limited hardware release, shipped only
with the new systems (or system upgrades) listed below. It is not
separately orderable and will not be distributed via Consolidated
Distribution.
o VAX 4000 Model 100A
o VAX 4000 Model 500A
o VAX 4000 Model 600A
o VAX 4000 Model 700A
ECO KIT SUMMARY:
An ECO kit exists for TTDRIVER on OpenVMS VAX V5.5 through V5.5-2H4. This
kit addresses the following problems:
PROBLEMS ADDRESSED IN VAXTTDR09_U2055 KIT
o BCNT problem for SMART READ.
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).
This problem is fixed in 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 VAXTTDR08_U2055
o When the DCL SEARCH command is used with the /HIGHLIGHT qualifier
(which is the default), the line does not wrap at the correct
position on the terminal screen.
o Data Terminal Ready De-assertion takes more than 2 seconds on Modem
Control.
o The time between the De-assertion of Carrier Detect (CD) and Data
Terminal Ready (DTR) is greater than the 2 seconds recommended for
modem control.
This problem is fixed in OpenVMS VAX V6.0.
o SSRVEXCEPT occurs in routine IO_POST (in MOVBUF) because the
IRP$W_BCNT field is negative (FFFx) and tries to copy 64k of buffer
space.
This problem is fixed in OpenVMS VAX V6.1.
o INVEXCEPTN bugcheck occurs at TTDRIVER+2554. This problem is caused
by POSIX related code in the TTDRIVER.
This problem is fixed in OpenVMS VAX V6.1.
o INVEXCEPTN bugcheck occurs with the PC equal to
SCH$RELEASE_CAPABILITY+0066. This problem is also caused by POSIX
related code in the TTDRIVER.
This problem is fixed in OpenVMS VAX V6.1.
o Carrier (CAR) modem signal is dropped at the wrong time and is not
reset properly.
This problem is fixed in OpenVMS VAX V6.1.
o TTDRIVER fork routines 'LINKFORK' and 'UNLINKFORK' do not require the
devicelock needed. This can corrupt the Unit Control Block (UCB).
This problem is fixed in OpenVMS VAX V6.1.
o The typeahead buffer is not cleared when the port is reset.
This problem is fixed in OpenVMS VAX V6.1.
o The Asian fields are not cleared when the port is reset.
This problem is fixed in OpenVMS VAX V6.1.
o The modem signals in TTY$SETUP_UCB are not reset properly.
This problem is fixed in OpenVMS VAX V6.1.
o R4 register corruption.
This problem is fixed in OpenVMS VAX V6.1.
o IPL 6 corruption.
This problem is fixed in OpenVMS VAX V6.1.
o TTDRIVER allows the user to set a port to COMMSYNC even if the port
does not support modem signals. This can cause the port to hang.
This problem is fixed in OpenVMS VAX V6.1.
RELATED ARTICLES:
Detailed articles describing the problems listed above may exist in the
OPENVMS and POSIX databases. To view these articles, open the appropriate
product database and perform a query using either of the following search
strings: 'VAXTTDR09_U2055' 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 |
+----------------------------+----------+-----------------+--------------+
| | Overall | Image File | Image Link |
| Image Name | Checksum | Identification | Date/Time |
+----------------------------+----------+-----------------+--------------+
| TTDRIVER.EXE |%X1A5D961E| X-19 | 6-OCT-1994 |
| | | 19:34:35.79 |
+----------------------------+----------+-----------------+--------------+
|
