Problems with LCTERM 2.14 (Observed on the Rainbow 100+, connected to a DEC-20) * Possibly model dependent: 1. Can't use EMACS on the DEC-20. Screen fills with blotches, Rainbow sends thousands of ^S's, which EMACS interprets as search commands. If left alone, the Rainbow will eventually hang and need rebooting. Changing the parity in setup mode apparently has no effect. The problem does not occur in firmware terminal mode. 2. Can act as an interactive terminal to the DEC-20 at 9600 baud. But as soon as you SET HOST to another DEC-20 (using DECnet virtual terminals), you get only blotches on the screen. Again, changing the parity in setup mode has no effect. * Protocol problems: 1. LCTERM can only interact with a server, not with a "manually controlled" KERMIT; there is no passive RECEIVE command. This also means you can't SEND FOO (as) BAR from the host to have it arrive at the Rainbow with a different name. Also, there's no setting in LCTERM for filename collision handling (overwrite, fail, or attempt to construct a new name) -- LCTERM always fails if a file of the same name exists. Therefore, there's no way to GET a remote file whose name happens to be the same as one in the current path on the Rainbow. 1. The REMOTE DIRECTORY command doesn't work. LCTERM sends a command packet to the server that looks like this: ^A* GDoo.bar6 where the user specified "foo.bar". The "f" is missing, and also the length field that is supposed to precede the file name. This packet should look like ^A, GD'foo.barG 3. 8th bit quoting doesn't seem to work. When I go to the DEC-20, run KERMIT, SET PARITY ODD, and put it in server mode, then go back to LCTERM, toggle 8th-bit quoting ON, and attempt to GET a file, the result is R,12:21:46/31,. Rv:frx50.comS S,12:21:54,, Sp- @-#&1~$ R,12:21:54/12,# N3 S,12:21:54,, Sp- @-#&1~$ R,12:21:54/12,. Rv:frx50.comS R,12:21:54/31,# N3 This goes on for a while... LCTERM sends the correct GET command, KERMIT-20 responds correctly with a Send-Init of the proper form, and LCTERM NAKs the Send-Init instead of ACKing it. There seems to be no mechanism in LCTERM for setting the parity, but I did it in setup mode. 4. The LCTERM SEND function puts the filename AS THE USER TYPED it in the file header, rather than the name as it appears in the MS DOS directory. Since users tend to type in lower case, this can be a problem unless the remote system happens to be Unix-based. 5. Users should note that there is no support for IBM mainframe communications, in particular the half-duplex line turnaround handshaking and the appropriate parity processing.