Just switched to, purchased and started using AT (SSH).

I wish to easily connect (SSH) to multiple different hosts.

I set up and saved several different .tnt files, one for each host.

When I start a new connection by invoking one of my saved .tnt files, AT closes the connection in the most recently opened window and re-uses that window for the new connection. It does not disturb earlier opened connections and windows. Seems like I have to manually start and run open in a new instance if I don't want to lose my most recently opened connection.

Is this intentional, or is there a way to avoid it?

Thanks
Jon Taft

The default behavior depends on a few things.

If you're in the classic (non-tabbed) interface, the behavior is as follows

If you are invoking it from windows explorer (double clicking the file from the desktop or similar), the default behavior is to ALWAYS open a new window.

If you invoke using File->Open or by selecting the filename from the MRU list on the FILE-> menu, the default behavior is to re-use the current window if the current window is currently in a disconnected state or to create a new window if the current window is in a connected state.

Can you be a bit more specific about how you're loading the .tnt file?

I had installed the (recommended) tabbed interface. I uninstalled the whole program (since I could not find any other way to change interfaces [btw I hate web-only based help] and re-installed AT in classic mode without the tabbed interface. As you intimated, that resolved my problem. Thanks for the help.

What I was (and still am) doing: Setting up a connection. Doing a "Save As" to the desktop as .tnt. Closing the program. Repeating for another host with a different hostname.

I would then attempt to start the connection to the specific host by clicking on the .tnt file on the desktop. That would work. Before however ("tabbed"), when I left the connection running (as I wanted to) and went back to the desktop to click on another .tnt file, AT would punt the first connection (or the most recently opened connection) and start the new connection in the exact same most recent pre-existing window. (Prior opened connection windows other than the most recent were not effected).

When I re-installed with the "classic" interface it behaves as you said. I always get a new connection when I click on a .tnt file on the destop (which is what I want).

Since I just want to get to my connections easily (one click) I am happy now and will just continue to use "classic" mode (a recurring crotchety theme in my affairs actually). Presumably what is going on is that there is some "tabbed" model that I am supposed to be grasping such that I open all connection from within AT, but that is definitely not the behavior I am looking for. I just want to be able to insta-click from outside AT to get to different hosts without having the intermediary mechanism get visibly in my face in any way.

Thanks Again
Jon Taft

Before however ("tabbed", when I left the connection running (as I wanted to) and went back to the desktop to click on another .tnt file, AT would punt the first connection (or the most recently opened connection) and start the new connection in the exact same most recent pre-existing window.

I believe what you were experiencing was that the most recent window would be used an a new TAB would be opened in it. THis allows you to have multiple connections within a single window. However, if you weren't looking for the tabs, you might overlook them. They're just below the toolbar.

If you don't like the tabbed behavior, the classic behavior should suffice. This allows for a single connection per window. If you want multiple connections, you open multiple windows. Absolute implements both so that you can choose what you like.

Enjoy!

Brian