The SNA protocol is a native IBM network protocol. TinyTERM does not support it for TN3270 or TN5250 emulations. Only TCP/IP connections are supported.

In this situation TinyTERM works with telnet, but SSH sessions connect and immediately disconnect. This only happens if you have “Login at connect” checked in the Login tab of TinyTERM’s Session Properties.

Early versions of SSH in TinyTERM require a username and password on the Login tab, but the “Login at connect” caused connection problems. Without that set, TinyTERM connects and logs in properly. In later versions of TinyTERM, that option is grayed out when SSH is set.

If that option is not checked, check the version of sshd running on the host. TinyTERM versions 4.10-4.13 use SSH version 1.5. SSH 2.0 daemons must be configured to allow pre-2.0 connections when using those versions of TinyTERM.

Using the telnet connection type, TinyTERM 4.0x may fail to connect. Older versions of TinyTERM work, as does Windows telnet. Switching between the hostname and IP address makes no difference. TinyTERM just seems to hang.

This happens when the host sends a signal that puts TinyTERM into binary mode. Binary mode is typically only used by TN3270 and TN5250 emulations. It can cause problems for other terminal emulations.

CR 65, fixed in TinyTERM 4.10

TinyTERM version 4 introduced much greater color and attribute flexibility for display. Not all users find the default settings to their liking, though. It’s easy to change the color pallette and other font attributes.

In TinyTERM, open the Session Properties and go to the Attributes tab. In the “Mappable attribute combinations” box are 16 different combinations: NORMAL, BOLD, REVERSE, etc. As you highlight each one by clicking on it, you can change both the foreground and background color, as well as the display attributes assigned to it. Use the “Display Attribute As” and color boxes on the right of the dialog.

Once you have configured each attribute the way you like, click the Save As button to give the new attribute scheme a name. It will be saved to the file attr.dat. If you would like to distribute the new scheme to other users, simply copy that file to their PCs in the C:\Program Files\Century\TinyTERM folder.

You can do this in TinyTERM 4.x by mapping a key to the CScript command SessionNew(). To do this, open the keyboard map and click on the key you want to use. Change the Action to COMMAND. In the Value field, enter:

SessionNew(“default.tpx”);

Replace default.tpx with the name of the session you want to open, enclosed in quotation marks.

If you don’t want to open a specific file each time, but select one on the fly instead, combine SessionNew() with StdOpen(), which will give you a standard file browse dialog. That command is:

SessionNew(StdOpen(“C:\\Program Files\\Century\\TinyTERM”,”tpx files|*.tpx|”,”tpx”,”TinyTERM Connection Files”));

TinyTERM and TERM for Windows can store multiple IP addresses and telephone numbers in a single configuration file. If you want to clean the list out, so it only shows one address or phone number, close TinyTERM. Open the .tap or .tpx file you’re using, such as default.tpx, in any text editor. Notepad or Wordpad will work.

Search for the line that starts “node=”. Delete everything after the equals sign =. Save the file and exit.

If there is one host address or phone number you want to save, make it the only entry after the =. Either way, the changes you made will take effect the next time you start TinyTERM.

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.

An entire host session or part of one can be saved to a file through TinyTERM’s data capture function. To set that up, open TinyTERM’s Settings or Session Properties and go to the Data Capture tab. Enter a path and file name, or accept the default.

The default file name is capt#.fil. The # will be replaced by a number when you start data capture, beginning with 00. This will create the file capt00.fil in the TinyTERM directory. If capt00.fil already exists, capt01.fil will be created, and so on up to capt99.fil. You can use the # sign in your own data capture file names as well.

To turn data capture on, go to TinyTERM’s Tools menu and select Capture File. This starts the capture process, represented by a butterfly net on the status bar at the bottom of the TinyTERM window. Go to the same menu option to turn data capture off.

The Capture device line allows you to select a file (the default option), a system device like LPT1, or the Windows print manager. If you choose PRINTMNGR, data will be captured to the default Windows printer.

Capture mode should generally be set to ASCII. The other mode options capture non-printable characters as special information, and are usually reserved for troubleshooting display issues.

Capture file creation describes what to do when the file name chosen already exists. If Append is chosen, the new data will be added at the end of the existing file. Overwrite causes the original file to be replaced with the new data. If you used the # sign in your file name, a new file will be created regardless of this setting, unless all files numbered 00 through 99 already exist.

The Flush receive buffer on capture off option makes sure everything captured gets written to the file when you stop data capture. Otherwise, the data will be written at the best available moment, or when TinyTERM is closed.

You may need to get data from your server to your PC for another application. For example, you may need to import a UNIX report into a spreadsheet.

There are three possible ways to do this. The one to choose depends on your particular environment.

1. File transfer
   If the data is in a file on the server, you can use TinyTERM’s file transfer function to download the file to your PC. This requires that you first start the transfer on the server. After that’s done, the steps in TinyTERM are:
   1. On the Tools menu, click Get File.
   2. In the File transfer protocol list, choose the protocol the host system is using.
   3. If you want to save the file to a directory other than the current directory on your machine, enter the destination directory in the Local destination directory box.
   4. Under Transfer type, choose ASCII.
   5. In the Source files to get box, type the name of the file on the host.
   6. Click Receive File to begin receiving.
2. Data capture
   If you’re working with a report from a database, you can display that report to the TinyTERM window and capture the information. To set that up, do the following:
   1. On the Edit menu, click Session Properties.
   2. Click the Data Capture tab.
   3. In the Capture device list, click FILE.
   4. In the Capture file or device name box, type the name of the file you want to create.
   5. Click OK.

   That configures the data capture. Next, in the server database set the report up, but do not start it. Go to TinyTERM’s Tools menu and select Capture File to start the data capture. Start the report on the server. When it finishes, select Tools | Capture File again to stop the data capture. You will probably need to edit the final file with Notepad to clean up information at the beginning and end.

3. Transparent printing
   If the server application allows transparent printing, you can print the data to a file on your PC’s hard drive. To set that up, do the following:
   1. On the File menu, click Printer Setup. The Printer Setup dialog box appears.
   2. Click the File radio button.
   3. In the File Name box, type the name of the file you want to create.
   4. Click OK to close the Printer Setup dialog box.

   Once that’s done, start the print job on the server. Nothing will print at your printer. Instead, the file you need will be created on your PC’s hard drive.

The preceding instructions are for TinyTERM 4.x. Similar capabilities exist in most Century Software, Inc., products. Regardless of which method or product you use, you’ll have a text file on your PC that you can then import into any application.

When using Wyse60 emulation in TinyTERM 4.42, printing the screen comes out fine. Transparent print jobs do not.

The Wyse60 emulation allows you to define up to three local printers. You can see these by going to the File menu and selecting Extra Printers. The above problem happens when the wrong printer gets chosen.

We have a patch for this issue. Download it to your PC, then do the following:

1. Locate the existing CenTE.ocx file. This should be in the folder C:\Program Files\Century\TinyTERM.
2. Rename that file as a backup to CenTE.OLD.
3. Copy the file cr696CenTE.ocx into the same directory as CenTE.OLD.
4. Rename cr696CenTE.ocx to CenTE.ocx.

The next time you start TinyTERM, the patch will be in effect.

CR 696, fixed in TinyTERM 4.43