[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference csc32::consolemanager

Title:POLYCENTER Console Manager
Notice:Kits, Scans, Docs on CSC32:: as PCM$KITS:,PCM$DOCS:, PCM$SCANS:
Moderator:CSC32::BUTTERWORTH
Created:Thu Aug 06 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1541
Total number of notes:6564

853.0. "No EIGHTBIT chars. in DECterm CONNECT ?" by 60549::SIMMONDS (Nature abhors people.) Thu Jul 06 1995 07:04

    Hope this hasn't been discussed here already (if it has, please show me
    where..:) ..
    
    Just upgraded to V1.6-100 (on OpenVMS VAX V6.1) and my Customer
    happened to mention that he cannot use TPU editor in a "CONNECT
    CONSOLE" window when the OPA0: terminal being connected to is set 
    EIGHTBIT.   We tried setting the DECterm window widget
    Option:General:VT300_Mode_EightBit_Controls on but no change..
    
    I think this behaviour is also true for Console Manager V1.5 and
    therefore not related to my upgrade to V1.6
    
    Question is:  What's going on here? Is there an eight-bit path from the
                  console wire to the DECterm window ?  (It seems as though
                  the <CSI> C1 char. is getting filtered out)  We did check
                  the LAT server port.. it is 8 bits, no parity.
    
    Thanks in advance..
    John.
T.RTitleUserPersonal
Name
DateLines
853.1CSC32::BUTTERWORTHGun Control is a steady hand.Thu Jul 06 1995 19:549
    The only thing that could be biting you hear is LTA device mapped to
    the the server port is set to NOEIGHTBIT. Use LATCP to figure out what
    ports are mapped to where and then find the server/port number of the
    node in question via the PCM config editor and map that to the LTA
    device that LATCP says is mapped to that port and do a SHOW TERMINAL
    against it.
    
    Regards,
       Danm
853.2BITTEN by the EightBIT BIT :-)60549::SIMMONDSNature abhors people.Fri Jul 07 1995 02:418
    Re: .1
    
    Danm, thanks for that suggestion.. I haven't looked at that yet, but
    just need to ask.. since PCM creates the LAT application ports itself
    now, we'd have to set the EIGHTBIT bit in the system parameter
    TTY_DEFCHAR, right ?
    
    John.
853.3CSC32::BUTTERWORTHGun Control is a steady hand.Fri Jul 07 1995 20:2612
    >Since PCM creates the LAT application ports itself
    > now, we'd have to set the EIGHTBIT bit in the system parameter
    > TTY_DEFCHAR, right
    
    It's not so much that it creates the lat ports themselves but rather
    that it does a IO$_SETMODE qio to change the volatile settings. I can't
    remember if the line is set to Noeightbit or not by the QIO. If it is,
    changing the TTY_DEFCHAR param will have no effect. I'll have to look
    at the code and see what it does.
    
    REgs,
      Dan
853.4set term/noeightbit29067::BUCKLEYski fast,take chances,die youngMon Jan 08 1996 14:182
I talked with Dan and he said that a check in login.com to see if they were
logged into OPA0: with a set term/noeightbit if they are should fix the problem.
853.5Serial ECU ?42798::ROWELLPaul Rowell @BBP - TMC UKTue Jan 09 1996 04:124
    I guess this will also prevent people from running the ECU for 2100's
    etc as this requires eight-bit mode?
    
    -Paul
853.6TTY_DEFCHAR=40269072019584::JFRAZIERWhat color is a chameleon on a mirror?Tue Jan 09 1996 12:3124
What I did was add this line to sys$system:modparams.dat on the system running
PCM

TTY_DEFCHAR=402690720

Now as to why...

In sys$library:ttdef.h is the line 

	#define TT$M_EIGHTBIT 32768


and in sysgen, the default value for TTY_DEFCHAR is 402657952,

so 402657952+32768 = 402690720.

Now I can use TPU in the C3 DECterm windows...



Enjoy


James	:-)
853.7And on Unix?42798::ROWELLPaul Rowell @BBP - TMC UKWed Jan 10 1996 07:355
    .-1 also allows ECU and srlmgr to run on PCM - Well done!
    
    How would you effect the same fix on Unix?
    
    -Paul
853.8Not Srlmgr42798::ROWELLPaul Rowell @BBP - TMC UKWed Jan 10 1996 09:325
    Spoke too soon the srlmgr (SWXCR serial utility) doesn't seem to
    recognise the cursor keys. I would be interested if anyone has got this
    to work.
    
    -Paul