home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.msdos.misc
- Path: sparky!uunet!stanford.edu!rock!taco!dspascha
- From: dspascha@eos.ncsu.edu (DAVID SCOTT PASCHAL)
- Subject: Re: Any good VT emulators out there?
- Message-ID: <1992Sep4.011624.5569@ncsu.edu>
- Originator: dspascha@c00131-100lez.eos.ncsu.edu
- Lines: 45
- Sender: news@ncsu.edu (USENET News System)
- Reply-To: dspascha@eos.ncsu.edu (DAVID SCOTT PASCHAL)
- Organization: North Carolina State University, Project Eos
- Date: Fri, 4 Sep 1992 01:16:24 GMT
-
-
- In article <1992Sep3.163105.28212@vela.acs.oakland.edu>, w8sdz@tacom-emh1.army.mil (Keith Petersen) writes:
- |>
- |> sci240s@monu6.cc.monash.edu.au (Wey Jing HO) writes:
- |> >Can anyone recommend a good VT emulator for use to communicate with
- |> >Unix mainframe via modem? Doesn't matter whether it is PD/Shareware/
- |> >Commercial as long as it is good. Also, doesn't matter the OS; can be
- |> >MS-DOS, Windows 3.x, OS/2 or even SCO Unix.
- |> >
- |> >Is there any reasonable VT-220 emulator for PC running MS-DOS to hook
- |> >up to an ICL Unix x86 box? (This is a separate question)
- |>
- |> MS-Kermit does excellent VT102/VT220/VT320 emulation.
- |>
- |> WSMR-SIMTEL20.ARMY.MIL directory PD1:<MSDOS.KERMIT>
- |> Filename Type Length Date Description
- |> ==============================================
- |> MSKER311.ZIP B 186841 911001 MS-Kermit v3.11 comm pgm for IBM-compatibles
- |>
-
- [..]
-
- |>
- |> Keith
- |> --
- |> Keith Petersen
- |> Maintainer of the MS-DOS archive at WSMR-SIMTEL20.Army.Mil [192.88.110.20]
- |> Internet: w8sdz@TACOM-EMH1.Army.Mil or w8sdz@vela.acs.oakland.edu
- |> Uucp: uunet!umich!vela!w8sdz BITNET: w8sdz@OAKLAND
- |>
-
- Hi. I've had a bit of trouble with Kermit 3.x with respect to VT emulation.
- Specifically, when I log into a certain VAX, after it says when my last
- interactive and non-interactive logins were, I get a string of at least 50
- linefeeds or something. This doesn't happen with previous versions of Kermit
- or any other emulator (Windows terminal, Pathworks SETHOST, etc.). I think it
- may be a problem with the VAX's trying to autodetect the terminal type. Also,
- the TPU editor isn't happy unless I say SET TERM/DEV=VT100 -- otherwise, I get
- a lot of garbage on the screen and messages saying "invalid escape sequence."
- Has anybody else had this problem? Perhaps it's something wrong with our
- (not NCSU's) VAX auto login sequence, or maybe this version of KERMIT mentioned
- above fixes this bug.
-
- Tschuess,
- David Paschal
-