There are several possible solutions to this error:

1. If the version printed on the activation key card or listed in the license email does not match the install version, then this error will come up. Verify that the serial number you have matches the TinyTERM version you are installing. For example, older serial numbers will not work with the current TinyTERM download. And the serial number that comes with a TinyTERM CD is specific to that version of TinyTERM.
2. Check the serial number and activation key for typographical errors. The serial number will always be 11 characters long: one to three letters, six to eight numerals, then two letters. No serial number ends in the letters “OEM”. The capital letter O will actually be the number zero in all cases.The activation key is always eight letters. Depending on the font, this may make the lower-case letter l look like the number 1. It’s never a number, though.
3. When installing TinyTERM 4.52 from CD, you’re seeing a timing error. Despite what the install says, it’s not ready for the license yet.In this case, click the 30-Day Eval button instead. The install will continue from there. Once the install is done, go to Start | Programs | TinyTERM and run the License Manager.

   In License Manager, click the Upgrade button. Enter your serial number and activation key, then click Update License. Close the License Manager. TinyTERM will then be licensed, rather than an eval copy.

4. For a serial number that starts with the letters MMA, do not let the CD autorun. Instead, on the TinyTERM CD you’ll find a folder named “setup32_v33.” Run the setup.exe program in that directory instead. That will accept your license information.

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.

When you run SecureFT, you may get the error, “The SecureFT license is expired or corrupt.” This is caused by registry damage to the SecureFT license. Normally TinyTERM will run properly when this happens.

To fix the damage, click on Start | Run and enter regedit, then click OK to open the Registry Editor. In the Registry Editor, go to HKEY_CURRENT_USER\Software\Century Software\SecureFT. You’ll see a License folder there. Delete that folder, then close the Registry Editor. SecureFT will run properly after that.

CR 764, fixed in TinyTERM Plus 4.60 with new licensing subsystem

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

You may see this error when installing TinyTERM on Windows 2000 or XP. It will reference the file AUTOEXEC.NT or CONFIG.NT.

It usually happens when the specified file is missing. You can find a replacement in either C:\Windows\Repair or C:\Windows\i386. Copy the file into C:\Windows\System32, then start the install again.

If AUTOEXEC.NT already exists in C:\Windows\System32, the error means that file has a setting that’s interfering with TinyTERM’s install. To fix the error, back up AUTOEXEC.NT by copying it to another location, then edit it to have the following three lines only:

lh %SystemRoot%\system32\mscdexnt.exe
lh %SystemRoot%\system32\redir
lh %SystemRoot%\system32\dosx

You won’t need to reboot. TinyTERM will install after those changes are made.

CR 730, fixed in TinyTERM 4.50

To change the font TinyTERM uses, go to the Edit menu and select Session Properties. From there, click on the Fonts tab. The Add Font button will allow you to add a new font.

For terminal emulators, a monospaced font is the best choice. Courier New and Lucida Console are both good choices and available on most Windows systems.

Once you’ve chosen a font and added it to the TinyTERM font list, click on the name to highlight it, then click the Up button on the Fonts tab until it’s at the top of the list. TinyTERM uses a font cascade, which means it checks the fonts in the order listed when drawing the screen.

You may find that lines and boxes draw with unusual characters after this. The default Term font used by TinyTERM has line draw characters in specific reference locations. Other fonts don’t always share these.

You can change the display by going to the Attributes tab of Session Properties and checking the Use Non-Font Based line draw characters box. That will use graphics to draw lines instead of characters.

The TN3270 and TN5250 emulations only use one font. To change that font, open the Session Properties and go to the Fonts tab. Click the Edit font button to select a new font. A monospaced font is still the best choice.