![]() ![]() If a script that called () was repeatedly run, it could cause terminal corruption and possibly a crash.If the Connect bar was removed from the toolbar through customization and then SecureCRT was restarted, attempting to bring up the customization dialog caused SecureCRT to crash.Mac: In the "Connect" dialog, the search string from the "Find Session" dialog was not remembered for subsequent searches.Ĭhanges in SecureCRT 6.7 (Beta 3) Bug fixes:.Mac: If SecureCRT was run on a Mac system with the keyboard and mouse being controlled from another system running Synergy in server mode, the arrow keys did not work.Windows: On Windows XP, if the display theme was set to Blue, Black, Aqua, or Silver and more than one SecureCRT window was connected to a session and "Send chat to all tabs" was used to send text to one of the sessions, it caused the other window to freeze.SSH2/SSH1: When a session established a port forward that launched an application, if the session attempted to connect using both an IPv4 and IPv6 address, two instances of the application were launched.Serial: After connecting to a Windows COM port and then pressing any key, the CPU was pegged.A pop-up error message was displayed if the script method GetOption() was called with an unknown option name.When the /F parameter was used on the command line to specify the location of the configuration folder and the menu or toolbar was customized, the changes were not saved.SecureCRT crashed after pressing OK on a script dialog if the session that launched the script had been closed after the dialog was displayed.SecureCRT crashed after pressing OK on the "Session Options", "Lock Session", or "Confirm Disconnect" dialog if the session that launched it had been closed after the dialog was displayed.SecureCRT crashed if a session with the "Auto reconnect" and "Close on disconnect" options enabled was disconnected.SecureCRT could crash on exit due to the way threads were being cleaned up.If the SecureCRT window was resized and trace options were on, the event was traced.Ĭhanges in SecureCRT 6.7 (Beta 4) Bug fixes:.If "/POS" was the only option specified on the command line, SecureCRT attempted to use the last argument as the remote host. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |