9 Apr 1995

Configuring Trumpet WINSOCK for Ethernet

Trumpet Winsock consists of an application program (TCPMAN) and a library (WINSOCK.DLL) that run inside the Windows environment. They use the services of WINPKT and a Packet Driver installed in the DOS environment before Windows starts. Trumpet makes no changes to the Windows configuration files or to the contents of the WINDOWS directory.

The original source of Trumpet files is ftp.trumpet.com.au, but the Internet connectivity to that server is unreliable. PCLT will offer an alternative US source of the files, but they may not be the absolutely latest release.

Click here to download the Trumpet WINSOCK 2.0A shareware package (load it to disk).

There are currently no update files, but should any appear they will be referenced here.

Unzip these files into a directory. The name C:\WINSOCK is suggested unless there is a better choice. In addition to documentation, there are three programs or groups of files in this directory.

  1. WINSOCK.DLL provides the library of subroutines that forms the WINSOCK programming interface. The structure of this library (the subroutines and their function) is the substance of the WINSOCK standard.
  2. TCPMAN EXE (the "TCP Manager") is the part of Trumpet WINSOCK that runs as a program. It calls WINDOWS services to allocate buffers and establish the necessary environment.
  3. Configuration files (HOSTS, PROTOCOL, SERVICES) are part of the standard Internet environment. These files were originally part of the Unix network setup and have been ported to most versions of TCP/IP.

When Trumpet WINSOCK runs on a LAN (instead of over a phone line) it is feasible to have TCPMAN load automatically when any Internet application starts up. To do this, place the Trumpet directory in the PATH. It is also a good idea to make sure that there are no other directories in the path that contain a WINSOCK.DLL module, and that the \WINDOWS directory does not contain such a DLL.

If an Internet application is loaded, and none of the Trumpet programs was previously loaded, the Windows system will note that the program depends on WINSOCK.DLL. It will search the path for this file name. If it finds the file, it will be loaded into memory. The Trumpet version of WINSOCK.DLL will, in turn, load TCPMAN.EXE. TCPMAN will find the parameter files and scripts. So if these files are in the path, the network can be started on demand.

An alternate strategy defines a Program Item for TCPMAN and makes its own directory the Working Directory when the program loads. The TCPMAN item can then be copied to the Startup Group, or it can be started manually. When TCPMAN starts, it loads WINSOCK.DLL from its own directory. While it is running, all subsequent Internet programs find an already active WINSOCK module and reuse it. With this strategy, the Trumpet directory does not have to be in the PATH, but TCPMAN must be explicitly started first before the network can be used.

The first time that TCPMAN is loaded, and then subsequently whenever Setup is selected from the File pulldown menu, a configuration dialog is displayed:

Because the box in the middle labeled Internal SLIP or PPP is not checked, Trumpet will find the WINPKT Packet Driver and use it to access the Ethernet. The fields on the top half of the form are filled in with the IP address assigned to this PC, and the Netmask and Default Gateway that define the range of IP addresses assigned to other machines on the same Ethernet and the machine that connects this LAN to the outside world. If your organization has a Domain Name Server, its address can be specified in the next box, and the trailing components of the domain name are entered in the Suffix field. Generally, the Maximum Transmission Unit for an Ethernet is 1500.

When this information has been entered, then TCPMAN should be ended and restarted for it to take effect.

Continue Back PCLT

Copyright 1995 PC Lube and Tune -- Windows on the World -- H. Gilbert