Managed by Trumpet Software International Pty Ltd.
Copyright (C) 1993,1994 by Peter R. Tattam
All Rights Reserved
INTRODUCTION
Thank you for using the Trumpet Winsock. It is through the kind support of many users out there that quality networking software has been available at affordable prices to the Internet community. The Trumpet Winsock is a Windows Sockets 1.1 compatible TCP/IP stack that provides a standard networking layer for many Windows(tm) networking applications to use, and has itself been a major vehicle in achieving widespread use of Windows Sockets 1.1.
The product is released as shareware, and as such you are permitted to evaluate it for 30 days. If you are satisfied with its usefulness, a registration form is provided which you should fill out and send to Trumpet Software International. A registration fee is requested to maintain the development and support of this software. Suitable arrangements have been made for site licenses, and details can be found in a later section.
DISCLAIMER & COPYRIGHT
These programs are Copyright (C) 1991-1994 by Peter R. Tattam,
All Rights Reserved.
They are provided as shareware with the following limitations:
These programs are shareware and are not to be resold or distributed for sale with other programs which are for sale. There is no warranty or claim of fitness or reliability. The programs are distributed AS IS, and as such neither the author, nor Trumpet Software shall be held liable for any loss of data, down time, loss of revenue or any other direct or indirect damage or claims caused by these programs.
INSTALLING THE TRUMPET WINSOCK.
The Trumpet Winsock will only run on your PC under the following conditions. You must have either a packet driver available for use by network programs, or if you wish to use SLIP, a free comms port. Additionally, packet drivers can only be used reliably under enhanced mode using WINPKT. Standard mode can be used, but care must be taken to avoid system crashes. NDIS and ODI can be used via packet driver shims, but their use is not supported. PKTMUX may also be used instead of WINPKT, and must be version 1.2c or later, but again its use is not supported.
If you already have some kind of TCP/IP networking package installed, it is most likely that the Trumpet Winsock will not run and you will have to massage your system configuration to install the Trumpet Winsock, possibly even to the extent of uninstalling that networking package. Alternatively, there may be a Winsock available for your package in which case the Trumpet Winsock will not be required.
USING TRUMPET WINSOCK OVER INTERNAL SLIP/PPP
SLIP is a simple protocol which allows an Async serial connection to send Internet Protocol (IP). You usually need to have access to a server which can understand SLIP. SLIP is usually accessed via a phone line, and with the advent of high speed modems, TCP/IP is a reality over a dial-up connection.
PPP (Point to Point Protocol) is a protocol that is more complicated than SLIP, which offers error correction and is more reliable than SLIP.
The Trumpet Winsock has facilities for managing a SLIP connection as well as the ability to use dialling scripts for logging in and out of your SLIP server.
INSTALLING THE WINSOCK FOR USE OVER INTERNAL SLIP/PPP
Before you do anything, copy the files winsock.dll, tcpman.exe, hosts, services and protocol to a suitable directory.
eg. c:\trumpet
the essential files are:
winsock.dll the guts of the TCP/IP driver
tcpman.exe controlling program for the Winsock
sendreg.exe registration program
hosts list of host names
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.
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 set up 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 help from qualified Internet support staff - it will save you a lot of time.
Firstly, click on Internal SLIP or Internal PPP. Some of the parameters will be greyed and others ungreyed.
IP address your Internet IP address or "bootp" in lower case only. Only use bootp if your server supports it, otherwise the winsock will delay for up to 2 minutes and the message "Unable to perform bootp" will come up. The winsock will not function should the bootp fail.
Name server your name server IP address for DNS searches. You may provide more than one address by separating the addresses with spaces (IP addresses only).
Time server at present unused - future winsock API's may support this (IP addresses only).
Domain suffix a space separated list of domain suffixes to be used when resolving names in the DNS system.
MTU Maximum Transmission Unit. Related to TCP MSS... usually TCP MSS + 40 (Numeric). For SLIP, we suggest 256 initially.
TCP RWIN TCP Receive Window. It is recommended that this value be roughly 3 to 4 times the value of TCP MSS (Numeric). For SLIP, we suggest 848.
TCP MSS TCP Maximum Segment Size, It is recommended that this be a smallish value when using SLIP - say 512 bytes for SLIP and lower for CSLIP. CSLIP is able to compress data more efficiently when it is less than 255 (numeric). For SLIP, we suggest 212 initially.
SLIP port your comms port number ..1=com1, 2=com2 etc., (numeric).
baud rate the speed you wish to run at (numeric). Up to 115200 is supported although speeds greater than 19200 require suitable hardware.
hardware
handshake recommended if your link supports it.
Van Jacobson CSLIP
Compression if your server will support it. You may also have to adjust MTU, MSS & RWIN to be suitable.
Online Status
Detection if your modem will support it, select DCD or DSR on-line status detection. You will need to make sure that your modem has a default power on setting of AT&C1 for this to function.
The rest of the details should be greyed out and you need not try to fill them in.
When you are done, click on <OK> and if all goes well, the Trumpet Winsock will be initialised. You are now ready to start using the winsock.
LOGGING IN TO THE SERVER.
You can use either the manual login or the automatic scripting to access your server. For the time being, choose manual and log into your server with the appropriate commands. Don't forget to use the <esc> key to get out when you have finished dialling in. After logging in, you may need to go and set your IP address if it is allocated dynamically.
If you wish to use another terminal program to dial in to the server, don't forget to issue AT&D0, or disable DTR dropping when exiting the program, or the connection will be severed when the application closes the comms port.
Try out pingw to a well known host IP address to see if all is well.
PROBLEMS WITH INTERNAL SLIP
Check your baud rates...
If using hardware hand shaking with an external modem, make sure the cable is correctly wired.
By default, all dialling must be done with 8 bits, no parity. This may not work for you... You may need to choose Dialler/Options to select Control Panel parity/word size if you are not using 8 bits, no parity.
If all else fails... contact us !!
Once you have determined your login sequence, you can set up a login script. A sample script is provided along with the disk.
Many Internet dialup providers will have their own scripts for connecting to their
