From:	MERC::"uunet!CRVAX.SRI.COM!RELAY-INFO-VAX" 12-JUN-1992 20:28:41.00
To:	info-vax@kl.sri.com
CC:	
Subj:	Undoc DECTerm features disclosed

I've just been talking to DEC Support about similar DECTerm issues 
as what's been posted here lately.  They told me about the following:

(1) All the DECTerms on the workstation go thru one DECTerm server.  So
if the DECTerm server crashes, you loose ALL your terminal windows
(seems unnecessary, but that's the way it is).  When the first DECTerm
is started up, it looks for the DECTerm server.  If it's not there, 
one is started.  You can trick the new DECTerm into thinking there isn't
a Server present by creating the DECTerm with the node name in a 
different case then the other server.  ie... if the workstation name is
topaz...

create/term/node="TOPAZ:0.0"
create/term/node="topaz:0.0"
create/term/node="Topaz:0.0"

Each of these commands will start a DECTerm on the "topaz" workstation,
but there will be a separate DECTerm server started for each one.
Disclaimer:  I haven't tried this yet, it is just what DEC support told me.
The rest I've tried...

(2) If your DECTerm server is crashing and you want more information as 
to why, you can set the logical DECW$DECTERM_OUTPUT to a file where you 
want to log the info.

(3) You can make the DECTerm menu bar insensitive with the following line
in your DECTerm resource file:

DECW$TERMINAL.main.*.sensitive: false

I've tried that and it works.  It seems like you should be able to specify
which pull down menus you want to make insensitive by specifying them 
in place of the "*", but I haven't tried that yet.

--
Jeff Dalton                    If a train station is where a train stops,
jsd@esl.com                            what does that make a workstation?
ESL Inc., S'vale CA                                     - swiped from net