 wyse_terminal_news.txt

 (Also Link terminals; Wyse Technologies bought out Link Technologies.)

 //////////////////////////////////////////////////////////////////////////////

 This mostly consists of archived messages not in
 any particular order.

 The very first question EVERYONE asks when first
 sitting down at a Wyse terminal is:

    How do I turn off the keyclick?

 Over the years, a variety of people have discussed
 this question in  "comp.terminals".  Here is one
 example....

 //////////////////////////////////////////////////////////////////////////////

Newsgroups: comp.terminals
Path: cs.utk.edu!darwin.sura.net!europa.eng.gtefsd.com!uunet!cs.utexas.edu
 !math.ohio-state.edu!magnus.acs.ohio-state.edu!sample.eng.ohio-state.edu
 !purdue!mentor.cc.purdue.edu!noose.ecn.purdue.edu!dynamo.ecn.purdue.edu!wb9omc
Message-ID: <wb9omc.746212325@dynamo.ecn.purdue.edu>
References: <24sh2t$9pk@babbage.ece.uc.edu> <6@fawlty.UUCP>
Date: Tue, 24 Aug 1993 17:12:05 GMT
From: wb9omc@dynamo.ecn.purdue.edu (Duane P Mantick)
Subject: Re: Wyse50 key click and Wyse manuals

wwg@fawlty.UUCP (Warren Gay) writes:

>In article <24sh2t$9pk@babbage.ece.uc.edu>,
> kg@myan.uc.edu (Ramaswamy G Krishnan) writes:
> >
> >Is there a way to turn off key-click in Wyse-50 terminal?

>	Of course!
>
>	Keyclick OFF:	ESC e $
>	Keyclick ON:	ESC e '

> I don't have a Wyse-50, but I suspect that you can disable it permanently
> in its setup.
>
> Warren.
> ncrcan.canada.ncr.ca!coutts!wwg@uunet.ca


Indeed.  You can toggle the keyclick with (control-) shift-enter.  Once it
is OFF (or on if desired) go into the setup mode and save the setup.
The keyclick will be "saved" in whatever mode you left it in.

Duane

 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\

 Once the clicking has ceased, the user next
 notices that "vi" is not working correctly.
 The lucky ones eventually discover that the
 problem is an incorrect termcap or terminfo
 entry supplied by the Unix vendor. The less
 perceptive users blame it on Rush Limbaugh.

 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\


Path: cs.utk.edu!darwin.sura.net!howland.reston.ans.net!vixen.cso.uiuc.edu
      !owens.slip.uiuc.edu!jbn
Newsgroups: comp.terminals
Organization: University of Illinois at Urbana
Message-ID: <jbn.765679074@owens.slip.uiuc.edu>
References: <elmvjh.764945459@rwc.urc.tue.nl>
Date: 7 Apr 94 00:37:54 GMT
From: jeffo@uiuc.edu (J.B. Nicholson-Owens)
Subject: Re: WYSE-50 doc needed: ESC-codes & jumper settings
Keywords: WYSE-50

Jeroen van Herel writes:

>I own a WYSE-50 monochrome terminal, but do not have the proper
>documentation.

Here's an incomplete but okay termcap entry:

w9|wy50|wyse50|wyse 50|Wyse Technology WY-50:\
        :am:bw:bc=^H:co#80:li#24:up=^K:do=0.5*^J:le=^H:ho=^^:nd=^L:cr=^M:\
        :sf=^J:sr=\Ej:dl=\ER:dc=\EW:nw=^M^J:al=\EE:ce=\ET:cd=\EY:cl=5.5*\E*:\
        :cm=\Ea%i%dR%dC:im=\Eq:ei=\Er:mi:ct=\E0:st=\E1:it#8:ta=^I:pt:bt=\EI:\
        :so=\EG4:se=\EG0:sg#1:us=\EG8:ue=\EG0:ug#1:mr=\EG8:mb=\EG2:mh=\EGp:\
        :mk=\EG1:mp=\E):is=100*\E`\072:rs=100*\E';:lq=F27:lr=F28:ls=F29:\
        :vb=\E`8\EA04\EA00\E'9:bl=^G:vs=\E'1\E'5:vi=\E'0:ve=\E'1\E'5:lt=F30:\
        :lu=F31:lv=F32:LO=\EA14:LF=\EA11:Nl#8:lw#9:ul:lh#1:ku=^K:kl=^H:kr=^L:\
        :kd=^J:kh=^^:kb=^H:kC=\EY:kD=\EW:kL=\ER:kM=\Er:kI=\EQ:kA=\EE:kN=\EK:\
        :kP=\EJ:ma=^Kj^Jk^Hh^Ll^^H:kE=\ET:kS=\EY:@8=\E7:%9=\EP:&3=\Er:nl=^J:\
        :#2=\E{:#4=^H:%f=\EP:%i=^L:me=\E(\EG0:kn#32:k1=^A@^M:k2=^AA^M:*8=\EY:\
        :k3=^AB^M:k4=^AC^M:k5=^AD^M:k6=^AE^M:k7=^AF^M:k8=^AG^M:k9=^AH^M:\
        :k0=^AI^M:k;=^AJ^M:F1=^AK^M:F2=^AL^M:F3=^AM^M:F4=^AN^M:F5=^AO^M:\
        :if=/usr/local/lib/tabset/wyse50.init:ic=\EQ:mi:ip=17*:\
        :rf=/usr/local/lib/tabset/wyse50.reset:

begin 660 wyse50.init
F/&-L96%R('1A8G,^"CQS970@=&%B<R!E=F5R>2`X(&-H87)S/@HA
`
end

begin 660 wyse50.reset
M/'-E="!S8W)E96X@=&\@.#`@8V]L=6UN<SX*/'1U<FX@;V9F(&%L;"!S<&5C
M:6%L(&5F9F5C=',L('!R;W1E8W1E9"!C:&%R<RP@<W1A='5S(&QI;F5S("8@
M9G5N8W1I;VX@:V5Y"B!L86)E;',^"CQD;R!E=F5R>71H:6YG(&EN('1H92!I
M;FET9FEL92`O=7-R+VQO8V%L+VQI8B]T86)S970O=WES934P+FEN:70^"CQC
M;&5A<B!S8W)E96X@=&\@<W!A8V5S/@H\8VQE87(@<V-R965N('1O(&YU;&QS
'('1O;S\^"G)E
`
end

Here's some of the technical stuff regarding the status line:

(All the following data is from the book "termcap & terminfo"
ISBN#0-937175-22-6.  I recommend everyone that reads this group get a
copy, it can answer most of the more specific questions [like the one
above] with a complete listing of termcap and terminfo capabilities.
It will change your life. Run right out and buy a copy!)

    http://www.ora.com/gnn/bus/ora/item/term.html


The Wyse 50's status line can be written to, so at least 'hs', 'ds='
and 'ws#' should be defined ('hs', 'tsl=' and 'fsl=' for terminfo
respectively).  However, 'ts=' and 'fs=' don't apply (strictly
speaking) since the escape sequence for this terminal takes the data
to place in the status line as an argument.

To write to the status line (called the 'host message field' by the
Wyse 50 documentation, the command:

<escape>F<46 or 100 character message><carriage return>

would need to be broken up into two parts:

(for the 80-column Wyse-50 termcap entry)  (for the equiv. terminfo entry)
:hs:ws#46:ts=\EF:fs=^m:                    hs, fsl=46, tsl=\EF, fsl=^m

(for the 132-column Wyse-50 termcap entry) (for the equiv. terminfo entry)
:es@:ws#100:tc=wyse50:                     es@, fsl=100, use=wyse50

One problem is that programs will need to use the "fs=" capability
immediately after sending the "ts=" entry and writing no more than 46
or 100 chars.  This involves planning and using the termcap/terminfo
database entries correctly.  In my experience, getting most
programmers to use the more common termcap and terminfo capabilities
correctly is not easy, so getting them to use these capabilities
correctly is probably going to be even tougher.  Any program that puts
more data than the status line can hold or thinks that the data should
end with a carriage return (instead of a "fs=" definition, the two
should be handled differently since the status line will only "absorb"
one of them) is broken, the termcap/terminfo definition is fine.

Notes:

* The message can be 46 chars long if you're in 80-column mode or 100
chars long if you're in 132-column mode.

* "es" (termcap and terminfo) means "can use other defined escapes on
the status line" and "es@" negates "es".

* "tc=" ("use=" in terminfo) means to include the termcap (terminfo)
definition for another terminal MINUS the attributes defined up to
that point.  Termcap requires only one "tc=" and it must be at the end
of the entry.  Termcap also requires that the end result of chaining
entries not be more than 1024 (1k) characters.  Terminfo allows more
than one "use=" entry to be given and makes no size restriction on the
total length of the entry.

=============================

There is another addressable area of the Wyse 50's status line (called
the 'local message field' in the documentation) and a way to allow
escape characters in the so-called 'host message field'.  The catch is
that the ENTIRE field has to have the same display attribute.  That
is, the 'local message field' and 'host message field' can have
different attributes, but the entire 'local message field' must have
the same attribute and the entire 'host message field' must have the
same attribute.

Using:

<escape>A2<display attribute code>  to change the local message field
<escape>A3<display attribute code>  to change the host message field

Here's a list of display attribute codes:
<space>  space code (20H)
0  normal               4  reverse             8  underscore
1  blank (no display)   5  reverse and blank   9  underscore & blank
2  blink                6  reverse and blink   :  underscore & blink
3  blank                7  reverse and blank   ;  underscore, blink & blank

<  underscore & reverse                 p  dim
=  underscore, reverse & blank          q  dim & blank
>  underscore, reverse & blink          r  dim & blink
?  underscore, reverse, blink & blank   s  dim & blank

t  dim & reverse          x  dim & underscore
u  dim, reverse & blank   y  dim, underscore & blank
v  dim, reverse & blink   z  dim, underscore & blink
w  dim, reverse & blank   {  dim, underscore, blink & blank

|  dim, underscore & reverse
}  dim, underscore, reverse & blank
~  dim, underscore, reverse & blink

>If not, does anyone know how to extract such info from a terminfo file?

You could decompile the terminfo entry or use the tput program.  I'll
describe the latter because I've just typed all this and I'm getting
tired.

By default, tput assumes that you are using the terminal type specified
by the TERM variable.  If you want to override the value of the TERM
variable, use the -T option:

$ tput -Twyse60 ...and so on...

In general, you simply feed tput the name of the terminal attribute
you want to know about.  To output the terminal's "is3" (init string
#3) capability:

$ tput is3

This output can be stored in a variable as such:

$ INITSTRING3=`tput is3`

(note those are backticks or backward single quotes)

>I can't seem to find a termcap entry that includes the required info

Not suprising since the majority of termcap and terminfo definitions
are substandard and incomplete with regard to features that aren't
used very often (such as writing in the status line or using special
keys).  Even the definition in the "termcap & terminfo" book listed as
a complete Wyse-50 entry is not complete.

Even with that shortcoming, I highly recommend the book since it
provides such enlightenment in termcap and terminfo creation and
editing areas.
-- 
J.B. Nicholson-Owens (*NO* NeXTmail please)
--

 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\
 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\

 Once the termcap has been set correctly (or
 as nearly as possible), then the poor user
 must face the inherent quirks of the Wyse
 design:

 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\
 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\

Path: cs.utk.edu!gatech!howland.reston.ans.net!vixen.cso.uiuc.edu
      !owens.slip.uiuc.edu!jbn
Newsgroups: comp.terminals
Organization: University of Illinois at Urbana
Message-ID: <jbn.770588328@owens.slip.uiuc.edu>
References: <Pine.3.89.9405131528.C3314-0100000@chulkn.chula.ac.th>
          <60.3448.2013.0N19E595@canrem.com> <2siesc$fgm@caslon.CS.Arizona.EDU>
Date: 2 Jun 94 20:18:48 GMT
From: jbn@uiuc.edu (J.B. Nicholson-Owens)
Subject: Re: What are the top ten popular terminals widely use

scott@CS.Arizona.EDU (Scott E Gilbert) writes:
>
>The biggest problem I noticed with ascii terminals is the brain dead method
>of setting attributes using ``magic cookies''.  At least this has been my
>experience using my Wyse-50 terminal.  Under Unix, it messes up the output
>on everything from manual pages to newsreaders.  At one point, I used a
>termcap entry that set all of the attribute sequences to the null string
>just to avoid this.
>
>Also the screen flashes that it gave were annoying.  (When an opening magic
>cookie was dropped, but the closing one hadn't been yet).


Usually I wouldn't quote all that, but my hint is relevant to it all.  I'll
give you (and the rest of the readership of this newsgroup) a hack that will
fix the following problems:

1. flashing when turning on characteristics,
2. the surrounding "magic cookie" character at either side of the effected
   string and
3. 100% compatibility with properly written programs.

Solutions:

1. Speed up the I/O rate to 38.4 kbps.  The flash is still there, but it's
   so quick it becomes less annoying.

   WARNING: What follows is an ugly hack and should not be counted on or
   distributed as a properly-written termcap or terminfo file for the
   Wyse-50.

2. Instead of using the proper attributes for standout do this:

   a) go to the config menu and find the choice that lets you display
      "protected" chars another way.  Select the way you prefer best.
   b) save the config.
   c) use protected chars for standout_on and standout_off (I think
      they're ESC-& and ESC-', but I'm doing this from memory, so don't
      quote me)
   d) be sure to redefine the clear sequence to clear to spaces (NOT
      clear to protected spaces, else that will make your screen clear
      to a reverse video screen).

3. Set the standout glitch factor to 0 since protected chars is an
   embedded characteristic on a Wyse-50.

I've tried this and it works fine, but it's not perfect since
protected chars are actually used for something other than this in
other apps and this causes you to lose a valuable characteristic.

I believe that the magic cookie way of storing characteristics was
done because RAM was so expensive and it was cheaper to store the
characteristic in the same memory address as a character.
--
No NeXTmail please

 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\


Path: cs.utk.edu!emory!swrinde!howland.reston.ans.net!vixen.cso.uiuc.edu
      !owens.slip.uiuc.edu!jbn
From: jbn@uiuc.edu (J.B. Nicholson-Owens)
Newsgroups: comp.terminals,comp.sys.sun.hardware,comp.sys.sun.misc
Organization: University of Illinois at Urbana
Message-ID: <jbn.771033230@owens.slip.uiuc.edu>
References: <2svt7h$126@panix3.panix.com>
Reply-To: jbn@uiuc.edu (J.B. Nicholson-Owens)
Date: 7 Jun 1994 23:53:50 GMT
Subject: Re: Wanted: Good termcap entry for Wyse50 terminal

tlod@panix.com (Thede Loder) writes:
> I have a wyse50 terminal.  For basic usage, such as vi the termcap
> entry we have now works ok.  However, when using Pine or lynx, the
> screen gets messy and doesn't properly highlight, underline, space, 
> etc.

This sounds more like the Pine and lynx software is broken more than
the termcap.  Most programs (even modern ones written recently) don't
bother checking on or using intelligent screen data placement
algorithms with terminals that don't have embedded attributes.  [See
references on "sg" and "glitch" for details.]

>The terminal itself can emulate ADDS ViewPoint,
>HZ1500, tvi910, tvi920, and tvi925.  None of these seem to work
>correctly all of the time.

Most likely the same problem as above.

>Does anyone have a fully functional or more functional termcap entry?  

Well, there you're in a bit of a jam.  There is no such thing as a
perfect Wyse-50 termcap entry unless you're using GNU termcap (which
allows arbitrarily long termcap entries).  BSD 4.3's termcap simply
doesn't allow the termcap entry to be long enough to properly describe
the Wyse-50.  Using terminfo, on the other hand, is quite adequate
since (like GNU's termcap) it too allows arbitrarily long database
entries.

>Please respond via email if possible...

I think on a group of this low content it is not too much to ask to
come back here to get your response.  Also, for every person that asks
a question there is another that wanted to ask but didn't or won't
have to because the question has already been answered.

Since you didn't specify what termcap you're using, I'll give you the
shorter one, the one that should work on all termcap-based systems
(GNU or otherwise).  I strongly urge you to use terminfo if at all
possible, however.  The switch will be well worth your while.

# Wyse 50 termcap by J.B. Nicholson-Owens
w9|wy50|wyse50|wyse 50|Wyse Technology WY-50:\
        :am:bw:bc=^H:co#80:li#24:up=^K:do=0.5*^J:le=^H:ho=^^:nd=^L:cr=^M:\
        :sf=^J:sr=\Ej:dl=\ER:dc=\EW:nw=^M^J:al=\EE:ce=\ET:cd=\EY:cl=5.5*\E*:\
        :cm=\Ea%i%dR%dC:im=\Eq:ei=\Er:mi:ct=\E0:st=\E1:it#8:ta=^I:pt:bt=\EI:\
        :so=\EG4:se=\EG0:sg#1:us=\EG8:ue=\EG0:ug#1:mr=\EG8:mb=\EG2:mh=\EGp:\
        :mk=\EG1:mp=\E):is=100*\E`\072:rs=100*\E';:lq=F27:lr=F28:ls=F29:\
        :vb=\E`8\EA04\EA00\E'9:bl=^G:vs=\E'1\E'5:vi=\E'0:ve=\E'1\E'5:lt=F30:\
        :lu=F31:lv=F32:LO=\EA14:LF=\EA11:Nl#8:lw#9:ul:lh#1:ku=^K:kl=^H:kr=^L:\
        :kd=^J:kh=^^:kb=^H:kC=\EY:kD=\EW:kL=\ER:kM=\Er:kI=\EQ:kA=\EE:kN=\EK:\
        :kP=\EJ:ma=^Kj^Jk^Hh^Ll^^H:kE=\ET:kS=\EY:@8=\E7:%9=\EP:&3=\Er:nl=^J:\
        :#2=\E{:#4=^H:%f=\EP:%i=^L:me=\E(\EG0:kn#32:k1=^A@^M:k2=^AA^M:*8=\EY:\
        :k3=^AB^M:k4=^AC^M:k5=^AD^M:k6=^AE^M:k7=^AF^M:k8=^AG^M:k9=^AH^M:\
        :k0=^AI^M:k;=^AJ^M:F1=^AK^M:F2=^AL^M:F3=^AM^M:F4=^AN^M:F5=^AO^M:\
        :if=/usr/local/lib/tabset/wyse50.init:ic=\EQ:mi:ip=17*:\
        :rf=/usr/local/lib/tabset/wyse50.reset:

