Free 14-Day Evaluations    
Product Downloads    

Sign in     


DESKTOP MOBILE DOWNLOAD PURCHASE SUPPORT INFO COMPANY
 Home  >>  Support  >>  Knowledge Base

Archive for the 'Login' Category

TinyTERM Crashes After Configuring Auto Login

Monday, April 23rd, 2007

Set up TinyTERM to establish a connection on open. Start TinyTERM, then login to the host. Open the Session Properties and go to the Login tab. Add a username and password. Check the Login at connect option. Click Apply, then click OK.

Back in TinyTERM, click the Disconnect button, or go to the Session menu and select Disconnect. TinyTERM crashes. This is due to a bug in the auto logout code.

CR 496, fixed in TinyTERM 4.31

Auto Login Doesn’t Retry

Friday, April 20th, 2007

In TinyTERM’s Session Properties, the Login tab allows you to configure an automated login process. However, regardless of the settings in the Retry and Wait fields, the login is only attempted once. If it fails to receive any of the Wait for strings, it never starts over. This was fixed in TinyTERM 4.30.

CR 311

Sharing Custom Configurations

Friday, April 13th, 2007

Once you’ve created a custom keyboard mapping, attribute scheme or other configuration in TinyTERM, you may want to distribute it to all users. There is an easier way than recreating the configuration on every single PC.

Once you’ve created a custom keyboard scheme in TinyTERM, it’s saved into the file C:\Program Files\Century\TinyTERM\keyboard.dat. To copy a scheme to another PC, you only need to copy the keyboard.dat file. Then the next time you start TinyTERM, the new scheme will be available on that PC as well.

Other custom configuration files that can be distributed the same way. There are several, all with the .dat extension:

attr.dat – contains attribute schemes: colors, etc.
codepage.dat – contains code pages for different character sets
login.dat – contains automatic login schemes

All this information is referenced by connection files, which have the .tpx extension. Those files contain all the connection information, but they also reference the .dat files. So no matter how much customizing you do in TinyTERM, you only need to distribute the four .dat files and any .tpx files you may have created.

Multiple Login Prompts

Wednesday, April 4th, 2007

If you see strange characters after connecting, and the host is prompting multiple times for login, you probably have a setting wrong. This usually happens when TinyTERM is set up to login automatically on connection, but the username and password aren’t set.

You can do one of two things. In the Login settings, you can either turn off the “login at connect” option, or you can set the username and password for the automatic login. Either way, the extraneous characters and multiple login prompts should disappear.

SSH Username and Password Saved

Thursday, March 29th, 2007

If you do not save a username and password in the Session Properties of TinyTERM Plus, it will pop up a dialog box requesting them when you connect. However, if TinyTERM is configured to save settings on exit, or if you click Yes when asked to save the session, TinyTERM saves the login information automatically.

In TinyTERM Plus versions prior to 4.31, this will happen even if TinyTERM Plus is configured never to save settings on exit. This bug was fixed in TinyTERM Plus 4.31.

To prevent this in TinyTERM Plus 4.31 and higher versions, go to TinyTERM Plus’ Edit menu and select Preferences. Under Save settings on exit, select the Never radio button. You can also choose the Protect all settings option, which will prevent any changes from being saved as long as it is set.

CR 479, fixed in TinyTERM Plus 4.31
CR 640

Prompting for Username and Password with SSH

Wednesday, March 21st, 2007

In TinyTERM 4.10 and 4.11, connecting via SSH requires you to save your username and password in the Session Properties. That is a potential security risk. It can be avoided by using this script. It will prompt for a username and password when connecting.

  1. You must use the connect button on the ribbon bar when connecting. Auto connect will not work with this script.
  2. Save the sshlogin.cs script to the C:\Program Files\Century\TinyTERM directory.
  3. Open TinyTERM and click the Session button on the Ribbon Bar, or from the Edit menu select Session Properties.
  4. Select the radio button labeled Post session start and click the Browse button below. Browse to the sshlogin.cs script in the TinyTERM directory.
  5. Select OK.
  6. On the Login tab, clear the username and password if they are saved there.
  7. Save the changes and exit Session Properties.

The next time you open TinyTERM and connect with this configuration, you will be prompted for a username and password.

CR 86, prompt added in TinyTERM Plus 4.12
CR 96, sshlogin.cs fails to connect at times

Sending a Command as Part of Automatic Login

Thursday, March 15th, 2007

TERM and TinyTERM for Windows have an automated login function that can readily be extended to execute system commands as part of the connection. Under the Login setup, or the Advanced Login setup, there are four “Wait for” and “Then send” options. The first two lines are taken for the login and password prompts. The last two can be used for anything.

Note that the “Wait for” items are case-sensitive. That’s why the first letters are missing from the words “login” and “password” there. Some systems send these in upper case, others in lower. But the rest of the word is virtually always lower case, so leaving the first letter off bypasses guessing its case.

The default “Then send” strings are composed of what look like control characters. Here they are, explained:

  • ^W – This causes TinyTERM to wait one second before performing the next operation.
  • ^U – This sends the username from the Login dialog down the comm line.
  • ^P – This sends the password. The password is stored encrypted, so it can’t be read directly from the configuration file.
  • ^M – This sends a carriage return, ASCII value 13.

Any other characters entered in a “Then send” line will be sent as plain text. All characters in a “Wait for” line will be read as plain text.

Given that information, you can send any command to the host using those text boxes. For example, to wait for a $ prompt, then send an “ls” command, you would enter:

$

in the third “Wait for” line. In the accompanying “Then send” line, enter:

ls^M

The one-second wait given by ^W may or may not be necessary. Experiment with the timing to see how the commands work out. We also recommend you go through the login manually before automating it, so that you can note any differences from the defaults. Different or additional prompts are the most common changes.

Odd Characters after Connecting

Friday, March 2nd, 2007

When connecting, you may see something like this display:

^L1^T5^S

This comes from a failed automatic login. To fix it, go to the automatic login configuration in TERM or TinyTERM. Clear out everything there, so no settings are left. Saving that configuration will get rid of those characters.

  Copyright © 2024 Century Software, Inc. All Rights Reserved999 TERMS OF USE PRIVACY POLICY EULA