[comp.unix.i386] Using Wyse-150 Terminals ??

howardl@wb3ffv.ampr.org ( WB3FFV) (01/03/90)

    Hello All,

I am wondering if anybody has tried using the Wyse-150 terminals under 
UNIX or Xenix ??  They look like nice terminals, and claim to have DOS
compatibility.  I am very interested in hearing how they work under VP/IP
as this is a concern of many customers.  Please Email or reply to comp.unix.
i386, as I read it daily...

If anybody has any termcap or terminfo files for the Wyse-150 I would very
much appreicate if you would mail me a copy!

-------------------------------------------------------------------------------
Internet  : howardl@wb3ffv.ampr.org	|	Howard D. Leadmon
UUCP      : wb3ffv!howardl		|	Fast Computer Service, Inc.
TELEX     : 152252474     		|	P. O. Box 171 
Telephone : (301)-335-2206		|	Chase, MD  21027-0171

campbell@Thalatta.COM (Bill Campbell) (01/07/90)

In article <2210@wb3ffv.ampr.org> howardl@wb3ffv.ampr.org ( WB3FFV) writes:
>
>    Hello All,
>
>I am wondering if anybody has tried using the Wyse-150 terminals under 
>UNIX or Xenix ??  They look like nice terminals, and claim to have DOS

I have tried the Wyse-150 extensively under SCO Xenix 386 and found them
better than a Wyse-60 or most other terminals for several reasons:
	1.	Better print-through in VT100 modes (it doesn't pass-through
		the printer-off codes through to the printer).
	2.	Passed all 8-bits through to the printer.
	3.	Standard Parallel printer port.

We use terminals on Point-of-Sale and accounting systems where we
print using the terminal's printer port.  Most terminals using
the TVI/Wyse50/Wyse60 (i.e. non-ansi) emulations have codes that
conflict with printer control information (^R is used for print
size control on many OKIDATA printers).  Many terminals aren't
smart enough when transparent printing to look-ahead far enough
to catch the printer-off codes in ansi emulations before they go
to the printer.  This results in 4i's throughout your printout
making the terminals useless with the multiplexing printer
drivers supplied on ARNET, computone, ... intelligent boards.

The Wyse-150 seems to work well in the native (almost wy60) mode,
but I have had some problems:
	1.	(vt100) The protected field attributes don't work so you cannot
		clear unprotected fields quickly.
	2.	With the 101-key board you cannot always get codes from
		the keys above the arrow keys.  Since there are no
		function keys above the keypad I like to use these keys
		as synonyms for function keys so the operator doesn't
		have to use two hands for data entry.

We were going to use wyse-150's as our standard terminal in spite
of these problems until we tried the LINK-MC5.  The mc5 seems to
be a much better terminal than the wy150 and they are about the
same price (Link is owned by Wyse).
	1.	Two serial ports and a standard parallel printer port (PC
		standard cable).  The data communications parameters are
		independent on each port and you can use the terminal on
		two separate ports and hot-key between the applications.
	2.	Many more emulations (vt320..., vt220, vt100, wy60...).
	3.	Better customer support.
	4.	The auxiliary keys above the arrows on the 101-keyboard
		all send codes in all the emulations we have tried.

We have found some bugs in the current (2.03) firmware on the mc5
including:
	1.	Remote printing doesn't work in VT220-7 emulation, but
		sends the printer output back down the active serial port :-).
	2.	The auxiliary port only seems to work with xon-xoff
		handshaking even though DTR is selected.
	3.	Software selection of the wy60 mode resets all the
		communications handshaking to xon-xoff overriding the
		setup.

These are being fixed in the 2.04 firmware to be released in the
next week or so.

Both these terminals have a PC-term mode and work with VP/IX at
least as I have been willing to mess with this mode.

Disclaimer:
	Celestial Software has no affiliation with any of the
	manufacturers mentioned above.
-- 
....microsoft--\					Bill Campbell; Celestial Software
...uw-beaver-----!thebes!camco!bill	6641 East Mercer Way
....fluke------/					Mercer Island, Wa 98040
....hplsla----/						(206) 232-4164

macy@fmsystm.UUCP (Macy Hallock) (01/09/90)

In article <2546@thebes.Thalatta.COM> campbell@Thalatta.COM (Bill Campbell) writes:
>In article <2210@wb3ffv.ampr.org> howardl@wb3ffv.ampr.org ( WB3FFV) writes:

[...discussion of WY-150 terminals and use of Link MC-5 terminals as
 a better alternative ommitted...]

We used WY-60 terminals here and tried the Link MC-3 as well.  Neither
terminal was perfect...

The primary problem with the WY-60 was reliability.  That's why we are
reluctant to commit to the WY-150, which seems to run OK.

The Link MC-3 had a couple of problems of its own:
	- no 101 key style AT keyboard, just a RT style 101 keyboard
	  with the functions keys in groups of file at the top, rather
	  than in groups of four like AT 101 style.  Our users bitched
	  a fit about this.  Not bad once you get used to it, though.
	- a tendency to lose the setup info stored in NVRAM.  We
	  originally thought this to be static related, but its not.
	  This is our most serious technical problem.

The MC-3 has a three year warranty, which was reassuring to us after the
WY-60 problems.  We haven't yet had to send back a Link MC-3 for repair
except for the setup loss problem mentioned above.  We still have no
solution for this problem, even though its very intermittent and you can
go months with no problems and then...

We have not tried the MC-5 yet, but we are thinking about it.
It does not have a three year warranty, though :(

Anyone know anything more about the MC-3 problem here?

 Macy M. Hallock, Jr.     macy@NCoast.ORG         uunet!aablue!fmsystm!macy
  F M Systems, Inc.      {uunet!backbone}!cwjcc.cwru.edu!ncoast!fmsystm!macy
 150 Highland Drive      Voice: +1 216 723-3000 Ext 251  Fax: +1 216 723-3223
Medina, Ohio 44256 USA   Cleveland:273-3000 Akron:239-4994 (Dial 251 at tone)
(Insert favorite disclaimer here)   (What if I gave a .sig and nobody cared?)