Continue to Sources for Winsock Information
Go back to Software Descriptions
Return to Contents

Windows and TCP/IP for Internet Access

TRUMPET WINSOCK
(TCP/IP protocol stack and basic clients, including telnet, ftp, ping, Archie)

Please see revision note at end of this page

Comment: You need this package (or some other TCP/IP protocol stack that supports Winsock such as the one included in Windows 95) before you can use any of the client software described later. Trumpet Winsock does not require any additional network software. Its TCP/IP functions can be installed over other network software such as Novell or Windows for Workgroups using a packet driver shim. Instructions for such installations are included in the Windows Help file that comes with the package. Note that beginning with version 2.1, Trumpet Winsock implemented a time lock feature so that an unregistered copy can be used for only 30 days following installation. You must register before that time to keep the software running.

Peter Tattam, author of Trumpet Winsock, is owed a great debt by the many Internet users who got started with his inexpensive shareware package. Commercial TCP/IP stacks cost hundreds of dollars, and few would have jumped on the Internet without the boost provided by Peter's work.

Trumpet Winsock is a model of simplicity and good manners when it comes to installing and uninstalling the package. Installation makes no changes to the Windows directory and no changes to the WIN.INI or SYSTEM.INI files. You do not have to restart Windows if you change the TCP/IP settings, you need only close and restart the executable TCPMAN.EXE. To uninstall, you need only remove the Trumpet Winsock directory from the DOS path.

Trumpet Winsock remains useful for users of Windows 3.1 and Windows for Workgroups. Although Trumpet Winsock can be used with Windows 95, it is preferable to uninstall Trumpet Winsock and to install the TCP/IP stack included with Windows 95.

Author: Peter Tattam, Trumpet Software International

Fee: $25 shareware fee.

Version: 2.1 Revision F

File names:
twsk21f.zip (July 24, 1995 | 307,478 bytes)
(Includes the TCP/IP protocol stack)
Note: Trumpet Software International has been hard to reach since the release of version 2.1 of Trumpet Winsock in mid-June. The company moved its ftp server to a new IP address to try to improve response. It reassigned the hostname ftp.trumpet.com.au from the old server to the new server. However, nameservers in various locations had not yet caught up to the change by late July. At that time, when I tried to use TSI's Trumpet Winsock Version 2.1 home page when it was still using links to ftp.trumpet.com.au, I got a message that the files were not found because the nameserver at my location was then associating this hostname with TSI's old ftp server. On this page, I use the alternative hostname b-box.trumpet.com.au for the links to the files because this worked from my location. By early September, the nameserver had caught up with the new links, but I've retained the alternate name in the URL's on this page.
Caveat: There were six releases of Version 2.1 of Trumpet Winsock issued in a five week period. Be sure you obtain the latest version. The reasons for the bug fixes are listed on the Version 2.1 home page.

winap21f.zip (July 24, 1995 | 169,370 bytes)
(Includes basic clients for telnet, FTP, Archie, and IRC)

Note: If you have difficulty connecting to TSI's official distribution site, you may want to try some alternatives. For example, you can get both files from the SimTel20 archive.

winpkt.com (June 15, 1995 | 3,516 bytes)
You need this file when using Trumpet Winsock over a packet driver. With version 2.1, winpkt.com is not included in the ZIP file as it was in previous releases. This version of winpkt.com is identical to earlier releases included with previous versions of Trumpet Winsock.

Installation:

  1. Create directory C:\TRUMPWSK and unzip TWSK21F.ZIP and WINAP21F.ZIP into this directory.
  2. Install software drivers.
  3. In Program Manager, create a program group named Network. Use File Manager to drag and drop the EXE files in C:\TRUMPWSK into the Network program group.
  4. Edit the PATH statement in AUTOEXEC.BAT to include C:\TRUMPWSK. This enables Winsock applications to find WINSOCK.DLL when they are launched.
  5. Reboot the computer and start Windows.
  6. Launch TCPMAN from the Network program group. Select Help from the menu bar to learn more about the software.
  7. Select Setup on the menu bar. Enter your IP address, gateway address, and nameserver address as assigned by your local network administrator. (Some SLIP and PPP servers, as well as some direct network connections, do not use permanent IP addresses. Instead, the server assigns a temporary IP address at the start of each session. If you are using PPP, then the IP address usually will be set automatically at login. If you are using SLIP, then the IP address will need to be entered manually or by a dialler script.) If you are using ethernet, enter the software interrupt used by the packet driver. If you are using SLIP or PPP, check the appropriate box and enter the appropriate COM port number in the SLIP port box. Exit from TCPMAN. The file TRUMPWSK.INI will be created in the C:\TRUMPWSK directory.
  8. Launch any Winsock compliant application. TCPMAN.EXE will start automatically if it is not already running. (If you are using SLIP or PPP, you must first connect to the server and start a session. This can be done with the dialing function in TCPMAN.) Several clients are included with the Trumpet Winsock, including TRMPTEL.EXE version 0.08 for telnet, WINARCH.EXE for searching Archie databases, and TRUMPING.EXE to ping another machine on the network. TRUMPET PING provides the simplest means of verifying that you have a network connection. Launch TRUMPING and enter the name of an Internet host at the prompt. For example, you might try to PING ftp.trumpet.com.au. If your connection is working, and if the host is operating, you will receive a response from the remote host.

Note: The WINSOCK.DLL file for the Trumpet Winsock remains in the C:\TRUMPWSK directory. Some vendors may require that their WINSOCK.DLL be copied to the C:\WINDOWS directory. If you have used Winsock software from another vendor, but now want to try the Trumpet Winsock, be sure to remove the other vendor's WINSOCK.DLL so that it will not interfere with the Trumpet Winsock implementation.

Tip: The WINARCH client for Archie searching defaults to searching the Archie server at archie.au. You can access a different Archie server by using a command line argument. For instance, to use the Archie server run by AT&T, use the command line winarch.exe -archie=ds.internic.net.

SLIP or PPP usage: Trumpet Winsock includes a simple dialing function. You can connect to your server by manually issuing the dialing commands. You can also write a script that will dial and start your session automatically.

PITFALL: After dialing with TCPMAN.EXE and establishing the SLIP or PPP session, you must press the <ESC> key to escape from dialing mode and to re-enable the TCP/IP mode in TCPMAN.EXE.

You may want to dial your server automatically without writing a custom dialing script for TCPMAN.EXE. A utility named DIALER can be set up to automatically issue the commands and passwords needed to start a session on your server. DIALER version 2.0A is available by anonymous FTP from:
ftp.demon.co.uk
/pub/ibmpc/windows/utilities/dialexe.zip
(May 27, 1994, 31,072 bytes)


Continue to Sources for Winsock Information
Go back to Software Descriptions
Return to Contents
Revised: September 15, 1995
(The information on this page was last verified on September 15, 1995. There will be no further updates to this information about Trumpet Winsock as I have switched to using the
Win95 TCP/IP stack. --H. M. Kriz, 6/3/96)
Harry_M_Kriz, [hmkriz@vt.edu]