Originally I thought MS's TCP/IP would allow for DOS apps to use
   32-bit TCP/IP in the same way IPX apps would (such as NetDOOM or
   Descent), but some TCP/IP apps provide their own complete TCP/IP
   stack, and use the pure packet interface (characterized by Packet
   Drivers that leave transport protocols to the apps themselves).
   
   There's an NDIS 3.0 packet driver you can install as a Win95
   "protocol" at http://ndtl.harvard.edu/ndis3pkt/ or at
   ftp://nic.switch.ch/mirror/novell/drivers/ which
   provides the packet driver interface for any network card. The driver
   is re-entrant so multiple DOS sessions can access it. The big catch
   is, if you use MS's TCP/IP Protocol at the same time, AND you have DOS
   packet apps that provide their own TCP/IP stack, you cannot have MSTCP
   and the packet app use the same IP address. You are effectively
   running two TCP/IP stacks (one for Winsock apps and the one provided
   by the packet app) and these can't have the same IP address.
   
   However, multiple DOS sessions running TCP/IP packet apps can use the
   same IP address. This packet driver can interpret TCP/IP packets from
   DOS packet apps and multiplex them. This is a special case which a
   packet driver would not normally handle.
   
   So with this aside, to install the virtual packet driver for Win95:
    1. Download the ndis3pkt "protocol" from the above address
    2. Install a net card driver for Win95
    3. Install the packet driver as a Protocol
    4. Check the Bindings tab for each net card you have, and make sure
       you enable the Virtual Packet Driver only for the cards you want
       to use it for (turn it OFF for the Dial-up Adapter).
    5. Re-start the computer. Use your packet apps as normally in DOS
       sessions.