- Call to undefined dynalink
A call has been made to a non existent routine in a Windows library. In the case of the Trumpet Winsock
the error message is caused by having multiple winsock.dll or wsock32.dll files on the machine. Please do
a search for winsock.dll and wsock32.dll on the machine and delete or rename any that are not in the Trumpet
directory.
- CTL3DV2.dll not correctly installed
The Trumpet Winsock will only use this file if it is available, however an error message is produced when
multiple copies are found.
The file ctl3dv2.dll should only be in one directory, which is usually: C:\windows\system.
Use the File Manager/Windows Explorer to search for ctl3dv2.dll starting from your c:\ drive, and remove
any multiple copies that might appear in the path statement of your autoexec.bat file.
- DB overflow
This error message relates to getXbyY queries (especially async forms), and suggests one of two
possibilities:
- The application is not providing a large enough buffer for the reply.
- A DNS reply is too large (perhaps due to a damaged UDP packet).
A DNS trace may give some indication of the problem. It may only be specific to certain sites.
Sometimes the application may be able to resolve the problem by restarting the call with a large
buffer. In this case, one can simply ignore the message.
- Exec error: 2
This error indicates "file not found". The exec command in a script will generate this command
if the file referred to, does not exist or has been mistyped.
Note that the backslash "\" symbol is interpreted as a special character, so be sure to put the
pathname in quotes (""). For example:
Exec "C:\dir\program.exe"
- get_recv_mode failed = X
This is generated by the packet driver interface, and indicates that the packet driver did not
support the get receive mode call. It should not affect normal operation.
A possible cause, is that multicast is being used with a packet driver that doesn't like the way
the Winsock tries to use it.
- Modem is not responding
Please check your modem. Is it configured so that the commands can be typed in, executed and display the
appropriate result code on the screen. For most commands, the results should be "OK".
If this is not the case, then the default login.cmd script will give a "Modem is not responding" error
message.
The most common reasons for a modem not appearing to respond (aside from the modem being turned off or
not plugged in) are as follows:
- The baud rate set in the Dialler/Settings screen, is not supported by your modem.
Please consult your modem's manual to discover which baud rates are valid. The baud rate
should usually be one of 9600, 19200, 38400, 57600 or 115200.
- The modem is set, to not echo characters as they are entered. To enable echoing, put
the command "e1" into the modem init string.
- The modem is not returning numeric result codes at all. To enable codes, put the
command "q0" into the modem init string.
- Password does not match - Try again
After you have registered the software you will be given a password. This password is normally generated as a function of your registration name.
If you are receiving an error after you have used the software, please make sure that you have entered the correct details and correct password for the right
version of software. The password may be for an earlier version of the Trumpet Winsock and you may need to update your password.
For example, the password for 2.1 will not work with 3.0. Please make sure that you enter the registration name and password exactly as provided without the
quotes, that is ("").
When entering you password, delete the contents of the field before entering anything and please be careful not to confuse the numbers 0,1 and 8 with
the letters O,I,B.
For information on the registration process, see Registrations.
- Runtime error 202
Runtime error 202 is a stack overflow, which is often caused either an application error, or by one of
the traces in the Winsock being turned on (in particular DNS).
- Script aborted
A "Script Aborted" message will be given if the script aborts for any reason before completion.
The most common cause of an aborted script seems to be due to an input command timing out. This is
usually the result of misconfigured server setting.
The Winsock assumes that your script is correctly configured, and therefore that the SLIP/PPP connection
has been established correctly. An error message is passed back to any applications which tries to access the
Winsock. This is usually relayed by that application to the screen. For example, Netscape displays, "Unable to
intitialise network layer".
From 2.1 onwards, Winsock applications are not able to connect to the Internet if "Script aborted" is
returned.
Please ensure that your script is suitably debugged and that all error conditions have been accounted for within
the script.
- Unable to initialise network layer
Netscape will return this error message in response to an aborted login script. See SCRIPT ABORTED.
- Unable to load TCP
This message will be displayed whenever the TCP/IP stack fails to load. There are many possible causes
of the error, so it is necessary to look in the Trumpet Winsock display for the specific cause. If you're
using a packet driver or packet driver shim, check that the packet driver is loaded properly. You will be able to
do this by observing the screen as the '.bat' file loads the packet driver and exectures. This will tell you whether
the WINPKT has managed to locate it. The WINPKT will also inform you if the TCPMAN chose the correct vector.
- Unable to perform bootp
There was no reply received to send BOOTP request. This means that there is either no BOOTP server available or the connection is not properly
established. If you have got BOOTP set unnecessarily, replace your IP address with 0.0.0.0 before dialling
again.
- Comm Error [Overrun]
Overruns are the result of the modem going too fast for the comm port and/or Windows. There are a number
of possible causes, some of which can be overcome.
If you are receiving lots of overrun errors, you may be able to rectify the problem with one of the
following:
- The first thing to try is lowering your baud rate in the Trumpet Winsock.
- If you have a high speed modem (14400 or higher), please make sure that you're using a 16540
or 16550 UART, as opposed to the older 8550 UART. If you wish to see what type of UART you have on
your modems comm port, please use MSD.
- If you are using Windows 3.1, please check the "comm.drv=" line in the [boot] section of your
system.ini file. If this reads "comm.drv=comm.drv", you are probably using the
original comm driver that was designed for the 8550 UART. You may like to try
another type such as Cybercom or Winfaxpro.
- Add the following statements to the [386Enh] section of your system.ini file:
comXfifo=1
comXbuffer=1023
comboosttime=8
Where X is the number of your Comm port.
- Some video drivers are built around the s3 video chip also hold CPU cycles and therefore
causing overruns as well. S3 have apparently released driver updates that cure the
problem. Several OEM vendors using the s3 based design have now followed suit.
- Unfortunately, there is one cause of overruns that cannot be avoided...
When accessing local disk(s), Windows will halt any I/O to the comm ports for a short period of time. This
in turn causes the overruns when the Winsock is unable to access the comm port. This is a glitch in the internals of Windows.
- PPP Frame Check Error
To check if there are any errors when a PPP packet is sent, a Frame Check Sequence (FCS) is performed.
This is calculated by the sender, by adding together the binary values of all the bytes in the packet and then sending it
as part of the packet. The receiver makes the same calculation and if the two values are not the same,
a frame check error occurs.
'PPP frame check errors' generally occur when transferring a large amount of data over your PPP connection.
These errors are usually caused by Comm error [Overrun] errors.
- enablecommnotification failed
The "enablecommnotification" call is implemented in new version of Windows. Some older comm drivers
(for example turbocomm) don't recognise it.
The solution to this is to either obtain a new comm driver or an update your old one. There are plenty
available (cybercom, winfaxpro, etc). If you are unable to obtain a new comm driver the original Windows
comm driver should work.
