********************************************************************************
* README.TXT for NDIS 2.0 Packe Driver support over Windows for Workgroups 3.11*
********************************************************************************

Any software provided here is "as-is" with no warranties or other obligations.
"Software" includes the OEMSETUP.INF file  in this archive.

This archive is only provided as a temporary work-around method for users that need
packet-driver support under WFW 3.11, until an NDIS 3.0 packet-driver emulator is developed.

NB. I did not develop any of the provided executables, nor am I responsable for referenced
software packages, including Trumpet Windows Sockets TCP/IP, WinQVT or other.

Sorry for the disclaimers, but...

I have recieved a lot of mail, asking how to make NDISPKT.DOS work with WFW 3.11. This for people
using applications (mainly TCP/IP) that needs a packet-driver interface, software like Peter Tatthams
Trumpet TCP/IP needs this driver, also FTP s/w TCP/IP, WinQVT etc. etc.

Another solution would be to use the MS TCP/IP, but having tested that (DOS based !!! from a company
that cries Windows, Windows, Windows - everywhere...) I found that it basically "stinks" (sorry for the
language).

I personally use Trumpet - a 100% Windows based TCP/IP that takes 0 kB DOS RAM and works like a marvel.
On top of that I use WinQVT/NET v.3.94 for Windows Sockets. These products can be found as shareware
on several Internet sites, here are the reference:

WinQVT:
Host: biochemistry.bioc.cwru.edu (129.22.152.44)
Files:
/pub/qvtnet/qvtne394.zip - Windows 3.1 packet driver and Winsock executables
/pub/qvtnet/qvtnt394.zip - Windows NT version

Trumpet:
Host: biochemistry.bioc.cwru
File:
/pub/trumpwsk

Until yesterday I had not recieved my WFW 3.11, so I was in the dark...

I had heard that WFW 3.11 uses NDIS 3.0 as card-drivers, but that there was a compatibility-mode
with earlierNDIS2.0style drivers. Theissuewasto provide a simple installation procedure - asI had 
done earlier for WFW 3.1.

Here it is, this time in the form of an OEMSETUP.INF - this is "cleaner" than modifying NETWORK.INF
or other related files.

Installation Instructions:

- Unzip this archive to an empty sub-directory.
- Start WFW 3.11 Network Setup.
- Choose the button "Protocols".
- Choose "Unlisted or updated..." as the option.
- When asked for a diskette, indicate the location where you unzipped this archive.

Choose "OK" repeadetely, until the setup reboots the machine.

Done.

Notes: You must **not** use ODI as the card driver !!! I could have written a script for ODI as well, but
the packet-driver emulator would then be ODIPKT.COM and I do not plan to use ODI, plus the fact that I
can not re-distribute the other needed modules, LSL, IPXODI, etc. due to Novell copyright.

However, I include ODIPKT.COM in this package - i anybody want's to give it a try...:-)

So, you must use the "NDIS 3.0 with NDIS 2.0 support" as the card-driver.

If you wish to use Netware with this setup, you must use MSIPX.COM - please follow the instructions
given in NETWORKS.WRI on how to configure WFW 3.11 with MSIPX.

I have created a script for this installation, but can not re-distribute it, for the above mentioned
reasons..."en plus" I would probably get MS on my back...

If somebody is working on an NDISPKT.386 (NDIS 3.0), please let me know...

Regards,
Ingemar Lampa
OECD
Paris
France

PS. Thsi setup has not been widely tested, however, the modules in here have been running with WFW 3.1 for
over a year with no problems, so itshould continue to work.