Most Century Software, Inc., products have file transfer capabilities. They can send and receive files using several common protocols, as well as the proprietary TERMCRC and WTERMCRC protocols. But all the protocols have some common requirements:

• An active connection. FTP transfers create TCP/IP connections on the fly. For any other protocol, you must already be connected to the remote system before starting a transfer.
• A valid source file name and directory path. If the name of the file to be transferred or the directory its in is misspelled, or if the file does not exist in the specified directory, the transfer will fail.
• A valid receive directory. If the directory where the file should go does not exist, the results are unpredictable. A file of the wrong name may be created, a new directory may be created, or it may not transfer at all.
• A file transfer application running on both the sending and receiving system. TinyTERM and TERM count as file transfer applications. When sending a file to a remote system, that system must be running an application that will receive the file. Likewise, the host system must send the file if you are trying to receive it through TERM or TinyTERM.

If these conditions are not met, the transfer will fail. The exact failure depends on what’s missing.

Note that there are no limits to the size of files that can be transferred. Larger files will take longer to transfer, of course, so plan accordingly when using a serial or modem connection.

This entry was posted on Monday, April 16th, 2007 at 2:55 pm and is filed under File Transfer. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.