Path: utzoo!attcan!uunet!samsung!usc!apple!netcom!jbreeden
From: jbreeden@netcom.UUCP (John Breeden)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Novell Ethernet card running PC-NFS
Message-ID: <11285@netcom.UUCP>
Date: 29 Jun 90 14:14:18 GMT
References: <2111@east.East.Sun.COM> <308@megadata.mega.oz> <994@idunno.Princeton.EDU>
Organization: NetCom- The Bay Area's Public Access Unix System {408 241-9760 guest}
Lines: 24

In article <994@idunno.Princeton.EDU> marty@puppsrPrinceton.EDU (Marty Ryba) writes:
>Is there a working packet driver interface for PC-NFS???  I've tried the
>packet drivers in drivers.arc on sun.soe.clarkson.edu along with pktd.sys
>with both a 3c501 and a WD8003E card.  PC-NFS does not seem to be receiving
>any packets when it starts up.  I'd like to get this working since the telnet

The original pktd.sys code from Geoff had a bug. If the hardware source 
address that pktd.sys sends out is all 0's, the you've got the old code 
(and it won't work).

Take a look at pktd.asm. It makes a call to the packet driver to get the
ethernet card info. You need to set two registers before you make the
call, Geoff's code only sets one. When the call is made, no error returns,
just all 0's for the address. Adding code to set the second register before
the call fixes the problem.

Sorry for not being more precise, I'm sending this from home and don't have
the info here. Check the FTP Packet Driver spec. for the name of the call.

I sent the fix to Geoff and I know he posted it at least once on the net.
Russ may still have the old code at Clarkson.

PC-NFS works fine on the Packet Driver with this fix, I have it running on
AT&T Stalan10 and 3Com ELKII cards at a bunch of sites in the country.