Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!usc!sdd.hp.com!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!FTP.COM!jbvb
From: jbvb@FTP.COM ("James B. Van Bokkelen")
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: TCP/IP for X under Windows3 ... do any work?
Message-ID: <9103151607.AA11244@ftp.com>
Date: 15 Mar 91 16:07:45 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: jbvb@ftp.com
Organization: The Internet
Lines: 21

I wish you had given the version numbers for both the PC/TCP kernel and
the Clarkson packet driver in use.

My first guess at your problem is that it is the same one a number of other
people have reported in some versions of the Clarkson 3C503 driver.  You
could try either our direct-to-the-hardware kernel (3C503.EXE) or get the
3Com NDIS driver for the 3C503 and try it with the DIS_PKT NDIS to PDS
adapter module (I've done a driver for that board myself, and I wound up
feeling that the only way to get it entirely right would have been to work
just down the hall from the people who designed the hardware, which is
presumably where the 3Com NDIS driver was done).

Given that current versions of the BYU Netware can't run on the DIS_PKT
adapter module, the best solution that lets you use a Novell 802.3 w/o
802.2 header encapsulation is one of the "Netware over NDIS" products.
3Com is shipping one, a company in Washington State has one in beta.
Novell will eventually release the "Packet Driver MLID", but that only
helps if you have Netware 386.

James B. VanBokkelen		26 Princess St., Wakefield, MA  01880
FTP Software Inc.		voice: (617) 246-0900  fax: (617) 246-0901