~terry
Wed, Jul 24, 1996 (13:22)
seed
Conference Categories | Apps Conference | Terminal Apps Topics
QVT/Term -- The telnet client has always been the best application
of the WinQVT (QVT/Net) 'net suite. Finally, this app has been
released as a standalone client and is immediately a quick and easy
recommendation for anyone looking for an inexpensive, solid telnet
client. Both 16-bit and 32-bit versions of QVT/Term are currently
available. Features include DEC VT-220 emulation, file transfer
support (using the Kermit protocol and in the near future Zmodem
as well), extensive configuration settings, automatic saving of these
config settings, file and screen logging, sufficient on-line help, and
printing capabilities. QVT/Term also works well as a web browser
helper application. While lacking some of the features found in its
competitors, including CRT and NetTerm's Zmodem file transfer
support, EWAN's freeware status, CRT's SOCKS support, and
NetTerm's scripting and address book capabilities, QVT/Term is a
strong application that performs with ease and efficiency.
Pros: Kermit transfer support, send/receive files in a telnet session,
efficient and easy to use
Cons: Expensive relative to EWAN, lacks some features found in
the competition
New: 32-bit version released, several
New options, bug fixes
Version Reviewed: 4.0.5
Date of Review: 5/24/96 Reviewer: Forrest Stroud
Location: ftp://biocserver.bioc.cwru.edu/pub/windows/qvtnet/term32.zip
~claese
Fri, Sep 6, 1996 (17:30)
#1
For talking to VAXen, this has got to be the best telnet client yet. It does a perfect emulation of a VT220 in 8-bit mode, including national characters. The keypad is mapped to the VT200 as you would expect it to be. The only thing I haven't yet figure out, is where the "Compose character" key is hiding. I bet it's in here somewhere... :-)
~musicattriumf
Wed, Apr 30, 1997 (17:42)
#2
Can you get it to do doublehigh and doublewide characters??
.. FWB music@triumf.ca
~davidsadler
Fri, Aug 22, 1997 (10:04)
#3
Our site is a user of QVT net (150 users). Our host machine is an IBM RS6000. We are experiencing problems in that when users close sessions or qvt crashes etc rogue processes are left running on the RS6000. We then have to kill the process, which we believe in certain circumstances is causing file corruption.
Is there anyway we can make QVT more user proof. ie no close off unless session is cleanly exited by a logout