CRT(TM) 4.0.9 (Official) -- October 16, 2003 Copyright © 1995-2003 VanDyke Software, Inc. All rights reserved. This file contains a CRT product history. It includes lists of new features, changes, and bug fixes sorted by release. For a product description, installation notes, registration information, and contact information, please refer to Readme.txt (downloaded with this installation). Changes in CRT 4.0.9 (Official) -- October 16, 2003 --------------------------------------------------- Bug fixes: - Some printer drivers returned a null pointer as the printer port name, which caused CRT to crash at start up. - Serial: CRT sometimes disconnected when there was a serial error. Changes in CRT 4.0.8 (Official) -- August 19, 2003 -------------------------------------------------- Changes: - Added a global INI file-only option "EnableFontSmoothing" to specify whether or not ClearType fonts should be rendered as ClearType under Windows XP. Bug fixes: - In VT220 emulation, certain "non-printable" characters were being displayed as they would be for Linux emulation, which resulted in strange output when using a standard VT font. - In the Session Options dialog, leading spaces are now stripped from the Hostname field. - CRT can now be associated with Telnet URLs. - After upgrading from CRT 3.4, CRT 4.0 was not finding the old configuration path location. Changes in CRT 4.0.7 (Official) -- June 19, 2003 ------------------------------------------------ Changes: - Under Windows XP, when a ClearType font is used as the session font, it is not rendered as a ClearType font so that the characters display correctly in the session window. - Changed the session printer font selection to allow both printer fonts and screen fonts. Bug fixes: - In Wyse 60 emulation, CRT was clearing the PROTECTED state when it received character attribute escape sequences (e.g., DIM, BLINK, REVERSE). - If the option to add the command-line tools directory to the path was selected in the installer, the directory was added to the path multiple times on multiple installs. - If a session INI file from a CRT installation prior to 3.4 was used and a keyboard emulation other than "Default" was used, the alternate keyboard emulation would be incorrectly unchecked on the session Emulation page. - In a custom menu, the STRINGTABLE entry for tooltip or status bar text could not be overridden for built-in commands. Changes in CRT 4.0.6 (Official) -- April 17, 2003 ------------------------------------------------- Bug fixes: - With the Microsoft Hebrew or East Asian (CJKV) language packs installed, line-drawing characters were being incorrectly displayed. As a workaround, a session INI file-only option, "Use Unicode Line Drawing", was added. When this option is enabled, the current font's graphics characters are mapped to Unicode line-drawing characters. - Find did not correctly match some strings with repeated characters. For example, if the search string was "abc", the string "abcc" would not be found. - Changes made to any of the printer settings in the "Print Setup" dialog were not saved. Changes in CRT 4.0.5 (Official) -- April 3, 2003 ------------------------------------------------ Changes: - Added handlers for the Wyse 50 80/132 column switching escape sequences. - Added support for the Wyse 60 answerback request escape sequence. - the CRT log file is now readable by other Windows applications while CRT is running. Bug fixes: - Attempting to open several connections to the same CRT session with a logon script defined resulted in an error. - In Wyse 50/60 emulation, when clearing unprotected characters with spaces or other characters, protected characters were not being honored. Changes in CRT 4.0.4 (Official) -- February 20, 2003 ---------------------------------------------------- Changes: - Transferring files using bulletin board Zmodem implementations caused CRC errors with implementations that did not understand DEL encoding. Added session option "Zmodem Encodes DEL". - Added support for 32-bit CRCs when performing Zmodem transfers. Bug fixes: - CRT could crash when the Raw Log Session option was enabled and there was heavy network traffic. - The "/pos" command-line option was not honoring negative pixel positions. - The Select Menu Toolbar File dialog was a Save dialog rather than an Open dialog, which resulted in SecureCRT trying to save the custom menu file rather than open it when selecting a custom menu file to use. Changes in CRT 4.0.2 (Official) -- December 3, 2002 --------------------------------------------------- Changes: - Changed the printer font selection to allow both printer fonts and screen fonts. This allows line drawing characters to be printed. Changes in CRT 4.0.1 (Official) -- November 7, 2002 --------------------------------------------------- Changes: - Added support for UTF-8 output. RedHat 8.0 shipped with UTF-8 as their default output encoding and this caused problems with the display of some characters in CRT. Bug fixes: - Using the SAM tool on HP-UX resulted in screen artifacts due to an emulation error related to the handling of the cursor position. - CRT crashed on exit if "Close on disconnect" was turned on. - Wyse emulations failed to line wrap when using certain applications like vi. - When dumping binary output to a printer in raw mode over a Telnet connection, CRT did not strip NULs after carriage returns. - When top and bottom margins were set, the wrong lines were added to the scrollback history. Changes in CRT 4.0 (Official) -- October 8, 2002 ------------------------------------------------ - No changes. Changes in CRT 4.0 (Beta 7) -- September 26, 2002 ------------------------------------------------- Bug fixes: - Xmodem uploads caused CRT to hang if the receiver failed to acknowledge the EOT. Changes in CRT 4.0 (Beta 6) -- September 12, 2002 ------------------------------------------------- New features: - Session and global options for configuring the serial port when using direct pass-through printing. - Support for multiple pages when using Wyse 60. - Support for printing when using Wyse 50/60. Changes: - Added support for passing empty strings to scripts when using the /ARG switch on the command line. Bug fixes: - CRT had a resource leak that could result in the error "No fonts installed" being displayed after resizing the CRT window. - CRT could display blank dialogs or crash when using TAPI as the protocol. Changes in CRT 4.0 (Beta 5) -- August 29, 2002 ---------------------------------------------- Changes: - Added "reverse" pass-through printing so that output can be captured from a COM port and passed through to a Telnet session. Bug fixes: - If both the global option "Use auto session" and the session option "Close on disconnect" were set and the default session's host was not accepting connections, CRT started and then immediately exited. - In Wyse 50/60 emulation, line drawing characters were displayed as spaces. Changes in CRT 4.0 (Beta 4) -- August 13, 2002 ---------------------------------------------- New features: - The License Wizard reads license information from the clipboard if that information is present. Changes: - The Zmodem upload list now allows the specified files to be transferred as ASCII. - Added a ZmodemUploadAscii scripting interface which causes the files in the Zmodem upload list be transferred as ASCII. - Modified the Keymap Editor to allow keys to be disabled. - Added support for line drawing in Wyse 50 emulation. - Wyse 50 emulation now supports the " ;" sequence. - CRT's application icons now use the color red to indicate when the current session is not connected. Bug fixes: - Sometimes the current session options were not correctly saved when CRT exited. - Zmodem uploads hung when the user did not have read access to the file being uploaded. Changes in CRT 4.0 (Beta 2) -- July 23, 2002 -------------------------------------------- Changes: - Handle the escape sequence ESC [ ? 1 i, which prints the current line. Bug fixes: - The built-in Wyse 50/60 keymaps mapped the CTRL keys and the function keys to the wrong values. - Telnet and rlogin: Sessions could display an unformatted error. - Serial: DTR flow control should have defaulted to handshake when DSR flow was enabled - If the auto reconnect option was on, the session would reconnect after a manual disconnect. - Changed the default VT100 keymap from "VT100" to "Default". - When using SOCKS 5 with client authentication, an error dialog was infinitely displayed if the username or password were incorrect. - CRT could hang when launching the Opera web browser. - Administrative options were ignored if they were in the old registry location. - Fixed a highlighting problem in Wyse 50 emulation. Changes in CRT 4.0 (Beta 1) -- July 2, 2002 ------------------------------------------- New features: - Basic Wyse 50/60 emulation. - Customizable toolbar and menu bar support. - Minimal character set mapping (character sets supported include: EUC-JP). - Selecting and printing of multi-byte characters. - The /ARG command-line option added to support passing arguments to scripts. - The Sleep() scripting function is now supported. - Improved support for the JAWS screen reader. - Added Most Recently Used Sessions list to Activator menu. - New improved Zmodem transfer dialog. - Config file-only support has been added to configure serial pass-through printers. Changes: - To improve compatibility, Xmodem now defaults to packets of 128 bytes. - Added mappings for SHIFT+PGUP and SHIFT+PGDN to Linux keymap. - Restored pre-3.4 ability to set logical and physical window sizes independently. - ANSI emulation now handles ENQ. Bug fixes: - Attempts to underline text by overprinting during pass-through printing failed to show other than the last character output to each character position. - Serial: A number of minor bug fixes related to DTR/DTS handling. - Auto reconnect would continue after receiving a Windows shutdown command. - A terminal reset would not clear VT_HOLD_SCREEN. - Changing the keyboard emulation could result in the path of the custom keymap file being blanked. - A crash could occur when CTRL+C was entered in an unconnected window. - A script that calls Disconnect() followed by an immediate call to Connect() could cause CRT to crash.