Using the FTP protocol in SecureFT, you get the above error when uploading a .zip file over about 5 Mb in size. Other file extensions of the same size or larger transfer without problems. Downloading doesn’t generate any errors, either.

CR 666

On Windows XP or Vista, if a non-administrator user starts SecureFT, an error immediately displays:

The instruction at “0x77fc8fe1” referenced memory at “0x00720075”. The memory could not be “written”.

The user who installed TinyTERM Plus can always use SecureFT, even if the administrator rights required for install are later taken away.

You can work around this by enabling Windows 98 compatibility mode. To do this, login as an administrator. Right-click on the SecureFT shortcut and select Properties. Go to the Compatibility tab. Check the box labeled Run this program in compatibility mode for. Select Windows 98 / Windows Me from the drop-down list. Click OK to make the change permanent.

CR 648

Century Software, Inc., has had a request to add a scripting language to SecureFT. This would allow automation of file transfers for the FTP, SFTP and SCP protocols.

This has not yet been implemented. The workaround for FTP is to use TinyTERM and the CScript language.

CR 417

Century Software, Inc., has had a request to implement RFC 2228 in SecureFT. This has not been done thus far.

CR 413

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

Open SecureFT and configure a connection. Set the Initial Remote Expanded Path on the Server tab of the Edit Configuration dialog. Regardless of the protocol selected, you’ll still get put into your home directory on the remote system after connecting.

This is in part due to the different protocols available (FTP, SFTP and SCP) and the requirements of different file transfer servers. There is no general case that will allow any protocol on any server to be read perfectly, which limits how the remote path can be selected, if at all.

The Initial Local Expanded Path also fails, but in a different way. If you specify a directory — for example, C:\Temp — it expands that path, but it still displays the local files from the top of My Computer rather than taking you to the directory you chose.

CR 49, Century FTP local directory
CR 476, SCP
CR 669, general

These were added to the SecureFT graphical file transfer client in TinyTERM Plus 4.30. They are not available in any emulator.

CR 242, SecureFT
CR 464, request to add SCP to emulator
CR 781, request to add SFTP to emulator

When you run SecureFT, you may get the error, “The SecureFT license is expired or corrupt.” This is caused by registry damage to the SecureFT license. Normally TinyTERM will run properly when this happens.

To fix the damage, click on Start | Run and enter regedit, then click OK to open the Registry Editor. In the Registry Editor, go to HKEY_CURRENT_USER\Software\Century Software\SecureFT. You’ll see a License folder there. Delete that folder, then close the Registry Editor. SecureFT will run properly after that.

CR 764, fixed in TinyTERM Plus 4.60 with new licensing subsystem

The Century FTP Client included in TinyTERM Plus versions prior to 4.40 can only copy one directory at a time. However, the SecureFT application included in TinyTERM Plus versions 4.40 and higher can copy multiple directories in a single operation.

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