Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!ucsd!ucbvax!FTP.COM!jbvb
From: jbvb@FTP.COM ("James B. Van Bokkelen")
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: WIN TCP R4.1 w/packet driver
Message-ID: <9010311943.AA12828@ftp.com>
Date: 31 Oct 90 19:43:17 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: jbvb@ftp.com
Organization: The Internet
Lines: 24


            3) using another card (Hughes LAN Systems 4140)
               and loading the driver S/W (MPD4140, MPDINIT)
               which I am guessing creates a PD I/F since
               PC/TCP works fine with both that combination
               and with a packet driver...
    
    Your option #3 doesn't work because MPD4140 and MPDINIT do not constitute
    a PD interface. ....

I would say that if the Class 1 Packet Driver version of PC/TCP (ETHDRV.EXE)
runs on it, it is at least arguably a Class 1 packet driver.  I could
understand not wishing to support it except with your own product...

As to why the WIN/PC stuff might not work where PC/TCP does, there are a
number of potential causes, most historical (we encountered the driver
bugs long ago, and built in code to cope with them, where Leo may not
have heard of this one till the original post).  My first guess is that
the packet length passed in CX to the first receiver() upcall is wrong.
Does the TWG product have any keyboard commands to display low-level
errors like "too short" or "too long" or "unknown type"?

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