<< Previous Message Main Index Next Message >>
<< Previous Message in Thread This Month Next Message in Thread >>
Date   : Tue, 06 Jun 1989 08:05:00 EDT
From   : "Gary Hutchison" <GHK%NCCIBM1.BITNET@CORNELLC.cit.cornell.edu>
Subject: Remote computing terminals

       Charles West asks...

> I have found qterm as an excellent vt-100 emulator with a few except ions.
> UALR is on a vax,  phone and help use some other form of screen call s
> and will not work with the vt100 in qterm, yet kermit vt52 will any  suggesti
> Charles West
> CHWEST@UALR.BITNET

Many of the VAX system these days expect support of the double width
and double height characters available in later versions of DEC's
terminals without reguard for the user that has older equipment.  Many
of the older VT100 emulators as well as REAL VT100 s will NOT support
the enhanced character sets.  This leaves many users rs in the cold.

I think that supporters of remote access systems need to be more
conscious of the user comunity and stop putting fancy frills on their
system.  Frills are nice when you can afford them but with lower baud
rates and remote terminals being everything from Atari's to IP sites
the remote user community cannot survive with ANSI overhead driving
2400 baud down to 1200 baud screen update e times if users can support
ANSI at all.

Sorry, I kinda got off the track, but in my 10 years of remote
computing experience I have seen systems go from helping the users to
severly handicapping the users.

Back to the original point: many of the comm programs such as IMP,
ZMP, M740, MEX and Kermit rely on the users terminal equipment to be
defined to the BIOS.  Some such as Kermit will play tricks by knowing
the terminal type you are and simulate VT52 or Z-19 term commands.
However, it is usually best, if possible, to use your built in
terminal (BIOS defined if not physical).

        Thanks for listinin'
          Gary Hutchison
          GHK@NCCIBM1



<< Previous Message Main Index Next Message >>
<< Previous Message in Thread This Month Next Message in Thread >>