CRT(TM) 6.1.4 (Official) -- February 24, 2009 Copyright (C) 1995-2009 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 6.1.4 (Official) -- February 24, 2009 ---------------------------------------------------- Bug fixes: - If a custom menu file that contained MENU_SCRIPT_MRU_FILE1 was used, selecting a script from the recently used script list could launch the wrong script. - If the "User Arranged Tree" option was set in the Connect dialog and sessions were rearranged, the changes were not saved. - If two sessions had different color schemes and a session was sent to a new window, and then a session was dragged into the other window, it had the first tabbed session's color scheme. - Selecting "Print Setup" from the File menu always displayed the printer settings for the first tabbed session. - RLogin: RLogin sessions could disconnect after a large amount of data was received. Changes in CRT 6.1.3 (Official) -- December 2, 2008 --------------------------------------------------- Bug fixes: - CRT could crash if the "Auto reconnect" option was set and the username was changed when attempting to connect to a server that does not allow the username to change. - If the INI-file-only global option "Disable Close" was set and CRT was closed using the red "X", CRT hung. - If a script was specified on the command line and the "Show connect dialog on startup" option was set, the Connect dialog was displayed. - If there was an error during script recording and the error message was longer than 64K, the message could not be displayed. Changes in CRT 6.1.2 (Official) -- November 6, 2008 --------------------------------------------------- Bug fixes: - If a script was specified on the command line, CRT was in a hung state after the script executed. - With ANSI color enabled, if a color escape sequence was received, only the portion of the row that contained characters was correctly displayed. Changes in CRT 6.1.1 (Official) -- October 2, 2008 -------------------------------------------------- Bug fixes: - If the auto-reconnect option was set for a session and the connection was lost, an error dialog was displayed. The 5.5 behavior of not displaying a dialog was restored. - If the session option "Display logon prompts in terminal window" was not set and a logon script was specified, the script was started before the connection was established. The 6.0 behavior of starting the script after the connection is established was restored. - Logon scripts were run when the administrative option to disallow scripts from being run in CRT was set. - If the global option "Show confirm disconnect dialog" was set and multiple sessions were open in different windows, exiting the Activator could cause CRT to crash. - CRT crashed when cancelling out of the select log file dialog if the session tab no longer existed. - In the Connect dialog, doing a Find Next after deleting a session that had been found using Find caused CRT to crash. - In the Global Options dialog, on the Firewall page, double- clicking the empty space below the firewall list or pressing the DEL key when no firewall was selected caused CRT to crash. - After answering "No" to the confirm disconnect dialog, CRT became unresponsive. - Under certain circumstances, if there were multiple CRT windows and the menu bar was toggled, CRT could become unresponsive. - After selecting text in the scrollback buffer using a triple- click, it was no longer possible to select text in the scrollback buffer. - If the CRT window was maximized after scrolling up, garbage was displayed in the session window. - If an "exit" command was sent to a session in a script and then another connection was immediately attempted, it could cause the script to hang. - If a session was connected using the Session.Connect(/s ) scripting method, the initial position specified in the session options was not honored. Changes in CRT 6.1 (Official) -- August 21, 2008 ------------------------------------------------ Bug fixes: - Under certain circumstances, CRT could not write log files to a mapped drive. - Under certain circumstances, when Quick Connect was used to make multiple connections, the authentication dialog was associated with the initial session window. - If nothing had previously been typed into the session window, pressing ALT+ sent the number to the session rather than switching to the specified tab. - When Windows was configured to use large fonts (120 DPI), some text in the Session Options dialog did not fit in the dialog. - If a URL that spanned multiple lines had extra spaces at the end of a line, the extra spaces were not removed when the URL was opened. - Serial: After a serial session was disconnected, the tab connec- tion status indicator was not updated to reflect that the session had been disconnected. Changes in CRT 6.1 (Beta 4) -- July 31, 2008 -------------------------------------------- Bug fixes: - CRT crashed when running a script that attempted to connect to multiple sessions. - Calling Config.GetOption("Password") in a script caused CRT to crash. - After calling the script Session object method Connect, execution of the script continued regardless of whether or not authentication had completed. - When the global option "CTRL+TAB switches to most recently used tab" was set, pressing CTRL+TAB cycled between all the tabs rather than going to the most recently used tab. - Under certain circumstances, launching CRT caused MFC80U.dll errors to be reported in the Windows Event Viewer. - Serial: After sending CTRL+C to a serial device, CRT hung. Changes in CRT 6.1 (Beta 3) -- July 17, 2008 -------------------------------------------- Bug fixes: - CRT crashed when the Script menu option was selected if the Recent Script list contained at least six items. - Leading spaces were removed when copied from the terminal window to the clipboard. - When a second session was started in a new maximized window, the logon prompt was displayed part way down the screen. - Under certain circumstances, if CRT was started and then maximized, the logon prompt was not visible. - When custom log data was specified, long lines were wrapped in the log file. - If a session was reconnected while minimized and then it was restored, the size would be different. - The Activator used a different configuration folder than CRT when CRT specified the /F command-line option. - When the custom menu (.MNU) option MENU_TAB_LIST1 was used, the menu did not display the list of tabbed sessions. - RLogin: CRT could crash when an RLogin session was disconnected. - TAPI: CRT crashed when the remote host was VMS and the session was disconnected by logging off the host machine. Changes in CRT 6.1 (Beta 2) -- July 2, 2008 ------------------------------------------- Bug fixes: - If CRT was running during an upgrade install, the installer continued to report that a file was in use after CRT was closed and Retry was selected. - The installer did not handle the answer file option INSTALLATION_PROFILE. Changes in CRT 6.1 (Beta 1) -- June 19, 2008 -------------------------------------------- New features: - Added the ability to search sessions and folders in the Connect dialog, which supports searching for a session name, hostname, folder name, or a keyword in the description. - Added items to the File menu to reconnect all disconnected sessions and disconnect all connected sessions. - Added support for an unlimited number of automated logon Expect/Send sequences and the ability to delete and reorder the sequences. - Added scripting support for sending special keys such as function keys, control keys, and other special characters, which makes it easier to write scripts that are protocol and emulation independent. - Added Clipboard scripting functions provide access to the current selected text and also to available Clipboard data, which allows setting up actions such as running a script that uses the contents of the Clipboard to send a command to the session, or selecting text in the session and running a script which launches a web browser to google that text. - Added scripting support for accessing session options, which makes it possible to do operations such as configuring a session before connecting and converting session information stored in a file to saved sessions. - Added error handling methods to the Application scripting object. The new methods GetLastError and GetLastErrorMessage provide flexibility to how errors are handled in scripts. - The script method Connect can be called without arguments in order to reconnect a session. Changes: - When the "Single Instance" and "Launch New Windows in a Separate Process" options are set, sessions cannot be opened in a separate window. - The serial port can now be changed in the Default session. - Added read access to the crt.FileTransfer.ZmodemUploadAscii property. Bug fixes: - When the session option "Retain size and font" was set, if the window was resized to be smaller than the number of logical rows, it was not possible to scroll to the rows that were cut off. - If a session was maximized and the "Synchronize view to size" option was set, if the session was sent to a new window, the logical rows and columns in the new window were incorrect. - Unicode output was not displayed correctly in a tabbed session other than the first tab. - Under certain circumstances with CRT maximized, text could be cut off when switching between tabbed sessions. - Opening a new window while in full screen mode caused the new window to appear partially off screen. - Under certain circumstances, a second CRT window for an existing session was cascaded when it shouldn't have been. - If two sessions with different initial positions were connected, only the initial position for the first session was honored. - If the "Auto reconnect" option was set and authentication was cancelled by the user, the session attempted to auto reconnect. - Under certain circumstances when the "Auto reconnect" option was enabled, a session attempted to reconnect even though its associated tab had been closed. - When the "Save expanded folder state in connect dialog" option was set and a session in a folder was renamed in the Connect dialog, it caused other folders to be expanded. - It was not possible to map a key or button to "Trace Options" or "Raw Log Session". - The recent scripts menu item MENU_SCRIPT_MRU_FILE1 did not work when used in a custom .MNU file. - In a script, certain crt.Screen.ReadString syntax errors could result in a crash. - In a script, if a Connect call was made immediately after a Disconnect call, CRT could think the session was not connected. - Under certain circumstances, the line number reported when a script was cancelled was incorrect. - Paste output did not continue if a WaitForStrings script method matched something in the pasted text.