TinyTERM version 4 has several command-line parameters. They can be used in any combination, except where conflict is evident.

• -nosplash
  Starts TinyTERM without the introductory splash screen.
• –debug
  Starts TinyTERM in debug mode. This causes extended debug information to write to the debug monitor if it’s open. By default the debug monitor is installed to C:\Program Files\Century\TinyTERM\dbmon32\dbmon32.exe.
• –mkdefs
  Does not run TinyTERM. Instead, it makes a new copy of default.tpx with all default settings.
• –a1 telnet://address
  Brings up OLE mode 1. This starts TinyTERM in the default browser with the URL helper address as shown; e.g.,

  tt –a1 telnet://208.219.23.12

  and connects the session.

• –a2 file.tpx
  Brings up OLE mode 2. This also starts TinyTERM in the default browser, using the listed tpx file.
• tpx1.tpx tpx2.tpx tpx3.tpx etc.
  Opens the specified .tpx file(s). This is the only argument that does not start with a dash. Up to nine may be listed on a single command line, separated by spaces. The .tpx extension does not need to be supplied, as it will be assumed if it’s not present.

There will also be a license argument. The value will be the first three characters of your serial number. The specific value depends on the version of TinyTERM you have installed. See the version table for more information.

If the specified license is not available, TinyTERM will generate a license error instead.

Some versions of TinyTERM Plus will cause VCFSD errors after install. This is caused by the NFS client.

When this happens, uninstall TinyTERM Plus and NetUtils. Delete the C:\Program Files\Century directory, then reboot the PC.

Once that’s done, you can reinstall TinyTERM Plus. Don’t install the NFS component of the Network Utilities, and you won’t see the error again.

This error happens most often with TinyTERM 4.0x versions. It indicates a damaged install of either TinyTERM or Windows 95. There are two possible fixes.

1. On Windows 95, the Winsock2 update is missing. You can download that patch here. Save it to a temporary directory on your PC, then run it. Reboot when the patch install finishes.
2. If you have TinyTERM 4.04 or 4.05, the product itself needs to be patched. There are separate patches for TinyTERM 4.04 and TinyTERM 4.05. To use the patch, unzip it to a temporary directory. It will create new copies of the tt.exe and cencom.dll file. Locate the current copies of those files on your PC in C:\Program Files\Century\TinyTERM. Rename the originals as backups, then copy the new files into that same directory.Next, open a command prompt in Windows. Change directory at the prompt to C:\Program Files\Century\TinyTERM, then run the command
   

   regsvr32 cencom.dll

   Exit the command prompt and reboot your PC to finish installing the patch.

If you have a newer version of TinyTERM, the error indicates file corruption. To fix that, uninstall TinyTERM. Delete the Century directory from C:\Program Files. Then reboot the PC and reinstall TinyTERM.

In the Century FTP Client, if the Set_FACL command has been used to restrict access to files via a File Access Control List, the FTP Client cannot see these files on the server. To resolve this problem you will need to replace the ftp32.exe file. You can download a patch for this here.

To use the patch, locate the existing ftp32.exe file in C:\Program Files\Century\TinyTERM\NetUtils. Rename it as a backup. Copy the patch file Ftp32_FACL.exe into that same directory. Then rename the patch as ftp32.exe. The next time you start the Century FTP Client, the patch will be in effect.

This patch applies to TinyTERM Plus versions 4.10 and earlier. Later versions of TinyTERM Plus incorporate the patch.

Turning on data capture in TinyTERM 4.04 will cause it to crash and close, unless the Status Bar is turned off. To do that, go to the View menu and uncheck the “Status Bar” option.

The crash is caused by a bug in the butterfly net graphic that normally displays in the status bar. Other versions of TinyTERM do not have this problem. There is no patch available.

In the Session Properties for TinyTERM version 4.x, on the Session tab, there is a Setup button for the terminal emulation type. Clicking that brings up the “Emulation Setup” dialog.

The first line in that dialog is “IBM 3101/3151 turn around character.” In most cases this should be set to 13 (the ASCII value of the carriage return character) for the function keys in the IBM3151 emulation to work correctly.

TinyTERM version 4.04 will only accept a single digit in this field. To set it properly, you will need to edit your .tpx file manually, using Notepad or another text editor. Search for the line:

TurnChar=

Edit that to add the number 13 to the end of the line:

TurnChar=13

Save the changes and exit. If you open the “Emulation Setup” dialog after this and save any changes, you will need to make this manual edit again.

There may be times when you want to dial out by typing commands, rather than allowing TinyTERM or TERM to connect the modem automatically. To do this, configure TinyTERM to connect to the serial port your modem is attached to.

If it’s an internal modem, it will still be associated with a serial port. Check your operating system documentation for help locating the appropriate port.

Once connected, type

AT

and hit Enter. You should see an OK message come back. If there’s no response, or if you can’t see the letters you typed, try this command:

ATE1Q0

Most modems will respond to this with a clearly visible OK. You can then type the ATDT command to dial the modem, followed by the phone number. For example:

ATDT1-801-268-3088

The AT commands are all part of the Hayes modem command set. Most modems will accept them readily. For a complete list, see http://www.modemhelp.net.

TinyTERM and TERM can dial a calling card, then enter an access code before dialing a modem number. You simply need to enter the entire calling sequence as the phone number, using commas to pause the dialing for two seconds each.

For example, suppose I need to dial 1-800-555-5555 to access my calling card. Six seconds later, it connects and asks for my PIN, which is 1111. Four seconds after that, I can dial the number I need, 801-268-3088. I would enter that number like this:

1-800-555-5555,,,1111,,801-268-3088

This assumes I don’t need to dial 1 for the actual number when using my calling card. You don’t actually need the dashes in the phone numbers, either. They’re ignored when dialing, but they do make it easier to read.

When printing a screen in TinyTERM 4.03, lines will sometimes print as odd characters instead. This is corrected with this patch, through the implementation of multiple code pages for printing. Installation instructions and documentation are in this document. TinyTERM versions 4.04-4.12 incorporate the patch.

The problem was reintroduced in TinyTERM 4.13 with the Use printer fonts option in the new Printer Setup dialog. The same thing happened printing direct to device. This was fixed in TinyTERM 4.21.

CR 318, fixed in TinyTERM 4.21
CR 429, not fixed in VT100
CR 584

This file transfer error means that TinyTERM or TERM could not get information from the host system. There are only a few possible causes:

1. The username or password is incorrect.
2. The remote directory does not exist.
3. The user does not have rights to read the directory.

For items 1 and 2, check the spelling. Also verify that the username in question does exist on the host system.

If the user does not have rights to read the host directory, then you’ll need to correct that. Another user may have rights. You might change the directory and file permissions so the user can read them. Or you might move the necessary host files to a different directory before downloading. If uploading, you can also select a different destination directory.