Do you remember win3.1? Well, i've got a problem just with this O.S. (and trumpet winsock): I've got a little LAN, at home, connected via modem to internet. The "server" mount win98, with a DHCP server that help me configuring automatically the various clients. Now, all clients with win95/98 works correctly... The problem came up when i tried to connect to the lan a little 386, with 8 Mb Ram, an NE2000 compatible network adapter and a MGA video adapter (Hercules), with win3.1. When i boot this 386, the machine find properly the network adapter, configuring itself all tcpip parameters (ip, gateway, etc.), and if i use some service as ping or ftp _under_ MSDOS, it work properly too. Where's the problem? As soon as i launch win3.1 and i try to launch e.g. ie5 (or any other program that need trumpet winsock), the machine hang up, or the program don't seem to work. Now, i'm not an expert (or a little genius :)), and i don't know if all the drivers i load MUST be loaded. So,there's a list of drivers written in autoexec.bat (if they can help you,ok?) c:\dosnet\client.com <=(a driver needed to be loaded, if i want to see the network under win3.1)(it seem) lsl.com <=what is this? ne2000o.com <=NOT a packet driver...it seem to be the network adapter driver. It work with lsl.com tcpip <=this allows me to use tcpip services under dos ne2000.com 0x60 5 0x320 <=this is the packet driver (used by trumpet winsock, is true?) pktmux <=? pktdrv <=? I need all them? I need something I haven't? Please, help me! Ah! A last thing: i'm not too sure about my trumpet winsock configuration... And, if is useful, i'm unable too to ping other machine, _in_ my lan, from this 386, even under win3.1 Hoping that someone help me... Gianluca Nardin

No experience with setting up LAN, but I think you might be able to tweak a little settings in your trumpet winsock. First of all make sure you got the latest version of Winsock which you can prolly find on the net. So your LAn thing uses a packet driver? I think there is a section in trumpet winsock settings that you need to check that says 'packet driver' or gateway or something like that, check that out. Did you say you use IE5? I didnt even think IE5 on a 386 with 8 megs of ram would INSTALL, much less work. Maybe you could try out Netscape 2.0 or something similar. Hope that Helps

You use a Dos-Network from Novel ??? Suggestion: Upgrade to WfW 3.11 and install the TCP32b package. But do not use IE5 on a 386 with 8Megs it will not work. Try to use Netscape 2.02 This is the Novel-Network-Client: c:\dosnet\client.com <=(a driver needed to be loaded, if i want to see the network under win3.1)(it seem) This is a Novel-Network-Driver: lsl.com <=what is this? ne2000o.com <=NOT a packet driver...it seem to be the network adapter driver. It work with lsl.com tcpip <=this allows me to use tcpip services under dos This must be the Packet Driver: ne2000.com 0x60 5 0x320 <=this is the packet driver (used by trumpet winsock, is true?) pktmux <=? pktdrv <=?

an older version of T.W. used WINPKT.COM as a packet driver

