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

Conference bulova::decw_jan-89_to_nov-90

Title:DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:STAR::VATNE
Created:Mon Oct 30 1989
Last Modified:Mon Dec 31 1990
Last Successful Update:Fri Jun 06 1997
Number of topics:3726
Total number of notes:19516

1987.0. "<esc>#6 kills Decterm windows" by SETH::FITZGERALD () Tue Jan 02 1990 17:03

Since upgrading our LAVC from VMS 5.1 to 5.3 about a week ago, any time a
file containing  <esc>#6  is  typed  all  the  Decterm windows disappear.
However, most of our  satellites  are VS2000's, GPX's and 1 VS3100.  This
problem does NOT happen on the 3100.

We use VWSLAT or set  host  to others nodes that use this escape sequence
in welcome.txt.

Any ideas??

Bill
T.RTitleUserPersonal
Name
DateLines
1987.1Font problem of some kind, I'd guessHANNAH::MESSENGERBob MessengerWed Jan 03 1990 18:5010
Re: .0

<esc>#6 sets the current line to double width, single height characters.  For
some reason, DECterm wasn't able to load the double width font and it
didn't fall back correctly to the default font.

Have you specified your own fonts in a resource file somewhere?  I'm not
sure why you'd be getting this error.

				-- Bob
1987.2Bad Font?SETH::FITZGERALDThu Jan 04 1990 15:098
Thanks for the reply. No we haven't specified any fonts of our own. 

I find  that  if  I  customize  the  window  to use 'Big Font' or set the
terminal width to 132 columns the esc#6 sequence works fine.  Do I have a
font problem? How/where do I check?

Bill
 
1987.3LESLIE::LESLIENew, improved, thinner modelFri Jan 05 1990 06:071
    Don't suppose the Session Manager Log shows any messages?
1987.4It does seem to specific to that fontNOON::MESSENGERBob MessengerFri Jan 05 1990 12:2816
Re: .2

Since DECterm works normally with big or condensed fonts, this does seem to
be a font problem.  The font file that DECterm can't handle is either
sys$common:[sysfont.decw.75dpi]terminal_wide14.decw$font or
sys$common:[sysfont.decw.100dpi]terminal_wide10_100dpi.decw$font, depending
on whether you're on a 75 or 100 dpi system.  One thing that might be
worth trying would be to copy the corresponding font from the VS3100 and
then restarting the server.

It might be worthwhile to get a DECterm log file.  To do this, define
the logical name DECW$DECTERM_OUTPUT in your LOGIN.COM as the name of the
log file and then restart the DECterm controller (e.g. by quitting out of
the session and logging back in).

				-- Bob
1987.5That's it!SETH::FITZGERALDFri Jan 05 1990 14:5313
Bob,

Fantastic. Thanks.  It's  a  corrupt  font  file.   I  copied  the  files
indicated in .4 from a standalone system and  it still didn't work.  So I
copied all  the sys$common:[sysfont.decw.75dpi]*.decw$font files from the
standalone to the LAVC and it worked. 

BTW, the VS3100 was also having this problem.  The user had his decterms
customized to  'Big  Font' and I didn't think twice about it.  That's why
his was the  only  system  on the cluster working when I entered the base
note.

Bill