Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!ucsd!ucbvax!BERRY.RRZ.UNI-KOELN.DE!a0045
From: a0045@BERRY.RRZ.UNI-KOELN.DE (Jochen Roderburg)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Windows and NCSA Telnet - unholy marrriage?
Message-ID: <9011270933.AA109888@berry.rrz.Uni-Koeln.DE>
Date: 27 Nov 90 09:33:08 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 26

>>	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.

 In my first tests with WINQVTNET I found that it *does* support 
 domain name servers, but wants every host listed in its config file.

 What it doesn't: no RARP, doesn't work with FTP's NDIS-to-packet-converter,
 so it looks like is it based on some older TCP/IP kernel.
 And, like all the QVT Windows programs before, it doesn't like my
 german keyboard. 

 So I think it is an interesting and promising program, but needs some
 polishing before it's really usable.

 Jochen Roderburg
Regional Computing Center
University of Cologne
Robert-Koch-Str. 10                    Tel.:     +49-221/470-4564
D-5000 Koeln 41                        Internet: Ro @ RRZ.Uni-Koeln.DE
(Reunited) Germany                     BITNET:   A0045 @ DK0RRZK1