Xref: utzoo comp.protocols.tcp-ip.ibmpc:3451 comp.protocols.nfs:1139
Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!know!zaphod.mps.ohio-state.edu!samsung!munnari.oz.au!bruce!gdwb.oz.au
From: was@gdwb.oz.au (Warren Stokes)
Newsgroups: comp.protocols.tcp-ip.ibmpc,comp.protocols.nfs
Subject: NCSA Telnet, PC-NFS and Packet Drivers
Message-ID: <419@rome.gdwb.oz.au>
Date: 30 Jul 90 23:24:55 GMT
Sender: was@gdwb.oz.au
Followup-To: comp.protocols.tcp-ip.ibmpc
Organization: Geelong & District Water Board, Australia
Lines: 49

I am using PC-NFS 3.0.1 with a 3C503 board using the packet driver
"glue" PKTD.SYS out of compat.tar.Z from clarkson.  I changed the
jumpers on the board to use shared memory and installed the packet
driver 3C503.COM from drivers.  PC-NFS works just fine.  However,
NCSA telnet works but is hanging PC-NFS after exitting from telnet.
I have set CONFIG.TEL to use the hardware option of 3C503.  This
implies it is using the hardware directly and leaving it in a funny
state.

The other option in CONFIG.TEL is to specify hardware=packet.
I get the following messages:


	NCSA Telnet 2.3b8, reading configuration file . . .
	Marning, packet driver vector invalid, using default search
	W
	Packet Access Type Error 10

	Can't Access IP handle interface type 1
	Packet driver probably not loaded

	Packet Access Type Error 10

	Can't Access IP handle interface type 1
	Packet driver probably not loaded

	Board initialisation failed!  Error code=2
	Error initialising network or getting configuration file
	Cannot initialise board.


The essential bits of my autoexec.bat are:

	3C503 0x60 3 0x300 0

and my config.sys:

	device=pcnfs.sys
	device=sockdrv.sys
	device=pktd.sys

Has anyone any ideas on this?  Does documentation exist for NCSA
Telnet 2.3b8 yet?  Will Sun be releasing a version of PC-NFS which
will allow third party telnets (and other goodies) to sit on top
their drivers?

Warren Stokes
Geelong Water Board, Australia.
was@gdwb.OZ.AU