begin 644 /usr/local/lib/tabset/wyse50.init
F/&-L96%R('1A8G,^"CQS970@=&%B<R!E=F5R>2`X(&-H87)S/@HA
`
end

begin 644 /usr/local/lib/tabset/wyse50.reset
M/'-E="!S8W)E96X@=&\@.#`@8V]L=6UN<SX*/'1U<FX@;V9F(&%L;"!S<&5C
M:6%L(&5F9F5C=',L('!R;W1E8W1E9"!C:&%R<RP@<W1A='5S(&QI;F5S("8@
M9G5N8W1I;VX@:V5Y"B!L86)E;',^"CQD;R!E=F5R>71H:6YG(&EN('1H92!I
M;FET9FEL92`O=7-R+VQO8V%L+VQI8B]T86)S970O=WES934P+FEN:70^"CQC
M;&5A<B!S8W)E96X@=&\@<W!A8V5S/@H\8VQE87(@<V-R965N('1O(&YU;&QS
'('1O;S\^"G)E
`
end

References:
O'Reilly & Associates "termcap & terminfo"
Gopher: gopher.ora.com


 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\
 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\

 Here are codes emitted by certain keyboard
 keys on a Wyse 50 terminal. This information
 is taken from O'Reilly's book "termcap and
 terminfo" by John Strang, Linda Mui, and Tim
 O'Reilly; ISBN 0-937175-22-6, $22.

    http://www.ora.com/gnn/bus/ora/item/term.html


  ******* Most of the examples in that book feature the Wyse 50! *******

 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..

Direction keys:

   left-arrow   control-H
   right-arrow  control-L
   up-arrow     control-K
   down-arrow   control-J
   home         control-^

Function keys:

   Funct-1      Control-A @ Return
   Funct-2      Control-A A Return
   Funct-3      Control-A B Return
   Funct-4      Control-A C Return
   Funct-5      Control-A D Return
   Funct-6      Control-A E Return
   Funct-7      Control-A F Return
   Funct-8      Control-A G Return
   Funct-9      Control-A H Return
   Funct-10     Control-A I Return

where Control-A is the hexadecimal code 01, Return is the usual carriage-return
format effector 0D, and the middle character is just an uppercase letter.

The Wyse 60 in "Wyse mode" uses essentially the same control sequences as the
Wyse 50.

 ...RSS

 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\
 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\

Here are some notes about getting the Lynx text-mode Web browser to work
usefully with a Wyse 50:

    http://www.flora.org/lynx-dev/html/month1097/msg00205.html
    http://www.flora.org/lynx-dev/html/month1097/msg00229.html


(October 1997)

 //////////////////////////////////////////////////////////////////////////////
 \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\

http://www.wyse.com/service/support/kbase/wits/13209.txt

TOPIC:      WYSE 99GT TERMINAL RESET INSTRUCTIONS

DATE:       OCTOBER 18,1991

THE ISSUE:
        WY 99GT  RESET PROCEDURES

RESOLUTION:
                     WYSE 99GT TERMINAL RESET INSTRUCTIONS

 ***   The following procedure will reset all setup parameters back to the
 ***   factory default.   PLEASE  take note of them before performing
 ***   the following steps.

      1. Power off terminal and disconnect all cables except for power.

      2. Power up terminal holding the letter G depressed. Hold this key
         down until you pass self tests.

      3. Go into setup, select default all, save and exit setup menu.

      4. You can now go back into setup and configure your terminal to your
         required settings.

 //////////////////////////////////////////////////////////////////////////////

http://www.wyse.com/service/support/kbase/wits/13205.txt

WY99GT INSTALLATION INSTRUCTIONS


Directions to change firmware in the 99GT display terminal:

1.      Unplug the power cord from the terminal and turn the rear of the
        terminal toward you (see illustration).

2.      Remove the 2 logic board screws from the rear panel.

3.      Slide the logic board out until two firmware ICs are exposed (it is not
        necessary to slide the logic board out the entire way).

4.      Using a small flat blade screwdriver, carefully pry out present
        firmware in locations 3D and 11D.

o       Be careful when positioning the screwdriver as not to damage the IC
        socket.

5.      Install new firmware:

o       P/N 250624-01 program in location 3D.

o       P/N 250622-01 graphics in location 11D.

   Note:  Be sure notch on the chip is going the same direction as the
          other chips.

           ____________________________________________
         /             ___________                     |
       /              |___________|                    |
      |                ________                      __|__
      |               | 11 D   |                    |     |
      |               |________|                    |     |
      |                ______                       |_____|
      |               |______|                         |
      |                ______                          |
      |               |______|                         |
      |                ________                        |
      |               |________|                       |
      |                ________                        |
      |               |________|                       |
      |                ________                      __|__
      |               | 3 D    |                    |     |
      |               |________|                    |     |
      |                ________   ________          |_____|
      |               |________| |________|            |
      |                                                |
      |                                                |
      |________________________________________________|

               View from Component Side of Board


o       Verify that the IC direction is correct.  The "notch" on the end of the
        chip should be positioned towards the front of the logic board (look
        at the other IC's on the board, they are all pointing toward the
        front, too).

o       Watch to see that all the IC pins push into the socket and do not
        bend over.

6.      Slide the logic board back into the unit; fasten the logic board screws.

7.      Hook up keyboard and power connections


WY99GT "G-Key" RESET INSTRUCTIONS


Please be sure to reset the terminal after installation of firmware chips as
follows:

1.      Turn the terminal off, and remove the cabling from the Auxiliary and
        Modem ports.

2.      Hold down the "G" key on the terminal keyboard while booting up.  (You
        must keep holding the "G" key down throughout the power up sequence).

3.      Wait for the terminal to finish its screen diagnostic during the power
        up sequence.  You can tell when this is over when you see that the
        screen stops flashing.  The status line may appear after a few seconds.

4.      Release the "G" key and go into setup:  (Shift-SetUp.) or (Shift-Select)
        or (F4).

5.      Default all setup parameters by highlighting "DEFAULT ALL":
        (Enter the right arrow key three times) and then the F10 key.
        (Enter F10 again to EXIT or you may change the terminal settings at
        this time.

        Occasionally the terminal's personality parameter will "disappear".
        Repeating step 5 several times should correct this.


      * The key sequence to get into SETUP will vary depending on the keyboard
        type.

 //////////////////////////////////////////////////////////////////////////////

http://www.wyse.com/service/support/kbase/wits/80198.txt

TOPIC:  CODES to change personalities in VT100/220 AND TEK4010/4014

DATE:   07/05/89

PRODUCT:        WY-99GT

THE ISSUE:
        CONFINED TO:    FIRMWARE D0.1
        The following are the WY99GT emulation change commands.

RESOLUTION:
                        CTRL[ = ESC
        ________________________________________________________
        FROM          COMMAND SEQ.                       TO
        --------------------------------------------------------

        VT220/7        CTRL[[61"p                        VT100
        VT100          CTRL[[62;1p                       VT220/7
        VT220/7        CTRL[[?38h                       TEK4010/4014
        TEK4010/4014   CTRL[[?381                        VT220/7
        VT100          CTRL[[?38h                       TEK4010/4014
        TEK4010/4014   CTRL[[?381                        VT100
                       CTRL[[61"p
        TEK4010/4014   CTRL[[42h                         99GT
                       CTRL[[?381
        VT220/7        CTRL[[42h                         99GT
        TEK4010/4014   CTRL[[42h                         WY50
                       CTRL[~"
        VT220/7        CTRL[[?21                         VT52
        TEK4010/4014   CTRL[[42h                         VT220/8
                       CTRL[~=
        TVI910+        CTRL[~<                           VT220/7
        VT220/7        CTRL[[42h                         TVI910+
                       CTRL[~#
        TEK4010/4014   CTRL[[?381                        VT220/8
                       CTRL[[62;2p

   *** All command sequences in TEK4010/4014 mode must be executed in
       block mode (BLK) or be down loaded from the operating system.

 //////////////////////////////////////////////////////////////////////////////

http://www.wyse.com/service/support/kbase/wits/80458.txt

TOPIC: ESC CODES TO DO POWER ON RESET, DEFAULT ALL, SAVE SETUP
 
DATE: 12/6/91

PRODUCT: Wy60, Wy160, Wy99gt in native mode

THE ISSUE:  
     Undocumented escape codes 
 
OVERVIEW: 
     These very useful escape sequences were never documented in
     the Wy60 users or programmers guides as they are in the Wy160,
     even though they are available.
      
RESOLUTION: 
     ESC c T = Default all modes
     ESC c V = Save setup modes to nonvolatile memory
     ESC c W = Save setup modes and tabs to nonvolatile memory
     ESC c X = Power on reset

 //////////////////////////////////////////////////////////////////////////////

http://www.wyse.com/service/support/kbase/wits/80368.txt

TOPIC:  Can I use the WY-85 keyboard with the WY-99GT?

DATE:   06/01/90

PRODUCT:        WY-99GT

THE ISSUE:
        Can I use the WY-85 keyboard with the WY-99GT?

RESOLUTION:
        Yes, with keyboards manufactured after June 1987.  This keyboard
        should be used if you plan on using a VT52, VT100, or VT220
        personality on the Wy99gt.

        WY85 keyboards which WILL WORK can be identified by a 
        metal plate around the opening where the keyboard cable
        plugs into the keyboard.

 //////////////////////////////////////////////////////////////////////////////

http://www.wyse.com/service/support/kbase/wits/80560.txt

TOPIC:  KEYBOARDS FOR WYSE ANSI TERMINALS

DATE:   08/14/92

PRODUCT: WY185  WY285  WY325  WY370

THE ISSUE:
        Which WYSE ANSI keyboards work on which terminals?

OVERVIEW:
        This matrix is the keyboards WYSE has designed for ANSI
        personalities ONLY.  Some of these terminals also support
        ASCII and PCTerm personalities, and therefore may use other
        WYSE keyboards also.

        THESE ARE THE ONLY KEYBOARDS WYSE OFFICIALLY SUPPORTS FOR
        ANSI PERSONALITIES.

        Using other WYSE keyboards in ANSI personalities is NOT
        RECOMMENDED.


RESOLUTION:
        TERMINALS
               WY185           WY285           WY325           WY370

KEYBOARDS
   P/N

ANSI/VT100                                       X
 101 key
900128-02


ANSI/VT220      X                 X                X              X
 105 key
900243-01


ANSI/VT420      X                 X
 107 key     900987-04         900988-04

 //////////////////////////////////////////////////////////////////////////////

http://www.wyse.com/service/support/kbase/wits/80263.txt

TOPIC:  KEYBOARD INTERFACE CABLING ON WY85

DATE:   11/16/89

PRODUCT: Wyse WY-85

THE ISSUE:
        Discussion of keyboard compatibility on WY85.

OVERVIEW:
        1)  How do I determine whether I have an old WY85 keyboard or a
            new Wyse 85 keyboard (manufactured after June 1987)?

        2)  My 3161 keyboard doesn't work on my WY85,  I have documentation
            that says it's supposed to work.

RESOLUTION:
        1)  The new keyboard has a metal shield around the RJ11 connector
            on the keyboard.

        2)  The 3161 keyboard will not work with the WY85,  This information
            was printed in error.

 //////////////////////////////////////////////////////////////////////////////

http://www.wyse.com/service/support/kbase/wits/80671.txt

TOPIC:  ARROW KEYS DIFFERENCES BETWEEN WY85 AND WY185 TERMINALS

DATE:   10/06/92

PRODUCT:           WY-85 WY-185

THE ISSUE:
        Arrow keys are not compatible.

OVERVIEW:
        There is a functional difference between the arrow keys on
        the WY-85 terminal and the WY-185 terminals. The differences
        are detailed as follows:

        Arrow Key               WY-85    WY-185
        ---------------------------------------
        <Up Arrow>  Book Says   Esc[A    Esc[A
                    Actual Code EscA     Esc[A

        <Dn Arrow>  Book Says   Esc[B    Esc[B
                    Actual Code EscB     Esc[B

        <Rt Arrow>  Book Says   Esc[C    Esc[C
                    Actual Code EscC     Esc[C

        <LftArrow>  Book Says   Esc[D    Esc[D
                    Actual Code EscD     Esc[D
        ---------------------------------------

        Notice that the WY-185 terminal produces the CORRECT code. The
        WY-85 omits the "[" . Differences include all personalities,
        except VT-52, and it doesn't matter whether you have 7 or 8
        bits selected.

RESOLUTION:
        The solution for this problem will have to be a software
        solution, since the WY-185 terminal does the codes correctly,
        there will not be a hardware fix for this. One solution for
        UNIX/XENIX systems would be to change the termcap definitions
        to reflect the correct codes. Applications which are written
        for the WY-85 terminals will require modifications to the
        applications to work correctly.


 //////////////////////////////////////////////////////////////////////////////

Path: cs.utk.edu!gatech!europa.eng.gtefsd.com!MathWorks.Com
      !transfer.stratus.com!xylogics.com!Xylogics.COM!carlson
Newsgroups: comp.terminals
Organization: Xylogics Incorporated
Message-ID: <2g1g3g$l62@newhub.xylogics.com>
References: <jeffo.757321161@uiuc.edu>
Date: 31 Dec 1993 15:22:24 GMT
From: carlson@Xylogics.COM (James Carlson)
Subject: Re: Wyse-50 questions

In article <jeffo.757321161@uiuc.edu>,
   jeffo@uiuc.edu (J.B. Nicholson-Owens) writes:
|>
|> I have some questions about the Wyse-50 terminal:
|> 
|> (1) On my Wyse-50, when I print a string with some underlined or
|> inversed part in the middle, there are spaces inserted around the
|> underlined or inversed area.  For instance:
|> 
|> TheBrownFoxJumpedOverTheFence  becomes  The BrownFox JumpedOverTheFence
|>    ^^^^^^^^
|>    this part is underlined
|> 
|> Why does this happen and is there something I can do to properly render
|> the text?  I have the feeling the terminal treats the inverse_on and
|> inverse_off mode setting chars as spaces when printing, but I don't know
|> why.

There are two (major) types of attributes used in terminals -- character
and embedded.

Your terminal is using embedded attributes.  These are special non-
displaying characters which tell the display driver to begin doing a
particular attribute following a screen location, until another
attribute character is encountered.  Since they take up screen memory,
they have to take up display space, and are usually rendered as a blank.
These attributes have the advantages that they can turn on and off
blocks of attributes in a single operation (just overstrike the
attribute location) and make the terminal cheaper to build.

The other type, used by VT100-type terminals, are character attributes,
which can be thought of as "wide" characters, where each screen position
has extra bits to describe the attributes for each individual character.
These have the advantage that you don't have to waste a screen position
to change attributes, but require you to overstrike all of the
characters in a string to reset the attributes and require more memory.

If you have a VT emulation mode on that beast, use <ESC>[<param>m to set
the character attributes.

(If you're trying to do 3270 emulation, embedded attributes are exactly
what you want, anyway, since the 3270 uses that type.)

--
James Carlson <carlson@xylogics.com>            Tel:  +1 617 272 8140
Annex Software Support / Xylogics, Inc.               +1 800 225 3317
53 Third Avenue / Burlington MA  01803-4491     Fax:  +1 617 272 3159

 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\

Newsgroups: comp.terminals
Path: cs.utk.edu!cssun.mathcs.emory.edu!emory!swrinde!howland.reston.ans.net
      !news.sprintlink.net!news.clark.net!rahul.net!a2i!nntp-hub2.barrnet.net
   !news1.digital.com!pa.dec.com!mrnews.mro.dec.com!hannah.enet.dec.com!hedberg
From: hedberg@hannah.enet.dec.com (Bill Hedberg)
Subject: Re: Need ADDS help
Date: 10 APR 95 10:35:30
Organization: Digital Equipment Corporation
Lines: 33
Message-ID: <3mbh8a$4in@mrnews.mro.dec.com>
References: <3m4vhp$ju3@usenet.ucs.indiana.edu>
NNTP-Posting-Host: raynal.enet.dec.com


In article <3m4vhp$ju3@usenet.ucs.indiana.edu>,
 jedick@ezinfo.ucs.indiana.edu (jeffrey dick) writes...
> 
>I use an ADDS terminal (I think the model is 2020) and I am attempting to
>write a vt100/vt220 emulation for it.  Everything works fine, except when
>I try to change the character attributes (underline, reverse, etc.) 
>Before my terminal changes to the new attribute, it inserts a space that
>causes the words on the screen to be shifted to the right and sometimes
>off the edge.  When I try to remove the inserted space, the new character
>attribute becomes turned off as if it had never been sent in the first place.
 
  The "space" is probably an embedded attribute.  This means that the
  terminal is interpreting the data stored in the "space" as attribute
  data.  The attribute data applies to the characters following it.
  Deleting the "space" removes the attribute data.

  Embedded attributes is a trick for conserving memory.  It came from
  a time when memory was "expensive" and tricks were needed to add
  features without adding to hardware cost.  Non-embedded attributes
  use additional memory to record attributes.  Although these scheme
  no longer has a significant impact on hardware cost, it is necessary
  to implement it in followon products for backwards compatibility.

  Embedded attributes are found in WY50 and a few other early terminals.
  VT family products (VT100/200/300/400/500) use non-embedded attributes.
  VT510/20/25 models implement embedded attributes in ASCII emulations.

< rest of msg removed...>
..............................................................................
Bill Hedberg Digital Equipment Corp. Video Architecture Engineering
For more info call 1-800-777-4343 or e-mail terminals@digital.com
http://www.digital.com               ftp://gatekeeper.dec.com/pub/DEC/termcaps



 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\ 

Newsgroups: comp.terminals
Path: utkcs2!ornl!rsg1.er.usgs.gov!darwin.sura.net!zaphod.mps.ohio-state.edu
      !sol.ctr.columbia.edu!destroyer!ais.org!dexter!jsr
From: jsr@dexter.mi.org (Jay S. Rouman)
Subject: Re: wyse 75 -- how do you turn off the keyclick?
Message-ID: <BwtxKF.F2B@dexter.mi.org>
Organization: Private System, Mt. Pleasant, MI, USA
References: <GLASS.92Oct27180838@erewhon.postgres.Berkeley.EDU>
Date: Wed, 28 Oct 1992 11:36:14 GMT
Lines: 10

In article <GLASS.92Oct27180838@erewhon.postgres.Berkeley.EDU>,
 glass@postgres.Berkeley.EDU (Adam Glass) writes:
>
>We've inherited a wyse 75 and it seems like a relatively cool terminal
>with one really really annoying attribute.  Basically it has some sort
>of 'keyclick' turned on, and it is driving everybody crazy.  We've

CTRL-SHIFT-ENTER toggles the keyclick.  Then go into setup mode and
do a save to make this the power-on default.
-- 
Jay Rouman  (jsr@dexter.mi.org  jsr@ais.org)

 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\ 

Newsgroups: comp.terminals
Path: cs.utk.edu!emory!swrinde!zaphod.mps.ohio-state.edu!uwm.edu!cs.utexas.edu
      !qt.cs.utexas.edu!yale.edu!jvnc.net!netnews.upenn.edu
      !anat3d1.anatomy.upenn.edu!hseung
From: hseung@anat3d1.anatomy.upenn.edu (Hyunsuk Seung)
Subject: Re: Keybindings for Wyse-75
Message-ID: <102634@netnews.upenn.edu>
Date: 18 Dec 92 20:17:22 GMT
References: <9212182009.AA11352@anat3d1.anatomy.upenn.edu>
Organization: University of Pennsylvania

I wrote:
> My Wyse-75 terminal is scrolling lines pixel-by-pixel instead of in
> raw chunks.  This "smoothness" loses the connection sometime, because
> it does not update in real-time.  Unfortunately, the SetUp menu does
> not have the "SCRL" field like other models.  Is there a keybinding to
> disable this feature?  What is the tech support number for Wyse?  
>    Any help is appreciated.

Oops, I just discovered that I can control the scrolling speed by...

	Control-UP_ARROW
	Control-DOWN_ARROW

Sorry for the disturbance.

Hyunsuk Seung
hseung@anat3d1.anatomy.upenn.edu

 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\ 

Newsgroups: comp.terminals,comp.unix.misc,comp.sys.sequent,comp.unix.bsd
Path: cs.utk.edu!gatech!concert!seq!futrell
From: futrell@seq.uncwil.edu (andy futrell)
Subject: RE: NEED TERMCAP entry for wy60
Message-ID: <1993Mar26.165131.16083@seq.uncwil.edu>
Keywords: termcap terminfo
Organization: Univ. of North Carolina @ Wilmington
Date: Fri, 26 Mar 1993 16:51:31 GMT

Well, I got great response to my request for a wy60 termcap entry.  So 
thanx to all!  The best response though was, since I had a terminfo entry
on my SYSV box, the infocmp command has a -C option that will dump the
termcap entry from the terminfo lib.  So, I guess it was another case
of RTFM.  Anyway, thanx much, I've got the wy60 entry added and it seems
to be working great.

andy

futrell@seq.uncwil.edu

 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\ 

Newsgroups: comp.terminals
Path: cs.utk.edu!nntp.memst.edu!ukma!wupost!uunet!uunet.ca!canrem!dosgate
      !dosgate![blair.groves@canrem.com]
Subject: wyse terminal cursor key
Message-ID: <1993Mar31.2013.2043@dosgate>
From: "blair groves" <blair.groves@canrem.com>
Date: 31 Mar 93 22:06:36 EST
Reply-To: "blair groves" <blair.groves@canrem.com>
Organization: Canada Remote Systems

Edward Yagi wrote the following:

-> At work, I have a true-blue wyse terminal. I dont know the model
-> number, but what I would like to know is if there is a way to
-> 'redefine' the cursor keys to send the 'correct' code so that pine
-> can recognize them. Currently it sends incorrect keys like ^J and ^M
-> and what-not. I heard taht you could 'bind' keycodes to keys?

Some Wyse terminals will allow the cursor and other non-alpha-numeric
keys to be redefined through the setup facility. An example of one of
these is the Wyse 30. However, the Wyse 50, (a supposedly superior
terminal), doesn't have this capability.

Wyse terminals generally don't have the model number printed in any
visible area on the front, but if you look for a silver-colored sticker
on the back panel of the monitor housing. Somewhere on it, in fine
print, you should see a designation for the model number. With the model
number in hand, there is a better chance that someone here can tell you
exactly what needs to be done, if this is possible on your Wyse model.

blair.groves@canrem.com
--
Canada Remote Systems - Toronto, Ontario
416-629-7000/629-7044

 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\ 

Newsgroups: comp.terminals
Path: cs.utk.edu!gatech!howland.reston.ans.net!torn!nott!cunews
      !freenet.carleton.ca!Freenet.carleton.ca!ab773
From: ab773@Freenet.carleton.ca (Guy Cousineau)
Subject: Re: WYSE 50
Message-ID: <C98vDx.D76@freenet.carleton.ca>
Organization: The National Capital Freenet
References: <1993Jun22.014328.23069@edsi.plexus.COM>  
Date: Sat, 26 Jun 1993 19:56:20 GMT
Lines: 134

In a previous article, jdt@edsi.plexus.COM (John Thompson) says:

>
>I have an old WYSE 50 terminal (literally dug out of a dumpster, 
>but still working) and am wondering if the WYSE 50 emulation 
>setting is compatible with any of the DEC terminals -- I've 

I don't have a WYSE terminal, but I wrote an emulation overlay (blindly)
for a friend of mine.  He says it works great......:

;
; System Equates
;
BDOS	EQU	5		;memory location of BDOS system call
CONOUT	EQU	2		;BDOS function number for console output
;
ESC	EQU	1BH		;Ascii Escape character
;
	ORG	100H		;all programs start here
;
	JP	START		;skip over terminal code to start of program
;
;ZCPR3 data area, do not change
;
	DB	'Z3ENV'
	DB	1
	DW	0
	DW	100H
GOTORC:	JP	GORC		;jump to cursor addressing code
COUT:	JP	COUT0
PRINT:	JP	PRINT0
;
;sequence to turn inverse (or dim) video on
;
IVON$:	DB	ESC,')',0,0,0,0	;must be exactly 6 bytes - fill with 0
	DB	0		;end of string marker - do not change
;
;sequence to turn inverse (or dim) video off
;
IVOFF$:	DB	ESC,'(',0,0,0,0	;must be exactly 6 bytes - fill with 0
	DB	0		;end of string marker - do not change
;
;sequence to clear screen and home cursor
;
CLEAR$:	DB	ESC,'*',0,0,0,0
	DB	0,0,0,0,0,0	;must be exactly 12 bytes - fill with 0
	DB	0		;end of string marker - do not change
;
;sequence to clear from cursor to end of line
;
CEOL$:	DB	ESC,'T',0,0,0,0	;must be exactly 6 bytes - fill with 0
	DB	0		;end of string marker - do not change
;
;sequence to clear from cursor to end of screen
;
CEOS$:	DB	ESC,'Y',0,0,0,0	;must be exactly 6 bytes - fill with 0
	DB	0		;end of string maker - do not change
;
;sequence to turn cursor on
;
CURON$:	DB	ESC,'`2',0,0,0	;must be exactly 6 bytes - fill with 0
	DB	0		;end of string maker - do not change
;
;sequence to turn cursor off
;
CUROF$:	DB	ESC,'`0',0,0,0	;must be exactly 6 bytes - fill with 0
	DB	0		;end of string maker - do not change
;
;sequence to insert line
;
INSLN$:	DB	ESC,'E',0,0,0,0	;must be exactly 6 bytes - fill with 0
	DB	0		;end of string maker - do not change
;
;sequence to delete line
;
DELLN$:	DB	ESC,'R',0,0,0,0	;must be exactly 6 bytes - fill with 0
	DB	0		;end of string maker - do not change
;
;terminal init sequence
;
TINIT$:	DB	0,0,0,0,0,0	;must be exactly 6 bytes - fill with 0
	DB	0		;end of string maker - do not change
;
;terminal deinit sequence
;
DINIT$:	DB	0,0,0,0,0,0	;must be exactly 6 bytes - fill with 0
	DB	0		;end of string maker - do not change
;
;move the cursor to the row in D and the column in E
;
GORC:
	LD	A,ESC		;start escape sequence
	CALL	COUT0		;send to screen
	LD	A,'='		;no send goto command
	CALL	COUT0		;send it
	LD	A,D		;row in A
	ADD	A,' '		;add offset
	CALL	COUT0		;send it
	LD	A,E		;column in A
	ADD	A,' '		;add offset
				;fall through to send it
COUT0:				;send character in A to screen
	PUSH	AF		;save all registers
	PUSH	BC
	PUSH	DE
	PUSH	HL
	LD	E,A		;put character in E as required by BDOS
	LD	C,CONOUT	;function 2
	CALL	BDOS		;do it
	POP	HL		;restore registers
	POP	DE
	POP	BC
	POP	AF
	RET
;
Other codes I have for WY-50 - untested - are:
 

HOME    	ESC {
ROW25 ON	ESC }
ROW25 OFF	ESC e
GOTO ROW25	ESC F
GRAPHICS ON	ESC H ^B
GRAPHICS OFF	ESC H ^C
STORE SCREEN	ESC K
RECALL SCREEN   ESC J
CURSOR OFF	ESC \ 0
CURSOR CHAR	ESC \ char_value

-- 
Guy Cousineau                  On FidoNet CPMTECH and ADAM echo
Ottawa Canada                  Home RCPM (613) 829-6354  8N1
Proud ADAM owner!                               After 11 pm    300-2400 BPS


 //////////////////////////////////////////////////////////////////////////////
 \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\

 It also occurs that Wyse terminals
 can malfunction.  Here follows some
 discussion on what to do.

 Within this web site, there is also a
 collected discussion of "repair hints"
 for several terminal brands.  Wyse
 terminals figure prominantly in this
 discussion.

 //////////////////////////////////////////////////////////////////////////////
 \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\

Newsgroups: comp.terminals
Path: cs.utk.edu!gatech!swrinde!cs.utexas.edu!uunet!tarpit!bilver!bill
Organization: W. J. Vermillion - Orlando / Winter Park, FL
Date: Fri, 23 Jul 1993 21:52:59 GMT
Message-ID: <1993Jul23.215259.8625@bilver.uucp>
References: <7JUL199321223144@rosie.uh.edu>
            <1993Jul23.023808.27782@cs.wisc.edu>
From: bill@bilver.uucp (Bill Vermillion)
Subject: Re: what's a used WYSE-50 worth?

In article <1993Jul23.023808.27782@cs.wisc.edu>,
 finton@barney.cs.wisc.edu (David J. Finton) writes:
>
>I have a used WYSE-50 which I'm going to try to get repaired 
>and sell.  So I was wondering what it's worth.  The screen is
>in great shape, since I've been very careful with the dimmer
>knob and the screen saver.  But it seems to need a new flyback
>transformer, which the local repair shop estimated at $75 - $85,
>including labor.

That's a better deal than most places would charge.

>Can anyone tell me what the terminal would be worth once repaired?

They go for about $150 - when sold with a 30 to 90 day guarantee.

>While we're at it, can anyone tell me what a used Zenith Z-29
>would be worth?

On the Wyse terminals, I have used a place called Automated Systems in
Lincoln, Nebraska.  Flat rate $75 repair on wyse 50's.  If it's only a
board problem, they do board repairs for a flat $50.   Lots of places
do this - and it's only a 5 minute (or less) job to pull the board from
a 50.  (don't have their number handy, but you might call 1-800
information for it)

-- 
Bill Vermillion - bill@bilver.uucp  OR  bill@bilver.oau.org

 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\ 

Newsgroups: comp.terminals
Path: cs.utk.edu!emory!gatech!europa.eng.gtefsd.com!darwin.sura.net
      !haven.umd.edu!purdue!mentor.cc.purdue.edu!noose.ecn.purdue.edu
      !dynamo.ecn.purdue.edu!wb9omc
From: wb9omc@dynamo.ecn.purdue.edu (Duane P Mantick)
Subject: Re: what's a used WYSE-50 worth?
Message-ID: <wb9omc.743706538@dynamo.ecn.purdue.edu>
Organization: Purdue University Engineering Computer Network
References: <7JUL199321223144@rosie.uh.edu>
            <1993Jul23.023808.27782@cs.wisc.edu>
Date: Mon, 26 Jul 1993 17:08:58 GMT
Lines: 61

finton@barney.cs.wisc.edu (David J. Finton) writes:
>
>I have a used WYSE-50 which I'm going to try to get repaired 
>and sell.  So I was wondering what it's worth.  The screen is
>in great shape, since I've been very careful with the dimmer
>knob and the screen saver.  But it seems to need a new flyback
>transformer, which the local repair shop estimated at $75 - $85,
                                                       ^^^^^^^^^
Horse Hockey.  A brand new MPS board (upon which the flyback is resident)
will cost under $120 and takes about 10 to 15 minutes to install and
adjust with a voltmeter.  As long as your logic board is OK, said MPS board
ought to last you at LEAST 3 years not counting lightning strikes.  :-)

>including labor.

	If they're going to charge you $75 and up to replace a flyback
and labor, you're getting charged about 12 to 15 bucks for the flyback
if they are getting them through the wyse-authorized parts centers.
A good technician can replace this flyback in about 15 minutes.
So if the charge is $75 and the flyback costs you $15, you're paying a
$60 labor charge for 15 minutes of work, or approx. $240 per hour!

>Can anyone tell me what the terminal would be worth once repaired?

	Given the above, if you get only the flyback replaced and the
terminal is more than 3 years old, I wouldn't give you 10 bucks for it.

        Unfortunately the WYSE50 has an annoying tendancy to blow up
MPS boards at anywhere between 3 1/2 years and 5 years of age.  A
"repaired" MPS board can last anywhere from 15 minutes to 6 months
from what we've seen here.

	We have had a hard time finding a depot that WILL repair them,
and warranty is either short or nonexistant in these cases.

	On the other hand, a good used wyse (that is, good logic board
and good keybaord) with a brand new MPS board should bring you
a fair piece of change providing you show the prospective buyer a
receipt or other means of proving the board is new.

	We have nearly 300 WYSEs, mostly 50's in our organization.  They
all fail in annoyingly identical and predictable ways.  If you buy the
new MPS board, the biggest favor you can do yourself is to have
your technician REMOVE C206 and replace it with a Nichicon HA series
UHA1H4R7KRA capacitor, 4.7 microfarads at 50 volts non-polarized.

	This capacitor can handle around 7 AMPS of ripple current, and
at high temperatures to boot.  C206 failures on the MPS board are one
of the biggest killers of WYSE50 terminals that WE have seen.

	If you cannot find a local vendor for this capacitor, try
Jacques Ebert Associates in Locust Valley NY.  You will pay several bucks
for this capacitor, but we have not seen a single one fail YET after
around 2 years of installing them.  That beats the pants off of anything
else we've tried, some of which don't last 3 weeks.  The key is the
spec on ripple current.

Duane
Supervisor of Terminal Repair
Purdue University Engineering Computer Network
wb9omc@harbor.ecn.purdue.edu

 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\ 

Newsgroups: comp.terminals
Path: cs.utk.edu!emory!europa.eng.gtefsd.com!howland.reston.ans.net
     !math.ohio-state.edu!cyber2.cyberstore.ca!nwnexus!amc-gw!dsinet!jaws!daveb
From: daveb@jaws (David Breneman)
Subject: Re: WYSE TERMINAL BROKEN - NEED GOOD REFERENCE FOR REPAIR
Message-ID: <2504@dsinet>
Date: 27 Oct 93 14:44:15 GMT
References: <29eq73$25v@titan.ucs.umass.edu>
Organization: Digital Systems International, Redmond WA
Lines: 31

Vera Britto (verab@titan.ucs.umass.edu) wrote:
: Hello all - I have a WYSE terminal that broke (wyse -75) and I wanted a 
: reference of where I could send it to be repaired. Please tell me
: of any positive experience you've had with repairs  (or troubles
: also). The  first problem I had was that although the screen would
: be on, the cursor would remain paralyzed at the top corner and 
: nothing that you tried to type would be processed. Now I have
: moved (so the terminal went through transportation) and the cursor
: doesnt appear and there is this continuous beep when you turn on the
: terminal.
: Thanks in advance,
: Vera
: (p.s. I had it sent to my university repair service before and they said that
: without another keyboard they could not determine if the first
: problem was in the keyboard or the main board.)

A good source for Wyse terminal repair is

    Intelogic Trace
    981 Isom Road
    San Antonio, Texas 78216
    1-800-929-8448

You have to call first for an RMA number before you ship the terminal
(800-929-8448).  Their standard price to fix just about anything is
$125, and about $200 if they have to replace the tube.  Their turnaround
time is about 2-3 weeks.  I've been using them for 4 years, and the
only problem I've had is once they sent me a terminal belonging to
someone else.  They immediately sorted it out and got me mine back and
had the other one picked up at their expense.  "A satisfied customer."

--
David Breneman                        Email: daveb@jaws.engineering.dgtl.com
System Administrator,                 Voice: 206 881-7544  Fax: 206 556-8033
Software Engineering Services
Digital Systems International, Inc.        Redmond, Washington,  U. S. o' A.

 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\ 

Newsgroups: sci.electronics.repair, comp.terminals,
            biz.marketplace.services.computers
Date: Wed, 18 Feb 1998 15:32:11 -0500
From: depotdig <depotdig@gate.net>
Subject: 15 Years in WYSE Repairs!

Are your Wyse terminals acting up?
We can help!  We've got  15 years experience
repairing Wyse products.  Low, flat rates.

             DEPOT DIGITAL SERVICES
 Questions?  Call 813-881-9388 or  Email us!

 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\ 

Newsgroups: comp.terminals
Path: cs.utk.edu!gatech!howland.reston.ans.net!news.sprintlink.net!uunet
      !comp.vuw.ac.nz!actrix.gen.nz!pcowley!peter
From: peter@pcowley.actrix.gen.nz (peter cowley)
Subject: Re: Wyse 30-How to switch between AUX and MODEM Ports
Message-ID: <CwsIzH.78B@pcowley.actrix.gen.nz>
Date: Tue, 27 Sep 1994 13:33:16 GMT
References: <365jil$m4q@newsbf01.news.aol.com>
Lines: 42

GCloseAZ (gcloseaz@aol.com) wrote:
: Hi,

: I am the new owner of a Wyse 30 terminal (anybody have any more?) and need
: to know how to switch between the AUX and MODEM ports. Specifically, I am
: using the MODEM port to access a service, and I'd like to hook the other
: port up to a printer. Is this easy or hard?

: Thanks,
: Gregory Close
: email: gcloseaz@aol.com

Hi Gregory,

Sounds just the sort of thing the terminal was made for. All data normally
goes to the modem port and can be copied to the aux port. 
There appears (I have not tried this but am reading from the users guide)
to be two ways to do what you want.

1) Press PRINT PAGE button. This sends the screen's contents to the printer
attached to the AUX port. The data is formatted exactly as shown on the 
screen.
(Pressed with the SHIFT key, it sends formatted data to the screen.)

  Press COPY PRT button. Turns copy print mode on/off. (Sometimes called
extension/auxiliary mode.) Pressed with the SHIFT key, it turns transparent
print mode on/off.

2) ESC L or ESC p prints an unformatted page.
   CTRL R turns copy print mode on 
   CTRL T turns all print modes off
   CTRL X turns transparent print mode on (enhance mode must be on)

Hope this helps.
If you want a photocopy of all the setup and control stuff then give me your
postal address and I will send it to you.

Cheers, Peter
-- 
Internet : peter@pcowley.actrix.gen.nz   
Post     : 7 Archbold Street, Newlands   
           Wellington, NEW ZEALAND	
Phone    : (64)(4) 477-0927             

 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\ 

Newsgroups: comp.terminals
Path: cs.utk.edu!emory!sol.ctr.columbia.edu!howland.reston.ans.net!EU.net
    !Germany.EU.net!news.dfn.de!urmel.informatik.rwth-aachen.de!fangorn!michael
Organization: An old and gray machine, somewhere in Moria.
Message-ID: <941031945@fangorn>
NNTP-Posting-Host: kaa.informatik.rwth-aachen.de
Date: Mon, 31 Oct 1994 22:16:04 MET
From: Michael Haardt <(michael)u31b3hs@pool.informatik.rwth-aachen.de>
Subject: Tips on fixing Wyse 60 terminals

I own a few of those and thought I should share what I learnt about how
to fix them by now.  Someone else posted a few other hints some time
ago, perhaps we could merge our knowledge.  The usual warnings apply: It
worked for me, but I give no warranty on any advice at all.  Be careful
or you or your terminal may get seriously hurt! High voltage is nothing 
to mess with.

Too dark letters
----------------
The variable resistors VR 202 and VR 401 control base brightness and
dark/bright ratio.  They are tiny white ones, and have the number
written just next to them.  DO NOT CHANGE THE BIGGER BLACK VARIABLE
RESISTOR! A friend of mine did and he has a terminal less now.

Different character height in different lines
---------------------------------------------
The variable resistors VR 302 and VR 303 can be readjusted to fix that.
You may have to try a little for best results.  They are also tiny white
ones, just looking like VR 202 and VR 401.

The display is not straight
---------------------------
This is a little difficult to fix, because you can make things worse
very easy.  Don't say I would not have warned you.  Around the display
tube are small square magnets.  By turning them a little, you can fix
the above problem, sometimes to be again perfect, other times only to
be at least acceptable.  If the pixels do not appear clear at a certain
location (say the upper middle of the screen), then this may help as
well.  It takes some time to change this, though.

Flaky display
-------------
I had the display change its shape out of a sudden or disappear at all.
Hitting the terminal :) fixed it for a while, but eventually it got
pretty bad.  The reason was a capacitor which pins were not bent down
on the soldering side before soldering.  The plastic material which is
fixed on the soldering side of the board bent it down, and broke the
soldering spot a little.  Resoldering it fixed all trouble.  The
soldering quality of the PCB seems rather moderate to me, so probably
there are other people who have terminals with bad soldering spots,
too.

Michael
--
Twiggs and root are a wonderful tree (tm) Twiggs & root 1992 :-)
d? H- s(+)/(-) g! au a- w v(---) C++(+++) UUL++++S++++?++++ L++ 3 E-
                N+++ tv b+ e+ h f+ m@ r++ n@ y+

 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\ 

Newsgroups: comp.terminals
Path: cs.utk.edu!gatech!howland.reston.ans.net!Germany.EU.net!nntp.gmd.de
      !news.rwth-aachen.de!fangorn.moria!michael
Organization: An old and gray machine, somewhere in Moria.
Message-ID: <9503141975@fangorn.moria>
References: <3jucln$d4b@news.primenet.com>
From: Michael Haardt <michael@cantor.informatik.rwth-aachen.de>
Subject: Re: wyse 60 questions
Date: Tue, 14 Mar 1995 23:29:01 MET

web@primenet.com (Wayne Bouchard) writes:
> On this terminal are a few keys I am unfamiliar with. First is the
> 'funct' key (Not F1 etc, this key is labeled 'funct') . Second, the
> 'del' key in vt100 mode seems only to cause problems (is it just
> me?) by preventing input from being sent out the comm port.

I have a few wyse 60 with German keyboards, but they have no funct key
and the del key works fine.  NB: If someone needs German wyse 60
keyboards, I have a few spare ones which I would sell _really_ cheap.

> On the status bar is a clock. This clock always starts at 8 am. Is
> there any way to set this clock and get it to stay set when the
> terminal is powered off?

In wyse 60 personality, you can use ESC c hhmm to set the clock.  Other
than that, just switch on the terminal at 8 am.  :) I don't know why
they did not use a RTC.

> In the keyboard menu, we have a "Wyse word" option and I don't
> understand what the "labels" menu is supposed to do at all.

labels I don't know off hand either, although I guess it are soft
labels.  Wyse Word is nice, press control-capslock to start it.  Btw,
the calculator has no scientific notation and the calendar lacks the
julian calendar correction, but it is nice else and needs no
description to be used.

> The terminal will set its comm port all the way up to 38400 but if I
> stick a modem up to it and try to talk to the modem at 38400, the
> output tends to get garbled.

My terminals do not offer RTS/CTS handshaking and even 19200 baud is
flaky if you have a fast machine which sends as much as possible.  9600
never gave me trouble.

> Okay, last one. This terminal's monitor, unfortunantly, has a tendancy
> to squeal on occassion soon after power on. For the time being, it
> goes away after a few minutes but the time is variable.

I had that happen, too.  After looking around for ages, it turned out
that the plastic cover mounted on the soldering side of the pcb was
fixed that hard, that it broke a soldering spot.  Resoldering it fixed
it, but you need to look very well for it.  The wire on that spot was
bent down some when the plastic/shielding cover was fixed at the pcb.  I
would not wonder if more terminals have that problem.  Try hitting the
terminal, that helped me for a while until one day when it decided to
have been hit and cursed at enough, then later I found that soldering
spot.  I have heard of other hardware problems in this group, although
most related to the wyse 50, which is commonly called a self-nuking
device.  ;-)

I noticed my terminals have different firmware releases, so their menues
and features differ some; don't wonder if someone tells you a menue
choice not offered by your model.  You may readjust the tiny white VRs,
but DO NOT MESS WITH THE BIGGER BLACK ONE.  We lost a terminal that
way, at least we think it was related to that.  Nobody wanted to try it
on a second terminal.

I don't have a wyse manual, but a televideo manual and the model in
question can emulate a wyse 60, so I can tell you escape sequences if
needed.  Unfortunately, this does not tell me the wyse-specific
sequences by which I can reach functions like setting the clock in
vt100 mode.  Btw, it is not a true vt100 emulation: It supports various
functions offered by vt220.  I use a vt220 termcap entry which works
fine.

Michael

 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\ 

Newsgroups: comp.terminals
Date: 12 Apr 1997 22:32:26 GMT
Message-ID:   <5ip2hq$oco$1@apakabar.cc.columbia.edu>
From: Jeffrey Altman <jaltman@watsun.cc.columbia.edu>
Subject: Re: How do you set the clock on WYSE terminals?

In article <5iovro$eg2$1@news.si.usherb.ca>,
Patrick Bernier <bernier@Mlink.NET> wrote:
:
: I have a few WYSE terminals that I use to connect to my
: Linux system as additional consoles. I've noticed that
: they have a clock on the status bar. Does anyone know
: how to set that clock to the correct time, other than
: powering up the terminal at midnight? :)


ESC c 8 hh mm


    Jeffrey Altman * Sr.Software Designer * Kermit-95 for Win32 and OS/2
                 The Kermit Project * Columbia University
       612 West 115th St #716 * New York, NY * 10025 * (212) 854-1344
    http://www.columbia.edu/kermit/k95.html * kermit-support@columbia.edu


 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\ 

Newsgroups: comp.terminals
Path: cs.utk.edu!stc06.ctd.ornl.gov!fnnews.fnal.gov!uwm.edu!news.alpha.net
      !news.mathworks.com!uunet!in1.uu.net!world!mv!usenet
From: bob@erb.mv.com
Subject: Re: WYSE50 Keyclick
Message-ID: <D6C7HC.BJ7@mv.mv.com>
Nntp-Posting-Host: erb.mv.com
Organization: MV Communications, Inc.
Date: Sat, 1 Apr 1995 03:39:11 GMT
References: <3lame9$8n9@wizard.uark.edu>
Lines: 12

In <3lame9$8n9@wizard.uark.edu>,
 kfandre@comp.uark.edu (Kevin C. Fandre) writes:
>
>Does anyone know how to turn off the annoying keyclick on a Wyse 50? 

Hold down the left shift key, then press the enter key on the numeric keypad.
If that doesn't work, then it's control-left shift, and the enter key.

If that doesn't work, call me sloppy and slap me silly -- let me know and
I'll figure it out.

//
//	bob erb		bob@erb.mv.com 
//

 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\ 

Newsgroups: comp.terminals
Path: cs.utk.edu!stc06.ctd.ornl.gov!fnnews.fnal.gov!mp.cs.niu.edu!vixen.cso.uiuc.edu!uxh.cso.uiuc.edu!dawn
Organization: University of Illinois at Urbana
Lines: 37
Message-ID: <3lvar3$hgq@vixen.cso.uiuc.edu>
References: <3luq0b$5js@gandalf.rutgers.edu>
NNTP-Posting-Host: uxh.cso.uiuc.edu
Keywords: wyse50
Date: 5 Apr 1995 23:58:27 GMT
From: dawn@uxh.cso.uiuc.edu (Dawn Owens-Nicholson)
Subject: Re: backspace in wyse50

beaudoin@gandalf.rutgers.edu (D. Beaudoin) writes:
>
> Is there some entry in termcap/terminfo that can be used to make the
> backspace on a wyse50 behave as a real destructive backspace instead of
> just a left arrow? (I'm using a Link MC2 terminal emulating a wyse50 and I
> can't redefine the backspace key in the MC2 setup, so that's not an option.)

You could, in a private termcap or terminfo entry, but you shouldn't
redefine the wyse50's backspace because it is *really* your terminal
settings or your Link MC2's Wyse50 emulation that is broken.

First, I'd try checking your stty settings and make sure you have
destructive backspaces turned on.  "stty echoe" or "stty crterase"
would be a good place to start, but check the man pages on your system
to be sure.

If that fails, I'd check your wyse50 termcap or terminfo entry (you
don't say which you're using) to make sure it's set correctly ("bc=^H"
should be in there, and bc= shouldn't be redefined to anything else in
the entry, I've included a good [but not 100% complete due to space
limits in BSD termcap] wyse50 termcap entry in another post on
comp.terminals.  Check for my name in other posts).  You could use the
include other entry option redefining only bc=, check the manpage for
termcap or terminfo for details on this.  If you've got the manual for
your terminal, you'd be 200% better off creating a whole new entry for
the native mode (don't use emulations of other terminals!).  Get a
copy of "termcap & terminfo" from O'Reilly & Associates.

Lastly, and only in a private termcap/terminfo entry or one that is
suitably marked as being LinkMC2's emulation of a Wyse50 (do *not*
redefine the real wyse50 entry), you could set bc= to "^H ^H" (careful,
there's a space in there).  This is incredibly ugly and improper and
will probably break other things, but it should work for the Unix
shell.  The only reason I mention this is to be complete in answering
your question, but I urge you to investigate stty options first.
Doing this is not only more hassle, but risky for all the other users
on your system that use this termcap or terminfo entry that DON'T want
destructive backspaces.

 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\ 

Newsgroups: comp.terminals
Path: cs.utk.edu!cssun.mathcs.emory.edu!hobbes.cc.uga.edu
      !news-feed-1.peachnet.edu!news.Gsu.EDU!gatech!udel!rochester
      !cantaloupe.srv.cs.cmu.edu!das-news2.harvard.edu!oitnews.harvard.edu
      !news.cs.umb.edu!betsys
From: betsys@cs.umb.edu (Elizabeth Schwartz)
Subject: Re: Anyone using WYSE terminals on Sun OS 4.1.3? Any other terminals?
Date: 04 May 1995 14:00:49 GMT
Organization: University of Massachusetts at Boston
Lines: 34
Message-ID: <BETSYS.95May4100049@terminus.cs.umb.edu>
References: <BETSYS.95May3143612@terminus.cs.umb.edu>
            <3o8qgi$fbp@darkstar.UCSC.EDU>
NNTP-Posting-Host: terminus.cs.umb.edu
In-reply-to: urbick@cats.ucsc.edu's message of 3 May 1995 20:53:38 GMT

In article <3o8qgi$fbp@darkstar.UCSC.EDU> urbick@cats.ucsc.edu (Paul) writes:
>
>In article <BETSYS.95May3143612@terminus.cs.umb.edu>,
>Elizabeth Schwartz <betsys@cs.umb.edu> wrote:
>[snip]
> >
> > Have you used Wyse terminals on Sun OS 4.1.3 and did you have any
> > problems?  We're worried about VT100 emulation, 
>
> [snip]
>
> I recently installed a wy55 (with ascii keyboard) on our Sparc 1000 
> as the system console and had problems emulating VT100 (ansi).  I was
> advised by Wyse that the ascii keyboard was not compatible with VT100
> emulation and ended up emulating wy60.


That's good to hear!

Actually, I had a long talk with Ray at Wyse Tech Support about keyboard
mapping. The issues with the VT100 mapping are that some of the keypad keys
are remapped to PF keys, and some of the function keys are mapped/remapped
in some way. This was of no concern to us since we don't use those keys
anyway, on our Unix system. Our biggest worries were getting the ESC, 
CTRL, and " ~ " keys in familiar places.

If the vt100 emulation works with Emacs, Pine, Elm, and lynx, with 
correct cursor movement and screen re-drawing, we'll be happy.

thanks, Betsy
--
System Administrator                  Internet: betsys@cs.umb.edu
MACS Dept, UMass/Boston               Phone   : 617-287-6448
100 Morrissey Blvd                    Staccato signals
Boston, MA 02125-3393                      of constant information....


 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\

Newsgroups: comp.terminals
Path: cs.utk.edu!cssun.mathcs.emory.edu!emory!gatech!howland.reston.ans.net
      !agate!news.mindlink.net!vanbc.wimsey.com!news.rmii.com!rainbow.rmii.com
      !mdaymon
From: mdaymon@rmii.com (Maxwell Daymon)
Subject: Re: Wyse terminal - keyboard?
Date: 10 May 1995 02:05:29 GMT
Organization: Rocky Mountain Internet Inc.
Lines: 23
Message-ID: <3op719$cv2@natasha.rmii.com>
References: <3oaa15$356@natasha.rmii.com> <3ooih5$8c2@mrnews.mro.dec.com>
NNTP-Posting-Host: rainbow.rmii.com
X-Newsreader: TIN [version 1.2 PL2]

Bill Hedberg (hedberg@hannah.enet.dec.com) wrote:
: In article <3oaa15$356@natasha.rmii.com>,
:  mdaymon@rmii.com (Maxwell Daymon) writes...
: >I've got a Wyse terminal (actually, a Wyse PC, but I want to use it as a 
: >terminal).

: >Can I make an adapter for a "normal" 6-pin DIN PC keyboard or do I need a 
: >Wyse keyboard? If I need a Wyse keyboard, where and how much?

:  Most likely, WYSE PC's use standard PC keyboards.  It would be easier
:  and more likely to work to find a PC keyboard with a 6-pin connector.

Actually, they use the same large DIN connectors as old Wyse terminals. I 
see them in many places (public library) and the dimensions are the same.

A normal PC keyboard definately does NOT work. It's a loaded 10-pin DIN 
and about 1 or 2mm larger than a PC 6-pin DIN connector.

:-(  Looks like I'm out of luck.

------------------
  Maxwell Daymon
 mdaymon@rmii.com
------------------

 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\ 

Article 4077 of comp.terminals:
Path: cs.utk.edu!news.msfc.nasa.gov!europa.chnt.gtegsc.com
      !howland.reston.ans.net!math.ohio-state.edu!uwm.edu!reuter.cse.ogi.edu
      !news.co.intel.com!chnews!inews.intel.com!itnews.sc.intel.com!usenet
From: Bennet Wong <bennet_wong@ccm.sc.intel.com>
Newsgroups: comp.terminals
Subject: Re: Wyse terminal - keyboard?
Date: 12 May 1995 20:18:26 GMT
Organization: Intel - Internet Information Technologies
Lines: 6
Message-ID: <3p0fqi$s6r@itnews.sc.intel.com>
References: <3oaa15$356@natasha.rmii.com> <3ooih5$8c2@mrnews.mro.dec.com>


If you have the old DIN connector, the only way is to get a old Wyse 
keyboard. The key signal between the RJ-11 style, PC style and the old 
Wyse DIN are all different. (I know, I use to work at Wyse).


 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\ 

Newsgroups: comp.terminals
Path: cs.utk.edu!gatech!news.sprintlink.net!noc.netcom.net!netcom.com!jolomo
From: jolomo@netcom.com (Joe Morris)
Subject: Re: wyse150 info needed
Message-ID: <jolomoD903D2.MMM@netcom.com>
Organization: Bozo Central in Atlanta
X-Newsreader: TIN [version 1.2 PL1]
References: <3pp1nj$oe3@giga.bga.com>
Date: Mon, 22 May 1995 22:19:49 GMT
Lines: 22
Sender: jolomo@netcom20.netcom.com

On 22 May 1995 03:51:15 GMT Doug Maxey wrote:
> Greetings,
> Have just become the proud owner of a coupla wyse150 terminals,
> as surplus from a bank.

> No docs, etc.

> Some questions:
>
> 1) how do you get into setup mode?

First try hitting the "Select" key in upper right corner, if that
doesn't work try shift-Select

> 2) if there is no setup mode, how do you set the beast to half-duplex?

In setup mode screen, hit F4 for Comm, then arrow down to "Comm ="
field and press the space bar till you get "Comm = HDX".

Then hit F12, then space to toggle "save" to "yes" and hit
F12 again.

Good luck
--
  Joe Morris, SysAdmin and Not Insane
  "Honey, they're in *everybody's* eggs"  --firesigns


 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\

Newsgroups: comp.terminals
Path: cs.utk.edu!willis.cis.uab.edu!nntp.msstate.edu!emory!swrinde
      !howland.reston.ans.net!xlink.net!rz.uni-karlsruhe.de!news.uni-ulm.de
      !news.belwue.de!news.belwue.de!fu-berlin.de!cs.tu-berlin.de!hausutzu
From: hausutzu@cs.tu-berlin.de (Utz-Uwe Haus)
Subject: Re: RJ11 <-> DIN Keyobard connector ?
Date: 6 Jun 1995 13:16:16 GMT
Organization: Technical University of Berlin, Germany
Lines: 30
Message-ID: <3r1kf0$mc@news.cs.tu-berlin.de>
References: <3qhsnn$3ct@news.cs.tu-berlin.de> <3r0iho$3jp@mrnews.mro.dec.com>
NNTP-Posting-Host: para.cs.tu-berlin.de

hedberg@hannah.enet.dec.com (Bill Hedberg) writes:

[have to followup to my own article..]

>In article <3qhsnn$3ct@news.cs.tu-berlin.de>,
 hausutzu@cs.tu-berlin.de (Utz-Uwe Haus) writes...
>> 
>>I just got two used Olivetti Terminals (WS 785, build around 1990), and
>>they both don't have a keyboard :< 
>>
>>Supposedly they understand standard PC-keyboards, but the connector is a
>>4-pin RJ style one. How can I wire those 4 lines to a standard DIN connector?
>>
>>Or do I have to get an Olivetti - keyboard (:<)?

>  Try using a WYSE 60 keyboard.

Thanks for the tip - I got the same one from somebody via e-mail. However, 
I just talked to a guy from Olivetti, and he told me, thak while most
parts were built by Wyse (Wyse 120 is the one he mentioned), the keyboard
used a proprietory chip, making it impossible to use the Wyse keyboard.
He also told me that he sold the last one he had about 2 month back :<

Anybody care to send me a leftover keyboard ? :*{

Utz
-- 
+----------------++-----------------------------------------------------------+
| Utz-Uwe Haus   ||  contact me via INTERNET: hausutzu@cs.tu-berlin.de        |
|                ||                           haus@math.tu-berlin.de          |
| Berlin/GERMANY ||                    or     root@pse.bln.sub.org            |


 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\


Newsgroups: comp.terminals
Path: cs.utk.edu!gatech!howland.reston.ans.net!news.moneng.mei.com!uwm.edu
      !reuter.cse.ogi.edu!news.ssd.intel.com!chnews!itnews.sc.intel.com!usenet
Organization: Intel - Internet Information Technologies
Message-ID: <3rqlp5$3jp@itnews.sc.intel.com>
References: <3r67lu$srl@freenet.vancouver.bc.ca>
To: dastow@freenet.vancouver.bc.ca
From: Bennet Wong <bennet_wong@ccm.sc.intel.com>
Subject: Re: alloy link terminal
Date: 16 Jun 1995 01:12:05 GMT

Link PCST/G! haven't heard that term for a long time - I am one of the 
original designers.

Here is the bad news, you need to find a OLD Link keyboard, new Link's
keyboard have a different design (WYSE) and will not work. Try to find
a keyboard for the following LINK model: MC3, L125 or L220.

Link is now part of Wyse Technology, I believe their old 800 number still 
work (1-800-HIT-LINKS). As for Alloy, last time I heard they are in very 
bad shape and may be a goner by this time (??)

The old keyboard is kind of expensive: $70 - $100 US each, if you buy it 
new from Wyse/Link.

Good Luck.

 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\

Path: cs.utk.edu!cssun.mathcs.emory.edu!emory!metro.atlanta.com
      !news.sprintlink.net!cs.utexas.edu!math.ohio-state.edu
      !hobbes.physics.uiowa.edu!news.uiowa.edu!orpheus
From: orpheus@isca.uiowa.edu (Orpheus)
Newsgroups: comp.terminals
Subject: Re: Wyse-60
Date: 17 Jun 1995 19:48:04 GMT
Organization: University of Iowa, Iowa City, IA, USA
Lines: 30
Distribution: world
Message-ID: <3rvbhk$bv5@nexus.uiowa.edu>
References: <3rtjcm$40h@raffles.technet.sg>
NNTP-Posting-Host: serial.music.uiowa.edu

mchong@technet.sg (Michael Chong) writes:

>We just inherited some wyse terminals with no manuals and we can't get 
>the terminals into setup mode.

>Most of our terminals go into setup mode a la VTxxx terminals, with the 
>F3 key.

>Any help appreciated.

>Thanks in advance.

>Cheers.

   A lot depends on which keyboard you have. If you have the new keyboard,
with 16 function keys, hitting shift-Setup will get you into setup. 

  On the PC101 keybaord, use shift-Select (upper right corner).

  If you have the old AT keyboard, which is really small and nifty, I think
it's shift-control-tab or something. You probably want to get a new keyboard
if you have the AT-style one, becuase the WY60 cannot do VT emulation with that
keybaord. 
 
If you have more specific questions, or my answer wasn't clear, feel free to
mail me.
-- 
__________________________________________________________________________ 
   --Jeffrey Dunitz  (orpheus@kahless.isca.uiowa.edu) (319)354-1830
     Apollo/DOMAIN System Administrator, CondoLAN

 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\

Newsgroups: comp.terminals
Path: cs.utk.edu!stc06.ctd.ornl.gov!rsg1.er.usgs.gov!jobone!newsxfer.itd.umich
      .edu!agate!howland.reston.ans.net!news.sprintlink.net!globe.indirect.com
      !stu.firstsol.com!user
From: sir@firstsol.com (Stu Rutkin)
Subject: Re: Wyse break
Date: Wed, 12 Jul 1995 06:26:43 -0700
Organization: 1ST SOLUTIONS, INC.
Lines: 19
Message-ID: <sir-1207950626430001@stu.firstsol.com>
References: <3tv6p0$3js@news.nde.state.ne.us>
NNTP-Posting-Host: stu.firstsol.com

In article <3tv6p0$3js@news.nde.state.ne.us>,
chammack@genie.esu10.k12.ne.us (Chris Hammack) wrote:

> Argh!  I don't turn on the wyse for 3 weeks, and now...no picture!  When 
> you type on the keyboard, it does the usual beeping...but no picture ever 
> appears...and it's not a simple resolution problem. 
> 
> It's an older wyse, I think a 60 (maybe a 50?)...any thoughts?  Is it 
> roasted beyond general fixing or is this some wierd screen saving thing 

Type of terminal is shown on a plate either on the top of the base
(Wyse 50's) or back of the cover (Wyse 60's and newer Wyse 50's).
Sounds like the monitor/power supply  (MPS) board has croaked.

There are plenty of repair services around that will fix those kind of
boards for less than $65 (some around $40).  You'll have to pay for
freight to get it there and maybe back, too.

Call me--we sell Wyse terminals new and used, but I often refer people
to repair places close to where they are, to minimize the freight.
+1 602/997-5703.

 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\

Dealer for new Wyse-30 terminals.

Monochrome ASCII terminal; includes 83-key keyboard with 4 dedicated function
keys shiftable to 16.  80 column by 24 line display, 2 asynchronous RS-232
serial ports.  New, no manual, 90-day warranty.

DEALER: Electrified Discounters, 110 Webb Street, Hamden, CT 06517.  M-F 9-7
EST.  FAX: (203)777-7853.  Orders to: (800)678-8585 or (203)787-4246.

 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\

Dealers in the United Kingdom that sometimes handle used Wyse equipment:

WDP..................0181-464-9011  (in early 1998 sold Wyse 60s for 95 pounds)
Lightning Systems....0181-866-8001
MPC Services.........0181-908-6710

 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\

Newsgroups: comp.terminals
Path: cs.utk.edu!gatech!howland.reston.ans.net!newsfeed.internetmci.com
      !globe.indirect.com!stu.firstsol.com!user
From: sir@firstsol.com (Stu Rutkin)
Subject: Re: wyse 60 setup?
Date: Mon, 16 Oct 1995 06:15:04 -0700
Organization: 1st Solutions, Inc.
Lines: 26
Message-ID: <sir-1610950615040001@stu.firstsol.com>
References: <Pine.SOL.3.91.951015184053.16150A-100000@web>
NNTP-Posting-Host: stu.firstsol.com

In article <Pine.SOL.3.91.951015184053.16150A-100000@web>, Goldarg
<goldarg@azstarnet.com> wrote:

> How do you get into and change the setup on a wyse 60, I dont have a 
> manual and would like to try to config this thing.
> 
>
e-mail didn't work.

Depends on the type of keyboard.  Try either (simultaneously) Shift-Setup 
or  Shift-Setup-SysReq, or Shift-Select.

You'll get a series of menus, starting with the top setup, a directory to
the other ones.  Function keys  will
get you through that, then arrow keys.  To get out of where you are, use
F10, then right arrow to Save All, then F10 again, so you
don't have to do it after powering off and on.
 
Stu R.

-- 
stu rutkin  
1st Solutions, Inc.  
11460 N. Cave Creek Road #12, 
Phoenix, AZ 85020
602 997-5703 Fax 602 997-1688

 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\

Newsgroups: comp.terminals
Path: cs.utk.edu!news.msfc.nasa.gov!newsfeed.internetmci.com
      !globe.indirect.com!stu.firstsol.com!user
From: sir@firstsol.com (stu rutkin)
Subject: Re: Link 125 help needed
Date: Thu, 07 Dec 1995 07:13:29 -0700
Organization: 1st solutions, inc.
Lines: 106
Message-ID: <sir-0712950713290001@stu.firstsol.com>
References: <4a60ud$5s5@crl14.crl.com>
NNTP-Posting-Host: stu.firstsol.com

In article <4a60ud$5s5@crl14.crl.com>, drseuss@crl.com (David Bedno) wrote:

> Ok...I've got this ancient Link 125 terminal that Link/Wyse
> can't help me with.  The user's guide isn't available anymore.
> The tech support person tried to convince me that if I put the
> terminal into wy50 mode, I'd be able to use any wy50 code; 

Speak to Chris, Rose, or David K. at tech support.  They know that
terminal cold.  And, they're great.
1-800/448-5465.
 
> A) Reset terminal to factory defaults.

Get to the Setup menu by simultaneously pressing Shift-Setup.

Within the setup menu, push the letter "D" (for default), "S" (Save),
then "E" (exit) to fully implement the factory settings.  Then, go
back into setup and configure the terminal how you want it.  If
something strange still occurs, turn the terminal off for 10 seconds,
hold down the letter "G" while you power it back on and release it
when you see the cursor, then default the terminal.  On some of the
newer terminals, this procedure re-initializes a PROM within.

> B) Reset the arrow keys to defaults.

If you did A) above, then change the emulation, you'll need to push the
letter "F" which causes all screen attributes, c ursor and function key
default values to be loaded for that emulation.

> C) Program the function keys via setup mode

I don't believe you can do it.

> D) Program the function keys via ESC sequences

To program cursor and function keys, enter the following code in the exact
sequence:
 
   SHIFT   ESC |  p1  p2  "message" CTRL Y
 
The vertical-bar character after the ESCape key is like a colon but is
[one vertical line or perhaps two] (my keyboard doesn't have it).  p1
is the "value" number of the key you want to program,

                                    p1 value codes:

Key to program    Unshifted code Shifted code
F1                            1                    A
F2                            2                    B
F3                            3                    C
F4                            4                    D
F5                            5                    E
F6                            6                    F
F7                            7                    G
F8                            8                    H
F9                            9                    I
F10                           :                    J
F11                           ;                    K
F12                           <                   L
F13                           =                   M
F14                           >                   N
F15                           ?                    O
F16                           @                 P
up arrow                   -                    )
down arrow              .                    *
right arrow                0                   ,
left arrow                   /                    +

(I hope that the formatting is not lost in cyberspace.)

p2 is one of the following:
 
   1 send to the computer 
   2 send to the screen (local)
   3 send to computer and screen (half duplex)
   4 send to printer only
   5 send to printer and computer only
   6 send to printer and screen only
   7 send ot printer, computer, and screen.
 
The message may be up to 10 characters.
 
This sequence will enable you to program in all modes.  If you are using
Wyse 50 emulation, you can program like a Wyse 50.  ESC z Key Value Code,
Message, DEL.    The key value code for Wyse 50 is different.  Unshifted,
same keys to program as above, starts with @ then is A through O for the
function keys; for Shifted, ` then a through o, again for the function
keys only.
 

> 
> Currently my down arrow key is programmed to "...|^[=", and that
> just doesn't cut it.

By the way, we're a Link distributor, and if you let me know an address,
I'll make a copy of the manual and mail it to you.

Stu R.
Stu Rutkin   (sir@firstsol.com)
1st Solutions, Inc.
11460 N. Cave Creek Rd. #12
Phoenix, AZ 85020

 voice: +1 602/997-5703
   fax: +1 602/997-1688

 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\

Newsgroups: comp.terminals
Path: cs.utk.edu!willis.cis.uab.edu!nntp.msstate.edu!cssun.mathcs.emory.edu
      !swrinde!newsfeed.internetmci.com!in2.uu.net!nntp.news.primenet.com
      !news.primenet.com!news.primenet.com!not-for-mail
Organization: Data Pro
X-Posted-By: ip208.cap.primenet.com
Message-ID: <30DDC1EB.6E4@primenet.com>
References: <4amtmi$bdm@alterdial.UU.NET> <30D05A4D.6C49@verity.com>
Date: 24 Dec 1995 14:12:02 -0700
From: Samartha Deva <devasam@primenet.com>
Subject: Re: Wyse 150 Terminals

Ben Wong wrote:
> 
> jim@jmconsult.com wrote:
> >
> > Looking for info on the Wyse 150 (or sucessor).

> > know where I can get a programmer manual (not user manual)
> > for it.

WARNING: manual is thin and _very_ expensive for it's size ( $ 50 )
or so and the same size as the users manual but if you want to do
anything with this terminal, you need it.

  WY-120/WY-150 Programmer's guide, Part # 880984-02 Rev. A

was very upset and frustrated when I got the manual, still am @$%@#$%@#$!

Samartha

 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\

Newsgroups: comp.terminals
Path: cs.utk.edu!stc06.ctd.ornl.gov!fnnews.fnal.gov!uwm.edu!math.ohio-state.edu
      !howland.reston.ans.net!torn!news.dal.ca!news.nstn.ca!inforamp.net!usenet
From: Blair Groves <blair.groves@canrem.com>
Subject: Re: Help with Wyse WY-60
Date: Tue, 26 Mar 1996 22:37:32 -0500
Organization: informamp.net
Message-ID: <3158B7FC.1294@canrem.com>
References: <u3zkd6qh.fsf@hasler.gt.org>

John Hasler wrote:
>
> I would be very thankful if someone  would advise me about a Wyse terminal
> I am attempting to use with my Linux system.
>
> The data plate reads:
>
>         Model No.       WY-60
>         Part No.        900109-01
>         Serial No.      01311600534
>
> The ROM on the board is a 27512 labeled:
>
>         (c) Wyse Tech
>         91 Rev. A
>         251057-01
>
> When I send 9600 baud ascii to the terminal, it displays it as expected.
> When I type on the keyboard, however, the terminal sends what appear to be
> scancodes.
>
> Here is a sample of codes sent (in hex):
>
> Key Label   Key Press    Key Release
>     1         82           02
>     2         83           03
>     3         84           04
>     4         85           05
>     5         86           06
>
> Is there any way to get this terminal to transmit normal ascii?
>
> Thank you for any help you can give.  I have no data at all on this terminal.
>
> --
> John Hasler
> jghasler@win.bright.net
> N6512 110th St.
> Dancing Horse Hill
> Elmwood, Wisconsin 54740


John, your terminal is running the "PC Terminal"
mode, whereby it does exactly as you said: it will
take in ASCII and ANSI information to display to
the screen, and when you press a key on the
keyboard, you will get the PC scan code for that
key. Best bet is to use the native mode (WY-60
mode), as it is a   known standard, and termcaps
are often included.

-Blair Groves


 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\

Newsgroups: comp.terminals
Path: cs.utk.edu!news.msfc.nasa.gov!newsfeed.internetmci.com!in2.uu.net
      !winternet.com!inforamp.net!usenet
From: Blair Groves <blair.groves@canrem.com>
Subject: Re: Adapting WYSE 60 for 120V ?
Date: Sat, 06 Apr 1996 18:00:53 -0500
Organization: informamp.net
Message-ID: <3166F7A5.5706@canrem.com>
References: <4ju4om$pf5@news.be.innet.net>
NNTP-Posting-Host: ts30-16.tor.istar.ca

Marc wrote:
> 
> Hi,
> 
> does anyone know if it is possible to modify 240V WYSE 60 terminals
> (modelnbr WY 900109-02) for 120V ?
> 
> Thanks !
> 
> Marc

Most terminals (the Wyse 60 included) that are 
manufactured for international use can be converted 
by opening the case, locating the jumper that 
selects the voltage, and moving it from 240 to 120. 
The jumper in question has a large plastic handle 
that usually colored grey, or sometimes white or 
translucent plastic. Make sure that you also put 
the appropriate line fuse in for the voltage you 
are running at (ie: if the fuse was 1 ampere, when 
configured for 240 volts, you will probably need to 
replace the line fuse with a 2 ampere since the 
current draw will usually double). Best bet is to 
follow the manufacturer's instructions and if you 
are not sure about working on this, take it to a 
qualified technician.

-Blair Groves

 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\

Path: cs.utk.edu!stc06.ctd.ornl.gov!fnnews.fnal.gov!uwm.edu!vixen.cso.uiuc.edu
      !newsfeed.internetmci.com!in2.uu.net!nwnews.wa.com!news1.halcyon.com
      !chinook!dagon
From: dagon@chinook.halcyon.com (Mark Rafn)
Newsgroups: comp.terminals
Subject: Re: How to enter set-up mode on Wyse 120?
Date: 8 May 1996 16:44:49 GMT
Organization: Northwest Nexus, Inc.--Professional Internet Services
Message-ID: <4mqj21$acp@news1.halcyon.com>
References: <318BDD7F.764ED54B@pncl.co.uk> <4mifb3$m24@lyra.csx.cam.ac.uk>

>Graham Burst  <boik@pncl.co.uk> wrote:
>>
>> ...I've just got 2 Wyse 120 terms with a
>>promise of a manual--but until then, can anyone enlighten me as to how
>>to enter set-up mode to change emulation, etc.

Ben Harris <bjh21@thor.cam.ac.uk> wrote:
>
>Shift-Setup works for me.

If it's in scancode keyboard mode, try CTRL-setup and ALT-setup as well.

>>Any hints as to termcap
>>entries for these under Unix also appreciated.

>Mine seem to work resonably well using the standard vt100 settings, but in
>VT100 mode their delete keys don't work and just freeze the screen.  DoeS
>aNyBody know of a cure for this?

We use a bunch of wy150s, which use almost exactly the same termcap as
the wy120.  Both of them have a wy50 mode which is very serviceable
EXCEPT for the stupid wyse arrow key usage (arrows send a single control
character rather than a unique sequence).

Depending on your flavor of Unix, you should see if there's a wy60ak or
wy120ak definition, which uses the Wyse native mode, but VT-style arrow
keys.  I use a slightly hacked wy120ak for everything, including
WordPerfect 5.1 for SCO Unix.  If you'd like a copy of this, email me.
--
Mark Rafn    dagon@halcyon.com    <http://www.halcyon.com/dagon/>   !G

 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\

Path: utkcs2!stc06.ctd.ornl.gov!fnnews.fnal.gov!uwm.edu!math.ohio-state.edu
      !howland.reston.ans.net!psinntp!psinntp!psinntp!psinntp!usenet
From: croweg@usa.pipeline.com (Gary Crowe)
Newsgroups: comp.terminals
Subject: WYSE/LINK/ADDS 4 sale
Date: 12 Jun 1996 15:03:57 GMT
NNTP-Posting-Host: 38.8.60.7

WYSE/LINK/ADDS 4 sale

We have a huge stock of these terminals, either new or refurbished,
for sale.  All our refurbs carry a 6-month warranty. 
Call 1-800-695-1951 and ask for Gary.

 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\

Newsgroups: comp.protocols.kermit.misc
Path: utkcs2!stc06.ctd.ornl.gov!fnnews.fnal.gov!uwm.edu!news.cse.psu.edu
      !rutgers!news.columbia.edu!watsun.cc.columbia.edu!fdc
From: fdc@watsun.cc.columbia.edu (Frank da Cruz)
Date: 26 Jun 1996 19:16:49 GMT
Organization: Columbia University
Message-ID: <4qs2b1$28v@apakabar.cc.columbia.edu>
Subject: Re: K95 wyse60 emulation soon?


In article <4qrsbc$mrm@samba.rahul.net>, Clarence Dold  <dold@rahul.net> wrote:
: Robert J. Strickler (bstrickl@thrunet.net) wrote:
: : We have a client that is currently using w3.1 and procomm with wyse60 
: : emulation, the accounting system has been modified to generally expect the 
: : wyse60 and it looks to be expensive to unmodify it to a more generic vt100 
: : expectation. They would like to move about 25 workstations to w95 and a 95 
: : terminal emulator. K95 looks like a great fit except that it needs this 
: : emulation. Any estimates on the availability?
: 
:  You don't mention what kind of connection you are using.
:  I used MSKermit under Win95 for dialup access for a while, until I got K95.
:  If you need TCP/IP connectivity that would be a different story, but the
:  serial portion of MSK 3.14 worked fine.


But MS-DOS Kermit does not include Wyse60 emulation, only Wyse50, which
is different.

Kermit 95 1.1.5 will emulate Wyse 30, 50, 60, and 370.


-- 
fdc
voice: +1 212 854-3703
  Web:  http://www.cc.columbia.edu:80/kermit/


 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\

Newsgroups: comp.databases.pick
Path: utkcs2!stc06.ctd.ornl.gov!fnnews.fnal.gov!cbgw1.lucent.com
      !cbgw3.lucent.com!news.PBI.net!super.zippo.com!zdc!www.nntp.primenet.com
      !nntp.primenet.com!news-peer.gsl.net!news.gsl.net!news-paris.gsl.net
     !news.gsl.net!news-feed1.globalnet.co.uk!news-feed3.globalnet.co.uk!usenet
Date: Fri, 01 Nov 1996 22:47:42 GMT
Message-ID: <327a7d36.1935525@news.globalnet.co.uk>
References: <geolin.2.0011DAC1@iafrica.com> <531p6m$a17@world.picksys.com>
Lines: 20
From: johnj@globalnet.co.uk (John Jenkins)
Subject: Re: Slave printing for wyse50 emulation

On Fri, 04 Oct 1996 01:52:57 GMT, tonyg@picksys.com (Tony Gravagno)
wrote:

>geolin@iafrica.com (George Woodman & Linette Goddard) wrote:
>
>  [printing through a Wyse 50]
>
>> I am experiencing a problem with the @(-17) function in Pick Basic. The
>> 'define-terminal' definition lists the code for 'slave on' as 'DC2'. I
>> changed this to 'CAN', but it does not seem to have made any difference.
>> Has anybody had a similar problem. I am running AP version 5 on a 486
>> processor. Thanks in advance.
>
> snup snip snip snip snip.....

Watch this one--many Wyse 50's do not correctly support flow control
to the slave port !

By choice I would use a Wyse 60, but maybe they've fixed the firmware
bug by now???

Regards

John Jenkins

 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\

Path: utkcs2!stc06.ctd.ornl.gov!news.er.usgs.gov!jobone!newsxfer3.itd.umich.edu
      !howland.erols.net!vixen.cso.uiuc.edu!news.stealth.net!uunet!in3.uu.net
      !208.206.176.15!dimensional.com!news.wizard.com !news.ici.net!dme
Newsgroups: comp.sys.hp.hardware,comp.terminals,telrad.system
Date: Sun, 02 Feb 97 15:10:46 GMT
Organization: PencilNet, Inc.
Message-ID: <5d2apm$12s_004@news.ici.net>
References: <32F44E9C.1643@tmx100.elex.co.il>
NNTP-Posting-Host: d-ma-newbedford-42.ici.net
From: david@pencilnet.com (David Ehrens)
Subject: Re: Q: Power usage of monitors?


We supply a fair number of terminals for various Unix multiuser
applications, and we have found that configuring terminals for screen
saver or "powersaver" mode is generally preferable to turning them off
and on--on a daily basis.  They simply seem to last longer when
avoiding the shock of powering on.

Wyse terminals, in particular, seem to benefit greatly from leaving
them on; they seem to burn out the most of the 5 or 6 brands we sell.


 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\


Newsgroups: comp.terminals
Path: utkcs2!stc06.ctd.ornl.gov!news.er.usgs.gov!jobone!newsxfer3.itd.umich.edu
      !news-peer.sprintlink.net!news.sprintlink.net!Sprint!newsfeed.nacamar.de
      !news.seicom.net!news.ruhr-uni-bochum.de!news.rhrz.uni-bonn.de
      !news.rwth-aachen.de!fangorn.moria!michael
Organization: An old and gray machine, somewhere in Moria.
Message-ID: <970908320@fangorn.moria>
References:
 <827E155DF374D24A.20D66BD510F63317.6FA33D4D80CEECB3@library-proxy.airnews.net>
NNTP-Posting-Host: cantor.informatik.rwth-aachen.de
Date: Mon,  8 Sep 97 21:41:05 MET
From: Michael Haardt <michael@cantor.informatik.rwth-aachen.de>
Subject: Re: Huge number of Wyse 60 Failures after about 1.5 years

broswell@syssrc.com (Bob Roswell) writes:
> For the first year or so we had a large, but manageable, number of
> failures.  Now , suddenly,  they are showing up dead at the rate of
> one or two per day!
>
> I don't see any power problems at the customer site, and no other
> equipment is failing.
>
> Has anyone seen this problem?


I repaired a few Wyse 60 terminals, and, from what I saw,
they are broken by design.

Personally, I always found screws that hold a cover are fixed in a way
that soldering spots have to break.  Other people complained about
capacitors which have to be replaced with better ones.  I don't think
the customer's site is the problem.  The terminals are.

Michael
-- 
d? H- s(+)/(-) g! au a- w+ v(---) C++(+++) UL++++S++++?++++ L++ 3 E-
                N+++ tv b+ e+ h f+ m@ r++ n@ y+

 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\

Path: utkcs2!stc06.ctd.ornl.gov!news.he.net!feta.direct.ca!newsfeed.direct.ca
      !newsfeed1-hme1!newsfeed.internetmci.com!204.238.120.130!jump.net
      !grunt.dejanews.com!not-for-mail
Newsgroups: comp.terminals
Message-ID: <873722649.24814@dejanews.com>
References:
 <827E155DF374D24A.20D66BD510F63317.6FA33D4D80CEECB3@library-proxy.airnews.net>
X-Originating-IP-Addr: 207.16.245.43 (ts1-p4.min.prysm.net)
Date: Mon, 08 Sep 1997 07:51:11 -0600
From: starlle@prysm.net
Subject: Re: Huge number of Wyse 60 Failures after about 1.5 years

I have 6 Wyse 60 terminals that are dead also. Most of these were
purchased new or refurbished about 1-2 years ago. I assumed that we
were having power problems, but, after adding data line protectors,
the problem continues.
-- 
Melissa Davis
Star Manufacturing

 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\

Newsgroups: comp.databases.pick
Date: Fri, 13 Sep 1996 22:19:16 GMT
From: Louis Popovsky <ytsejam@ias.ga.unc.edu>
Subject: Re: Basic WY60 Terminal Emulators

>keygroup4@aol.com (KeyGroup4) wrote:
>
> Procomm Plus v3.0 has a Wyse60 emmulator with keyboard mapping
> capabilities. I am not sure how much color control it offers. It should
> cost about $130 US for the Windows version.
> Jeff Kaufman, Key Data Systems

$130 vs. $25, Thats why I keep saying try Anzio. I de-installed
Procomm, it was such a behemoth. Monday I'm gonna write some
Info-Basic code on our Prime so it will download some data thru an
Anzio Telnet session, Fire up MS-Access, import it, and give the user
a Report & Mail-Merge. Termite could do this, but I doubt if Procomm
could. 

    http://www.teleport.com/~rsi/anzioscl.html

 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\

Newsgroups: comp.terminals
Message-ID: <6erc6f$pbo$1@apakabar.cc.columbia.edu>
References: <Pine.LNX.3.96.980319121439.24355N-100000@eek.ucg.ie>
Date: 19 Mar 1998 15:04:47 GMT
From: Jeffrey Altman <jaltman@watsun.cc.columbia.edu>
Subject: Re: Windows Emulation for Wyse-320?

In article <Pine.LNX.3.96.980319121439.24355N-100000@eek.ucg.ie>,
Peter Corcoran  <pcor@eek.ucg.ie> wrote:
:
: Does anyone know of freeware or GNU software for Windows-95
: which can emulate a Wyse-320 terminal?

I'm not familiar with the Wyse-320 terminal.  Do you mean Wyse-370?

I doubt that you will find a free implementation of a terminal of this
complexity.

Kermit-95 provides an emulation of the Wyse-370 minus the 64K color
palettes.  For info look at http://www.kermit-project.org/k95.html


 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\

Newsgroups: comp.terminals
Message-ID: <35c7792c.1286901927@news.demon.co.uk>
References: <01bdb66d$b8c74700$63636363@laptop-brc>
Date: Fri, 24 Jul 1998 12:19:32 GMT
From: Harry Broomhall <haeb@demon.net>
Subject: Re: Wyse-50 emulation recomendations wanted

On 23 Jul 1998 19:11:39 GMT, "Bill Creager" <creager@norfolk.infi.net>
wrote:

>I am about to write a program that must emulate a Wyse-50 terminal, and I
>am looking for recommendations regarding the information I will need. At
>this point, I do not have any consolidated information about the control
>sequences.

   Why not buy a Wyse50 emulator?   Surely it would be easier?  <grin>

>
>I have just ordered the book, "Termcap & Terminfo".  Will this book provide
>sufficient detail to develop an emulator?

   Not at all.

> If not, what additional documentation is recommended?

   You need the Wyse programming handbook.  It also helps to have a
*real* Wy-50 to hand to see where you went wrong!

> My previous experience is with vt100 for
>which there seems to be much more technical information on the internet,
>but it is almost impossible to develop a satisfactory emulator without Dec
>documentation.
>
>Does anyone have recommendations on where to locate a comprehensive set of
>control sequences? Is there a test program similar to vttest that can be
>used to validate the functionality of a Wyse-50 emulator? Any
>recommendations will be greatly appreciated.


    The problem is that Wyse50 and similar terminals are *very*
different in style from the VT100 series.  I have always mentally
divided terminals into two groups:  'hardware' and 'software'.

  Wyse-50 and Prestel belong to the 'hardware' group, and VT100 and
friends to the 'software' group.

   In the hardware group  screen effects are done almost totally with
the hardware.  As an example, if you set the highlight bit on
*highlight is now on until the end of the screen, or the place where
it is set off, whichever comes first*.  This is a *totally* different
concept from the VT100, where, after putting highlight on, it is on ONLY
for characters subsequently *written* until switched off.

  Unix does not really understand such an idea, and termcap and
terminfo merely hack at it a bit, which is why the book is not
particularly useful on its own.

  You also have to deal with the tiresome 'cookie-glitch'; a product
of limited hardware capabilities of the day.  [early 1980s]

  Regards,
        Harry  (who has written a Wyse50 emulator).

 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\

Newsgroups: comp.terminals
Message-ID: <6pa576$je4$1@apakabar.cc.columbia.edu>
References: <01bdb66d$b8c74700$63636363@laptop-brc> 
Date: 24 Jul 1998 14:20:22 GMT
From: Jeffrey Altman <jaltman@watsun.cc.columbia.edu>
Subject: Re: Wyse-50 emulation recomendations wanted

In article <35c7792c.1286901927@news.demon.co.uk>,
Harry Broomhall <haeb@demon.net> wrote:
:     The problem is that Wyse50 and similar terminals are *very*
: different in style from the VT100 series.  I have always mentaly
: divided terminals into two groups:  'hardware' and 'software'.

This is the first time I have ever heard it described quite like that.

I look at it from two different perspectives.  There are text
terminals which are based on the ANSI X3.64-1979 standard (replaced by
ISO-6429) upon which most modern day terminals are based (VT100 and
higher; SCOANSI; AT386; IBM LFT,HFT,AIXTERM; SNI; WY350 family; and
most Unix consoles) and those that are not based on this standard
(VT52; Wyse 30,50,60, and their decendents; HP; TVI; DG; IBM 31xx;
and many others).

The other dimension is defined by how are attributes implemented.
They can either be VISIBLE or HIDDEN and applicable to the following
CHARACTER, LINE or PAGE.  A VISIBLE atteibute tkaes up a character
position whereas a INVISIBLE one does not.  Some terminals allow any
of the six possible combinations to be used.  Others limit you to just
one.

ANSI X3.64 terminals always use HIDDEN/CHARACTER attributes and the 
Wyse 50 uses VISIBLE/PAGE attributes.  The Wyse 60 for example defaults
to INVISIBLE/PAGE attributes but can be configured either locally or 
remotely to use CHARACTER or LINE attributes instead.

---

When developing terminal emulators always have two things:

 *  copies of the manufacturer's manuals

 *  a real terminal 

The manual will give you a feeling for what the escape sequences are
and what they are supposed to do.

For an ANSI X3.64-1979 or ISO-6429-based terminal, you can implement a
very simple parser that will work regardless of the things you do not
know.  Command sequences that you do not recognize will be absorbed
and ignored, if you do it right.

Non-ANSI-X3.64 terminals are not that forgiving.  They are unparsable
and, unless you know all of the sequences that the terminal accepts,
the visual appearance of the data will be corrupted by unprocessed
escape sequences.

The real terminal is necessary so you can test the behavior of the 
terminal against your implementation and so that you determine all
of the undocumented behaviors that the terminal provides.

I agree with Harry that implementing a good emulator, even for simple 
terminals such as VT100 and WY50, is a non-trivial piece of work. 
Unless you are doing it as a hobby or because there is no other piece 
of software available that can perform the job that you need, it is
significantly cheaper to just buy an emulator from someone else.

Extremely good emulators can be had for a few dollars a copy in
quantity and if the quantity is small the overall cost must be less
than the cost of your time.  See

    http://www.columbia.edu/kermit/k95pricing.html

for the pricing model;
for the Kermit 95 terminal emulation and file transfer product see

    http://www.columbia.edu/kermit/k95.html

    Jeffrey Altman * Sr.Software Designer * Kermit-95 for Win32 and OS/2
                 The Kermit Project * Columbia University
              612 West 115th St #716 * New York, NY * 10025
  http://www.kermit-project.org/k95.html * kermit-support@kermit-project.org

 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\

Newsgroups: comp.terminals
Message-ID: <35c8a128.1297137975@news.demon.co.uk>
Date: Fri, 24 Jul 1998 15:08:10 GMT
From: Harry Broomhall <haeb@demon.net>
Subject: Re: Wyse-50 emulation recomendations wanted

On 24 Jul 1998 14:20:22 GMT, jaltman@watsun.cc.columbia.edu (Jeffrey
Altman) wrote:

>In article <35c7792c.1286901927@news.demon.co.uk>,
>Harry Broomhall <haeb@demon.net> wrote:
>:  
>: ...I have always mentaly
>: divided terminals into two groups:  'hardware' and 'software'.
>
>This is the first time I have ever heard it described quite like that.

  Well--it *is* my own invention!  (Cue the White Knight)  So I don't
expect to find it in the literature.  <grin>

>
>I look at it from two different perspectives.  There are text
>terminals which are based on the ANSI X3.64-1979 standard (replaced by
>ISO-6429) upon which most modern day terminals are based (VT100 and
>higher; SCOANSI; AT386; IBM LFT,HFT,AIXTERM; SNI; WY350 family; and
>most Unix consoles) and those that are not based on this standard
>(VT52; Wyse 30,50,60, and their decendents; HP; TVI; DG; IBM 31xx;
>and many others).

   This is a slightly different classification. For my purpose as a
developer my classification is more useful in determining how hard an
emulation is to do.  This is because to do a 'hardware' terminal is
*much* harder than a 'software' one.  It also tends to be slower, as
you have to 'extend' the attribute forwards.

  Note that while VT52 may not be a 'standard based' terminal it is,
in my classification, a 'software' terminal, and thus not so hard to
do.

[SNIP]
>
>When developing terminal emulators always have two things:
>
>. copies of the manufacturer's manuals
>. a real terminal 


    Good solid advice here!

     Regards,
            Harry.

 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\

Newsgroups: comp.unix.solaris, comp.terminals
Message-ID: <kgemu4vyzs.fsf@voodoo.pandhm.co.uk>
References: <eh3eakrg4j.fsf@hammond.amnh.org>
Date: 26 Aug 1998 11:06:15 +0100
From: Dom Mitchell <dom@phmit.demon.co.uk>
Subject: Re: WYSE Term "break" key vulnerability

Fil Krohnengold <fil@amnh.org> writes:
>
> And while I'm here...
>
> I recently bought a Wyse terminal for a console for several servers--
> in the past I've used terminals which required a combination of keys
> in order to send a break to the OS--not this one.  Just one key.
> Sitting out there in the open waiting for someone to put mail on it.
> Any ideas how to deal with that and make it more safe?


If you go into the Wyse Setup program (probably on F3), there should
be an option to turn the break key off.  You'll have to remember to
turn it on again though when you need it.

To be quite honest, if you've got servers in an environment where
somebody is liable to put mail on their consoles, then you're doing
something wrong--servers should be locked away so only you and your
assistants can get at them!

-- 
Dom Mitchell          -- Palmer & Harvey McLane
dom@phmit.demon.co.uk -- Unix Systems Administrator

 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\

Newsgroups: comp.unix.solaris, comp.terminals
Message-ID: <6s1mgo$ldt$1@tepe.tezcat.com>
References: <eh3eakrg4j.fsf@hammond.amnh.org>
Date: 26 Aug 1998 19:09:12 GMT
From: "Roger J. Allen" <rja@sis.rpslmc.edu>
Subject: Re: WYSE Term "break" key vulnerability

In comp.terminals Fil Krohnengold <fil@amnh.org> wrote:

> And while I'm here...

> I recently bought a Wyse terminal for a console for several servers -
> in the past I've used terminals which required a combination of keys
> in order to send a break to the OS - not this one.  Just one key.
> Sitting out there in the open waiting for someone to put mail on it.
> Any ideas how to deal with that and make it more safe?

Wyse terminals have about a half dozen different keyboard styles,
depending on the model of terminal.  Unfortunately, most vendors do not
let you know which one they will ship you unless you specify the exact
model that you want.  If your supplier will swap, then choose a keyboard
layout that best fits your application.

Three different layouts are shown on:

    http://www.wyse.com/terminal/

Also, your Wyse manuals should list the keyboard layouts that are
available for whatever model of terminal that you have.

--
Roger J. Allen                Rush-Presbyterian-St. Luke's Medical Center
System Administrator                                   Chicago,  IL   USA
Surgical Information Systems                       Voice:  (312)-942-4825
Internet: rja@sis.rpslmc.edu                         FAX:  (312)-733-6921


 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\



Newsgroups: comp.terminals
Message-ID: <6s7u4o$hst$1@apakabar.cc.columbia.edu>
References: <6s7sj9$2em$1@cletus.bright.net>
Date: 29 Aug 1998 03:56:08 GMT
Organization: Columbia University
From: jaltman@watsun.cc.columbia.edu (Jeffrey Altman)
Subject: Re: WYSE/PC TERM Emulator?


In article <6s7sj9$2em$1@cletus.bright.net>,
TowerComm, Inc. <tower@bright.net> wrote:
: Has anyone out there seen or used an emulator for Wintel (DOS/Win3x/Win9x)
: that emulates a WYSE 150 which is, in turn, emulating a PC TERM personality?
: 
: Any input would be appreciated.  I've got a wacky application developed by
: a programmer that used some characteristics of the WYSE 150 terminal under
: PC TERM that is driving me nuts - most packages I've looked at emulate WYSE
: or PC TERM, but not "both at once", if you know what I am saying.
 
That is really interesting considering the fact that PCTERM is not an
emulation but a keyboard mode that may be applied to any terminal 
emulation.

Kermit 95 <http://www.kermit-project.org/k95.html> supports a Wyse 60
emulation that has all of the Wyse 150 extensions.  And it supports
PCTERM keyboard mode.
 
    Jeffrey Altman * Sr.Software Designer * Kermit-95 for Win32 and OS/2
                 The Kermit Project * Columbia University
              612 West 115th St #716 * New York, NY * 10025
  http://www.kermit-project.org/k95.html * kermit-support@kermit-project.org
 
 
 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\


Newsgroups: comp.terminals
Message-ID: <35EB022D.9F0AD1AA@GSC.GTE.Com>
References: <6s7sj9$2em$1@cletus.bright.net>
Organization: GTE Government Systems
Date: Mon, 31 Aug 1998 20:06:05 GMT
To: "TowerComm, Inc." <tower@bright.net>
From: "Scott G. Hall" <Scott.Hall@GSC.GTE.Com>
Subject: Re: WYSE/PC TERM Emulator?

TowerComm, Inc. wrote:
> Has anyone out there seen or used an emulator for Wintel (DOS/Win3x/Win9x)
> that emulates a WYSE 150 which is, in turn, emulating a PC TERM personality?

{ Actually Link and Altos terminals are the only other ones
  I saw that emulated Wyse-150 "PC Term" mode correctly --
  what a hoot to see this still around...                   }

As I posted in a previous post, try Procomm Plus for Windows.  Then set the
emulation to "PC Scan Codes" under the ANSI modes.  What the Wy-150 in PC-
Term mode is doing is sending back 8-bit codes per key that emulate the
scancodes of the original IBM PC/XT keyboard and upon return, is acting like
you have ANSI.COM running.

{ Don't laugh! This was perfect for those folks with Alloy boards that where
  an XT or AT on a card, and used a serial terminal in PC-Term mode as the
  screen and keyboard.  A Wyse-99GT would even provide HGA graphics emulation
  with these boards (the Hercules graphics mode) }


--
Scott G. Hall
GTE Government Systems
North Carolina Systems Center
email: Scott.Hall@GSC.GTE.Com

 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\

Newsgroups: comp.terminals
Message-ID: <361be1ba.16306079@netbsd.haeb.demon.org>
References: <01bdefa0$673256c0$63636363@laptop-brc>
Date: Sun, 04 Oct 1998 21:00:47 GMT
From: Harry Broomhall <haeb@pc60.demon.co.uk>
Subject: Re: Sending break with Wyse 50 emulator

On 4 Oct 1998 14:04:02 GMT, "Bill Creager" <creager@norfolk.infi.net> wrote:

>How is the equivalent of pressing the break key sent from a Wyse 50
>emulator?
>

This depends on the emulator--it should be in the docs for it.
I have seen several different combinations in various packages!

  Regards,
         Harry.


 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\

 ----------------------------------------------------------------------------

Message-ID: <70g3i3$lhd$1@apakabar.cc.columbia.edu>
References: <70g2ln$7aj$1@xenon.inbe.net>
Date: 19 Oct 1998 19:22:43 GMT
From: Jeffrey Altman <jaltman@watsun.cc.columbia.edu>
Newsgroups: comp.terminals
Subject: Re: Wyse-120 emulator

In article <70g2ln$7aj$1@xenon.inbe.net>,
Bart Vanden Driessche <bart.vanden.driessche@village.uunet.be> wrote:
: Hi,
:
: I am looking for an emulator that turns on NT4 for a serial Wyse-120
: terminal. This terminal works with scan codes instead of ascii key codes so
: most common emulators don't work.
:
: Does anyone knows an emulator which can handle a wyse-120 / scan code
: emulation?
:
: Thanks.
:
: Bart Vanden Driessche


Kermit 95 is a Wyse 60 emulator that supports most of the Wyse 120/160
extensions.  And it supports the PCTERM keyboard mode that you are looking
for.

See http://www.kermit-project.org/k95.html for details.

    Jeffrey Altman * Sr.Software Designer * Kermit-95 for Win32 and OS/2
                 The Kermit Project * Columbia University
              612 West 115th St #716 * New York, NY * 10025
  http://www.kermit-project.org/k95.html * kermit-support@kermit-project.org

-------------------------------------------------------------------------------

 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\

1999-01-19:      In the UK, Wyse may be contacted at

                 Wyse Technology
                 1 The Pavilions
                 Ruscombe Park
                 Twyford, Berks
                 RG10 9NN
                 United Kingdom

                 Voice: +44 118 934 2200
                   Fax: +44 118 934 0749


On the Web, there is some support information at

    http://www.wyse.com/service/faq/


 /^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\/^\


 //////////////////////////////////////////////////////////////////////////////

Message-ID: <36E46048.5F767A09@removemepond.com>
From: Michael Weiskopf <catfish@removemepond.com>
Date: Mon, 08 Mar 1999 23:38:45 GMT
From: Michael Weiskopf <catfish@removemepond.com>
Newsgroups: comp.terminals
Subject: Re: WY60 Garbled font

I am note sure but from it sounds like a U-19 chip problem.
the normal symptoms are: vertical lines on screen, chracters
missing pixels, "snow" all over screen.  wyse claimed that
only a few wyse60 (in the early '90's) were affected so i
thought we had all of them :).
the problem is that wyse "cold soldered" the chips
onto the boards. these heat up over time deteriorate.  the u-19
chip is for video display.  to fix it, one just needs to apply
solder to the -19 chip.  while the case is off, one might want
to brighten the display.  they come so dim from the factory (re-
gardless of the dimmer slide setting).

michael

Robert Norris wrote:
>
> Hi
>
> Recently received a WY60, hooked it up to my linux box, and it worked
> just fine. Turned it on the other day to find that the font had been
> garbled. By garbled I mean that many of the characters were not correct,
> in places you could see bits of two different characters within the same
> character 'cell'.
>
> G-reset doesn't seem to work, and I can't get the lid off to poke around
> inside. Thoughts?
>
> Regards
>
> Rob.

 //////////////////////////////////////////////////////////////////////////////


Message-ID: <36E467DE.419BC793@removemepond.com>
From: Michael Weiskopf <catfish@removemepond.com>
X-Complaints-To: Abuse Role <abuse@pond.com>, We Care <abuse@newsread.com>
Date: Tue, 09 Mar 1999 00:11:07 GMT
From: Michael Weiskopf <catfish@removemepond.com>
Newsgroups: comp.terminals
Subject: Re: Wyse-60 keyboard mappings

the wyse-60 basically has two keyboards: ascii and pc-101. the
ascii has 16 function keys across the top and the pc-101 has
12 function keys.  the pc-101 is just that.  a standard pc
keyboard with an rj-11 jack (instead of the regular din connector).
there are other styles available such as dec compatible though
rare.  also custom configurations were available as well.  the
problem you described is vague but is it possible that it is
related to the emulation( either on the terminal or in the os )?

michael

Eupsychia wrote:
>
> We are having problems with out Wyse-60 keyboard....i am unsure of what kind
> of keyboard it is exactly. I know that it does have the Wyse logo on
> it....our user is having a problem doing certain functions because the
> keyboard mappings are not correct. If there is anyone out there who could
> advise me as to what to do.
>
> Thanks,
>
> Toby Carver
> PC/Network Technician
> House of Lloyd
> Grandview, MO

 //////////////////////////////////////////////////////////////////////////////

Newsgroups: comp.terminals
Organization: Columbia University
Message-ID: <6pob5t$jr3$1@apakabar.cc.columbia.edu>
References: <35bf9c71.0@news1.ibm.net>
Date: 29 Jul 1998 23:27:57 GMT
From: jaltman@watsun.cc.columbia.edu (Jeffrey Altman)
Subject: Re: Ansi Commands For Wyse 60

In article <35bf9c71.0@news1.ibm.net>,
Greg Harker <gharker@generalpaint.com> wrote:
: Does anybody know how to either set the clock on the top of a Wyse 60 or
: erase the entire line the clock is on. I am using ANSI and VT100.
: 

There is no ANSI sequence for a VT100 to set a clock.  The Wyse 370
sequence is 

  <CSI> <hr> ; <min> , p

  <hr> and <min> are represented in ASCII digits in 24 hour format.

For Wyse 60 mode try:

  <ESC> c 8 <hh> <mm>

  <hh> and <mm> are represented in binary

    Jeffrey Altman * Sr.Software Designer * Kermit-95 for Win32 and OS/2
                 The Kermit Project * Columbia University
              612 West 115th St #716 * New York, NY * 10025
  http://www.kermit-project.org/k95.html * kermit-support@kermit-project.org

 //////////////////////////////////////////////////////////////////////////////

Newsgroups: comp.terminals
Organization: C.I.C. Ltd
Message-ID: <35c1b80a.3867269@netbsd.haeb.demon.org>
References: <35bf9c71.0@news1.ibm.net>
Date: Thu, 30 Jul 1998 00:03:38 GMT
From: haeb@pc60.demon.co.uk (Harry Broomhall)
Subject: Re: Ansi Commands For Wyse 60

On Wed, 29 Jul 1998 15:05:31 -0700, "Greg Harker"
<gharker@generalpaint.com> wrote:

>Does anybody know how to either set the clock on the top of a Wyse 60 or
>erase the entire line the clock is on. I am using ANSI and VT100.
>

   Interesting.  My Wyse-60 books make no mention of a clock, nor have
I ever seen one!  Are you sure that 1) it is a Wyse-60 or 2) the clock
is not a product of the app you are using?

   Regards,
          Harry.

 //////////////////////////////////////////////////////////////////////////////

Newsgroups: comp.terminals
References: <35bf9c71.0@news1.ibm.net> <35c1b80a.3867269@netbsd.haeb.demon.org>
Organization: BOSS Internet Group
Message-ID: <35c16c6b.0@news-out2.newsnerds.com>
Date: 31 Jul 1998 02:04:11 -0600
From: "Travis J. McKay" <tmckay@revolution.3-cities.com>
Subject: Re: Ansi Commands For Wyse 60

Greg Harker wrote:
>
>Does anybody know how to either set the clock on the top of a Wyse 60 or
>erase the entire line the clock is on. I am using ANSI and VT100.

Ya, you can set the clock through the <CTRL-CAPS> WyseWorks tools.  
You will discover that the clock resets at loss of power (to 8:00). Simple
solution:  turn it on at 8AM everyday. :)

If you want to kill the clock on the status line... enter setup
(on mine it is <SHFT-SETUP>), hit F1, and toggle the status line value.
'Extended' keeps the mode indicator and kills the clock and cursor pos.

I have no manual for this one and have learned what I know through
experimentation and FAQs.  If anyone has a manual that they would
be willing to photocopy, I would be most appreciative.

Best regards,

-- 
Travis J. McKay
tmckay@3-cities.com
tmckay@u.washington.edu

 //////////////////////////////////////////////////////////////////////////////

Newsgroups: comp.terminals
Message-ID: <35c4fbce.6089205@netbsd.haeb.demon.org>
References: <35bf9c71.0@news1.ibm.net> <35c1b80a.3867269@netbsd.haeb.demon.org> <35c16c6b.0@news-out2.newsnerds.com> <35deca65.1897519388@news.demon.co.uk> <35c28a09.0@news-out2.newsnerds.com>
Date: Sat, 01 Aug 1998 11:30:18 GMT
From: haeb@pc60.demon.co.uk (Harry Broomhall)
Subject: Re: Ansi Commands For Wyse 60

On 31 Jul 1998 22:22:49 -0600, "Travis J. McKay"
<tmckay@revolution.3-cities.com> wrote:

>While we are on this thread...
>
>Does anyone know how to set the delete key to actually act like a DEL
>key?  It switches to the block mode (whatever that is for, anyway it 
>impedes communication with the remote) and back to full duplex when
>pressed.
>

    My handbook says it transmits the 'DEL' character, and nothing
about it changing modes.  I don't remember having problems with using
it on a Wyse 60.  Are you sure that your host is not mis-interpreting
it?

    Regards,
          Harry.


 //////////////////////////////////////////////////////////////////////////////

From: sir@s2soft.com (stu rutkin)
Subject: Re: Link (Motorola) MC-5 manuals
Date: 19 Aug 1999 00:00:00 GMT
Message-ID: <sir-1908990658450001@d11-ts06.amug.org>
References: <Pine.9906191139470.22597@maynard.stratus.com>
Organization: s2 software, inc.
Newsgroups: comp.terminals
X-Complaints-To: newsabuse@supernews.com

In article <Pine.9906191139470.22597@maynard.stratus.com>, "Richard S.
Shuford" <shuford@REMOVE-EXTRA.cac.stratus.com> wrote:

> On 18 Jun 1999 18:10:35 GMT, "Max" <indigo<at>crl.com> wrote:
> > 
> > I recently acquired a project of trying to integrate a bunch of
> > MC-5 terminals into our data processing department....
> > What I need to find is a manual for the bloody things.
> > Specially want I need to find out is how to change the default
> > terminal emulation.
> 
> Sir Max:
> 
> Your situation is really not so bad.  Link Technologies was
> bought out a couple years ago by Wyse, but the MC-5 is still
> advertised by Wyse as a current product.  Here is a Web page:
> 
>     http://www.wyse.com/terminal/specs/mc5spec.htm
> 
> If the Motorola variants are like a normal Link MC-5, then typing
> Shift-Setup gets you to the setup menus (or Shift-Select on the
> optional EPC keyboard). Then most settings are fairly obvious.
> 
> I think you have to type an "s" to make the settings permanent.
> You can type "e", I think, to exit the setup menus.  (It may say
> this on the bottom of the first screen, but I don't remember
> precisely.)
> 
> Stratus used to re-sell MC-5s as the V103 model terminal, which
> are still in relatively wide use in Televideo-955-emulation mode.
> 

Hi, Max,
 
There was one other choice for entering set-up, and that is with the ANSI
(20 function key) keyboard: shift -F3.  

What I would also suggest is entering set-up, depressing the "D"
(default), saving those settings ("S"), then exiting from set-up ("E"),
which will fully implement the factory settings.  Then, re-enter set-up,
make the changes that you need, and, as Mr. Shuford says, "S" to save, and
"E" to exit.  Long ago, Wyse and Link also suggested holding down the 'g'
key before powering the terminal on, until you see the 'g' on the display,
then default the terminal, then configure it as you need to.  Holding down
the 'g' re-loaded some other setting, but my memory fails me and I can't
tell you why they suggested this.

stu

-- 
stu rutkin 
s2 software, inc.
4950 East Thomas Road
Phoenix, AZ 85018
602 840-5200 fax 602 840-5700 
<sir@s2soft.com>

 //////////////////////////////////////////////////////////////////////////////

Date: Thu, 16 Sep 1999 11:51:35 +0200
Organization: Nacamar Group Plc.
Newsgroups: comp.terminals
Message-ID: <7rqeig$1rk8$1@black.news.nacamar.net>
From: Andreas Lockau <andreas.lockau@rag-informatik.de>
Subject: Wyse Term

Hi,
who knows the wyse terminal 60? And can help us to change
the codepage to use a special language page.

We are searching for the german charakters 'ae', 'ue' and 'oe'.

Thank you in advance.

Andreas

 //////////////////////////////////////////////////////////////////////////////

Date: 16 Sep 1999 13:46:32 GMT
Organization: Columbia University
Newsgroups: comp.terminals
Message-ID: <7rqsbo$24f$1@newsmaster.cc.columbia.edu>
From: Jeffrey Altman <jaltman@watsun.cc.columbia.edu>
Subject: Re: Wyse Term

I'm not sure this helps but there is one escape sequence for
loading internally defined character sets:

  ESC @ <bank> <set>

  bank is 0 to 3
  Set is:
    @ - Native mode
    A - Multinational (CP437)
    B - Standard ASCII
    C - Graphics 1
    D - PC Equivalent
    E - Graphics 2
    F - Graphics 3
    G - Standard ANSI
    ` - 44-line native
    a - 44-line multinational
    b - 44-line PC
    c - 44-line Standard ASCII
    d - 44-line Standard ANSI

  where each set is 128 characters.

   @ is ASCII with line drawing in C0
   A is the upper half of CP437
   B is ASCII with control character descriptors in C0
   C,E,F are line drawing subsets
   D is the lower half of CP437 (PC Graphics in C0)
   G is ASCII with a different set of line drawing characters
        in the C0 range.

  ESC B <bank>   assigns the primary character set
  ESC C <bank>   assigns the secondary character set

The problem is that none of the above character sets contain 'oe' or 'ue'.

If you were using Kermit 95 as a Wyse 60 emulator you could configure
the client to use ISO-Latin1 to produce the characters you need but
unfortunately, ISO Latin1 is not supported by the Wyse terminals.

-- 
    Jeffrey Altman * Sr.Software Designer * Kermit-95 for Win32 and OS/2
                 The Kermit Project * Columbia University
              612 West 115th St #716 * New York, NY * 10025
  http://www.kermit-project.org/k95.html * kermit-support@kermit-project.org


 /////////////////////////////////////////////////////////////////////////////

Date: Thu, 16 Sep 1999 17:37:18 GMT
Newsgroups: comp.terminals
Message-ID: <7rr9sd$loi$1@nnrp1.deja.com>
From: Mark Greene <greenemj@hlthsrc.com>
Subject: Re: Wyse Term

In article <7rqeig$1rk8$1@black.news.nacamar.net>,
  "Andreas Lockau" <andreas.lockau@rag-informatik.de> wrote:
> Hi,
> who knows the wyse terminal 60? And can help us to change
> the codepage to use a special language page.
>
> We are searching for the german charakters 'ae', 'ue' and 'oe'.

IIRC, press shift-setup and the setup option appear at the bottom; you
can scroll through the listings witht the up/down arrow keys and change
values with the spacebar. Look for one labeled "Keypad", and there
should be a "German" option.  Also, I believe you have to have the
appropriate ROM chip installed.

HTH
--
Mark

 //////////////////////////////////////////////////////////////////////////////


References: <vLXn4.365$e05.13520091@news1.van.metronet.ca>
Date: Tue, 08 Feb 2000 18:14:43 GMT
Organization: RoadRunner - TampaBay
Newsgroups: comp.terminals
Message-ID: <m7n0as0m2jcdrvpabrcto5iali2rf08fuv@4ax.com>
From: Art Rice <arice@ue.itug.org>
Subject: Re: look up wyse60 esc sequence?

On Tue, 08 Feb 2000 16:46:19 GMT, "DET"
<NotValidBecauseOfSpammers@ipipeline.net> wrote:

>http://www.wyse.com/service/support/kbase/wyseterm.asp

Good question.  Here's the numbers

Screen and Cursor Display
Screen display off ESC ` 8
Screen display on ESC ` 9
Screen saver off ESC e P
Screen saver on ESC e Q
Reverse screen ESC ^ 1
Restore normal screen ESC ^ 0
Set scrolling speed and type ESC ` scroll
       Scrolling     Speed
scroll Type          (L/Sec)
----------------------------
  @    Jump scroll   N/A
  <    Smooth Scroll  1
  =    Smooth Scroll  2
  >    Smooth Scroll  4
  ?    Smooth Scroll  8
----------------------------

Set cursor display features ESC ` cursor
        Cursor
cursor  Display
----------------------
  0     Cursor display off
  1     Cursor display on
  2     Steady block cursor
  3     Blinking line cursor
  4     Steady line cursor
  5     Blinking block cursor

Cursor display off ESC ` 0
Cursor display on ESC ` 1


--
Art Rice   *
Special Data Processing Corporation

 //////////////////////////////////////////////////////////////////////////////


References: <vLXn4.365$e05.13520091@news1.van.metronet.ca>
    <m7n0as0m2jcdrvpabrcto5iali2rf08fuv@4ax.com>
Date: Thu, 10 Feb 2000 15:44:27 -0800
Newsgroups: comp.terminals
Message-ID: <2a7d0$f30a.1c5@news.kea.bc.ca>
From: Nader Behzad <naderbe@attachmate.com>
Subject: Re: look up wyse60 esc sequence?

ESC ` 6 assign wpca (set reverse and clear other wpca)
ESC ` 7 assign wpca  (set dim and clear other wpca)


 //////////////////////////////////////////////////////////////////////////////

Newsgroups: comp.terminals
References: <9rg909$ur6$1@dos.canit.se>
Message-ID: <4m8mr9.ijr.ln@Lonmay.wew.co.uk>
Date: Tue, 30 Oct 2001 13:13:30 -0000
From: Colin McKinnon <colin@EditMeOutUnlessYoureABot.wew.co.uk>
Subject: Re: WY60 eight-bit characters

Iggy Drougge <optimus@canit.se> wrote in message
<9rg909$ur6$1@dos.canit.se>...
>
> I've got a WYSE 60 which is behaving like an old 7-bit national charset
> terminal. That is quite annoying, since any backslashes, curls or brackets
> are rendered as Å, Ä, Ö. It makes for quite a funny BSD loading sequence.
> According to SCO, the WY60 is an eight-bit terminal, so what is one to do?
> I'm using VT100 emulation ATM, since the wy60 termcap in NetBSD really
> can't render much.

Sorry if this is obviious but you don't say what you've tried....

What does stty -a say?

Have a look at man stty (the bit you are looking for is about CS8) - of
course if you want the line initialized before you login you'll need to put
corresponding settings in your gettydefs file.....and that won't help with
console boot messages.

HTH

Colin

 //////////////////////////////////////////////////////////////////////////////

Newsgroups: comp.terminals
Message-ID: <94024c806a52355c@mayday.cix.co.uk>
Organization: Mayday Technology Ltd
Date: Wed, 31 Oct 2001 07:32:16 +0000
From: Robert de Bath <rd104096@mayday.cix.co.uk>
Subject: Re: WY60 eight-bit characters

On 30 Oct 2001, Iggy Drougge wrote:
>
> Robert de Bath skrev:
>
> >I've got a couple of wy120's, the 'economy version', and to make them
> >understand 8 bit characters they need to be in vt220 mode not vt100 mode.
>
> Unfortunately the WY60 doesn't have any VT220 mode.
>
> >You'll Also want to set the 'char mode' to multinational and the 'char set'
> >to 'ISO-Latin 1'.
>
> And I can't find any such options, either.


Oh. Okaaay... Right I've dug out the manual ...

It says nothing about iso-8859-1, shame that means most of the modern locale
stuff won't work directly. I does have IBM codepage 437 so you can display
some characters. It says the character set selection strings work in Native,
WY-50+ and ADM31 modes.

If your current terminfo for the wy60 is rubbish the one in Eric Raymond's
master terminfo is respectable; it's at:

   http://www.tuxedo.org/terminfo

If you want locale to work your best bet is probably to use GNU 'screen'
to do the translation. The uuencode data at the end of this message is
a line for the .screenrc that does ISO-8859-1 to CP437 translation.
for keyboard entry you'll have to define your favorite bindkey items.

In use you'll want to re-define the wy60's backspace key and probably
the arrow keys on the terminal itself. By default the left arrow and
backspace send the same character (^H) and the down arrow sends a ^J
which will be confused with a CR if the tty isn't in raw mode.

You can get lots of information on the wyse60 from the wyse website:

    http://www.wyse.com/service/support/kbase/wyseterm.asp
   http://www.wyse.com/service/support/kbase/KBmenu1.asp?Q=7
   http://www.wyse.com/service/support/kbase/SEQwt.asp?Q=7
   http://www.wyse.com/service/support/kbase/FAQwt.asp?Q=7

The cp437 upper characters are called 'multinational' by the wy60.
The FAQs also have wyse termcap and terminfo entries.

Have fun!


---------------- begin uuencoded part -------------------
begin 644 screenrc_line
M=&5R;6EN9F\@=WDV,"`G6$,]0B4L7#(T,%PS-S<L7#(T,5PR-34L7#(T,EPR
M,S,L7#(T,UPR,S0L7#(T-"XL7#(T-5PR,S4L7#(T-GPL7#(T-U,L7#(U,"(L
M7#(U,4,L7#(U,EPR-#8L7#(U,UPR-38L7#(U-%PR-3(L7#(U-2TL7#(U-E(L
M7#(U-UPS,#0L7#(V,%PS-S`L7#(V,5PS-C$L7#(V,EPS-S4L7#(V,S,L7#(V
M-%PP-#<L7#(V-5PS-#8L7#(V-GPL7#(V-UPS-S(L7#(W,"XL7#(W,3$L7#(W
M,EPR-#<L7#(W,UPR-3<L7#(W-%PR-30L7#(W-5PR-3,L7#(W-B\L7#(W-UPR
M-3`L7#,P,$$L7#,P,4$L7#,P,D$L7#,P,T$L7#,P-%PR,38L7#,P-5PR,3<L
M7#,P-EPR,C(L7#,P-UPR,#`L7#,Q,$4L7#,Q,5PR,C`L7#,Q,D4L7#,Q,T4L
M7#,Q-$DL7#,Q-4DL7#,Q-DDL7#,Q-TDL7#,R,$0L7#,R,5PR-#4L7#,R,D\L
M7#,R,T\L7#,R-$\L7#,R-4\L7#,R-EPR,S$L7#,R-W@L7#,S,%PS-34L7#,S
M,54L7#,S,E4L7#,S,U4L7#,S-%PR,S(L7#,S-5DL7#,S-E`L7#,S-UPS-#$L
M7#,T,%PR,#4L7#,T,5PR-#`L7#,T,EPR,#,L7#,T,V$L7#,T-%PR,#0L7#,T
M-5PR,#8L7#,T-EPR,C$L7#,T-UPR,#<L7#,U,%PR,3(L7#,U,5PR,#(L7#,U
M,EPR,3`L7#,U,UPR,3$L7#,U-%PR,34L7#,U-5PR-#$L7#,U-EPR,30L7#,U
M-UPR,3,L7#,V,&\L7#,V,5PR-#0L7#,V,EPR,C4L7#,V,UPR-#(L7#,V-%PR
M,C,L7#,V-6\L7#,V-EPR,C0L7#,V-UPS-C8L7#,W,%PS-34L7#,W,5PR,C<L
M7#,W,EPR-#,L7#,W,UPR,C8L7#,W-%PR,#$L7#,W-7DL7#,W-G`L7#,W-UPR
M,S`L+#`E+%\@+&`N+&%<,C8Q+&9<,S<P+&=<,S8Q+&I<,S,Q+&M<,C<W+&Q<
M,S,R+&U<,S`P+&Y<,S`U+&]^+'`M+'%<,S`T+'(M+'-?+'1<,S`S+'5<,C8T
M+'9<,S`Q+'=<,S`R+'A<,C8S+'E<,S8S+'I<,S8R+'M<,S0S+'PC+'U<,C,T
M+'Y<,S<R+%PQ-S<@+"Q!)2PC7#(S-"PL0R4L0"`L6UPR,38L7%Q<7%PR,S$L
M75PR,3<L8"`L>UPR,#0L?%PR,C0L?5PR,#8L?BTL+$4E+")<,C4V+"-<,C4W
M+$`@+%M<,C(R+%Q<7%Q<,S4U+%U<,C$W+&`@+'M<,C(Q+'Q<,S4U+'U<,C`V
M+'XM+"Q')2PD+BQ;7#(Q-BQ<7%Q<7#(S,2Q=7#(Q-RQ[7#(P-"Q\7#(R-"Q]
M7#(P-BQ^7#,P-"PL2"4L)"XL0%PR,C`L6UPR,38L7%Q<7%PR,S$L75PR,3<L
M7#$S-EPR,S(L8%PR,#(L>UPR,#0L?%PR,C0L?5PR,#8L?EPR,#$L+$HE+%Q<
M7%Q<,C,U+'Y<,S`T+"Q+)2Q`4RQ;7#(Q-BQ<7%Q<7#(S,2Q=7#(S,BQ[7#(P
M-"Q\7#(R-"Q]7#(P,2Q^7#,T,2PL3"4L0%,L6T$L7%Q<7%PR,#`L74\L>V$L
M?%PR,#<L?6\L?EPS-S`L+%(E+"-<,C,T+$!<,C`U+%M<,S<P+%Q<7%Q<,C`W
M+%U3+'M<,C`R+'Q<,C(W+'U<,C$R+'XB+"Q4)2PD7#(S-2Q^7#,P-"PL5R4L
M(2`L(B`L(R`L)B`L/R`L0"`L7%Q<7"`L7#$S-B`L7R`L8"`L>R`L?2`L?B`L
M+%DE+"-<,C,T+$!3+%M<,S<P+%Q<7%Q<,C`W+%U<,C`R+&!<,C(W+'M<,C`U
M+'Q<,C(U+'U<,C$R+'Y<,C$U+"Q:)2PC7#(S-"PD+BQ`4RQ;7#(U-2Q<7%Q<
M7#(T-2Q=7#(U,"Q[7#,W,"Q\7#(T-"Q]7#(P-RPL824L(U,L6UPR,C(L7%Q<
M7%PS-34L75PR,3<L>UPR,C$L?%PS-34L?5PR,#8L?GPL+&8E+"-<,C,T+$!<
M,C`U+%M<,S<P+%Q<7%Q<,C`W+%U3+&!<,S0V+'M<,C`R+'Q<,C(W+'U<,C$R
M+'XB+"QG)2Q`7#`T-RQ;02Q<7%Q<7#(P,"Q=3RQ[82Q\7#(P-RQ];RPL:"4L
M0%PS-S(L6UPR-34L7%Q<7%PR-#4L75PR,#`L7#$S-EPR-3`L>UPP-#<L?%PR
M-#0L?5PR,#<L?B(L+&DE+"0N+$!!+%M<,C(P+%Q<7%Q<,C,Q+%U<,C,R+&!<
M,C0P+'M<,C`R+'Q<,C(T+'U<,C`Q+'XB+"QN)2Q<7%Q<7#(S-2Q@("Q^("PL
M=24L)"XL7%Q<7"`L7#$S-B`L8"`L>R`L?2`L?B`L+'<E+$!<,C`U+%M<,C`S
M+%Q<7%Q<,C`W+%U<,C$P+%PQ,S9<,C$T+&!<,C(S+'M<,C`R+'Q<,C(W+'U<
M,C$R+'Y<,C(V+"QX)2Q`7#(P-2Q;7#(P,RQ<7%Q<7#(P-RQ=7#(Q,"Q<,3,V
M7#(R,"Q@7#(R,RQ[7#(P,BQ\7#(R-RQ]7#(Q,BQ^7#(R-BPL0"4L)"XL?EPS
M,#0L+&`E+%M<,C(R+%Q<7%Q<,S4U+%U<,C$W+'M<,C(Q+'Q<,S4U+'U<,C`V
(+'Y<,S`T)PI<
`
end

-- 
Rob.                          (Robert de Bath <robert$ @ debath.co.uk>)
                                       <http://www.cix.co.uk/~mayday>


 //////////////////////////////////////////////////////////////////////////////



Newsgroups: comp.terminals
Message-ID: <65089820.0110311908.112b2cf@posting.google.com>
Organization: http://groups.google.com/
Date: 31 Oct 2001 19:08:44 -0800
From: Ian Primus <ian_primus@yahoo.com>
Subject: Wyse 75 terminal problems

I recently accquired a used (read abused) Wyse 75 terminal and
keyboard. The terminal was filthy when I got it, and I dusted it off
and plugged it in. It beeps, and seems to work just fine, the screen
is legible, and I can get into the setup and everything. The only
problem is that the screen is kinda messed up/wavy, and it makes an
annoying whineing/squealing noise. It also smells really bad after it
has been running for a few minutes. I popped the cover off the monitor
part, and it doesn't look like any caps have burst. Any ideas? What
could cause this sort of a problem? Thanks!

Ian Primus
ian_primus@yahoo.com


 //////////////////////////////////////////////////////////////////////////////

Newsgroups: comp.terminals
References: <65089820.0110311908.112b2cf@posting.google.com>
Message-ID: <3BE06A10.A43A33B@rcn.com>
Date: Wed, 31 Oct 2001 21:16:01 +0000
From: Jim <microsyseng@rcn.com>
Subject: Re: Wyse 75 terminal problems

Just a guess, it sounds like the low voltage power supply is messed up.
Maybe the filter caps need replacing. Without a better description of
what wavy means it's a bit hard to be accurate. You may want to find out
what's getting overheated. Try the low voltage line transformer. I think
those terminals have one.  I am too lazy to take mine apart to find out.
I am thinking wavy means that there are one or two horizontal lines
slowly moving up the screen distorting the characters.

One other thing you might try is the horizontal oscillator may be off
frequency. There should be an adjust for that either in a coil or a pot
adjustment. I would do this as a last after you have checked for what's
overheating and causing the smell.  More than likely the oscillator
frequency will change with some percentage of change in the D.C. power
supply voltage. One method is to pull the D.C. power supply leads from
the rest of the circuit and see see if the transformer still heats up.
Meaning, separate the D.C. voltage generated at the power supply from
the circuit it powers.

In any case, you will need to check those power supply caps and the
diodes.. Hope you got a volt/ohm meter handy. If not go to radio shack
and get a cheap one. It will do the job you need done.

By the way, I have a Wyse 85 that I have been using for a few years.
It's quite reliable for my purposes and has a small footprint which
leaves plenty of space on the table it sits on. It's quiet as a
churchmouse although I have never heard a churchmouse....



 //////////////////////////////////////////////////////////////////////////////


Newsgroups: comp.terminals
References: <9s0cgp$10dmgq$4@ID-1927.news.dfncis.de>
    <e15f68fcec1e5aa4@mayday.cix.co.uk>
Message-ID: <9sgpeh$319$4@news1.Radix.Net>
Organization: RadixNet Internet Services
Date: 9 Nov 2001 14:32:49 GMT
From: Thomas Dickey <dickey@saltmine.radix.net>
Subject: Re: Wyse WY-60, Linux and the return key

Robert de Bath <rd104097@mayday.cix.co.uk> wrote:
> On Sat, 3 Nov 2001, Gunther Schmidt wrote:

>> I have a Wyse WY-60 attached to a PC running SuSE Linux 6.3, and apart
>> from the fact that I can't connect with speeds over 9600 it's running
>> quite well. But I have some problems with the return key - it's not
>> always recognized as such. For example in mc the return key brings a
>> 'M' onto the screen, so I have to type Ctrl-M instead.
>>
>> How can I solve this problem?


> This is a terminfo/termcap problem.
> The host is putting the keypad into application mode, a very silly idea
> from when terminals didn't have function keys. Application mode is
> just a PITA on a unix system.

> You'll probably want to start by removing the smkx and rmkx strings
>    rmkx=\E[?1l\E>, smkx=\E[?1h\E=,

> and adjusting the arrow key strings to ...
>    kcub1=\E[D, kcud1=\E[B, kcuf1=\E[C, kcuu1=\E[A,


I don't see in his posting any indication that the terminal was set to run
in vt100 mode.  (You seem to be assuming that he's confusing the numeric
keypad's "Enter" key with the return key).  The wy60 terminfo entry doesn't
contain smkx/rmkx.

-- 
Thomas E. Dickey <dickey@radix.net> <dickey@herndon4.his.com>
http://dickey.his.com
ftp://dickey.his.com


 //////////////////////////////////////////////////////////////////////////////

Newsgroups: comp.terminals
References: <9s0cgp$10dmgq$4@ID-1927.news.dfncis.de>
    <e15f68fcec1e5aa4@mayday.cix.co.uk> <9sgpeh$319$4@news1.Radix.Net>
Message-ID: <7ae0debbfea7776e@mayday.cix.co.uk>
Organization: Mayday Technology Ltd
Date: Sat, 10 Nov 2001 19:32:09 +0000
From: Robert de Bath <rd104097@mayday.cix.co.uk>
Subject: Re: Wyse WY-60, Linux and the return key

On 9 Nov 2001, Thomas Dickey wrote:

> I don't see in his posting any indication that the terminal was set to run
> in vt100 mode.

Oh haven't you installed the ESP module yet ?  :-)

Seriously tho, I've used wy60's and wy120's and they are _very_ good
terminals but if they were running in native mode he would have been
having problems with the backspace key and the left and down arrow keys
not return. (BTW: Most Users are used to the PC keyboard under windows,
or the linux console, and think Enter and Return are synonyms)

IME on most unix machines (But never the linux console) the commonest
termcapinfo problems are:


1) Wrong TERM= setting.
   If possible an auto-detect is best but can only be reliable if all
   the terminals are one of a small set of types.

2) VT100 Klone function keys.
   ARRRRRRRRRRRGGGGGG!!! ****! ****! ****! ****! ****! ****! ****!!!!
   I told a lie -- the linux console _is_ a culprit here!

   Nearly every terminal emulator has a vt100 klone emulation most of
   them agree on F1..F4 (Except Linux! and XTerm R5) but _none_ of them
   agree on the rest; and as for Shift Fkeys don't make me laugh!

3) VT100 Application keypad.
   This can be as evil as some termcaps having smkx and rmkx the wrong
   way around but the terminfo on the same machine is different. So one
   application will work until you use 'vi'. But just turning it on
   will effectivly disable the numeric keypad just when your 'User'
   wants to use it.

4) WY60 arrow keys.
   This is rare nowadays as it's much more likely that TERM= will be
   set wrongly.


Enough! I expect you know all this Thomas; for me it's an everyday
occurance, I was at a client's on Tuesday and they haven't even got
the 'stty' setting setup (let alone termcapinfo) on their HP-UX box.


"Is the caplock light turned off?"
"Press the colon key" -- "What's a colon."
"I can't find the 'any' key"
"The backslash is the key with a line from to left to bottom right"
"What's a tilda?" -- "The squiggle key"    (This was _yesterday_!!)

-- 
Rob.                          (Robert de Bath <robert$ @ debath.co.uk>)
                                       <http://www.cix.co.uk/~mayday>

 //////////////////////////////////////////////////////////////////////////////


Newsgroups: comp.terminals
References: <9s0cgp$10dmgq$4@ID-1927.news.dfncis.de>
    <e15f68fcec1e5aa4@mayday.cix.co.uk> <9sgpeh$319$4@news1.Radix.Net>
    <7ae0debbfea7776e@mayday.cix.co.uk>
Message-ID: <9sm50f$3em$2@news1.Radix.Net>
Organization: RadixNet Internet Services
Date: 11 Nov 2001 15:20:47 GMT
From: Thomas Dickey <dickey@saltmine.radix.net>
Subject: Re: Wyse WY-60, Linux and the return key

Robert de Bath <rd104097@mayday.cix.co.uk> wrote:
> 3) VT100 Application keypad.
>    This can be as evil as some termcaps having smkx and rmkx the wrong
>    way around but the terminfo on the same machine is different. So one
>    application will work until you use 'vi'. But just turning it on
>    will effectivly disable the numeric keypad just when your 'User'
>    wants to use it.


I've been spoiled by xterm, which lets me reset the cursor- and keypad-modes
from the popup menu (it's been a long time since I had to tinker with the
setup mode in a serial terminal).  So I guess it is inconvenient when you
run into a program that doesn't treat smkx/rmkx properly (but it's probably
better to just fix the program).

-- 
Thomas E. Dickey <dickey@radix.net> <dickey@herndon4.his.com>
http://dickey.his.com
 ftp://dickey.his.com

 //////////////////////////////////////////////////////////////////////////////

Newsgroups: comp.terminals
Message-ID: <20020111.173610.1186452551.20935@jeroen.fw.belnet.be>
Organization: BELNET
Date: Fri, 11 Jan 2002 17:36:11 +0100
From: Jeroen Valcke <jeroen@nspm.valcke.com>
Subject: break sequence on WYSE terminal

Hello,

I have a WY-520ES which is connected to a Cisco 2500 series router. 
When booting the cisco, I need to send a 'break' sequence. 
I tried the list provided by cisco

    http://www.cisco.com/warp/public/701/61.html

None seems to work.
Any ideas?

 //////////////////////////////////////////////////////////////////////////////

Newsgroups: comp.terminals
References: <20020111.173610.1186452551.20935@jeroen.fw.belnet.be>
Message-ID: <slrna3ups8.ep.hugo_villeneuve@jwales.EINTR.net>
Date: Fri, 11 Jan 2002 22:30:32 GMT
From: Hugo Villeneuve <hugo_villeneuve@no_private_reply_at_yahoo.com>
Subject: Re: break sequence on WYSE terminal

It depends on which keyboard you use (ANSI or PC), see:

    http://www.wyse.com/service/support/kbase/Keydetl1.asp?Q=27&R=4


  Extract:
  ---
  Cmd                                             ANSI    EPC
  Send break to host (for active session)         F5      Alt Pause
  ---

On my Wyse 520 with ANSI keyboard, the F1 to F5 keys did not have
special meanings until I enabled them in the setup menu.

With an ANSI keyboard, holding F3 while powering up the terminal
will bring you to the setup menu, from there follows the menu and
change the F5 key meaning to break. [You can change the meaning of
F3 to setup so that you can go into the setup at any time, not just
powerup.]

[I don't know what's the difference between an 520 and 520ES.]
[I don't know what's the difference between my 1994 unit and
 a 2002 one. Things could have get changed since then.]

Anyway, this is my Amber Wyse 520 terminal:

    http://www.eintr.net/systems/wyse520/index.html

Hugo Villeneuve

 //////////////////////////////////////////////////////////////////////////////


Newsgroups: comp.terminals
Message-ID: <14849043.0205160806.683e6ca4@posting.google.com>
Organization: http://groups.google.com/
Date: 16 May 2002 09:06:09 -0700
From: Darrin Filer <djfiler@yahoo.com>
Subject: WYSE150   v.   ASCII line graphics

I can't seem to get any line graphics to display on a WYSE150es. (The
upper 128 through 255 ascii characters) We're running it in vt100 mode
off of Red Hat Linux 6.2.

Using the Anita terminal emulation program in Windows, I've gotten the
line graphics to display by setting the character set to "IBM PC
(OEM)". However, we still have terminals in use so I need to get them
to display the characters properly as well. Since the characters are
displayed properly in the emulator, I'm assuming that they are being
transmitted properly and all I need to do is find the appropriate
setting for the WYSE150 in vt100 mode.

This probably has something to do with character set selection, but
all the limited doumentation I've found on the web has got me no
where...

 //////////////////////////////////////////////////////////////////////////////

Newsgroups: comp.terminals
References: <14849043.0205160806.683e6ca4@posting.google.com>
Message-ID: <Xns9210B5B4924E7newscelignecouk@209.249.90.100>
Organization: http://vt100.net
Date: Thu, 16 May 2002 16:56:15 -0000
From: Paul Williams <news@celigne.co.uk>
Subject: Re: WYSE150   v.   ASCII line graphics

djfiler@yahoo.com (Darrin Filer) wrote in 
news:14849043.0205160806.683e6ca4@posting.google.com:

> I can't seem to get any line graphics to display on a WYSE150es. (The
> upper 128 through 255 ascii characters) We're running it in vt100 mode
> off of Red Hat Linux 6.2.

This could depend on the fidelity of the Wyse terminal's VT100 emulation. A 
real VT100 only accepts 7-bit characters (ie. it'll just ignore the top 
bit).

- Paul
 //////////////////////////////////////////////////////////////////////////////


Newsgroups: comp.terminals
Message-ID: <14849043.0205160928.61bb17a6@posting.google.com>
Organization: http://groups.google.com/
Date: 16 May 2002 10:28:01 -0700
From: Darrin Filer <djfiler@yahoo.com>
Subject: tuxedo.org's terminfo - no destructive backspace for WYSE50 or
    WYSE150 ?

We've got a WYSE 150es which needs to display ascii line graphics.
Instead of bashing my head against the vt100 workarouds for this,
we've decided to run the terminal in its native personality, wyse 150
or 150+. Unfortunately, the backspace key isn't functioning properly,
behaving simply as a left arrow. control-b does the same thing as
control-h or the left arrow key.

In fact, I haven't found a control sequence for a WYSE 150 that
actually does do a destructive backspace. I'm becoming more familiar
with the terminfo file but even the one found at tuxedo.org doesn't
have a functional backspace.

With the terminal set to emulate WYSE 150 or 150+ (actually the native
personality) and TERM=wy150  --- screen attributes like reverse video
don't work
With the terminal set to emulate WYSE 50 or 50+ and TERM=wy50 or wy150
-- line graphics come out as other characters
With the terminal set to emulate WYSE 150 or 150+ and TERM=wy50 --
screen attributes are ok!

All three of these scenarios fail to produce a destructive backspace.
However, running as a WYSE150+ with TERM=wy50 at least gets me the
line art and correct text display attributes. The other choice is to
run as a vt100 with TERM=vt100 and use no line graphics but with a
destructive backspace.

Does anyone out there have a destructive backspace on their WYSE150
with TERM=wy50 or wy150 or ?????

darrin Filer

 //////////////////////////////////////////////////////////////////////////////


Newsgroups: comp.terminals
References: <14849043.0205160928.61bb17a6@posting.google.com>
Message-ID: <rshu_20020516181818@list.stratagy.com>
Organization: Stratagy Users Group
Date: Thu, 16 May 2002 18:18:18 -0400
From: Richard Shuford <shuford@list.stratagy.REM0VE-THlS-PART.com>
Subject: Re: no destructive backspace for WYSE50 or WYSE150? (terminfo)

Darrin Filer djfiler(at)@yahoo.com wrote:
| 
| We've got a WYSE 150es which needs to display ascii line graphics.
| ...
| In fact, I haven't found a control sequence for a WYSE 150 that
| actually does do a destructive backspace. I'm becoming more familiar
| with the terminfo file but even the one found at tuxedo.org doesn't
| have a functional backspace.


Unfortunately you don't say to what kind of system this Wyse 150-es
is attached, or what type of software application is communicating
with the terminal.
 
Putting on my Sherlock Holmes Detective Hat, I deduce from your
reference to a "terminfo" file that the host system has terminal
control of the type associated with System V Unix derivatives.

It would be a mild extrapolation to deduce that you have not read
the documentation for the "stty" command, as by typing "man stty".
Depending on the Unix flavor, other man pages of significance
might be ldterm, termio, and termios (as in the case of Solaris;
for other Unix implementations or for Linux, your mileage may vary).

Now, admittedly, man-page documentation is often useful only if you
already have an idea of what to look for.  If you'd like a kinder,
gentler introduction to the subject, I suggest you look here first:
    
    http://www.aplawrence.com/Unixart/terminals.html

and then follow up with resources listed at:
    
    http://www.cs.utk.edu/~shuford/terminal_index.html

Although not must use with most System V Unix products, the
following is useful for those with BSD-derived Unix systems:
    
    http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/term.html

 ...Richard Shuford
    shuford(at)list.stratagy.com

 //////////////////////////////////////////////////////////////////////////////


Newsgroups: comp.terminals
Message-ID: <b738160dd23d66ba@mayday.cix.co.uk>
Organization: Mayday Technology Ltd
Date: Fri, 17 May 2002 07:18:36 +0100
From: Robert de Bath <rd11824@mayday.cix.co.uk>
Subject: Re: WYSE150   v.   ASCII line graphics

On 16 May 2002, Darrin Filer wrote:

> I can't seem to get any line graphics to display on a WYSE150es. (The
> upper 128 through 255 ascii characters) We're running it in vt100 mode
> off of Red Hat Linux 6.2.

A real VT100 does NOT do codepage 437.

On Thu, 16 May 2002, Paul Williams wrote:

> This could depend on the fidelity of the Wyse terminal's VT100 emulation. A
> real VT100 only accepts 7-bit characters (ie. it'll just ignore the top
> bit).

In VT100 mode the Wy120 (the previous model) strips off the top bit ie it
ignores parity. In fact the wy120's emulation is so good that it even gets
the finer differences between the vt100 and the vt220 correct eg: NRC mode.

On 16 May 2002, Darrin Filer wrote:

> Using the Anita terminal emulation program in Windows, I've gotten the
> line graphics to display by setting the character set to "IBM PC
> (OEM)". However, we still have terminals in use so I need to get them
> to display the characters properly as well. Since the characters are
> displayed properly in the emulator, I'm assuming that they are being
> transmitted properly and all I need to do is find the appropriate
> setting for the WYSE150 in vt100 mode.

I don't think you will be able to do this in vt100 mode. If you're in
vt220 mode (assuming the wy150 has it) you can set the high bit characters
to ISO-8859-1 (or latin1) which is the character set that Windows cp1252
is based on. This way you'll have a for more standard high bit character
set for £ and áéíóú.

You can still access the real line drawing characters (the box corners
etc) by using the VT100 character set controls (if 'Anita' is any good
at all) by making sure that the TERM variable in Linux is vt100, vt220
or something similar.

If you get this right your next headache is function keys -- a real vt100
has _none_ ... though it does have four 'PF' keys.

> This probably has something to do with character set selection, but
> all the limited doumentation I've found on the web has got me no
> where...

If you can't access the characters you want in vt100 mode may have more
luck in native mode, but make sure the host knows it's talking to a wy150
not a vtklone. (TERM= variable) The wyse website has some documentation
on the terminals if you need to go past the basic terminfo.

BTW:
  I use ISO-8859-1 on all of wy120, Linux console, xterm and Windows
  terminal emulators (PuTTY, CRT etc). The wyse works fine (including
  boxes) in vt220 mode with a stock vt220 terminfo but the f-keys are
  mis-labeled so I use this instead:

vt220-120|Wyse120 in VT220 emulation mode,
      kf1=\EOP, kf2=\EOQ, kf3=\EOR, kf4=\EOS,                                         kf5=\E[M, kf6=\E[17~, kf7=\E[18~, kf8=\E[19~,
      kf9=\E[20~, kf10=\E[21~, kf11=\E[23~, kf12=\E[24~,
      use=vt220,


-- 
Rob.                          (Robert de Bath <robert$ @ debath.co.uk>)
                                       <http://www.cix.co.uk/~mayday>


 //////////////////////////////////////////////////////////////////////////////

Newsgroups: comp.terminals
References: <14849043.0205160928.61bb17a6@posting.google.com>
    <rshu_20020516181818@list.stratagy.com>
Message-ID: <a69226b7a8ead3d3@mayday.cix.co.uk>
Organization: Mayday Technology Ltd
Date: Fri, 17 May 2002 07:37:53 +0100
From: Robert de Bath <rd11824@mayday.cix.co.uk>
Subject: Re: no destructive backspace for WYSE50 or WYSE150? (terminfo)

On Thu, 16 May 2002, Richard Shuford wrote:

> Darrin Filer djfiler(at)@yahoo.com wrote:

> Unfortunately you don't say to what kind of system this Wyse 150-es
> is attached, or what type of software application is communicating
> with the terminal.

Tut, Tut Richard, please do pay attention, it's Red Hat Linux 6.2
as Darrin said in his other message. <smirk>

-- 
Rob.                          (Robert de Bath <robert$ @ debath.co.uk>)
                                       <http://www.cix.co.uk/~mayday>

 //////////////////////////////////////////////////////////////////////////////

Newsgroups: comp.terminals
References: <14849043.0205160928.61bb17a6@posting.google.com>
Message-ID: <f15295e4e1119eda@mayday.cix.co.uk>
Organization: Mayday Technology Ltd
Date: Fri, 17 May 2002 07:31:58 +0100
From: Robert de Bath <rd11824@mayday.cix.co.uk>
Subject: Re: tuxedo.org's terminfo - no destructive backspace for WYSE50 or
    WYSE150 ?

On 16 May 2002, Darrin Filer wrote:

> We've got a WYSE 150es which needs to display ascii line graphics.
> Instead of bashing my head against the vt100 workarouds for this,
> we've decided to run the terminal in its native personality, wyse 150
> or 150+. Unfortunately, the backspace key isn't functioning properly,
> behaving simply as a left arrow. control-b does the same thing as
> control-h or the left arrow key.

> Does anyone out there have a destructive backspace on their WYSE150
> with TERM=wy50 or wy150 or ?????

This is the main reason I don't like wyse native modes. The left arrow and
backspace both default to ^H. The normal workaround is to map one or the
other to some other sequence in the terminal then adjust the terminfo to
match. As down arrow (which is mapped to ^J) is also frequently a problem
I tended to remap the arrow keys. Once the arrow keys are out of the way

  stty erase ^H

will make the backspace destructive. Just to complete the problem the
function keys are also a little weird and occasionally give problems
as their sequences include ^A (which may get eaten) and ^M (which may
be translated to ^J)!

-- 
Rob.                          (Robert de Bath <robert$ @ debath.co.uk>)
                                       <http://www.cix.co.uk/~mayday>

 //////////////////////////////////////////////////////////////////////////////

Newsgroups: comp.terminals
References: <14849043.0205160806.683e6ca4@posting.google.com>
    <Xns9210B5B4924E7newscelignecouk@209.249.90.100>
Message-ID: <ac2sg6$nfi$1@news1.Radix.Net>
Organization: RadixNet Internet Services
Date: 17 May 2002 12:19:18 GMT
From: Thomas Dickey <dickey@saltmine.radix.net>
Subject: Re: WYSE150   v.   ASCII line graphics

Paul Williams <news@celigne.co.uk> wrote:
> djfiler@yahoo.com (Darrin Filer) wrote in 
> news:14849043.0205160806.683e6ca4@posting.google.com:

>> I can't seem to get any line graphics to display on a WYSE150es. (The
>> upper 128 through 255 ascii characters) We're running it in vt100 mode
>> off of Red Hat Linux 6.2.

> This could depend on the fidelity of the Wyse terminal's VT100 emulation. A 
> real VT100 only accepts 7-bit characters (ie. it'll just ignore the top 
> bit).

true (the reference to 128-255 sounds more like an emulator running on a PC)

-- 
Thomas E. Dickey <dickey@radix.net> <dickey@herndon4.his.com>
http://dickey.his.com
ftp://dickey.his.com

 //////////////////////////////////////////////////////////////////////////////

Newsgroups: comp.terminals
References: <b738160dd23d66ba@mayday.cix.co.uk>
Message-ID: <ac2so0$nfi$2@news1.Radix.Net>
Organization: RadixNet Internet Services
Date: 17 May 2002 12:23:28 GMT
From: Thomas Dickey <dickey@saltmine.radix.net>
Subject: Re: WYSE150   v.   ASCII line graphics

Robert de Bath <rd11824@mayday.cix.co.uk> wrote:

> BTW:
>   I use ISO-8859-1 on all of wy120, Linux console, xterm and Windows
>   terminal emulators (PuTTY, CRT etc). The wyse works fine (including
>   boxes) in vt220 mode with a stock vt220 terminfo but the f-keys are
>   mis-labeled so I use this instead:

> vt220-120|Wyse120 in VT220 emulation mode,
>       kf1=\EOP, kf2=\EOQ, kf3=\EOR, kf4=\EOS,                                         kf5=\E[M, kf6=\E[17~, kf7=\E[18~, kf8=\E[19~,
>       kf9=\E[20~, kf10=\E[21~, kf11=\E[23~, kf12=\E[24~,
>       use=vt220,

hmm - just looking at it, I don't see which is mislabeled.  (Is your
base 'vt220' numbering the keys off-by-one?)

-- 
Thomas E. Dickey <dickey@radix.net> <dickey@herndon4.his.com>
http://dickey.his.com
ftp://dickey.his.com

 //////////////////////////////////////////////////////////////////////////////

Newsgroups: comp.terminals
References: <14849043.0205160928.61bb17a6@posting.google.com>
    <f15295e4e1119eda@mayday.cix.co.uk>
Message-ID: <14849043.0205170714.56fb6258@posting.google.com>
Organization: http://groups.google.com/
Date: 17 May 2002 08:14:40 -0700
From: Darrin Filer <djfiler@yahoo.com>
Subject: Re: tuxedo.org's terminfo - no destructive backspace for WYSE50 or
    WYSE150 ?

Ok, getting closer. Thanks for the assistance.

I've used the setup screen on the WYSE150 to remap the left arrow key
to control-B. Pressing the left arrow key now produces ^B on the
screen. This can be deleted as a single character by pressing the
backspace key. Obviously the desired behavior is moving the cursor one
character to the left.

I assumed this behavior could be set in terminfo with the following
syntax:
kcub1=^B,
or (what's the diffence between these anyway)
cub1=^B,
However, hitting a control-B or the left arrow, which produces this
sequence, only puts ^B on the screen. The terminfo settings were
verified after running tic by looking at the output of infocmp and
they were in fact set. Next I tried typing: stty erase ^B to see what
would happen. Yet control-B still only displays ^B.

What am I missing?
(I've pasted the output from infocmp below)

Darrin Filer

==========================================================================

#       Reconstructed via infocmp from file: /u1/djf/.terminfo/w/wy120
wy120|wyse120|wy150|wyse150|Wyse 120/150,
        am, bw, hs, km, mc5i, mir, msgr, xon,
        cols#80, it#8, lh#1, lines#24, lw#8, nlab#8, pb#9601, wsl#45,
        acsc=+/\,.0[Iha2fxgqh1jYk?lZm@nEqDtCu4vAwBx3yszr{c~~,
        bel=^G, blink=\EG2, cbt=\EI, civis=\E`0, clear=\E+$<50>,
        cnorm=\E`1, cr=^M, cub1=^B, cud1=^J, cuf1=^L,
        cup=\E=%p1%' '%+%c%p2%' '%+%c, cuu1=^K, dch1=\EW$<7>,
        dim=\EGp, dl1=\ER$<3>, dsl=\EF\r, ed=\EY$<50>, el=\ET$<4>,
        flash=\E`8$<100/>\E`9, fsl=^M, home=^^, ht=\011$<1>,
        hts=\E1, il1=\EE$<3>, ind=\n$<3>, ip=$<2>, is1=\EcB0\EcC1,
        is2=\Ed$\EcD\E'\Er\EH\003\Ed/\EO\Ee1\Ed*\E`@\E`9\E`1\016\024\El,
        is3=\EwJ\Ew1$<150>, kHOM=\E{, kbs=^H, kcbt=\EI, kcub1=^B,
        kcud1=^J, kcuf1=^L, kcuu1=^K, kdch1=\EW, kdl1=\ER, ked=\EY,
        kel=\ET, kent=\E7, kf1=^A@\r, kf10=^AI\r, kf11=^AJ\r,
        kf12=^AK\r, kf13=^AL\r, kf14=^AM\r, kf15=^AN\r, kf16=^AO\r,
        kf2=^AA\r, kf3=^AB\r, kf4=^AC\r, kf5=^AD\r, kf6=^AE\r,
        kf7=^AF\r, kf8=^AG\r, kf9=^AH\r, khome=^^, kich1=\EQ,
        kil1=\EE, knp=\EK, kpp=\EJ, kprt=\EP, krpl=\Er, ll=^^^K,
        mc0=\EP, mc4=^T, mc5=\Ed#, nel=\r\n$<3>,
        pfloc=\EZ2%p1%'?'%+%c%p2%s\177,
        pfx=\EZ1%p1%'?'%+%c%p2%s\177,
        pln=\Ez%p1%'/'%+%c%p2%s\r, prot=\E), ri=\Ej$<2>,
        rmacs=\EcD, rmam=\Ed., rmcup=\Ew1, rmir=\Er, rmln=\EA11,
        rmxon=\Ec20, rs1=\E~!\E~4$<30>, rs2=\EeF\E`\:$<70>,
        rs3=\EwG\Ee($<100>,
        sgr=%?%p8%t\E)%e\E(%;%?%p9%t\EcE%e\EcD%;\EG%'0'%?%p2%t%{8}%|%;%?%p1%p3%
        sgr0=\E(\EH\003\EG0\EcD, smacs=\EcE, smam=\Ed/,
        smcup=\Ew0, smir=\Eq, smln=\EA10, smso=\EGt, smxon=\Ec21,

===============================================================================


> This is the main reason I don't like wyse native modes. The left arrow and
> backspace both default to ^H. The normal workaround is to map one or the
> other to some other sequence in the terminal then adjust the terminfo to
> match. As down arrow (which is mapped to ^J) is also frequently a problem
> I tended to remap the arrow keys. Once the arrow keys are out of the way
> 
>   stty erase ^H
> 
> will make the backspace destructive. Just to complete the problem the
> function keys are also a little weird and occasionally give problems
> as their sequences include ^A (which may get eaten) and ^M (which may
> be translated to ^J)!

 //////////////////////////////////////////////////////////////////////////////

Newsgroups: comp.terminals
References: <b738160dd23d66ba@mayday.cix.co.uk>
    <ac2so0$nfi$2@news1.Radix.Net>
Message-ID: <f36cb7367ab9029c@mayday.cix.co.uk>
Organization: Mayday Technology Ltd
Date: Fri, 17 May 2002 21:33:55 +0100
From: Robert de Bath <rd11824@mayday.cix.co.uk>
Subject: Re: WYSE150   v.   ASCII line graphics


On 17 May 2002, Thomas Dickey wrote:

> Robert de Bath <rd11824@mayday.cix.co.uk> wrote:
>
> > BTW:
> >   I use ISO-8859-1 on all of wy120, Linux console, xterm and Windows
> >   terminal emulators (PuTTY, CRT etc). The wyse works fine (including
> >   boxes) in vt220 mode with a stock vt220 terminfo but the f-keys are
> >   mis-labeled so I use this instead:
>
> > vt220-120|Wyse120 in VT220 emulation mode,
> >       kf1=\EOP, kf2=\EOQ, kf3=\EOR, kf4=\EOS,
> >       kf5=\E[M, kf6=\E[17~, kf7=\E[18~, kf8=\E[19~,
> >       kf9=\E[20~, kf10=\E[21~, kf11=\E[23~, kf12=\E[24~,
> >       use=vt220,
>
> hmm - just looking at it, I don't see which is mislabeled.  (Is your
> base 'vt220' numbering the keys off-by-one?)

These are the function keys in my vt220 terminfo.

   kf1=\EOP, kf2=\EOQ, kf3=\EOR, kf4=\EOS, kf5=\E[17~,
   kf6=\E[18~, kf7=\E[19~, kf8=\E[20~, kf9=\E[21~, kf10=\E[29~,

Hmmm, looking at the master it looks like I've got the 'vt220-old' version,
I still need to do the same with the new one though 'cause of F5.

-- 
Rob.                          (Robert de Bath <robert$ @ debath.co.uk>)
                                       <http://www.cix.co.uk/~mayday>

 //////////////////////////////////////////////////////////////////////////////

Newsgroups: comp.terminals
Message-ID: <26e512ffcd3eb2dd@mayday.cix.co.uk>
NNTP-Posting-Host: 62.252.20.222
X-URL: <http://www.cix.co.uk/~mayday>
X-Dev86-Version: 0.16.2
X-Complaints-To: abuse@ntlworld.com
X-Trace: news6-win.server.ntlworld.com 1021709405 62.252.20.222 (Sat, 18 May 2002 09:10:05 BST)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
NNTP-Posting-Date: Sat, 18 May 2002 09:10:05 BST
Organization: Mayday Technology Ltd
Date: Sat, 18 May 2002 08:55:32 +0100
From: Robert de Bath <rd11825@mayday.cix.co.uk> 
Subject: Re: tuxedo.org's terminfo - no destructive backspace for WYSE50 or WYSE150 ?


On Fri, 17 May 2002, Darrin Filer wrote:

> Ok, getting closer. Thanks for the assistance.
>
> I've used the setup screen on the WYSE150 to remap the left arrow key to
> control-B. Pressing the left arrow key now produces ^B on the screen. This can
> be deleted as a single character by pressing the backspace key. Obviously the
> desired behavior is moving the cursor one character to the left.
>
> I assumed this behavior could be set in terminfo with the following syntax:
> kcub1=^B,
> or (what's the diffence between these anyway)
> cub1=^B,

man 5 terminfo

      key_backspace             kbs    kb   backspace key
      key_left                  kcub1  kl   left-arrow key
      cursor_left               cub1   le   move left one space

The ones that begin with 'k' are for the sequences sent by keys.
The ones without are sent by the application to move the cursor round the
screen, don't change these.

Make sure your compiled terminfo is actually used by your application
(eg: get rid of the standard one in /usr/share/terminfo/w while testing)

Note, command line utilities (cat!) don't normally use terminfo however
any that have been linked with the readline utility (eg: bash) will if
/etc/inputrc or ~/.inputrc have been setup (man readline).

If you're using readline (bash) you may want to setup the keys in 'emacs'
mode 'cause readline doesn't always obey terminfo properly:

In terminfo
   kcub1=^B, kcuf1=^F, kcuu1=^P, kcud1=^N,

and in bash
  set -o emacs

or in inputrc
  set editing-mode emacs

> However, hitting a control-B or the left arrow, which produces this sequence,
> only puts ^B on the screen. The terminfo settings were verified after running
> tic by looking at the output of infocmp and they were in fact set. Next I tried
> typing: stty erase ^B to see what would happen. Yet control-B still only
> displays ^B.

This is what you get it you are using bash in 'vi' mode, bash thinks it
knows best, other programs know better.

-- 
Rob.                          (Robert de Bath <robert$ @ debath.co.uk>)
                                       <http://www.cix.co.uk/~mayday>

 //////////////////////////////////////////////////////////////////////////////

Date: Fri, 30 Aug 2002 03:21:30 GMT
Organization: Magma Communications Ltd.
NNTP-Posting-Host: 64.26.167.101
NNTP-Posting-Date: Thu, 29 Aug 2002 23:21:30 EDT
Message-ID: <3D6EE529.757CF12E@istar.ca>
From: Renato Carrara <carraraj@istar.ca>
Subject: Wyse 60 keyboard on a Wyse 150 terminal?

Hi,
Would a Wyse 60 keyboard work properly on a Wyse 150 terminal? I'm
planning on using this "combo" on Sun headless machines. Is there an
equivalent to a Sun keyboard Stop-A?

Thanks
Renato

 //////////////////////////////////////////////////////////////////////////////

Newsgroups: comp.terminals
Message-ID: <rshu_20020830_172001@stratagy.com>
References: <3D6EE529.757CF12E@istar.ca>
Date: Fri, 30 Aug 2002 17:20:01 EDT
From: "Richard S. Shuford" <shuford@list.stratagy.com>
Subject: Sun Stop-A equivalent (was: Wyse 60 keyboard on a Wyse 150 terminal?)


Renato Carrara <carraraj(at)istar.ca> wrote:
|
| Would a Wyse 60 keyboard work properly on a Wyse 150 terminal? 

From time to time, somebody pops up in "comp.terminals" and asks
if Wyse keyboards are interchangable between different models of
terminals made by Wyse.  Not having access to lots of different
Wyse models, I don't know if you can use a Wyse 60 keyboard with 
a 150.  And I'm not sure if you can extrapolate compatibility     
of that relatively older product from the characteristics of 
newer models. Perhaps you can try it and report back what happens?


| I'm planning on using this "combo" on Sun headless machines.
| Is there an equivalent to a Sun keyboard Stop-A?

Sun SPARC-based systems are designed to be configured headless (using
a character-cell console terminal communicating with the A serial port
at 9600,8,N,1 by default) while yet allowing operators to do this.   

Traditionally, the "Break" condition on the RS-232 serial line is
used to signal the OpenBoot PROM monitor to seize control from the
operating system, just as if you had typed Stop-A (or L1-A) on a  
directly attached Sun keyboard.

I think that Wyse terminals have a "Break" key that generates the
the RS-232 serial "Break" condition.  Press that key, or perhaps 
Control and Break together, and you should get the "ok" prompt.  

(The serial "Break" condition is a voltage level held for a certain
length of time; it is not an ASCII character. Also, it is not the  
same as Telnet's "break" signal, unless some terminal server
translates it so.)

A problem arises with serial Break:  voltage glitches from merely
unplugging the terminal's serial cable can *also* produce a serial
Break condition. Sometimes this has mystified system administrators,
not understanding why the machine suddenly dropped into PROM mode,  
suspending all other processing.  (They could recover from this, if
they knew to merely type "go" to the "ok" prompt quickly enough.)  

Therefore, Sun invented an "Alternate Break sequence" that can be
configured on the machine to avoid this voltage-glitch problem.  
By default, the Alternate Break sequence is a 3-character sequence:
Carriage Return, Tilde and Control-B [CR ~ CTRL-B].  For information
on how to set it up, read the following man pages from a recent
release of Solaris:  kbd, zs, se, asy.

An additional safety measure on all of Sun's newer enterprise-class
SPARC servers is a key switch on the frontpanel that enables or
disables the console-Break function.

Further information is archived at the "Unix keyboard" link from
the "system terminal setup" page of [this website] and see also

    http://www.stokely.com/unix.sysadm.resources/faqs.sun.html
    http://www.admin.com/
    
-- 
 ...Richard S. Shuford

 //////////////////////////////////////////////////////////////////////////////

Newsgroups: comp.terminals
References: <3D6EE529.757CF12E@istar.ca>
Message-ID: <3d6fd113$0$79563$3c090ad1@news.plethora.net>
Organization: Plethora.Net
Date: 30 Aug 2002 20:09:55 GMT
From: Peter Seebach <seebs@plethora.net>
Subject: Re: Wyse 60 keyboard on a Wyse 150 terminal?

In article <3D6EE529.757CF12E@istar.ca>,
Renato Carrara  <carraraj@istar.ca> wrote:
>
> Would a Wyse 60 keyboard work properly on a Wyse 150 terminal?

According to the WYSE keyboard/terminal cross-reference list, it should:

    http://www.wyse.com/service/support/kbase/Keydetl1.asp?Q=18&R=3

Everything seems to be compatible with either all three of the 120/150/160,
or none of them.

> I'm planning on using this "combo" on Sun headless machines. Is there an
> equivalent to a Sun keyboard Stop-A?

If you're doing a serial console, sending a "break" should work.  Haven't
gotten my terminal to function well enough to confirm anything yet.

-s
-- 
   Copyright 2002, all wrongs reversed.  Peter Seebach / seebs@plethora.net
   $ chmod a+x /bin/laden      Please do not feed or harbor the terrorists.
     C/Unix wizard, Pro-commerce radical, Spam fighter.  Boycott Spamazon!

 //////////////////////////////////////////////////////////////////////////////

See "Discussion of UNIX (or Linux) terminal use" for more information on
Stop-A equivalents.

 //////////////////////////////////////////////////////////////////////////////

Newsgroups: comp.terminals
References: <3D6EE529.757CF12E@istar.ca>
    <3d6fd113$0$79563$3c090ad1@news.plethora.net>
Message-ID: <3D780F06.82239664@istar.ca>
Organization: Magma Communications Ltd.
Date: Fri, 06 Sep 2002 02:09:53 GMT
From: Renato Carrara <carraraj@istar.ca>
Subject: Re: Wyse 60 keyboard on a Wyse 150 terminal?

Yes, it works! Thanks for the info, Peter.

-- 
Renato

 //////////////////////////////////////////////////////////////////////////////

Newsgroups: comp.terminals
Message-ID: <f73e9b0.0210250616.58262bfa@posting.google.com>
Organization: http://groups.google.com/
Date: 25 Oct 2002 07:16:43 -0700
From: scavenger <root@zonexbox.com>
Subject: wyse60 function keys error

ok, ill do my best to explain my problem. My english is terrible,
sorry.

First of all, we have SCO server 5, with a custom application on
it..the pc client were connecting via serial ports to the server to
log in the application..everything worked fine until we decided to
install a NIC in the SCO server to be able to trash all those serial
cable..The NIC is properly installed, everyone can ping everyone. The
server is using wyse60 emulation protocol. I have downloaded a wyse60
client for windows, i can log in the server as usual, but the display
isnt the same as the old serial connection ..but that is not the
biggest problem, still workable..

The biggest problem is when the user needs to type any Function Keys
such as F8, etc..the server write some @G caracteres..Anyone know what
is the problem and how to resolve it ? Any help is appreciated..thank
you.

Regards

Fred

 //////////////////////////////////////////////////////////////////////////////

Newsgroups: comp.terminals
References: <f73e9b0.0210250616.58262bfa@posting.google.com>
Message-ID: <yEcu9.16576$H67.73828@tor-nn1.netcom.ca>
Organization: AT&T Canada IES
Date: Fri, 25 Oct 2002 07:37:52 -0700
From: Dennis Edward <nothanks@nospam.com>
Subject: Re: wyse60 function keys error

The function key sequence returned by wyse60 on F8 is ^AG^M. Sounds like
your Wyse 60 client is sending those, but the server isn't seeing them as
the function key sequence.

Are you sure that your logins are getting TERM properly set to wyse60?
Easy way to check: log on to an account that will give you a shell (root
if you have to), type in "set", and look for the "TERM=" line. If it
isn't set to wyse60, there's your problem. If it is, then you have to
examine either your termcap or termlib (depending on your application,
you may even have a custom version of those) and see if the file agrees
on the definition of the function keys.

   [or printenv in csh]

 //////////////////////////////////////////////////////////////////////////////

Newsgroups: comp.terminals,comp.unix.shell
Followup-To: comp.unix.misc
Message-ID: <4eb1vbINNlba@duncan.cs.utk.edu>
References: <slrn4gbrhf.en.wsantee@wsantee.oz.net>
Keywords: termcap, Wyse, Link, terminal, key
Summary: you really need to check env vars (term)
Date: 26 Jan 1996 12:11:07 -0500
From: shuford%cs.utk.edu (Richard Shuford)
Subject: Re: How do I reprogram arrow keys on Link MC2 (in wyse50 mode)?

In article <slrn4gbrhf.en.wsantee@wsantee.oz.net>,
 wsantee@wsantee.oz.net (Wes Santee) writes:
>
> I've got a Link MC2 (with no documentation) in its default mode
> (which the Link Tech. Support rep said is wyse50 compatible).  The
> arrow keys are currently set to:
>
>   ^K
> ^H  ^L
>   \n
>
> which isn't exactly what I'm looking for.

Why would you look for something else?  That is that the arrow keys
of a Wyse 50 terminal send.

> Does anybody know what
> the correct escape sequence (or term setup sequence) is to have
> these keys move the cursor around instead of what they do now?

Those codes are the correct codes for the terminal to send to the
host, assuming that the host computer knows that it is supposed to
be talking to a Wyse 50.

In a full-duplex communication link (which is almost always what you
use with Unix), if the cursor moves around after you hit a key, it is
because the host computer sent something back to the terminal after it
detected the pressing of the arrow key.  The arrow key does NOT have a
direct link to the display screen.


> Right now whenver I hit the up arrow key on accident, it erases a
> line in Emacs! :(
>
> I tried changing the functions kd, kl, kr, and ku in the termcap
> entries to no avail because I don't know what to replace them with.

It appears that you are not correctly informing the Unix host computer
which termcap entry to use.  

Look to your environment variable TERM and your shell variable "term".
(I don't know what your system does, but many Unixes automatically sync
these two....)

You may be interested to know that the helpful O'Reilly and Associates
book "termcap & terminfo" by Strang, Mui, and O'Reilly uses the Wyse
50 for most of its examples.  ISBN  0-937175-22-6  $22.00 (US).  It
contains good advice on this sort of problem.


> I can also reprogram the terminal keys themselves, but I don't know
> what to set them to.  Any help appreciated.

If you want Wyse 50 mode, you don't want to do that.

 ..............................................................................

You can visit Link Technologies on the World Wide Web at this URL:

    http://www.batnet.com/linktech/   [Does this still work? Nope. It's a 404.]

and visit O'Reilly

    http://www.oreilly.com/
-- 
 ...Richard S. Shuford 

 //////////////////////////////////////////////////////////////////////////////

Newsgroups: comp.terminals
Message-ID: <aqf355$9g23p$1@ID-94599.news.dfncis.de>
Date: Fri, 8 Nov 2002 02:12:37 +0100
From: Christian Martin <sporranshieldedREMOVE-THIS@gmx.de>
Subject: substitute WYSE120 with AXEL PLATINE

Hi NG,

I have a _server_ to which are three wyse terminals, one dorio terminal and
one axel platine terminal are connected. now i bought one more axel platine
and tested it at the other axel´s place. work fine with _prolog 2/3_
emulation. when I replaced one of the wyses with the axel all I could see
was _bad_.

as I´m a newbie for that, I can´t check, at which emulation the wyse was
set, so I don´t know how to set the axel. Could you please help me on this?
The _ server_ is a Win2k, the mean application, which sets IMHO the
parameters for the terminals (?) is MediStar, a german program for medicine
doctors.

THX
Christian

 //////////////////////////////////////////////////////////////////////////////

Newsgroups: comp.terminals
Message-ID: <areq79$hqn7l$1@ID-94599.news.dfncis.de>
Date: Wed, 20 Nov 2002 02:56:59 +0100
From: Christian Martin <sporranshieldedREMOVE-THIS@gmx.de>
Subject: Re: substitute WYSE120 with AXEL PLATINE

As I found the solution, I post it for the great google archive :-)

not the emulation was the problem, but the configuration of the _server_
as i guessed. edit the file c:\windir\system32\sysconfig.s
from

COM4-1 = TERMINAL(WYSE120) BAUD(38400) TASK(15) LPT(SP0)
TITLE(Anmeldung_rechts) START(PW)
COM4-2 = TERMINAL(WYSE120) BAUD(38400) TASK(16) LPT(SP0)
TITLE(Anmeldung_rechts) START(PW)
COM4-3 = TERMINAL(WYSE120) BAUD(38400) TASK(17) LPT(SP0)
TITLE(Anmeldung_rechts) START(PW)
COM4-4 = TERMINAL(WYSE120) BAUD(38400) TASK(18) LPT(SP0)
TITLE(Anmeldung_rechts) START(PW)

to

COM4-1 = TERMINAL(AXEL) BAUD(38400) TASK(15) LPT(SP0)
TITLE(Anmeldung_rechts) START(PW)
COM4-2 = TERMINAL(AXEL) BAUD(38400) TASK(16) LPT(SP0)
TITLE(Anmeldung_rechts) START(PW)
COM4-3 = TERMINAL(AXEL) BAUD(38400) TASK(17) LPT(SP0)
TITLE(Anmeldung_rechts) START(PW)
COM4-4 = TERMINAL(AXEL) BAUD(38400) TASK(18) LPT(SP0)
TITLE(Anmeldung_rechts) START(PW)

If not already done start the driver for the terminal. the following german
text tells how and was written by Dirk Bräuniger on 1.2.96 in the document
AXELDOCU.WRI. search for it on your HD, if you use Medistar.

====================================
1. Allgemeine Installationshinweise

Ein Terminaltreiber ist als Dienst unter Windows NT zu installieren. Das
Treiberprogramm muß in das Verzeichnis %SystemRoot%\system32 kopiert werden.
Anschließend muß in einer speziellen Datenbank des Betriebssystems (genannt:
REGISTRY) die komplette Pfadangabe für das Treiberprogramm und ein
(theoretisch) frei wählbarer Name dazu eingetragen werden. Hierfür sollte
das von MediStar mitgelieferte Programm "SIAR.EXE" benutzt werden (d.h.
"service install and remove").

Beipiel für das Terminal Wyse 120:

Starten Sie bitte zu diesem Zweck die Eingabeaufforderung (MS-DOS
Kommandoebene).

Geben Sie folgendes ein:

siar "Wyse 120" %SystemRoot%\system32\wyse120.exe

Jetzt ist der Dienst (=Treiber) dem Betriebssystem bekannt. Mit den
Betriebsystemkommandos 'net start' und 'net stop' können Sie den Dienst
starten bzw. stoppen. Diese Kommandos beziehen sich immer auf den Namen des
Dienstes, nicht den Dateinamen des Treiberprogramms! Wenn der Name eines
Dienstes aus mehreren Wörtern besteht, muß er mit Anführungszeichen
eingegeben werden, siehe Beispiel:

net start "Wyse 120"
net stop "Wyse 120"

Der Dienst könnte bei Bedarf mit dem Kommando:

siar "Wyse 120" remove

wieder aus der REGISTRY-Tabelle des Betriebssystems entfernt werden.
Danach kann er nicht mehr gestartet werden.

Das Starten und Stoppen des Terminaldienstes kann natürlich auch alternativ
vom Desktop mit Hilfe des Control-Panels durchgeführt werden.

Wichtiger Hinweis:

An dieser Stelle sei noch einmal darauf hingewiesen, daß in der MediStar
Konfigurationsdatei "sysconf.s" der Name der Terminaltreiberdatei ohne
Extension ".EXE" für den Eintrag

com2-1 = terminal(wyse120) task(0) ... usw.

verwendet werden muß (und NICHT der symbolische Name des Dienstes, wie in
unserem Beispiel "Wyse 120").

?Namen der Treiberprogramme:

   WYSE60MF.EXE    (Terminal Wyse 60)
   WYSE60P.EXE     (Terminal Wyse 60 mit Prologue-Firmware)
   WYSE120.EXE     (Terminal Wyse 120)
   WYSE160.EXE     (Terminal Wyse 160)
   SN97801.EXE     (Siemens, Tastatur: PC-X, Schnittstelle: V.24)
   SN97801X.EXE    (Siemens, Tastatur: PC-X, Schnittstelle: SS97)
   MSTM.EXE        (DOS-PC mit MSTERM, Monochrom, Graustufen)
   MSTC.EXE        (DOS-PC mit MSTERM, Farbe EGA/VGA)
   WYSE325.EXE     (Terminal Wyse 325)
   VT510.EXE       (Terminal DEC VT 510)
   AXEL.EXE        (Axel Platine)
   F5420.EXE       (Terminal Falco 5420 und 5420/MP mit VT-Tastatur)
   F5220.EXE       (Terminal Falco 5220 mit VT-Tastatur)
===========================================================

Thanks, Dirk!

-- 
Christian

 //////////////////////////////////////////////////////////////////////////////

Newsgroups: comp.terminals
References: <qjHga.58357$Ty5.3798308@news0.telusplanet.net>
Message-ID: <3E845264.3F23A74E@taftpark.com>
Organization: Taft Park Data Co.
Date: Fri, 28 Mar 2003 13:47:20 GMT
From: Barry O. Andalman <news@taftpark.com>
Subject: Re: Troublshooting Wyse 150, font trouble???

Jeff Pratt wrote:
>
> Hello All,
>
> I've come accross a strange problem with one of my wy-150's.  The terminal
> powers on, no keyboard trouble, sends and receives data, the display is
> suitably bright, the "info bar" accross the top displays fine.
>
> BUT
>
> The setup screens do not highlight the cursor, and nothing from the remote
> machine displays.  If I edit a file on the remote machine, it works fine!
> I can open that file on another terminal a read it.  No odd characters etc.
> I just can't see what I'm typing as I type it.
>
> I'm flabbergasted.  Right now I'm thinking it MIGHT be the font bitmap in
> ROM corrupted somehow, but then I should have trouble with setup and the
> info line as well.
>
> I've googled all over and didn't find anything.
>
> any suggestions?  Please?
>
> Jeff


Sounds like a problem with full intensity / half intensity -- one displays but
not the other.

If the half intensity doesn't display because of hardware issues (turned down
all the way or just plain "broken" at the the board level), I could conceive of
getting the results you just described.


 //////////////////////////////////////////////////////////////////////////////

Newsgroups: comp.terminals, comp.dcom.sys.cisco, alt.os.citrix
Message-ID: <83ed3ab8.0304221059.46858b6f@posting.google.com>
References: <83ed3ab8.0304081255.10e35440@posting.google.com>
    <Xns9358E43FA643Fmap428hotmailcom@63.240.76.16>
Date: 22 Apr 2003 11:59:16 -0700
From: Michael Richardson <wolfrium@hotmail.com>
Subject: Re: DHCP failure Wyse term

Adam <nospam@hotmail.com> wrote in message
news:<Xns9358E43FA643Fmap428hotmailcom@63.240.76.16>...
>
> We had a problem with Wyse terminals and DHCP, but in a different way.  
> We have an NT 4.0 DHCP server with Wyse terminals in the same subnet.  We 
> found that the Winterms were completely taking IP's that DHCP already had 
> assigned to PC based clients.  This caused us several days of IP 
> conflicts, until we started assigning static addresses to our Wyse 
> terminals.  One variation you could try, is to have the router configured 
> with IP-Helper, that forwards DHCP broadcasts to a true DHCP server 
> instead of having the router serving DHCP.
> Adam
> 

Thanks,

We've been thinking about that, but we were planning to have all the
servers for this company hosted externally (similar to SunGard). 
Doing this will require we leave one server here to handle DHCP.  Wyse
has been ABSOLUTELY no help on this issue, so it looks like we'll have
to do it that way.

-Michael

 //////////////////////////////////////////////////////////////////////////////

Tony Lawrence wrote about his experience in 1999 with a new
Wyse Winterm 5000 Network Terminal:

    http://www.aplawrence.com/Reviews/wt5.1.html

 //////////////////////////////////////////////////////////////////////////////

Newsgroups: comp.terminals, comp.dcom.sys.cisco, alt.os.citrix
Message-ID: <32551130.0304231019.57e26aa1@posting.google.com>
References: <83ed3ab8.0304081255.10e35440@posting.google.com>
    <Xns9358E43FA643Fmap428hotmailcom@63.240.76.16>
    <83ed3ab8.0304221059.46858b6f@posting.google.com>
Date: 23 Apr 2003 11:19:58 -0700
From: Jim Kirby <jdkirby@bluebunny.com>
Subject: Re: DHCP failure Wyse term

Easy fix.  Chances are you need to enforce RFC 1048 style DHCP
responses or the Wyse terminals won't recognize the offer.  This is
true for most BOOTP devices I've encountered and some DHCP capable
devices.

With ISC's DHCP server you do this with the option: 

always-reply-rfc1048 on;

I don't know how to enforce this with a Cisco router; does anyone else?

jk

 //////////////////////////////////////////////////////////////////////////////

Newsgroups: comp.terminals
Message-ID: <f75149d7.0305210253.166248e2@posting.google.com>
Date: 21 May 2003 03:53:36 -0700
From: Andrew McGregor <Andrew.McGregor@amtrak.co.uk>
Subject: wyse 60 software configuration

hi,

is it possible to configure a wyse 60 with software through the aux or
modem port instead of pressing shift select on the keyboard?

the scenario is, we have a wyse 60 with a 2d barcode reader.  every
now and again during scanning the personality changes from wy60 to
vt100.

regards

andy

 ..............................................................................

Newsgroups: comp.terminals
Message-ID: <3ecc9d28@news.leadingedgeinternet.net.au>
References: <f75149d7.0305210253.166248e2@posting.google.com>
Organization: Ihug Limited
Date: Thu, 22 May 2003 19:49:18 +1000
From: Kieran Murphy <news@repertoire.com.au>
Subject: Re: wyse 60 software configuration

According to the manual the following applies:

   Change to WY-50+ mode send...        ESC~"

   Change to VT100 mode send...         ESC~;

I have never tried it, but am a mad collector of old terminal manuals
for just this type of need.  I hope it works.

 ..............................................................................

Newsgroups: comp.terminals
Message-ID: <f75149d7.0305230147.26b0b69d@posting.google.com>
References: <f75149d7.0305210253.166248e2@posting.google.com>
    <3ecc9d28@news.leadingedgeinternet.net.au>
Date: 23 May 2003 02:47:53 -0700
From: Andrew McGregor <Andrew.McGregor@amtrak.co.uk>
Subject: Re: wyse 60 software configuration

"Kieran Murphy" wrote:
>
>   Change to VT100 mode send...         ESC~;


I think that's it!

`~' is a field delimiter in our pdf417 barcodes.

Thank you!

 //////////////////////////////////////////////////////////////////////////////

[Archiver's Note:
 Discussion of using a serial MICR scanner with a Wyse 60
 terminal appears in another the file here:
 http://www.cs.utk.edu/~shuford/terminal/serial_news.txt
]

 //////////////////////////////////////////////////////////////////////////////

http://www.wyse.com/service/support/kbase/wits/80625.txt

TOPIC:  WY60 CODES NOT SUPPORTED IN WY150 WY160 WY325

DATE:   4-2-93

THE ISSUE:
        WY69 commands not supported on WY150 / 160 / 325.

OVERVIEW:
        WYSE Tech Support has encountered a few ESC codes from the
        original WY60 personality are not supported in the NATIVE
        or WY60 personalities on the WY150, WY160, or WY325. 

RESOLUTION:
        The following is the list of WY-60 native mode commands that
        are not supported in at least one Wyse product in the native
        or "WY-60" personality.   Commands that have additional
        parameters HAVE NOT been compared for completeness across the
        domain of terminals (except ESC G attr).

       CAVEAT:   NO CLAIM IS MADE AS TO THE COMPLETENESS OR ACCURACY 
       OF THIS DATA.  FURTHER, IT IS NOT KNOWN IF THE BEHAVIOR OF ANY
       ESCAPE SEQUENCE IS IDENTICAL IN ALL EMULATION INCARNATIONS.

                 150     160      325 
      ESC G G     n       n        n        Line attr normal BG
      ESC G H     n       n        n        Line attr bold BG
      ESC G I     n       n        n        Line ~ttr inv. BG
      ESC G J     n       n        n        Line attr dim BG
      ESC c O     n       Y        n        Modem params
      ESC c 1     n       Y        n        AUX params
      ESC c 2     n       Y        Y        modem rcv h/s
      ESC c 3     n       Y        n        AUX rcv h/s
      ESC c 4     n       Y        Y        modem xmit h/s
      ESC c 5     n       Y        n        AUX xmit h/s
      ESC c 6     n       Y        Y        max data xmit speed
      ESC c 7     n       Y        Y        max F-key xmit speed
      ESC c 8     n       Y        n        load time of day
      ESC c ;     n       Y        Y        prog answerback
      ESC c <     n       Y        Y        send answerback
      ESC c =     n       Y        Y        conceal answerback
      ESC c F     n       Y        Y        clr unprot rect 80-col
      ESC c G     n       Y        Y        box rect 80-col
      ESC c H     n       Y        Y        clr rect 80-col
      ESC c I     n       Y        Y        clr unpr col to char
      ESC c J     n       Y        Y        delete cursor column
      ESC c R     n       Y        Y        clr unpr col to nulls
      ESC c L     n       Y        Y        clr unpr to EOL w/null
      ESC c M     n       Y        Y        ins col of nulls
      ESC c N     n       Y        Y        box rect to right
      ESC c O     n       Y        n        clr unpr EOL spaces
      ESC c P     n       Y        n        clr unpr pg FG spaces
      ESC C Q     n       Y        n        clr unpr pg FG nulls
      ESC C R     n       Y        n        clr unpr line FG space
      ESC C 5     n       Y        n        clr unpr line FG nulls
      ESC c U     n       Y        Y        clr all prog keys
      ESC d SP    n       Y        Y        secondary rcv off
      ESC d !     n       Y        Y        secondary rcv on

                150     160      325
      ESC d S     n       Y        Y        bi-direction mode off
      ESC d %     n       Y        Y        bi-direction mode on
      ESC e SP    n       Y        Y        ans'back mode off
      ESC e !     n       Y        Y        ans'back mode on
      ESC e "     n       n        n        pg edit off
      ESC e #     n       n        n        pg edit on
      ESC e *     n       Y        Y        42 data lines 
      ESC e +     n       Y        Y        43 data lines
      ESC e 6     n       Y        n        ACK off
      ESC e 7     n       Y        n        ACK on
      ESC e 8     n       Y        n        select modem as host
      ESC e 9     n       Y        n        select aux as host
      ESC e :     n       n        n        don't init tabs
      ESC e ;     n       n        n        do init tabs
      ESC e J     n       n        n        don't save F-key label
      ESC e R     n       n        n        save F-key labels
      ESC e N     n       n        n        auto font load off
      ESC e O     n       n        n        auto font load on
      ESC e T     n       Y        n        CAPS is CAPS LOCK
      ESC e U     n       Y        n        CAPS is REV
      ESC ' H     n       Y        Y        line lock on
      ESC ' I     n       Y        Y        line lock off
      ESC ~ .     n       n        n        wyseword off
      ESC - /     n       n        n        wyseword on
      ESC - 2     n       n        n        appl key mode off
      ESC - 3     n       n        n        appl key mode on
      ESC   4  Various.  Select WY-60 pers., or select "native mode".
      ESC - ~  60:  null suppress off.  120, 160, 325:  VT220/7
      ESC - =  60:  null suppress on.   120, 160, 325:  VT220/8


        Other "WY-60" properties not consistently emulated in Wyse
        products:
                  1.  # display pages
                  2.  Fonts/bank select and character sizes
                  3.  I/O connectors and port types
                  4.  Code space
                  5.  F-key size, space
                  6.  F-key prog. re NVR
                  7.  ANSI 101 keyboard  ( VT100 style )
                  8.  44 row display
                  9.  status line placement and content


 //////////////////////////////////////////////////////////////////////////////

Newsgroups: comp.terminals, comp.sys.net-computer.misc
NNTP-Posting-Host: list.stratagy.com
References: <pan.2003.08.20.18.56.02.938255@sneakemail.com>
Message-ID: <rshu_20030822_154545@stratagy.com>
Organization: The Late, Great Stratagy Users Group
Date: Fri, 22 Aug 2003 15:45:45 -0400
From: Richard S. Shuford <shuford@list.stratagy.REM0VE-THlS-PART.com>
Subject: Re: wyse 520,  reset password

Simon Strandgaard wrote:
::
::  I got my hands on an old WY-520 terminal and want to try
::  it out. Unfortunately the 'setup' menu is password protected.


Wyse documented a complete-reset procedure given for a different
model terminal.  I don't know if it would work, but you could try:

    http://www.wyse.com/service/support/kbase/wits/13205.txt

WY99GT "G-Key" RESET INSTRUCTIONS

Please be sure to reset the terminal after installation of firmware chips as
follows:

1.  Turn the terminal off, and remove the cabling from the Auxiliary and
    Modem ports.

2.  Hold down the "G" key on the terminal keyboard while booting up.  (You
    must keep holding the "G" key down throughout the power up sequence). 
    
3.  Wait for the terminal to finish its screen diagnostic during the power
    up sequence.  You can tell when this is over when you see that the
    screen stops flashing.  The status line may appear after a few seconds.
    
4.  Release the "G" key and go into setup:  (Shift-SetUp.) or (Shift-Select)
    or (F4).

5.  Default all setup parameters by highlighting "DEFAULT ALL":
    (Enter the right arrow key three times) and then the F10 key.
    (Enter F10 again to EXIT or you may change the terminal settings at
    this time.
 
    Occasionally the terminal's personality parameter will "disappear".
    Repeating step 5 several times should correct this.

(The key sequence to get into SETUP will vary depending on the keyboard type.)

 ...RSS

 ..............................................................................

Newsgroups: comp.terminals
NNTP-Posting-Host: 0x50c4101e.boanxx9.adsl-dhcp.tele.dk [80.196.16.30]
References: <pan.2003.08.20.18.56.02.938255@sneakemail.com>
    <rshu_20030822_154545@stratagy.com>
    <pan.2003.08.22.22.07.17.756395@sneakemail.com>
Message-ID: <pan.2003.08.25.13.25.11.619081@sneakemail.com>
Organization: TDC Internet
Date: Mon, 25 Aug 2003 15:25:12 +0200
From: Simon Strandgaard <0bz63fz3m1qt3001@sneakemail.com>
Subject: Re: wyse 520,  reset password

Thanks Richard, the G-Key reset procudure is working great.

--
Simon Strandgaard

 //////////////////////////////////////////////////////////////////////////////

Newsgroups: comp.terminals
NNTP-Posting-Host: 65.92.159.195
NNTP-Posting-Date: Fri, 19 Dec 2003 01:08:06 EST
References: <brqfpq$vdk$03$1@news.t-online.com>
Message-ID: <3FE29590.AD17D57@myownboss.com>
Organization: Bell Sympatico
Date: Fri, 19 Dec 2003 01:07:12 -0500
From: stockwiz <Ffreedom@myownboss.com>
Subject: Re: Wyse 160: adjusting geometry

Matthias Czapla wrote:
>
> Hello!
>
> I have a Wyse WY-160ES terminal, and the image at the bottom and
> the left and right hand sides is bent to the center of the screen.
> It looks like this (heavily exxagerated):
> _____________
> \           /
>  \         /
>   )       (
>  /         \
> /  __---__  \
> --'       `--
>
> Is there a way to correct this, besides sending the device to a repair
> service? I already opened the terminal and found 4 plastic cross-head screws
> on the left and two on the right, but they only adjust vertical size and
> position and horizontal position. Two of them had no visible effect.
>
> I dont have a manual for the terminal but I have asked Wyse for one.
> Wyse hasn't answered yet. Anyone got one for me? :)
>
> Cheers
> lal


On the neck of the CRT tube you should see the yoke with some square
magnets glued to it.  Loosen them and turn each individual magnets to
get the best geometry for the display.


If the process does not improve the geometry you may have to change
the yoke. At least that's how it was done on a Wyse 60. I presume
it should be the same for the model 160.

Good luck.

 //////////////////////////////////////////////////////////////////////////////

	[circa-2005 commentary from 
	 http://aplawrence.com/Unixart/terminals.html
	]

Comments /Unixart/terminals.html
UnixartTerminals :

Well, it is the end of an era. After some 17 years of production, Wyse
Technology has retired the king of ASCII terminals, the venerable WY-60,
officially End-of-Life'd in November 2004.

The WY-60 is an all-time best seller, exceeding the sales of all of the
DEC VT models combined. I can't recall how many 60's I have installed
(and repaired) over the years, but it has to be in excess of a thousand
or so (one installation alone had over 30 of the suckers hooked up to a
SCO UNIX 3.2v4.2 box powered by a single 200 MHz AMD K6 -- it ran plenty
fast for the times). Even as Wyse developed newer models, the WY-60
continued to be the weapon of choice due to its features, easy-on-the-eyes
display, and reliability. In fact it was just before they EOLed the 60
that I sold one to a client who is still processing on terminals.

The funny thing is that even though everyone is enamored with GUI's,
mice, PC's, etc., terminals are still the preferred "human interface
device" in applications where reliability is paramount (e.g., airline
reservations systems). There's little to go wrong in a terminal, and,
once the firmware has been debugged (as was the case with the WY-60 long
ago), the system stability is limited only by the host machine. The
three WY-60's I have here (which are still in use -- I prefer them for
editing source code and performing admin on our UNIX boxes) have been in
service for close to 11 years, two of which still have the original CRT.

Anyhow, time marches on and I imagine a time will come when terminals
will take their place in computer museums alongside Tele-Type machines,
Osborne "luggables" and eight inch floppy drives. So, as the old saying
goes, the king is dead. Long live the king!

--BigDumbDinosaur 

 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 

Mon Apr 18 14:18:25 2005 Wyse 60 Emulation  richlove ( key XogXwUtZn)

Wyse 60 emulation is still popular with my clients using MacWise.
http://www.macwise.com/

 //////////////////////////////////////////////////////////////////////////////

