Win7 系统使用的串口工具

SecureCRT(R) 6.7.4 (Official) -- February 2, 2012 Copyright (C) 1995-2012 VanDyke Software, Inc. All rights reserved. This file contains a SecureCRT 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 SecureCRT 6.7.4 (Official) -- February 2, 2012 --------------------------------------------------------- Changes: - This version of SecureCRT is not compatible with older versions of the Activator and older versions of SecureCRT are not compatible with this version of the Activator. Bug fixes: - SecureCRT could crash while idle when several Telnet sessions were connected. - SecureCRT crashed if a tabbed session was disconnected while a script was running. - The URL syntax of telnet:<IP_address> did not work. - If an attempt to run a script in a locked session was made, SecureCRT incorrectly reported that a script was already running. - Windows: On Windows 7, if a second binary transfer was attempted after the first binary transfer completed, nothing was transferred. - Windows: If the "SCRTMenuToolbarV2.ini" file was corrupted, SecureCRT crashed on startup with a Windows runtime error. - Mac: Keys mapped to MENU_WINDOW_NEXT and MENU_WINDOW_PREV were not saved correctly. - Linux: On Ubuntu, SecureCRT crashed when attempting to establish an SSH2 connection to a local or remote host. - Linux: When Ubuntu ran on a system with an older processor, such as Pentium 4 or Pentium M, SecureCRT crashed when attempting to connect to a Secure Shell server. Changes in SecureCRT 6.7.3 (Official) -- November 8, 2011 --------------------------------------------------------- New features: - Added support for Ubuntu Linux 11.10. 32-bit and 64-bit installers are available. - Added support for Red Hat Enterprise Linux 6.0. 32-bit and 64-bit installers are available. Bug fixes: - If the default session was edited and the changes were written to all sessions, the logon actions were set to the default for all SSH2 sessions regardless of whether or not the logon actions had been changed. - If a script was running in a tabbed session and the tab was closed while the script was running, a script cancel error was reported. - With the "Show confirm disconnect dialog" option on, if a script was running and "Disconnect" was selected from the menu or toolbar and then the disconnect operation was cancelled, the script was stopped anyway. - Telnet: When CTRL+S was used to suspend output, the CPU usage went to 100%. - Mac/Linux: If the Public Key Assistant was used to generate a DSA key in OpenSSH key format and then upload the key file, the file had 0644 permissions instead of 0600 permissions, which meant that OpenSSH refused to use it. - Mac/Linux: If a license field, such as Name or Company Name, contained more than one line of text, the license was accepted, but could not be used when SecureCRT restarted. - Mac: On a system that previously had SecureCRT installed, after upgrading to OS X Lion, SecureCRT could not save license information. - Mac: On OS X Lion, the prompt for making SecureCRT the default Telnet application continued to be displayed when SecureCRT restarted after answering "Yes" to the prompt. - Mac: With the "Autoreconnect" option on, when a session connected through a forwarded port established by another session and a local session was also connected, if the sessions became disconnected, they did not reconnect automatically. - Linux: After exiting a local shell session, an I/O error was reported. - Linux: It was not possible to store passwords using the Password Properties dialog. Changes in SecureCRT 6.7.2 (Official) -- August 11, 2011 -------------------------------------------------------- New features: - Linux: Added support for Ubuntu 11.04. Changes: - Windows: The 32-bit installer can be installed on a 64-bit system. - Linux: Added an accelerator (ALT+M) to toggle the menu bar. Bug fixes: - Xmodem transfers failed over connections using the Raw protocol. - The hostname was not saved in sessions that used the Raw protocol. - The item MENU_GOTO_CONNECT_BAR did not work when it was mapped to a button on the button bar. - The Connect dialog allowed connect attempts to sessions with the protocol set to "None". - The extend evaluation feature did not work correctly. After the offer was accepted, there was no button to extend the evaluation on the "Enter License" dialog as described in the instructions that had been e-mailed. - Telnet/RLogin: On Windows 7, when multiple sessions were running in different windows such that they were separate processes and command output was streaming in them, one or more of the connections could get reset. - Windows: On 64-bit machines, if the menu or toolbar was customized in SecureCRT 6.0 and then version 6.7 was run and "Yes" was selected after the prompt "Would you like to update the toolbar and menu bar?" was displayed, SecureCRT crashed when it was closed. - Windows: When the SecureCRT window was restored after being maximized or in full screen mode, it was restored to the wrong size. - Mac: If the system language was set to Russian, SecureCRT crashed when it was launched. - Mac: Mapping a button on the button bar to launch an application did not work. - Mac: After going into full screen mode and connecting to another session, the last line of the new session was cut off. - Mac: The "Public Key Wizard" dialog was taller than necessary. - Mac/Linux: It was not possible to double-click a port forward item in order to open its "Properties" dialog. - Linux: Opening URLs did not work. - Linux: On Ubuntu, attempting to register SecureCRT by pressing the "Enter License Data" button on the dialog that appeared after the evaluation license expired did not work. Changes in SecureCRT 6.7.1 (Official) -- June 16, 2011 ------------------------------------------------------ Changes: - Mac: When GSSAPI authentication is specified for a session, SecureCRT now looks for "libgssapi_krb5.dylib" in addition to "libgssapi.so". Bug fixes: - If buttons were added to a new button bar and then an attempt was made to switch to a different button bar, SecureCRT could crash. - When Ymodem was used to transfer multiple files, only the first file was transferred correctly and sometimes the error "Invalid access to memory location" occurred. - In the Quick Connect dialog, if the port number was changed to something other than the default, the port number was reset to the default the next time the Quick Connect dialog was opened. - Windows: If a USB serial adapter was removed while the serial session was connected, SecureCRT could crash. - Windows: When the Windows 7 Areo snap feature was enabled, if the SecureCRT window was dragged so that it snapped to the side of the desktop and focus was switched to another application, when SecureCRT was restored from the taskbar, it reverted to its previous size. - Windows: If the Windows 7 Aero snap feature was enabled and SecureCRT was dragged by the title bar so that it was maximized using the snap feature, the SecureCRT window was partially off screen. - Mac: If the global option "Confirm when closing multiple tabs" was set and the "Do you wish to connect from all sessions?" prompt