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.

Using a TinyTERM script to execute a file transfer, the transfer status dialog box may come up. Depending on how your script is written, this may pause or stop script execution entirely.

To prevent the dialog box from coming up, you can disable it with a script command. The TERM Script Language command is:

set xferstat off

For CScript, use the command:

FTSetXferStat(0);

Enter the appropriate command anywhere in the script before the file transfer starts.

Using TERM for UNIX on HP-UX, XMODEM receives files from an EDI mailbox without a problem. However, sending files fails after a few packets with a CRC error. There are two possible issues in this case:

1. TERM maybe sending data, but not receiving acknowledgements. If you abort the TERM script and immediately connect to the UNIX device file using the Unix command “cu-l /dev/cul0p7 -m dir”, you may find that the telephone connection is still open. In this case, you may be able to continue the session manually.To resolve this, disable local flow control on the modem. The Hayes command for that is AT&K0. Please be aware each modem may have different local flow control commands. Check the documentation for specifics.
2. If you are connecting to a GEIS network, you will need to convert the UNIX-formatted file to DOS format before sending it. The GEIS network expects DOS-formatted files. You can use the HP-UX utility dos2ux to convert the file.

After upgrading from TERM for DOS 7.0 to version 7.2, trying to transfer a file using ZMODEM will give the error, “Can’t find FTZMOD.DLL.” You will need to go to the Century directory and rename the file FTZMODEM.DLL to FTZMOD.DLL.

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.

If the Century FTP Client won’t connect to the server, check the following:

• Make sure you do not have multiple TCP/IP items listed in your Network Neighborhood. If you do, remove all but the correct one, unless each TCP/IP entry has a known purpose.
• TCP/IP may have become corrupt on the PC. Write down all the TCP/IP settings and verify that they are correct for the PC. Then remove TCP/IP from the network properties, reboot the PC, and TCP/IP back in. Reboot the PC again if so prompted.
• Create a hosts file containing the IP Address and host name of the FTP server.

When file transfer is extremely slow using either of these protocols, you may need to increase the window and packet sizes. To do that:

1. From TinyTERM’s Edit menu, select File Transfer Properties,
   or
   From the File menu, select File Transfer.
2. Click either the Setup or Settings button.
3. Double the value in the “Zmodem/WTERMCRC window size” field. If you are using a serial or modem connection, do not set the value higher than the current connection speed.
4. Set the “Zmodem/WTERMCRC packet size” to match the window size.
5. Click OK in each dialog to close them, one at a time.
6. Save the session.

This configures the transfer settings for the best results for your connection speed.

Using TinyTERM 3.3 and the ZMODEM file transfer protocol, you may find a situation where you can download a file from the host to the PC, but not upload from the PC to the host. When that happens, do the following in TinyTERM:

• Click on the Transfer button.
• Enter the required information.
• Select ZMODEM as the transfer protocol, if it’s not already set.
• Click the Settings button.
• Place a check in the box next to Automatic Data Compression.
• Click the Advanced button.
• Set the ZMODEM/WTERMCRC Packet Size to 4096 or 8192.
• Set the ZMODEM/WTERMCRC Window Size to match the packet size.
• Click OK twice.

You should now be able to transfer files both directions.

If the PC is using the NTFS file system, the above instructions may not work when downloading files. It’s not just TinyTERM that’s affected by this. ZMODEM does not always write well to NTFS drives, regardless of the application you’re using.

CR 241, NTFS