Some swear by them, some swear at them. What ever the case, there are a
multitude of Wyse-50 and Wyse-60 terminals out there chugging along,
processing data on the Alpha Micro computer on a daily basis. While some
have great reasons for or against the purchase and use of a Wyse terminal
on an Alpha Micro system, the fact remains that they are out there.
There are about as many versions of the Wyse terminal driver as there are
Wyse terminals out in the field. I have seen installations where as many as
four different versions of a Wyse driver (.TDV) are used in the course of a
day, depending on what software package is currently in use. I have also
seen installations where in house software has been hard-coded to perform
well with a specific Wyse driver. This action most certainly violates
software rules and will eventually bite you where you sit.
I strongly urge anyone writing software for the Alpha Micro to utilize the
information in the AMOS TERMINAL SYSTEM manual DSS-10096-00. This document
describes how to properly use TCRT calls for terminals on an Alpha Micro
system.
More often than not, the major problem with the use of a Wyse terminal and
software is usually due to the Wyse terminal driver. The one true hope of
all Wyse terminal users is to find a perfect Wyse driver that will work
correctly with all properly written software packages.
For years the famed DMSI Wyse50 driver overcame many of the shortcomings of
the Wyse terminal for use with Alpha Micro software. Most notable was the
reprogramming of the function keys to respond to standard AMOS function key
values and the ability to handle the short status lines and position
addressable status line that Alpha Micro terminals and software are so fond
of using.
Perfection is a hard goal to obtain, but the WYSE5V and WYSE6V terminal
drivers discussed in this article perform exceptionally well with all
properly written software packages considering some of the shortcomings of
the Wyse terminals as compared to Alpha Micro terminals.
The WYSE?V drivers, discussed herein, are based on the DMSI Wyse driver.
Some new features have been added and optimization of the way addressable
status lines are handled, are among some of the enhancements.
The WYSE6V.M68 driver (WYSE60.TDV) is specifically designed for use with
the Wyse60 terminal in it's native Wyse-60 mode. A Wyse-60 in it's native
mode is a MODE terminal much like the AM65 terminal is in it's native mode.
The WYSE60.TDV performs very well with the Wyse60 as a MODE terminal.
Reverse highlights are handled properly. The reason for this caveat is that
some older software packages never considered the possibility of running on
a MODE terminal or were written improperly to support MODE terminals.
Usually this is seen with the REVERSE attribute display and can cause
terminal screens to present weird reverse attribute features. If this
happens it is usually the fault of the software program. Since the advent
of and popularity of Alpha Micro's AM65 terminal, many and most software
packages are now written to properly handle MODE terminals. So this should
not cause alarm, it is just to make you aware.
When assembled, the WYSE5V.M68 will produce WYSE50.TDV. WYSE6V.M68 will
produce WYSE60.TDV. Usually, terminal driver source code is placed in
DSK0:[10,2] account. All terminal drivers (.TDV's) must be placed in the
DVR: account or DSK0:[1,6]. Be sure and place WYSE50.TDV and/or WYSE60.TDV
in the DVR: account.
In order for these Wyse drivers to function properly, YOUR TERMINAL MUST be
TURNED ON AT BOOTUP TIME. (Another alternative is to use a program that
calls the driver's initialization routine, such as TRMINI.LIT which is on
the AMUS Network.)
These Wyse drivers perform some special reprogramming of the Wyse terminals
during this initialization routine, so that they perform as expected. You
will also note that during the bootup process the bootup job will pause for
a few seconds when processing a TRMDEF statement that uses the WYSE50.TDV
or the WYSE60.TDV. This is normal and expected. Some of the reprogramming
during the initialization process is extensive and determinate upon the
baud rate that the attached terminal is running at.
Overcoming the Shortcomings
While it is true that through the use of terminal driver system, an Alpha
Micro is terminal independent, almost all Alpha Micro software products and
third party software products are written with the one of the many Alpha
Micro terminals in mind. Therefore, in the situation of non-Alpha Micro
terminals, it is the job of the terminal driver to emulate Alpha Micro
desired features.
The WYSE5V and WYSE6V terminal drivers address the following shortcomings
of the Wyse terminals as compared to standard Alpha Micro terminals.
Properly handles the shortened Top status or Host message field.
Properly handles position addressable top and bottom status lines.
Returns standard Alpha Micro Function key values.
Provides for an EXECUTE and Shift-EXECUTE key.
Properly handles terminal attribute calls.
In addition to the above features, the WYSE6V terminal driver specifically
takes advantage of some of the features of the Wyse-60 terminal and
supports the following.
Supports WYSE60 in Native Wyse60 mode (performs as a MODE terminal)
Provides a HELP key
Provides a PRINT key
Supports special characters for TCRT calls 64 - 78 and TCRT 163 - 172
Keypad function keys perform as indicated. (Except for INS/REPL which
is the EXECUTE/Shift EXECUTE key.)
Provides for setting internal terminal clock.
Provides for aux port interface and main port interface TCRT calls.
Function Keys
One of the advantages to using the WYSE5V with a Wyse-50 terminal or the
WYSE6V driver with a Wyse-60 terminal is that the function keys are
re-programmed to be compatible with Alpha Micro's function key translation
files.
Wyse Function keys are reprogrammed to return standard AMOS function key
values. This is done within the initialization routine in the terminal
driver. It is strongly suggested that AFTER the system has been brought up
using the new driver and the function keys have been reprogrammed (the
terminal must be on during the boot up procedure) you should go into SETUP
mode (press Shift-SETUP keys simultaneously) and save the reprogrammed keys
by pressing Shift-SETUP again and then pressing 'A' on a Wyse 50 terminal
or SAVE ALL for a Wyse 60 terminal. This will prevent future problems of
the function keys not functioning properly after a power failure or after
someone has turned the terminal off.
- NOTE -
Some users have found that they can reprogram the function keys
on a Wyse terminal to perform predesignated functions. Since this driver
pre-programs the function keys so that they are compatible with the AM65
function key sequence, those users will not be able to reprogram their
function keys and still have this driver perform well with AMOS function
key translation files. Users can still program their function keys to
perform desired tasks by using the SET PFK function provided in the SET
command. See SET command in the AMOS Systems Command documentation.
The WYSE?V.TDV terminal drivers, reprogram the Wyse terminal F1-F16 and
Shifted F1-F16 function keys to return the same values as the AM65
terminal. This makes creating function key translation tables for the Wyse
terminals a breeze. Just copy an AM65.??X function key translation file to
the appropriate WYSE?0.??X function key name and you will have function
keys on the Wyse terminal that return the same response as an AM65
terminal.
When installing one of the Wyse terminal drivers, it is necessary for you
to copy all function key translation files that are released by Alpha Micro
(e.g. AM65.CAX[7,13], AM65.WRX[7,12], AM65.VUX[7,0], etc) or other third
party software vendors (e.g. AM65.SVX) into WYSE50.??X for the WYSE50.TDV
driver and/or WYSE60.??X for the WYSE60.TDV driver, in the same account
that these function key translation files already exist.
In other words, if AlphaWRITE is installed on the system, you should log
into WRT: and
COPY WYSE50.WRX=AM65.WRX
for the WYSE50.TDV
In doing this you enable function translation for use with AlphaWRITE when
using the WYSE50 terminal driver.
Many other Alpha Micro software products have function key translation
files. To enable those function key translation files to work with the
WYSE50 driver you must copy those function key translation files to the
appropriate WYSE50.??X name. To enable those function key translation files
to work with the WYSE60 driver you must copy those function key translation
files to the appropriate WYSE60.??X file name.
Be sure and copy an appropriate WYSE50.??X function key translation file
from the AM65.??X function key translation file for any Alpha Micro or
third party software packages that use a function key translation file.
This will allow you to have Alpha Micro compatible function keys on your
Wyse terminal without having to take the time to create one yourself.
EXECUTE Key
Many Alpha Micro software products refer to the EXECUTE key. While most
Alpha Micro terminals have an EXECUTE key the Wyse terminals do not. This
driver translates the INS/REPL key as Alpha Micro compatible EXECUTE key.
The INS/REPL key on a Wyse keyboard is in the upper right hand corner of
the key pad. Pressing the INS/REPL will return the proper EXECUTE sequence
to the program. Pressing Shift-INS/REPL will return the proper
Shift-EXECUTE sequence code to the program.
HELP and PRINT
If you are using a Wyse-60 terminal and the WYSE60.TDV you will also have
the use of a HELP and PRINT key. The SEND key on the Wyse-60 terminal will
return the proper key value for the HELP key. The Shifted-SEND or PRINT key
on the Wyse-60 terminal will return the proper PRINT key value.
STATUS Lines
While the Wyse 50 and Wyse 60 do have top and bottom status lines, they are
not position addressable status lines and they are not of standard Alpha
Micro length. Most Alpha Micro software that uses the status lines, use
addressable status lines in that they are capable of positioning the text
at a certain location on the status line. The Wyse terminals are not
capable of addressable status lines. This version of the WYSE50.TDV and
WYSE60.TDV DO SUPPORT ADDRESSABLE status lines. They handle the method of
addressable status lines internally in the terminal driver.
You will note that the impure area of this WYSE50.TDV is LARGE, 246+ bytes.
The status line position display and shortened lengths are handled in the
impure area of the terminal driver and are displayed accordingly.
- NOTE -
If your specific sight calls for a situation where the terminal driver must
be changed to accommodate different terminals, such as a dial in modem set
up, ALWAYS use the WYSE?0.TDV driver as the driver attached to that
specific TRMDEF statement at BOOTUP time. This will allocated the larger
impure area so that changing of the drivers can occur without destroying
memory locations because of initially using a driver with a smaller impure
area.
Conclusion
For these terminal drivers to perform well with the Wyse-50 and Wyse-60
terminals and provide all the neat features, there is a cost. This is the
amount of CPU time that these drivers will chunk up. Due to the
optimization of the handling of the status lines, these drivers perform
much better and with less CPU time than the older DMSI versions of the Wyse
driver. Most users will not notice it, some will. It is the price to pay to
provide all the desired necessary features on a non-Alpha Micro terminal.
(See "Reasons for Not Buying a WYSE Terminal", AMUS.LOG Journal, Volume 12,
Number 9, Page 53, for more information on Wyse problems).
I have used the WYSE5V (WYSE50.TDV) on my Wyse-50 terminal and the WYSE6V
(WYSE60.TDV) on my Wyse-60 terminal with the following software packages:
There have been reports that some Wyse terminals have different firmware
PROMs that do not work well or perform differently with the codes that
these WYSE?V drivers output. The Wyse terminals that I have tried the
WYSE?V.M68 drivers on, all worked well. Again, not to alarm, just to make
you aware that the firmware for Wyse terminals may be different and stray
from the Wyse documentation that these drivers were written with. Your own
Wyse terminal may or may not perform as these drivers expect them to
perform depending on the year and model of your Wyse terminal. So the
source code is available for you to make the appropriate modifications
where necessary.
If you do find any "bugs" with these drivers or lacking features that you
can't live without, leave E/MAIL on the AMUS Network to GR/AM or contact
AMUS at 1-303-449-6917 for additional assistance.
Additional Information
Following is partial list of standard function key translation file
extensions.
