banner@einstein ( infotech) (04/18/91)
After reading all the good comments about the Clarkson Packet drivers and NCSA telnet I downloaded them. The packet drivers run fine but I am having difficulty getting NCSA Telnet to work properly with them. Can some kind soul mail me the pertinent parts of their config.tel for NCSA Telnet 2.3b9 that they use to run PCNFS, NCSA Telnet and the Clarkson drivers together? Although I have the "hardware=packet" line in my config.tel, I continue to get this error: Can't access IP handle interface type 1 Packet Driver probably not loaded Packet Access Type Error 10 But I know that the packet drivers are loaded, and seem to be working just fine with PCNFS. My goal is to run PCNFS and use NCSA telnet instead of PCNFS telnet. Is this possible?? Tanks in advance, -- ======================================================================== Ross Bannerman | Usenet: banner@mitel.com MITEL Corp. Kanata, Ont. | ========================================================================
nelson@sun.soe.clarkson.edu (Russ Nelson) (04/19/91)
In article <7474@einstein> banner@einstein ( infotech) writes:
Although I have the "hardware=packet" line in my config.tel, I
continue to get this error:
Try commenting out all hardware-related parameters (ioaddr, membase,
interrupt, etc).
My goal is to run PCNFS and use NCSA telnet instead of PCNFS
telnet. Is this possible??
Sigh. No. You would be running two TCP/IP stacks at the same time.
That just won't work. You need to run the version of CUTCP that uses
PC-NFS's TCP/IP stack. It's somewhere on omnigate.clarkson.edu, I
don't know exactly where...
--
--russ <nelson@clutx.clarkson.edu> I'm proud to be a humble Quaker.
It's better to get mugged than to live a life of fear -- Freeman Dyson
I joined the League for Programming Freedom, and I hope you'll join too.ted@arsocomvax.socom.mil (Ted Nolan) (04/19/91)
This has come up before, and packet drivers are sort of a red herring in that they obscure what you really need. The two issues involved (Running PC-NFS with packet drivers, and running Clarkson's modified NCSA telnet on PC-NFS) are really separate. It is difficult (though possible) to run the packet driver version of the Clarkson cutcp telnet with PC-NFS, since both telnet and PC-NFS (even with the packet driver interface) both want all the packets. What is (easily) possible is to run the version of cutcp telnet which was built with the PC-NFS toolkit, and uses PC-NFS to do it's network i/o. This version will use whatever ethernet driver PC-NFS uses, whether it is the packet driver driver or not. The toolkit version of telnet was v2.2-A and is available on omnigate.clarkson.edu in pub/cutcp/v2.2-A/pc-nfs.cutcp.zoo. There is a bug in the tn3270 provided in that "auto skip fields" do not work properly, but we have been using the vanilla telnet with general success. Ted Nolan ted@usasoc.soc.mil