Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!dali.cs.montana.edu!milton!pentch
From: pentch@milton.u.washington.edu (Dean Pentcheff)
Newsgroups: comp.protocols.nfs
Subject: Re: Updating pktd.sys
Summary: Also having problems, with suspicions on causes
Keywords: PC-NFS
Message-ID: <10762@milton.u.washington.edu>
Date: 7 Nov 90 23:46:23 GMT
References: <1164@ellen.sal.wisc.edu>
Reply-To: pentch@u.washington.edu (Dean Pentcheff)
Followup-To: comp.protocols.nfs
Organization: Department of Integrative Biology, UC Berkeley
Lines: 19

I'm also having trouble with the "pktd.sys" driver from the Clarkson
compat kit.  I've tried both the "compat.zip" version and the "compat.tar.Z"
versions.  When I unzip the zipped version (on the PC) then look at the
executable code using the Norton Commander filescan, it looks as though
either a) a text file partially overwrote the driver, or b) the text is
supposed to be in the driver, but linefeeds got translated into double
linefeeds at some point, hence hashing the code as well.  The situation
is similar with the tarred version (uncompressed and untarred on a UNIX
host, then binary transferred to the PC).  Could an bad CR/LF
translation somewhere along the transmission of the originals be the
culprit?  Could that be fixed?

Meanwhile, could someone mail me a (uuencoded) working version of pktd.sys?

Thanks.
-- 
Dean Pentcheff  (pentch@u.washington.edu)
Department of Integrative Biology, University of California, Berkeley CA 94720
Presently at:  Friday Harbor Labs, 620 University Rd., Friday Harbor, WA 98250