Xref: utzoo comp.protocols.tcp-ip.ibmpc:3598 comp.protocols.tcp-ip:12639 comp.dcom.lans:5716 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!naitc!karl From: karl@naitc.uucp (Karl Denninger) Newsgroups: comp.protocols.tcp-ip.ibmpc,comp.protocols.tcp-ip,comp.dcom.lans Subject: PC/NFS and Packet Drivers, Alternate Telnet's Summary: PC/NFS & Packet drivers work, but we need NCSA Telnet too! Message-ID: <1990Aug22.185901.23007@naitc.uucp> Date: 22 Aug 90 18:59:01 GMT Reply-To: karl@naitc.naitc.com (Karl Denninger) Organization: A.C. Nielsen Bannockburn, IL Lines: 26 Well, we're getting there. I have PC/NFS working with the Clarkson packet drivers. I have NCSA Telnet working with same (all the way to 2.3b8). That's fine. What isn't fine is that I can't manage coexistance. I have tried the NCSA version from Clarkson that is supposed to work with PC/NFS, and all I get is a hung session when I connect (it does initialize properly). Curiously enough, I can hit M a few times and get on, but it appears that no processing is taking place until I go away from the display screen! Needless to say, this is a real bummer. Does anyone have any ideas for coexistance on these? I'd really like to be able to use NCSA Telnet and PC/NFS simultaneously, 'cause the Telnet that Sun supplies with PC/NFS stinks to high heaven, and some of our users really want things like the Tek mode and 3270 capability.... Ideas or further suggestions solicited. -- Karl Denninger AC Nielsen kdenning@ksun.naitc.com (708) 317-3285 Disclaimer: Contents represent opinions of the author; I do not speak for AC Nielsen on Usenet.