🚀 go-pugleaf

In article <12J+85D@cs.widener.edu>, poulson@cs.widener.edu (Joshua Poulson) writes...
>I'm looking for a solution to a wierd problem I'm having.  (I have a
>call in with CDC Support on this). 
> 
>Whenever a user with a WYSE 50 terminal logs into our Cyber (running
>L750AB NOS/VE) at the end of the user prolog a set of strange and
>unusual characters are sent to the terminal.  On normal terminals, for
>example PC_Connect_20's, these characters are not seen and probably set
>up some features on the terminal.  On WYSE 50's this causes the terminal
>to have a soft lockup.  (It can be removed by resetting the terminal
>without losing the connection).
> 
>It's annoying.
> 
>I checked through $SYSTEM.PROLOGS_AND_EPILOGS.SYSTEM_PROLOG as well as
>the users' prologs and could find no source for these characters.  I'd
>love to disable them.
> 
>Has anyone else maneuvered around this problem or have any pointers for
>me?    
> 
>Thanks a lot for your help.
> 
>Later,
>-- 
>Joshua R. Poulson                          [Joshua.R.Poulson@cyber.Widener.EDU]
>"I speak only for myself, okay?"           [poulson@cs.Widener.EDU]
>"It is better to play the game and lose than it is to argue about the
>instructions." (Me, 1991)

We've seen control-X control-Y as a prefix to the log in "Welcome to..." 
message.  It does a reset of the Wyse terminal.  So far, I've found no 
solution, nor received a response from inquiries to our sys group. Please, 
let me know if you find a solution... 
   John G. Otto   jgo@fsu.bitnet   jgo@rai.cc.fsu.edu  fsu1::otto

In <12J+85D@cs.widener.edu> poulson@cs.widener.edu (Joshua Poulson) writes:

>I'm looking for a solution to a wierd problem I'm having.  (I have a
>call in with CDC Support on this). 

>Whenever a user with a WYSE 50 terminal logs into our Cyber (running
>L750AB NOS/VE) at the end of the user prolog a set of strange and
>unusual characters are sent to the terminal.  On normal terminals, for
>example PC_Connect_20's, these characters are not seen and probably set
>up some features on the terminal.  On WYSE 50's this causes the terminal
>to have a soft lockup.  (It can be removed by resetting the terminal
>without losing the connection).

>It's annoying.

>I checked through $SYSTEM.PROLOGS_AND_EPILOGS.SYSTEM_PROLOG as well as
>the users' prologs and could find no source for these characters.  I'd
>love to disable them.

>Has anyone else maneuvered around this problem or have any pointers for

My guess is that this sequence of junk characters is due to an
enable_command_redo in the prolog file. Redo activates at the
very end of the prolog and sends the redo_screen_mode and
redo_line_mode sequences from the TDU to initialize the terminal
in case it has downline loaded function keys or a keypad that must
be activated. Check the TDU that you are using to see what sequences
are specified to be sent. They must not be right for the Wyse 50.
You can remove the enable_command_redo from the prolog to verify that
this is the problem.
--
Richard R. Ragan   rrr@svl.cdc.com    (408) 496-4340 
Control Data Corporation - Silicon Valley Operations
5101 Patrick Henry Drive, Santa Clara, CA 95054-1111

In article <33254@shamash.cdc.com> rrr@svl.cdc.com writes:
>In <12J+85D@cs.widener.edu> poulson@cs.widener.edu (Joshua Poulson) writes:
>>Whenever a user with a WYSE 50 terminal logs into our Cyber (running
>>L750AB NOS/VE) at the end of the user prolog a set of strange and
>>unusual characters are sent to the terminal.  On normal terminals, for
>>example PC_Connect_20's, these characters are not seen and probably set
>>up some features on the terminal.  On WYSE 50's this causes the terminal
>>to have a soft lockup.  (It can be removed by resetting the terminal
>>without losing the connection).
>
>My guess is that this sequence of junk characters is due to an
>enable_command_redo in the prolog file. Redo activates at the
>very end of the prolog and sends the redo_screen_mode and
>redo_line_mode sequences from the TDU to initialize the terminal
>in case it has downline loaded function keys or a keypad that must
>be activated. Check the TDU that you are using to see what sequences
>are specified to be sent. They must not be right for the Wyse 50.
>You can remove the enable_command_redo from the prolog to verify that
>this is the problem.

It was indeed enable_command_redo that caused the problem.  Right now
I'm trying to get the SET_TERMINAL_MODEL program from CDC1.CC.LEHIGH.EDU
to recognize the differences between WYSE_50, VT100, and all the
PC_CONNECT's.  Once this works well I'll put them both back in the
system prolog.  Also, support found a TDU (for NOS, but it's
convertible) for the WYSE 50.

I would like to thank all the people that replied to me on this one...
quite a few were from CDC... ;-)

Thanks again,
-- 
Joshua R. Poulson                          [Joshua.R.Poulson@cyber.Widener.EDU]
"I speak only for myself, okay?"           [poulson@cs.Widener.EDU]
"It is better to play the game and lose than it is to argue about the
instructions." (Me, 1991)