In a CScript that does multiple FTP file transfers, the second transfer can generate the message, “Error (4514) Bad argument to function: Expected number, got undefined.”

The following script also exhibits the problem:

FTSetProtocol(“FTP”);
FTSetHostName(“ftp.domain.net”);
FTSetUserName(“anonymous”);
FTSetPassword(“user@domain.com”);
FTSetSync(1);
FTSetXferStat(false);
FTGet(“/pub/README”,”C:/Temp”);

If you use FTSetXferStat(true); instead of false, the error doesn’t happen. But it does if you set the End of transfer acknowledgement option in TinyTERM’s File Transfer Properties.

This error is not consistent across versions of TinyTERM or Windows, nor does every script with multiple FTP file transfers exhibit the problem.

CR 234, multiple transfer error resolved in TinyTERM 4.7.2, 15 March 2012
CR 778, script

When using FTP, file permissions on uploaded files — the UNIX umask setting — are controlled by the FTP daemon. Century Software, Inc., has had a request to add a umask option to our FTP clients. This has not been implemented at this time.

CR 207

When using the Century FTP Client to connect to an FTP server using the QNX realtime operating system, no files are displayed. The command-line FTP client on the same PC will list files properly.

This problem has not been reported with SecureFT, the replacement for the Century FTP Client.

CR 113

Some customers would like to have SecureFT start up the same way the Century FTP Client did, with a dialog that shows the different connections available. Some customers prefer the older interface in general to the newer.

This is something Century Software, Inc., has taken under advisement. It would require a substantial rewrite of the user interface for SecureFT. We can’t simply port the old interface over, as we’ve added SCP and SFTP to the available protocols.

Also, SecureFT writes each connection configuration to a separate file. The Century FTP Client wrote them all as sections of one large file, which became unwieldy and hard to read if enough connections were created. Nevertheless, it’s not an idea we’ve discarded.

TinyTERM Plus 4.53 has been adjusted so that SecureFT automatically opens the last connection used, provided you attempt to connect immediately after opening it. If you use any of the menus first, that saved configuration is lost.

CR 453, more “user-friendly” interface
CR 679, restore Century FTP interface
CR 700, alter behavior to be more like Century FTP
CR 717, default startup configuration
CR 746, on-the-fly file renaming

The Century FTP Client “Configuration Info” dialog has three tabs: Session, View/Sort and Transfer. The last two are switched in name only. If you go to the Session menu and select View/Sort, it takes you to the tab named Transfer, which has the View/Sort settings. The reverse is true of the Transfer menu option.

CR 431, fixed in TinyTERM 4.30

Create an FTP session using the graphical Century FTP Client. From the Session menu, select View/Sort, or go to the View/Sort tab in the Configuration dialog. In the Directory Item Structure at the bottom, make UNKNOWN the first word. Save the settings. When you connect, there’s a program error and Ftp32.exe crashes. This was fixed in TinyTERM Plus 4.30.

CR 379

When you have two sessions open in TinyTERM 4.12 and do an FTP transfer in one, the transfer succeeds. But when you switch to the other session, you get the error “Error (4558) Set property ‘AutoAddValue’ failed: Invalid object instance.” Also, the Ribbon Bar is lost. There is no patch for this problem.

CR 150, fixed in TinyTERM 4.20.

In TinyTERM 4.0x, the Source file to get box in the Get File dialog will not accept upper case letters when using the FTP protocol. The only solution is to upgrade to a newer version of TinyTERM. There is no patch.

TinyTERM Plus and TERM Professional 3.3 include an FTP server for Windows 95 and 98. Once you’ve added Century Internet Services to the Network Properties, you can configure it with these steps:

1. Right-click Network Neighborhood and select Properties.
2. Select Century Internet Services.
3. Click the Properties button.
4. Under the Services tab, click ftp to highlight it.
5. Click the Enable button.
6. Select Configure.
7. Add a new user.
8. Click OK and exit Network Neighborhood.

The FTP server is now available for use with the user you created.

If you cannot get the FTP server to work on Windows 98, disable the Internet services. Then locate the file inetd.exe in the Century directory and run it. That will allow you to access and configure the FTP server manually.