After installing TinyTERM Plus or TERM Professional version 3.3 from the October 1998 CD, you may not see an option for the FTP Client, LPR Printing or NFS Server, though they should be installed. (NFS is only installed with TERM Professional.)

To resolve this, manually uninstall the current product and reboot. Next, install TERM Professional using the 30-day evaluation. Make sure that the correct components are check-marked.

We also suggest you change the TinyTERM install path. It defaults to C:\Program Files\Century. Change the path to C:\Century (delete Program Files).

Once installation is complete, run the License Manager and upgrade your license. You should now have FTP Client, LPR Printing and NFS Server.

Using TinyTERM versions prior to 4.0, if you try to download a file from the host to a directory path with a space in the name; e.g., C:\Program Files\Century\TinyTERM, the transfer will fail. This happens because of the space in the path. Putting the path in quotation marks will not help.

Instead, use the DOS 8.3-style name associated with the path. In the example above, that would be C:\Progra~1\Century\TinyTERM. Or download to a path with no spaces, then move the file when the download completes.

The Century FTP Client included in TinyTERM Plus versions prior to 4.40 can only copy one directory at a time. However, the SecureFT application included in TinyTERM Plus versions 4.40 and higher can copy multiple directories in a single operation.

Any network connection requires a TCP port be open and available on the server. There is an excellent list of common TCP ports at www.iss.net.

If you are using a non-standard port in TERM, you can specify the correct port by adding to the address, after a colon. For example:

term -l telnet:192.168.0.1:1023

will cause TERM to use telnet to connect to port 1023, rather than using the default port of 23. TinyTERM for DOS can also be configured this way.

In TinyTERM for Windows, you will need to go into the advanced setup for the telnet, SSH or SSL/TLS protocol. That dialog box will include a port number that can be edited.

At this writing, no file transfer protocol has this capability. This includes FTP in the emulator, as well as the protocols available in the Century FTP Client or SecureFT. The NFS client and server likewise cannot be changed.

CR 235, Century FTP Client
CR 620, FTP in emulator
CR 828, SecureFT

This NFS client error is a name resolution error. To bypass it, create a hosts file on your PC, or edit the existing one. Add the NFS server to the file. Make sure the server is listed there only one time, then use the hostname you gave it in NFS.

If you have a problem connecting to an NFS share from your PC, or copying a file to or from the NFS share, there are several things to check:

• Do not use “root” as your NFS username. A number of NFS daemons see the root user as equivalent to no user, and will not allow it to connect.
• Do not bypass the Windows login, especially if your Windows username is the same as your UNIX username.
• Verify that your username has the correct rights for the directory on the host, usually both read and write.
• The host must be running pcnfsd version 2. To check that, go to a shell prompt and execute this command:
  

  rpcinfo -p | grep nfs

• In the NFS client setup, try both case-sensitive and case-insensitive operation.
• Also in the NFS client setup, try turning the “Cache Reads” and “Cache Writes” options on and off.
• On the host, check the /etc/exports file to make sure the directory you need is exported.

As you can see, there is no one optimal configuration for all NFS servers. Trial and error is usually the best way to determine what will work for a given setup.

You may encounter a situation where you can upload files to the remote system, but not download them to your PC. Or download may work, but uploading fails. There is a set of configuration changes that will fix this problem in most cases.

For systems running TinyTERM 3.3 for Windows, or any version of TERM on any operating system, write a script that includes three lines:

SET ESC8BIT ON
SET COMPRESS OFF
PROTOCOL NONE

Save that script as “onewayft.cmd”, then run it when you start TERM by adding it to the command line:

term onewayft.cmd

Add any other command-line arguments as needed. If you are transferring files between two versions of TERM, create and use the script on both systems.

For TinyTERM 4.x for Windows, the settings are in the file transfer properties. To access them, go to the Edit menu and select File Transfer Properties. On the resulting dialog, clear the check box marked Use automatic data compression.

Next, click the Setup button in the upper right. In the resulting File Transfer Protocol Setup dialog, check the Use 7bit transfer over 7bit connection (esc8bit) box. Click OK twice, then save the session.

This will take care of the problem in most cases. Once in a while, you may need to add this command to the TERM script:

SET ESCCTL ON

In TinyTERM 4, go to the File Transfer Protocol Setup dialog and check the Escape Control Characters option to accomplish the same thing.

CR 229

This error is the result of a bug in TinyTERM 4.11. The only solution is to use a different version of TinyTERM.

The “print on” code for Wyse50 emulation is ^X. That’s the same code used to end a file transfer in the ZMODEM and WTERMCRC protocols.

To avoid problems, use a different file transfer protocol with Wyse50. Or use a different emulation with ZMODEM and WTERMCRC. Either solution will work.

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.