11 Apr
2011
11 Apr
'11
1:23 p.m.
On Mon, Apr 11, 2011 at 3:57 PM, Rich Alderson <RichA at vulcan.com> wrote:
A *good* VT100 emulator should do VT52 emulation (it's fully described
in the relevant documentation). The problem is that there are few
*good* VT100 emulators. As I've mentioned on the list before, my
threshold for VT52 emulation is successfully running the VTEDIT Macro
on the OS/8 version of TECO (it works perfectly on a real VT52).
Besides 'vttest', my threshold for VT100 emulation is successfully
running emacs on TOPS-20 (I had some issues a few years back with
almost-emulation that vanished when I used a real terminal to drive
sessions on the "Panda" distro of klh10+TOPS-20 - I don't recall why I
couldn't/didn't use Kermit, but it probably has to do with being in a
sunless place for months at a time).
-ethan
From: Ethan Dicks
Another edge-case where there are few alternatives.
Indeed. ?Kermit-12 is quite handy.
We also use Kermit-10 on the 2065 to provide file transfer capabilities,
since we do not have TCP/IP for Tops-10 (nor a Tops-10 driver for the
Stanford MEIS[1] even if we did). Other than
that, I tend to use Kermit more often as a VT100 emulator
than a file-transfer application.
In addition, I use Kermit 95 for *VT52* emulation (VT100 emulators are
a dime a dozen, but try to find a VT52 emulator!) for connecting to the
ITS system we're restoring.[2]