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

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.

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

“Invalid object instance” means that the file transfer object is unable to be located. It happens when items are not registered properly.

To resolve this, open a Windows command prompt and change directory to C:\Program Files\Century\TinyTERM. Run the following four commands:

regsvr32 cente.ocx
regsvr32 cenft.dll
regsvr32 cenbrows.ocx
regsvr32 cencom.dll

Each should give you a success message. Once that’s done, the file transfer error should be fixed.

This may happen on Windows NT when the Century NFS client is installed. If you are not using NFS, you can fix the problem by uninstalling TinyTERM Plus and NetUtils. Reboot, then reinstall TinyTERM Plus without the NFS component.

No version of TinyTERM Plus designed for Windows 2000 or XP installs NFS by default. The NFS client is not supported in those environments, so those systems should never see this error.

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.

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.

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.

Some FTP servers will show an empty directory in the Century FTP Client or SecureFT. This happens when the server uses a different directory item structure than the client’s default. The following steps will change the default in the Century FTP Client:

1. Open the Century FTP Client. It displays the configuration dialog automatically.
2. Click the View/Sort tab.
3. Set the Directory Item Structure value by clicking the Set Default button.
4. Edit the Directory Item Structure value for the required format.

The steps for SecureFT are (also available as a screencast):

1. Go to the Edit menu and select Setup.
2. Click the Directory Structure tab.
3. Click the item under Active Items you want to change.
4. Click the Push button to move it to the Inactive Items. Or use the up and down arrows on the left to change the item’s position in the list.

The required format may be found by connecting to the FTP server using a command-line client, such as the one included in Windows. After connecting, type “dir” at the prompt for a directory item listing. The default format used by the graphical FTP client is:

-rwxrw-rw- 1 owner group 32 May 19 21:35 file.txt

This corresponds to Directory Item Structure:

ATTRIBUTE UNKNOWN USER GROUP SIZE MON DATE TIME FILENAME

Compare the listing on the FTP server with the listing above and change the order as needed, removing any directory items not displayed. The most common change needed is to remove the GROUP item.

Accessing or saving files on a network drive may generate this error. It means that the NFS client driver is installed, but not licensed.

To get rid of the error, uninstall TinyTERM. Reboot the PC, then look for one or more of these files:

cennfs.sys
marnfs.sys
mar_nfs.386

They should have been removed by the uninstall. If any are left behind, delete all copies found, then reboot the PC again.

After you reboot the PC, you should not see the error any more. You can now reinstall TinyTERM. Make sure you do not install the NFS component as part of that.

CR 362