Using TERM-to-TERM server mode transfer, download a file to your Linux PC. Nothing transfers. The same is true for uploading to TERM in server mode using term -1x or term -2x. Both manual and scripted file transfers fail. This works using TinyTERM connecting to Linux.

CR 852

Flow control issues in file transfer can manifest several different ways in a TERM-to-TERM environment. CRC errors typically occur. Often a file can only be transferred one direction. Only a portion of the file transfers, or perhaps none at all. There are several troubleshooting steps:

1. Make sure you have selected the same protocol on both sides.
2. Login to the remote system and put it in the server mode appropriate to the protocol. Server mode is invoked with term -1x for WTERMCRC, or term -x for TERMCRC.
3. Initiate the file transfer by doing an XFER or GET. Enter the complete path in the source or destination directory, or use a period . for the default directory. Transfers from UNIX to DOS require that file conversion be turned on as well.
4. If you still cannot transfer the file, you may have flow control problems. You may have to turn flow control off, location by location, beginning with your modem if possible. Flow control is turned off in each modem differently, so see your modem documentation.
5. The next location to turn flow control off is in TERM itself. This is done by editing the .termsys file in the user’s home directory or the C:\Term directory. Add the following entry in the “!file transfer” section:
   

   protocol NONE

   This must be done in TERM on both sides.

6. If the file will still not transfer, try turning flow control off at the unix ports themselves. The UNIX command stty -a display the “ixon,” “ixany” and “ixoff” flow control parameter settings. The command stty -ixany will turn off “ixany,” and the command stty ixany will turn it on. You will need to experiment with various combinations of these flow control parameters.

In TERM for UNIX, WTERMCRC file transfers move much more quickly over an rlogin connection than they do over a telnet connection. The fastest file transfer protocol for TCP/IP connections is FTP, but that does not include the benefits that come from TERM-to-TERM transfers.

CR 518

The server.cmd script included with TERM for AIX does not list the ZMODEM or WTERMCRC file transfer protocols. So if you run:

term -x server

those protocols are unavailable from the menus. To work around this, run TERM in server mode instead:

WTERMCRC: term -1x
ZMODEM: term -2x

CR 129

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.

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.