Closed jayjwa closed 7 months ago
Can you try running the same tests with "-d 22" on the command line? This will generate a log of cterm commands and tty operations on standard error. I'm most interested in the overwritten lines in the file create test and extra echoes with C-Kermit.
The failure to change terminal type is because dnlogin explicitly disables such changes. I'll have to check the spec to see what it would take to enable such changes.
dnlogin -d 22 lunast 2> dnterm.log
I snipped the actual password key sequence. Hopefully that's OK. Line creation test as before, Kermit 'show version'.
dnterm.log
The latest version of dnprogs/dnlogin/cterm.c should fix the double echoing seen with c-kermit. Still working on the line overwriting issue.
Extra echos seems to be fixed.
I believe the latest code should fix the line overwriting issue (cterm.c, dnlogin.h, found.c and tty.c). This version will no longer claim to be a VMS system, instead using a customer reswerved value (193). This works OK for VMS but may cause problems with other systems.
That will do it. Thank you.
Though I've seen this behavior for awhile, I've been hesitant to report it as I was not sure it was a local issue or not. Now, with 4 ways (telnet, rlogin, LAT, dnlogin/sethost) to remote login to a VMS node, I think I can say with some degree of certainty something is off with dnlogin/sethost's terminal handling. This behavior is noticeable with various utilities, such as Kermit, MAIL, the edit/tpu (EVE) editor, or even (see test at the end) CREATE.
Consider a correctly working terminal via TELNET:
A correctly working terminal via llogin (LAT):
Rlogin is similar to the above two (example omitted for brevity). Dnlogin session with terminal problems:
Properly working mail editing via rlogin session (note lines):
dnlogin mail session keeps overwriting message space (note "Line three"):
It is not possible to change the term type to vt100 like the working examples:
Strange behavior with Kermit, via dnlogin, not present with LAT login (note echos):
DUA1:[JAYJWA] C-Kermit>sshhooww vveerrssiioonn
The easiest way to test this is likely with CREATE. xterm VAX 5.5 dnlogin:
xterm VAX 5.5 llogin (LAT):
xterm dnlogin VAX 7.3:
xterm telnet VAX 7.3:
All tests from the same UXterm ( xterm -class UXTerm -u8 -fg bisque1 -bg black -fn -xos4-terminus-medium-r-normal--14-140-72-72-c-80-iso10646-1 -bc +ai -132 +cm -j -kt vt220 +mesg +si) (TERM=xterm) and Tmux (TERM=sixel-tmux). The same behavior occurs with no Tmux. While Xterm is most likely the most "DECnet friendly", the same occurs with Urxvt (TERM=rxvt-unicode), or even just "xterm" (TERM=xterm).