USING TRUMPET WINSOCK WITH PACKET DRIVER. Firstly, if you don't know what a packet driver is; it is a small piece of software which sits in between your network card and your TCP program. This provides a standard interface which many programs can use in a similar manner to BIOS calls using software interrupts. Why is it called a packet driver? This is because modern networks send information using packets of information rather than sending information one byte or character at a time. For example, Ethernet sends information in frames of up to 1514 bytes long. The reason for sending things in packets is that information can be transmitted much more efficiently in packets. Central to the concept of the packet driver is a vector which is used to communicate with it. The 80x86 family of processors allows programs to communicate with the operating system through what is called a "software interrupt", which always has a number in the range 0 to 255. This is termed a "vector" and is the one of the key mechanisms to pass control to the MS-DOS operating system. Usually the vectors are expressed in hexadecimal, with the range 0x00 to 0xFF. The 0x in front of the numb er means that we are using hexadecimal numbers instead of decimal numbers. They may also be expressed in the notation 00H to FFH, or $00 to $FF. If you are dealing with packet drivers, hexadecimal notation is much more common, but occasionally they are expressed in decimal. Examples of software interrupts in use on PC's are 0x10 for the video BIOS, or 0x21 for calls to DOS. Packet drivers are only allowed to have a software interrupt vector in the range 0x60 to 0x7F. Normally, you will pick 0x60 as the default place to install your packet driver, but certain machine configurations may make that vector unavailable. Just choose one that is free - the packet driver should tell you if you can use it or not. The Trumpet Winsock also uses a special virtual packet driver "wrapper" which enables your packet driver to function correctly in Windows. While the packet driver is an efficient way to communicate with your network card, it will not work correctly from Windows without a little assistance. The program "WINPKT" was written by some clever people on the Internet to allow a packet driver to work correctly within Windows by making sure that packets get directed to the correct "virtual machine" un der Windows enhanced mode. A "virtual machine" can be either the entire Windows session, or any DOS session active within Windows. Refer to the Windows system documentation for more details. In addition to this, you will need to have some understanding of IRQ vectors and I/O addresses that may be relevant to installing your network card. WHERE DO I OBTAIN PACKET DRIVERS FROM? These days, packet drivers are usually provided with your network card, otherwise a comprehensive collection of public domain packet drivers can be obtained from a packet driver collection called the "Crynwr Packet Driver Collection." Information o n where to get this packet driver collection from is provided as an appendix to this document. INSTALLING THE WINSOCK FOR USE WITH PACKET DRIVERS Before you do anything, copy the files winsock.dll, tcpman.exe, winpkt.com, hosts, services and protocol to a suitable directory eg., c:\trumpet the essential files: winsock.dll the guts of the TCP/IP driver tcpman.exe controlling program for the winsock sendreg.exe registration program winpkt.com virtual packet driver interface for windows hosts list of host names & aliases services list of Internet services protocol list of Internet protocols Modify the path line in your autoexec.bat to contain a reference to that directory. eg., path c:\dos;c:\windows;c:\trumpet Make sure it is active by rebooting your computer or by executing autoexec.bat again. SETTING UP YOUR PACKET DRIVER. The packet driver command lines in the examples below would normally be part of a batch file used to connect to your network although it could be placed in autoexec.bat or in a batch file to start Windows in which case you would need to add a third line to start Windows. The most basic setup of packet driver and WINPKT would look something like this example (for an NE2000 compatible network card). Note that the packet driver name for other types of network cards will of course be different to ne2000: ne2000 0x60 2 0x300 WINPKT 0x60 The first line installs an NE2000 packet driver on vector 0x60 using IRQ 2 and I/O address 0x300. The second line installs the WINPKT virtual packet driver using the same vector that the ne2000 packet driver was installed on. The next example shows the setup for a Western Digital 8-bit network card using vector 0x61, IRQ5 and I/O address 0x320. wd8003e 0x61 5 0x320 WINPKT 0x61 These of course are only examples so your mileage will vary. Of prime importance is the need to make sure your network card IRQ, I/O address settings and shared memory addresses don't conflict with other cards in your computer. Some more example configurations are described later in this document under the heading Sample Configurations for Packet Driver. Choose the one which suits you the best and modify it to your requirements. Now you are ready to start windows. Start it up!! From windows, start up tcpman by selecting File/Run from the file manager, then type "tcpman". If this fails, the path is probably not set up correctly, so fix it. Later, you can setup tcpman as an icon so it can be started directly. Assuming you are a first time user, a setup screen will appear giving you a number of options to fill in. You will need to fill in the following details to enable the TCP package to function. If you are unclear on any of them, try to seek some hel p from qualified Internet support staff - it will save you a lot of time. IP address your Internet IP address, "bootp", or "

I posted a excerpt from the instal.txt from trumput winsock 2.0 by Peter Tattan because there is a example setup for your ne2000