wallis@wsucsa.uucp (10/04/89)
Dear Netlanders:
Has anyone out there in Netland seen the following problem under
ULTRIX 3.1 running DECWindows? It seems like when you use your DECterm window
under ULTRIX 3.1 as a VT300+ type terminal to DLOGIN into a VMS machine and
use EDIT/TPU there, that EDIT/TPU and the terminal window are not communicating
correctly. Also, the PF keys seem to not behave right. Has anyone else seen
this behavior from there machines? Any fixes known? Some of our users use
both ULTRIX and VMS and want the full VT300+ functionality. I already have
one rather dumb workaround, which is to set your DECterm to VT100 mode. Then
things start working, BUT you lose the nice VT300 keyboard, graphics, etc...
This is pestering a lot of my users.
Thanks in advance.
Tom Wallis
PS> We are running VAXstation 3100s, ULTRIX 3.1, and ULTRIX worksystem software
2.1, and ULTRIX DECnet.
--
-------------------------------------------------------------------------------
Thomas Wallis BITNET: WALLIS@TWSUVAX
System Manager, Computer Science Dept. BITNET: TWWALLIS@TWSUVM
Wichita State University UUCP: uunet!ncrlnk!ncrwic!wsucsa!wallis
Wichita, Ks. 67211
DISCLAIMER: The opinions expressed here are my own, and do not reflect the
views of the Computer Science Department or Wichita State University.
-------------------------------------------------------------------------------thomas@mipsbx.Berkeley.EDU (Matt Thomas) (10/06/89)
> Has anyone out there in Netland seen the following problem under > ULTRIX 3.1 running DECWindows? It seems like when you use your DECterm window > under ULTRIX 3.1 as a VT300+ type terminal to DLOGIN into a VMS machine and > use EDIT/TPU there, that EDIT/TPU and the terminal window are not communicating > correctly. Also, the PF keys seem to not behave right. Has anyone else seen > this behavior from there machines? Any fixes known? Some of our users use > both ULTRIX and VMS and want the full VT300+ functionality. I already have Do a dlogin node -e# (or some othe character besides ~). Why not ~? Because way on the past of dlogin (probably for rlogin compatibility sake) it was decided that ~ is the default escape character. Now what does that have do with the above? Because the Fn keys end their escape sequences with ~ and so dlogin patiently waits for the next character (to see if you wanted to escape) before allowing the ~ to pass. Also make sure that you run in 7-bit controls mode, dlogin does not handle 8-bit escape sequences. -- Matt Thomas Internet: thomas@decwrl.dec.com DECnet-ULTRIX Development UUCP: ...!decwrl!thomas Digital Equipment Corporation Disclaimer: This message reflects my own Littleton, MA warped views, etc.