All the file names in the TERM for UNIX/Linux portion of the combined CD are in upper case. Our documentation and install scripts refer to them in lower case. This was fixed in the January 2002 CD.

CR 279

The early releases of the CScript documentation were difficult to follow and often cryptic. Also, several commands were undocumented. The documentation was significantly improved in TinyTERM 4.21.

The TinyTERM Programmers Reference Manual compiles the current CScript documentation into a single PDF file. If you have suggestions for further improvements, please contact Technical Support.

CR 153
CR 246
CR 676

Using the German user interface, opening the Help gives the error: “Cannot find the ttde.hlp file.  Do you want to try to find this file yourself?” The help file does come up when using the English or French user interface.

CR 120, fixed in TinyTERM 4.12.

TinyTERM version 4.20 and higher can be installed unattended. For versions 4.20-4.43, the document that describes the process is available here. It’s also installed with TinyTERM, though it’s not available on all CDs without installing first.

The first releases of the AutoInstT.rtf file do contain errors when installing the Network Utilities included in TinyTERM Plus. The document linked above corrects those errors.

For TinyTERM version 4.53, an MSI install file is available instead for customers with a current maintenance contract. Contact Technical Support at +1-801-268-3088 ext 5, or by email at support@centurysoftware.com.

CR 53, automated install
CR 54, record and play back install steps
CR 180, custom data files during install (handled by MSI)
CR 255, network push install (handled by MSI)
CR 278, MSI
CR 467, AutoInstTT.rtf copied to root of TinyTERM CD
CR 517, NetUtils correction
CR 783, MSI documentation

With TinyTERM’s display language set to German, the Help file may not come up. The workaround is to locate the ttus.hlp file in C:\Program Files\Century\TinyTERM and double-click it. This was fixed in version 4.12.

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 TinyTERM 3.3 and 4.0 installs had the potential to delete all printers installed in Windows NT. To restore printing functionality in this case, uninstall TinyTERM. Then apply this patch. The patch documentation can be downloaded from this link.

Once the patch is installed, you can reinstall TinyTERM. Do not install the NFS component, as that’s what causes the problem.