On operating systems with a root or administrator login, always use that login or one with equivalent rights to install TinyTERM or TERM. When the install requires a reboot, login as an administrator when the reboot is complete, also.

Otherwise, TinyTERM’s and TERM’s installs can’t access the files and registry settings they need. Errors during install or when running the emulator will happen if this isn’t done.

This error happens during install of TinyTERM version 4 on Windows 95. It means that Internet Explorer version 4 or higher is not installed. For normal desktop usage, this error can be ignored.

TinyTERM accomplishes web-to-host connections using an ActiveX control. That control requires Internet Explorer 4 at a minimum. If an earlier version of Internet Explorer is installed, TinyTERM will not be able to open in the browser. However, it will still function as a standalone application.

When installed with a valid license, TinyTERM 4.12 still expires after 30 days as an evaluation. There is no workaround for this issue. Using a different version of TinyTERM is the only solution.

This does not affect any other version 4.12 product: TinyTERM Plus, TinyTERM Thin Client or TinyTERM Web Server.

CR 164

TinyTERM versions prior to 3.0 and TERM versions prior to 7.0 store connection information in files with the .con extension. TinyTERM 3 and TERM 7 use the .tap extension, and TinyTERM version 4 uses the .tpx extension. Century Software, Inc., provided utilities to convert between the various formats, so you don’t have to set the connections up all over again.

For updating .con files to .tap files, TinyTERM 3 and TERM 7 include a convtap.exe program. To use it, run it at a command prompt, using the name of the .con file as an argument. For example, to convert the file sample.con to sample.tap, the command would be:

convtap.exe sample.con

To convert a .tap file to a .tpx file, use the script TAPtoTPX.cs included in TinyTERM 4. (You can also download a copy.) See the file C:\Program Files\Century\TinyTERM\TAPtoTPX.wri for documentation of this script.

Both TinyTERM versions 3.x and 4.x store keyboard mappings in the file keyboard.dat. The format of the two files is nearly identical, in fact. The only difference is in the section heading. For example, a keyboard scheme named “My Keyboard” would be set apart in version 3 like so:

[My Keyboard.kbd]

In version 4, it would be set apart like so:

[My Keyboard.keyboard]

So to copy a keyboard scheme from version 3 to version 4, you can simply copy the entire section of keyboard.dat, changing .kbd to .keyboard in the process.

Some versions of TinyTERM install from a setup.exe program. If you run that program and get an error that says you need to run setup.exe, then there’s actually a different install needed. Close the error and look for the file install.bat instead. That calls setup.exe with the required command-line parameters.

If you get errors when installing TinyTERM from CD or from a network share, copy the install directory to your local hard drive instead. Run the install from that copy.

If that still fails, boot the PC in safe mode. As long as the version of TinyTERM you have is supported on your version of Windows, the local install copy will run in safe mode.

SecureFT will give this error when it is blocked by a firewall. Check your PC’s firewall settings first, and exempt SecureFT if necessary. If there is a firewall on the host, you’ll need to verify that it has port 21 open for FTP or Secure FTP, or port 22 for Secure Copy transfers.

TinyTERM Plus version 4.05 will use 100% of the CPU if a session is configured for TN3270 or TN5250 emulation. TinyTERM Plus 4.10 will do the same thing with two or more sessions open using those emulations.

TinyTERM 3.3 will sometimes use 100% of the CPU regardless of the emulation chosen. Older versions of TERM or TinyTERM for Windows will do the same thing. TinyTERM does not need to be connected for this to happen.

There is no workaround for these situations. TinyTERM must be upgraded to improve its CPU utilization.

TinyTERM Plus Edition 4.05 may use 100% of the CPU after install on Windows NT 4.0, even when the TinyTERM Emulator is not running. That’s caused by the NFS client included with TinyTERM Plus Edition. To fix that, uninstall TinyTERM and NetUtils. Reboot the PC, then reinstall without the NFS component.

TinyTERM 4.31 and higher will use 100% of the CPU on Windows 98 or Me when connected via TCP/IP or modem. This does not happen on Windows 98 Second Edition, nor does it happen with serial connections.

CR 72, improved in TinyTERM 4.12
CR 294, reported in TinyTERM 4.20
CR 647, Windows 98 and Me

The TN3270 emulation type includes the HLLAPI programming interface. This was added to TinyTERM Plus in version 4.30 in the TN3232.exe program found in C:\Program Files\Century\TinyTERM\HLLAPI, rather than the default TinyTERM emulator.

TN3232.exe is no longer included in TinyTERM versions 4.60 and higher. For these versions, use the Whlapi32.dll for the HLLAPI interface.

CR 92

There is one option common to all file transfer methods and protocols: ASCII or binary mode. Each has a specific use. Using the wrong mode can corrupt files during transfer, even when everything else is correct.

ASCII file transfer mode is intended for plain text only. Files transferred in ASCII will have carriage returns and line feeds adjusted for the receiving system. If both systems are running the same OS, such as two Linux systems communicating, nothing special happens. But DOS and UNIX, for example, handle text files in slightly different ways. ASCII mode makes the necessary changes automatically.

Binary mode, on the other hand, makes no changes at all. The file is transferred in a raw data format. This makes binary the required mode for image files, programs and the like. If you have any doubt, use binary mode for the file transfer.

There’s an irreverent but in-depth discussion of the two available at htmlgoodies.com. It’s specific to FTP, but the advice about ASCII and binary modes applies across the board.