After uninstalling TinyTERM Plus, on reboot you may see load errors about mar_nfs.386 and ncdnp32.dll. To fix that, do the following:

1. Open Windows Explorer or My Computer and remove any Century folder (C:\Century or C:\Program Files\Century).
2. Go to the C:\Windows\Temp folder. Remove any files or folders that start with _istmp.
3. Search the C: drive for files named mar*.*. From the list of files found, delete the following:
   • marathon.*
   • marsetup.*
   • mar_inet.exe
     You may receive an error that this file is in use. If so, check the far right of the Start bar, next to the clock. If a hammer&wrench icon is there, right-click it and select Exit. You will then be able to delete mar_inet.exe
4. Click the Start menu and select Programs. Delete any Century or TinyTERM Program group.
5. Click Start and select Run. In the Open line, type regedit and click OK.
6. In the Registry Editor, go to HKEY_Current_User\Software. Delete any “Century” or “NCD Software” folders found there.
7. Still in the Registry Editor, go to HKEY_Local_Machine\Software. Delete any “Century” or “NCD Software” folders found there. Close the Registry Editor.
8. Right click on Network Neighborhood and select Properties.
9. Remove “Century NFS” and “Century Internet Services” from the list of installed network components
10. Reboot your PC.

Using TERM Professional 3.3 on Windows 95, if you shut down the PC, it immediately reboots. If Century NFS is removed, the machine shuts down properly.

This is usually caused by a load order issue between NFS and TCP/IP. To clear it, remove NFS from the system, then remove TCP/IP. Reinstall NFS before adding TCP/IP back in.

Using TERM Professional 3.3 on Windows 95, you may get a blue screen error after adding the NFS client. When that happens, in the network properties add Microsoft IPX/SPX. If that does not resolve the issue, add the NetWare Client as well.

Using TERM Professional 3.3 on Windows NT, after installing NFS you can’t shut down Windows. Instead, you get a Dr. Watson error, followed by a blue screen.

To correct this error, you will need to download this patch. To use it, search the C: drive for the file mar_nfs.386. Rename any copy you find as a backup. Then copy the patch file into the same directory. The next time you start Windows NT, the patch will be in effect.

When you try to install NFS on Windows 98, you may get an error message stating that on the specific location there is no data about the hardware. To fix this, when the install asks if you want to restart your computer, click No. Next, type Alt-Tab until you get to a registry question. Click OK to add to the registry. You should now be able to set up the NFS Client.

This error happens when you have “Start Minimized” selected in the Century NFS Server options. To fix it, edit the nfssvr.ini file using any text editor. Find the line:

startminimized=ON

Change ON to OFF. Save the file. The Century NFS Server will start normally after that. If it does not, This error suggests that the server is not configured correctly. To resolve this problem, edit nfssvr.ini again and search for the line:

enabled=ON

Change ON to OFF there as well.

This error means the specified file is not found in a standard Windows directory. To fix it, search on that file name. You should find a copy in C:\Program Files\Century\TinyTERM\NetUtils. Copy that file to C:\Windows\System32 or its equivalent. The next time you start TinyTERM, you won’t see the error.

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.