Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!ames!ncar!gatech!rutgers!dorm.rutgers.edu!medici From: medici@dorm.rutgers.edu (Mark Medici) Newsgroups: comp.protocols.tcp-ip.ibmpc Subject: Re: Windows and NCSA Telnet - unholy marrriage? Message-ID: Date: 26 Nov 90 19:32:10 GMT References: <1990Nov23.223831.10209@fiver> <1990Nov26.150244.437@engin.umich.edu> Organization: Rutgers Univ., New Brunswick, N.J. Lines: 23 jal@acc.flint.umich.edu (John Lauro) writes: |In article <1990Nov23.223831.10209@fiver> palowoda@fiver (Bob Palowoda) writes: |> Forget it. Use WinQVT NET with Windows 3.0. You can have several |>telnet sessions each with there own window. Emulates vt200 terms. Works |>with packet drivers. And you can have ftp sessions going simultanous. | |I never head of this package before. Is it available via anonymous |FTP anywhere? Try cica.cica.indiana.edu <129.79.20.22>. That's where I found it last week. WinQVTnet does work, though it is a little rough. Since your already running NCSA, I assume you have properly installed packet drivers. The only other setup is a small TSR loaded before Windows, and set-up of a host table in the WinQVTnet config file. WinQVT does not seem to support domain name resolution, so plan to spend some time manually typing the host and ip assignments for each system you want to access. -- ---------------------------------------------------------------------------- Mark Medici/SysProg3 * Rutgers University/CCIS * medici@elbereth.rutgers.edu ----------------------------------------------------------------------------