Path: utzoo!utgpu!watserv1!watmath!att!ucbvax!CU.NIH.GOV!RAF
From: RAF@CU.NIH.GOV (Roger Fajman)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re:  Question about packet, NDIS, Clarkson, BYU, etc
Message-ID: <9105070330.AA05948@alw.nih.gov>
Date: 7 May 91 03:29:40 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The Internet
Lines: 14

>     ....  As a practical matter, LAN Manager requires an NDIS driver, so NDIS
>     isn't going away.  And I'm a crazy man, so the packet drivers aren't going
>     away either.
>
> Regardless of your sanity, which I wouldn't have questioned in any case, you
> can't unbind (disconnect) from a v1 NDIS driver except by re-booting.  This
> means that things like KA9Q and PC-IP whose protocol stack isn't a separate
> TSR will never be able to use NDIS directly unless v2 drivers start to appear.

3Com has something they call Demand Protocol Architecture, which allows
protocol stacks to be loaded and unloaded in an NDIS environment.  Is
this something layered on top of NDIS then, so that not all NDIS stacks
support it?