Beta: SecureCRT 6.2 Beta 2
SecureCRT BETA running on Windows 7 BETA :D
While the first beta for SecureCRT 6.2 introduced a lot of new features and changes to existing functionality, this one seems focused to fixing bugs… and, my oh my, that’s a lot of “crash” bugs 
Well, at least the color schemes are properly saved now; this bug made me give up trying to make my own color scheme some time ago.
SECURECRT 6.2 BETA 2 DOWNLOADS
Get it now: Download SecureCRT 6.2 Beta 2 (Windows, 32-bit)
64-bit version: Download SecureCRT 6.2 Beta 2 (Windows x64)
Portable version (U3): Download SecureCRT 6.2 Beta 2 for U3
WHAT’S NEW IN SECURECRT 6.2 BETA 2
- Under Vista, selecting a file using “Zmodem Upload List…” from the Transfer menu caused SecureCRT to crash.
- If the “Clear on disconnect” option was set and SecureCRT went into full screen mode after disconnecting from a session that had more than a page of output, SecureCRT crashed.
- SecureCRT could crash after attempting to connect to a host that was not responding.
- Under certain circumstances, SecureCRT could crash after scrolling back and then attempting to select some text.
- If a session setting was changed in the Session Options dialog and then the Session Options dialog was re-opened, SecureCRT sometimes crashed.
- If the X/Y/Zmodem upload and download folders did not exist and a Zmodem download was started and the “Browse for Folder” dialog was used after the transfer had timed out, SecureCRT crashed.
- If the command line specified a path for a script, the script was not launched.
- On a 64-bit machine, Help could not be launched.
- With the “Retain size and font” option set, under certain circumstances, data displayed in the session window could not be selected.
- If a Zmodem transfer was started and the download directory was not valid, if the “Browse for Folder” dialog was cancelled after the transfer timed out, garbage characters were sent to the
server.
- In the Connect dialog, if several sessions were selected and one was de-selected, when the mouse was right-clicked to display the context menu, the session was selected.
- New color schemes added to an active session were not saved to the configuration file.
- The 64-bit combined SecureCRT and SecureFX installer installed into the x86 location when run in silent mode.
- In the installer, on the dialog that shows where the application is going to be installed, long install location paths were cut off.
- The upgrade eligibility date displayed in the installer was not correct.
- If the “Clear on disconnect” option was set and SecureCRT went into full screen mode after disconnecting from a session that had more than a page of output, SecureCRT crashed.
- SecureCRT could crash after attempting to connect to a host that was not responding.
- Under certain circumstances, SecureCRT could crash after scrolling back and then attempting to select some text.
- If a session setting was changed in the Session Options dialog and then the Session Options dialog was re-opened, SecureCRT sometimes crashed.
- If the X/Y/Zmodem upload and download folders did not exist and a Zmodem download was started and the “Browse for Folder” dialog was used after the transfer had timed out, SecureCRT crashed.
- If the command line specified a path for a script, the script was not launched.
- On a 64-bit machine, Help could not be launched.
- With the “Retain size and font” option set, under certain circumstances, data displayed in the session window could not be selected.
- If a Zmodem transfer was started and the download directory was not valid, if the “Browse for Folder” dialog was cancelled after the transfer timed out, garbage characters were sent to the
server.
- In the Connect dialog, if several sessions were selected and one was de-selected, when the mouse was right-clicked to display the context menu, the session was selected.
- New color schemes added to an active session were not saved to the configuration file.
- The 64-bit combined SecureCRT and SecureFX installer installed into the x86 location when run in silent mode.
- In the installer, on the dialog that shows where the application is going to be installed, long install location paths were cut off.
- The upgrade eligibility date displayed in the installer was not correct.