Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!usc!ucsd!ucbvax!NMS.HLS.COM!nestor
From: nestor@NMS.HLS.COM (Nestor Fesas)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: WIN TCP R4.1 w/packet driver
Message-ID: <9010312250.AA28833@nms.>
Date: 31 Oct 90 21:50:35 GMT
References: <9010311943.AA12828@ftp.com>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 26



JBVB writes:

>     
>     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...
> 

Sorry,  James is right.  In my haste,  I mistated the facts.  I should have
said that MPD4140 and MPDINIT were not intended to function as general
Packet Driver interfaces and thus have not been tested in that capacity.

Nestor.

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
        Nestor A. Fesas, Jr.           =         Hughes LAN Systems
        nestor@hls.com                 =         1225 Charleston Road
                                       =         Mountain View, CA 94043
                                       =         415-966-7473
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=