Path: utzoo!attcan!uunet!samsung!emory!utkcs2!stc06!rm3
From: rm3@stc06.ornl.gov (MCBROOM R C)
Newsgroups: comp.windows.ms
Subject: Re: TERMINAL problem
Message-ID: <1990Oct11.140704.24192@cs.utk.edu>
Date: 11 Oct 90 14:07:04 GMT
References: <68801@lll-winken.LLNL.GOV> <787@tuura.UUCP>
Sender: news@cs.utk.edu (USENET News System)
Reply-To: rm3@stc06.ctd.ornl.gov (MCBROOM R C)
Organization: Oak Ridge National Lab
Lines: 18

In article <787@tuura.UUCP> risto@tuura.UUCP (Risto Lankinen) writes:
>rhodes@rogue.llnl.gov (Rhodes, Mark) writes:
>
>>I have tried using TERMINAL to connect to a VAX running VMS. The PC
>>arrow keys do not seem to work properly when running EDIT in full
>>screen mode for instance. Any ideas or fixes?
>
>A FOM had the same problem (not with the same host, though).  The cure
>was to use Scroll Lock, which toggles the 'special keys' between being
>used by the TERMINAL.EXE's (editing & Windows-related) functions and
>being sent to the host as keypress escape sequences.  Scroll Lock LED
>lit means that the host will have the keypresses, the opposite that you
>may view TERMINAL's back buffer by pressing 'Up', for instance.
>

Hallelujah!  Now where does it say that in the FM.

RCMC