VP/ix 1.1.1 with Wyse 60 loses "W" and "R" keys

[Jeff Liebermann]

In article <1256 at teslab.lab.OZ> charles at teslab.lab.oz.au (Charles Widepy) writes
>Using a Wyse 60 terminal, which supports a PC scan-code mode, works
>beautifully under VP/ix 1.1.1.  Alt keys, shift keys etc all work
>properly.  The only problem is that the W and R keys don't work at all.
>(Nothing wrong with the hardware.)  This makes it hard to do a "DIR"!
 
Very common problem.......
On the Wyse60 turn OFF xon-xoff handshaking and set it
to either hardware (DTR) handshake or none.
Turn ON XPC handshake.

On the computer, you *MAY* have to use hardware handshaking
or no handshaking to effectively use the PC-TERM mode.  Note
that to enable hardware handshake (ctsflow rtsflow) you will
need to use the modem control device name.  The following is
a tech note stolen from Digiboard's bbs on how to make hardware
handshake work with Wyse 60's.
---------------------------------------------------------------
                 Hardware Handshaking In SCO XENIX
                 ---------------------------------
In some cases it is necessary to use hardware handshaking in SCO XENIX.
For example, newer versions of SCO FoxPlus (TM) data base deactivate
XON/XOFF handshaking so that the ^Q key may be used during editing 
sessions.  To use FoxBase at above 9600 baud, it is necessary to use
hardware flow control, especially if graphics are extensively used.

Following is a scenario for setting up a Wyse 60 terminal (emulating
a Wyse 60) for DTR handshaking.

1. Setting the terminal.
   ---------------------
   Go into set-up mode by pressing the shift-select key combination.
   Press function key F4 to set communication parameters, then set
   RCV HANDSHAKE to DTR.  Use F10 to exit.

2. Setting the operating system parameters.
   ----------------------------------------
   There are many ways to institute hardware flow control within XENIX.
   The simplest is to issue the command "stty ctsflow" from the
   terminal in question.  This causes the port's CTS (Clear To Send) line
   to control the flow of outgoing data.  By putting this command
   in your ".login" or ".profile" files, it will automatically be
   executed whenever you log in.  It will remain effective until you
   log out, or another stty command is issued with a "-ctsflow" parameter.
   For other methods, consult your operating system documentation.

3. Cable Configuration.
   --------------------
   The Wyse 60 terminal set up for DTR receive handshaking outputs a
   HIGH on pin 20 (DTR) when it is ready to receive data, and a LOW
   when it is not.  This pin must be connected to the DigiBoard's CTS
   line on pin 5.  Pins 6 and 20 should be connected together at the
   DigiBoard end of the cable, but should not be connected to the
   terminal.

              DigiBoard                 Wyse 60
              ---------                 -------
                  2 ---------------------- 3
                  3 ---------------------- 2
                  5 ---------------------- 20
                  7 ---------------------- 7
                  6 -\
                 20 -/

4. Modifying the /etc/termcap initialization string.
   -------------------------------------------------
   The last step is to modify the initialization string for the Wyse 60
   in /etc/termcap.  Find the Wyse 60 termcap entry by searching for
   "wy60" (if you are using the vi editor, enter "/wy60").  The init-
   ialization string is the line beginning with ":is=" (usually the 2nd
   line of the entry).  Find the string "Ec21" and change it to "Ec22".
   You will probably want to make a new entry (I call mine "wy60x") with
   this change so that the original is left intact.  Change the 1st line
   to read:
   "wx|wy60x|wyse60x|Wyse WY-60 with hardware handshaking for FoxBase+:\"
---------------------------------------------------------------
Although the above note refers to foxplus problems, the method applies
to any program that uses the xon/off (DC1/DC3) characters for other
purposes (word perfect, pc-term emulators, vpix).  Although XPC
handshake is suppose to take care of handshaking in the PC-term
emulation mode, I've found it to be erratic.  Hardware handshake
works every time I've implimented it.

-- 
# Jeff Liebermann   Box 272   1540 Jackson Ave     Ben Lomond    CA  95005
# 408.336.2558  voice           WB6SSY @ KI6EH.#NOCAL.CA.USA   packet radio
# 408.699.0483  digital pager   73557,2074       cis
# jeffl at comix.santa-cruz.ca.us  uunet!comix!jeffl  jeffl%comix at ucscc.ucsc.edu