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

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.

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

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.