In TinyTERM Plus 4.7.0, opening a saved configuration file in SecureFT causes it to crash with the message, “SecureFT has stopped working.” This can also happen when saving a configuration.

CR 998, fixed in version 4.7.2, 15 March 2012

Using SecureFT, the Century FTP graphical client, a remote directory with a sufficiently large number of files will not open. Because the files won’t list, they can’t be downloaded to a local directory.

CR 937

SecureFT displays the date for local files in dd/mm/yyyy format. Century Software, Inc., has had a request to make the date format changeable.

CR 824

Century Software, Inc., has received a request to force the graphical FTP client to use only upper or lower case file names when transferring. This would include both options, or it could be disabled entirely.

CR 82

SecureFT always shows the size of an uploaded file as zero bytes, even after refreshing the directory multiple times. The correct size appears only after leaving the directory and coming back again.

CR 811

Using Windows XP, SecureFT reads zip files as directories. Uploading a zip file causes a new directory to be created on the host, and the individual files in the zip are uploaded into that directory. This is directly related to XP’s ability to show the contents of a zip as a virtual directory.

CR 806, fixed in TinyTERM Plus 4.53

Using SecureFT to transfer files via FTP from the PC to an IBM 4690 server generates the error above. Below is sample text from the output log window of SecureFT:

USER pos_dev
331 Password required for pos_dev.
PASS *****
230 User pos_dev logged in.
PWD
257 “c:” is current directory.
TYPE I
200 Type set to I.
SYST
215 OS 4690 operating system Passive mode on.
TYPE I
200 Type set to I.
c:\
Directory “c:” caused an error with message: “Bad pathname specification (e.g., syntax error).”.
CWD c:\c:
550 c:\c:: error 0.

In contrast, here is the output from a command-line FTP client:

220 FTP server (IBM 4690 TCP/IP FTP Version 1.0) ready.
User pos_dev
331 Password required for pos_dev.
Password:
230 User pos_dev logged in.
cd adx_upgm
250 CWD command successful.
pwd
257 “c:\adx_upgm” is current directory.
cd ..
250 CWD command successful.
bi
200 Type set to I.
get ace.dat
200 PORT command successful.
150 Opening BINARY mode data connection for ace.dat (55 bytes).
226 Transfer complete.
ftp: 55 bytes received in 0.00Seconds 55000.00Kbytes/sec.
quit
221 Goodbye.

CR 727

SecureFT requires you to enter a username and password for each connection. Leaving them blank produces the error, “Error occurred on connected event with message: Last command line completely unrecognized.”

Century Software, Inc., has had a request to add a login prompt to SecureFT. This would allow the connection to be set up with no username or password. On connect, it would prompt the user to enter them before continuing.

CR 716

Century Software, Inc., has had a request for RSA key authentication in SecureFT. This would apply to both the SCP and SFTP protocols if it were implemented.

CR 711

If you use SecureFT to download a from a symbolic link, it gives an error:

File “<link> – <target>” caused an error

(The words “<link>” and “<target>” are replaced with the actual file names.) The file itself can be downloaded, just not through the link.

CR 690