Saving Settings
When you have made changes to the settings, an asterisk (*
) is
displayed on the SSH Tectia Client title bar, after the name of the current
settings file (for example: default*
). This indicates that the
changed settings are not yet permanent - they have not been saved yet.
If you want to make the changes permanent, you can save them for later
use. Click the Save button on the toolbar, or select the
File -> Save Settings to save any changes you have made to
your current settings. The changes are saved in the default settings
file only if default.ssh2
is the current profile. Global
options are saved at the same time in the global.dat
file.
The default settings file is loaded automatically when you start the
client. Therefore all the settings that you save in the default settings
file take effect immediately when you launch the client. These settings
are also used for connections started with the Quick Connect
option (see Section Defining Quick Connect Options).
The positions of the currently open terminal and file transfer windows
can be saved separately with the File -> Save Layout
option. If you arrange your window positions and save the layout
settings in the default settings file, the windows will be automatically
positioned the way you prefer them when you next start the client.
Note that by default all of the windows will be opened at once. This can
be changed on the Appearance page of the Settings dialog so
that the defined windows are opened only when necessary when you open
new terminal and file transfer windows. See Section
Defining the Appearance.
If you spend a lot of effort specifying the settings, it is a good idea
to create backup copies of the modified settings files (*.ssh2
)
and store them in a safe location. This way you will not have to create
your personal settings again if your settings files are lost (for
example because of a hardware failure).
Multiple Settings Files
You can save separate settings files for each remote host computer. This can be
done by using the Profiles option. For more information on using
profiles, see Section Defining Profiles.