Install TinyTERM Thin Client to Windows 2003 Server with Citrix Metaframe XP. It works properly at the 2003 console or on a remote desktop.

Century Software has had a report that if TinyTERM is published to run in an independent window, it comes up completely. There is no text, no menus, no title bar — no display at all. This has not been duplicated

CR 628

Century Software, Inc., provides Samba source code, and a compiled binary for SCO UNIX. Both of these are supplied at no charge.

We have had requests for compiled binaries for additional operating systems. No others have been done so far.

CR 625, AIX

Connecting TinyTERM Plus 4.33 when the emulation is 5250 causes the screen to go blank. The host doesn’t appear to respond at all.

CR 624, fixed in TinyTERM Plus 4.40

This error indicates that TinyTERM can’t get into the specified directory. This could be because the directory doesn’t exist, or because the user doesn’t have rights to access it.

Check the spelling of the directory and file name. Any typos will cause file transfer to fail.

Also check the username and password being used. If either is incorrect, or if the user doesn’t have rights to the directory in question, that will also cause file transfer to fail.

TinyTERM will also give this error if you try to download over 100 files using the FTP protocol. It will appear to transfer correctly at first, but will eventually fail. No files are actually transferred when this happens.

CR 623

The Kermit file transfer protocol includes a server mode capability. Neither TinyTERM nor TERM recognizes this mode, so they can’t get files from it. They will send files to a Kermit server and receive files from a Kermit send. But neither will initiate a download from a Kermit server.

CR 622

Century Software, Inc., has had a request to add DDE functionality to the TN3270 and TN5250 terminal emulations. This has not been implemented thus far.

CR 621

When attempting to transfer files using the IND$FILE protocol, it times out with the error, “Remote host is not responding.” However, other IND$FILE clients can transfer files successfully to the same host.

CR 619

The first transparent print job works correctly. The second and subsequent jobs give the error, “Print already in process.” Other Windows applications can use the printer successfully. Restarting TinyTERM allows one transparent print job, then the error comes back. This has not been duplicated.

One report suggests that deleting the .tpx file, then recreating it from scratch gets rid of the error. This has not been duplicated either.

CR 618, Okidata Microline 320
CR 640, general case

Configure a file transfer using the YMODEM protocol. Connect to a Linux system running TERM. Use:

term -x server

to set the transfer up. You’ll get a handshake timeout.

CR 617

The CScript command te.read() does not accept input from the numeric keypad when NumLock is on. When NumLock is off, te.read() outputs odd characters instead.

CR 616, fixed in TinyTERM 4.7.2, 15 March 2012