What operating system are you on (and which version of that OS)?
(Windows, Mac OS X, Linux)
When using a desktop shortcut to launch SecureCRT.exe (no args), the default behavior is to launch a new instance. However, if the desktop shortcut has arguments that specify connecting to another session, those arguments may include command line options that tell SecureCRT to use an existing instance.
If you're on Windows 7 or newer, and you're using a 'pinned' icon on the taskbar to launch SecureCRT, the default windows behavior is to activate an instance of the application (typically the window that's been used most recently) that's already open -- such behavior is a feature of the OS, and isn't overridden by SecureCRT. However, you can hold down your Shift key as you click on the 'pinned' icon on the taskbar and a new instance of SecureCRT will be launched.
Additionally, there is a feature in SecureCRT that forces a single instance behavior such that, if it's enabled, SecureCRT resorts to activating an existing instance if it's already running. This option is one that exists only in the Global.ini file ('Single Instance' set to 00000001), and so an upgrade from v5 alone would not likely have affected/changed the behavior.
Also, even with Single Instance enabled, you can have multiple windows (all governed by the same SecureCRT.exe instance). When you right-click within the Session manager in SecureCRT 7.3, you can see a menu item 'Open Sessions in a Tab'. If there's a check-mark next to this menu item, any connections made will be opened up in a new tab within the same SecureCRT window. Otherwise, connections you make (if there aren't any connections open in the current window) will be made within a new SecureCRT window).
If this information isn't helpful in getting you to the behavior you desire, please provide us with more details about your configuration, history, usage scenario, steps you use to launch new connections, etc. and we'll be happy to continue providing assistance and information to help get you there.
If you would feel more comfortable discussing the specifics of your situation more privately, feel free to send email to support@vandyke.com referencing this forum thread (#12171).
--Jake
(Windows, Mac OS X, Linux)
When using a desktop shortcut to launch SecureCRT.exe (no args), the default behavior is to launch a new instance. However, if the desktop shortcut has arguments that specify connecting to another session, those arguments may include command line options that tell SecureCRT to use an existing instance.
If you're on Windows 7 or newer, and you're using a 'pinned' icon on the taskbar to launch SecureCRT, the default windows behavior is to activate an instance of the application (typically the window that's been used most recently) that's already open -- such behavior is a feature of the OS, and isn't overridden by SecureCRT. However, you can hold down your Shift key as you click on the 'pinned' icon on the taskbar and a new instance of SecureCRT will be launched.
Additionally, there is a feature in SecureCRT that forces a single instance behavior such that, if it's enabled, SecureCRT resorts to activating an existing instance if it's already running. This option is one that exists only in the Global.ini file ('Single Instance' set to 00000001), and so an upgrade from v5 alone would not likely have affected/changed the behavior.
Also, even with Single Instance enabled, you can have multiple windows (all governed by the same SecureCRT.exe instance). When you right-click within the Session manager in SecureCRT 7.3, you can see a menu item 'Open Sessions in a Tab'. If there's a check-mark next to this menu item, any connections made will be opened up in a new tab within the same SecureCRT window. Otherwise, connections you make (if there aren't any connections open in the current window) will be made within a new SecureCRT window).
If this information isn't helpful in getting you to the behavior you desire, please provide us with more details about your configuration, history, usage scenario, steps you use to launch new connections, etc. and we'll be happy to continue providing assistance and information to help get you there.
If you would feel more comfortable discussing the specifics of your situation more privately, feel free to send email to support@vandyke.com referencing this forum thread (#12171).
--Jake
Securecrt For Windows Xp
- SecureCRT 9.0 (Beta) for Windows introduces RDP support, so you can quickly connect RDP sessions in a tab, along with an integrated scratchpad tab for text editing and a script editor tab for editing local scripts, all right within SecureCRT. The status bar can be customized to show only the desired items, including the log file name and local.
- Windows Terminal provides many settings and configuration options that give you a great deal of control over the Terminal's appearance and each of the shells/profiles that you can open as new tabs. Settings are stored in a structured text file making it easy for users and/or tools to configure.
Securecrt For Windows Xp
- SecureCRT 9.0 (Beta) for Windows introduces RDP support, so you can quickly connect RDP sessions in a tab, along with an integrated scratchpad tab for text editing and a script editor tab for editing local scripts, all right within SecureCRT. The status bar can be customized to show only the desired items, including the log file name and local.
- Windows Terminal provides many settings and configuration options that give you a great deal of control over the Terminal's appearance and each of the shells/profiles that you can open as new tabs. Settings are stored in a structured text file making it easy for users and/or tools to configure.
Securecrt For Windows 7 32 Bit
TAPI / SecureCRT / Windows 7 I have been trying for several weeks to get SecureCRT to work with TAPI on Windows 7. What I am hoping to do is to use TAPI/SecureCRT as a replacement for hyperterminal which no longer ships with Windows 7.
