GivenHansco Main Page
Termulator
News
Termulator II (Windows®)
Technical Support
Downloads
Termulator Support Policy
Place an order
Termulator II (Windows®) Technical Support

If you are having problems with Termulator II, please perform the following steps to resolve your problem:

  1. Review the list of common problems and solutions, below.
  2. Contact the vendor who sold you Termulator II. They can answer many common problems quickly.
  3. Contact GivenHansco Inc. directly. For faster service, please use the first applicable method on the following list:
    • Review the list of common problems and solutions, below.
    • Contact the vendor that who sold you Termulator II. They can answer many common problems quickly.
    • Email your support request to: tlsupport@givenhansco.com

Common Termulator II Problems and Solutions:

Problem:
I am trying to use Termulator with a TELNET connection, but I get the error message "The descriptor is not a socket or no buffer space is available" or “Undefined Error Code: 1400”. I have McAfee VirusScan 7.0 or McAfee Firewall installed.

Solution:
McAfee Firewall (included in McAfee VirusScan 7.0) by default blocks almost all TCP/IP traffic, which includes TELNET connections. (It also blocks Microsoft Network Shares by default.) GivenHansco strongly recommends that customers do not use this product. If this is not feasible, you must disable the McAfee Firewall to restore TELNET connections.

To disable McAfee Firewall, do the following:

  1. Double-click the McAfee Firewall desktop icon, or click Start->Programs->McAfee->McAfee Firewall.
  2. Select ‘Set Startup Options’ from the Tasks menu.
  3. Click the ‘Stop McAfee Firewall’ button.
  4. Uncheck the box labeled ‘Start McAfee Firewall automatically’.
  5. Reboot your computer.
Installing Termulator II on Windows:
  1. Insert the Termulator II diskette in drive A:.
  2. From the Program Manager, click File then click Run. -or- From the Windows 95 desktop, click Start then click Run.
  3. Type A:SETUP and press Enter.
  4. Follow the instructions presented by the installation program.

Installing Unix Drivers for Termulator II:
  1. Start Termulator II.
  2. Login to the Unix host as the super-user (usually root). Alternatively, you may login as another user and 'su' to root.
  3. Click File.
  4. Click Install Unix Drivers.
  5. A warning message appears. Click OK.
  6. You will now see a box which lists the version of Unix on the left side, and the available drivers on the right. Click the appropriate Unix version.
  7. Now click the drivers you want to load. You may select one or more drivers.
  8. Click OK to transfer the drivers to the Unix host.
  9. When the driver files have been transferred to the Unix host, the Unix root prompt will return. Logoff by typing exit and press Enter.

Problem:
I'm using Termulator II (Windows) under Windows 95. Termulator II can not communicate with my modem.

Solution:
Perform the following steps:
  1. Click the START button.
  2. Click on SETTINGS.
  3. Click on CONTROL PANEL.
  4. Double-click MODEMS.
  5. Click the DIAGNOSTICS tab.
  6. Click on the entry for the modem you are using.
  7. Click on MORE INFO. Windows 95 will attempt to communicate with the modem. If Windows is unsuccessful, this indicates a problem in your modem configuration. Consult your modem's instruction manual or the Windows 95 help. If Windows successfully communicates with your modem, review the port settings in Termulator II.

Problem:
I can't get the hsend command to send a file.

Solution:
This problem can be caused by using XON/XOFF transmit handshaking in Termulator II. A workaround is included in the current shipping version of Termulator II.
Download the Termulator II 2.2 update by clicking here.

Problem:
I can't get the hrcv command to receive a file.

Solution:
This problem is usually caused by modems that use XON/XOFF handshaking between them. A workaround is included in the current shipping version of Termulator II.
Download the Termulator II 2.2 update by clicking here.

Problem:
I can't get the hrcv command to receive a file. I am connected via TELNET to an SCO Unix host.

Solution:
There is a bug in SCO's TELNET implementation. (The bug still exists in the 5.0.5 release of OpenServer.) A workaround to this bug is included in the current shipping version of Termulator II.
Download the Termulator II 2.2 update by clicking here.

Problem:
Local printing will not work. I am using a 1.x version of Termulator II.

Solution:
It is strongly recommended that you upgrade to the current shipping version of Termulator II.
Download the Termulator II 2.2 update by clicking here.

Problem:
Local printing will not work. I am using version 2.0 or higher of Termulator II.

Solution:
Perform the following steps:
  1. Click the START button.
  2. Click on SETTINGS.
  3. Click on PRINTERS.
  4. Right-click the printer you are trying to print to.
  5. Click on PROPERTIES.
  6. Click the DETAILS tab.
  7. Click the SPOOL SETTINGS button.
  8. Click SPOOL PRINT JOBS SO PROGRAM FINISHES PRINTING FASTER.
  9. Select RAW for the SPOOL DATA TYPE.
  10. Click OK.
  11. Click OK.
  12. Close the printers window. Local printing should function properly now.

Problem:
The hsend/hrcv commands do not work with SCO Open Server 5.0.5.

Solution:
Download the Termulator II 2.2 update by clicking here.

Problem:
Termulator II will not install on Windows 98. My system has a Microsoft Wheel Mouse.

Solution:
Download the Termulator II 2.2 update by clicking here.

Problem:
ASCII files transferred with hrcv with Termulator II 2.1 or 2.1a have garbage at the end.

Solution:
Download the Termulator II 2.2 update by clicking here.

Problem:
Trying to connect using TELNET. Termulator II gives a blank screen with no login prompt. I can PING the server, and Windows TELNET.EXE program gives a login prompt.

Solution:
Termulator II is a 16-bit Windows application which makes use of a Windows DLL called WINSOCK.DLL. The TELNET.EXE program in Windows 95/98/NT is a 32-bit Windows application which uses a different DLL called WSOCK32.DLL. Some programs overwrite the WINSOCK.DLL provided by Microsoft with their own version. This can cause other applications which need to use WINSOCK.DLL to fail.

The solution is to obtain the Microsoft version of WINSOCK.DLL and copy it to the directory where Termulator II is installed (normally C:\TLW). The Microsoft version of WINSOCK.DLL for Windows 98 is approximately 21504 bytes and will be dated 1998 or newer.

Problem:
After installing Termulator II version 2.2 thru 2.2g on the Windows ME operating system, I was able to successfully establish a TELNET connection after running for the first time. Now after exiting Termulator II and restarting, the TELNET connection is not working.

Solution:
Termulator II versions 2.2 thru 2.2g have a known bug which prohibits TELNET connections from working under the Windows ME operating system. You need to upgrade Termulator II to the latest version which corrects this problem.

Download the Termulator II 2.2 update by clicking here.

Problem:
I can't connect to a Unix system over a modem. I can hear the modem dial, I see a CONNECT message on my screen, but then the cursor just blinks or I see garbage.

Solution:
The modem on the Unix system you're calling is either a slow modem (9600 baud) or is programmed to only connect at a certain speed. You need to program your modem to match the Unix system's modem. To do this, you first need to find out what baud rate the Unix system's modem is answering at. (Contact the vendor that set up your Unix system.) Then, you need to find out what type of modem you have. In Windows, click START, click SETTINGS, click CONTROL PANEL, double-click MODEMS, then read the description of your modem in the box. Using the following chart, identify your modem in the left column, find the speed of the Unix system's modem in the middle column, then copy the modem init string from the last column.
Modem Description Desired
Baud Rate		 Modem Init Code
Rockwell/Conexant HCF 9600    AT+MS=V32,0,9600,9600,9600,9600 {CR}~~
  19200    AT+MS=V34,0,19200,19200,19200,19200 {CR}~~
Rockwell RC56 9600    AT+MS=9,0,9600,9600 {CR}~~
  19200    AT+MS=11,0,19200,19200 {CR}~~
Lucent Chipset 9600    ATN0S37=9 {CR}~~
  19200    ATN0S37=13 {CR}~~
US Robotics Sportster 9600    AT&K0&M0&N6&U6 {CR}~~
  19200    AT&K0&M0&N10&U10 {CR}~~
Hayes Accura 9600    ATN0S37=9 {CR}~~
  19200    ATN0S37=13 {CR}~~

When setting up a modem dialer entry in Termulator II, there is a box on the DESCRIPTION tab called MODEM INIT. Key in the modem init string from the chart above EXACTLY in this box, then click OK. Now test the connection by clicking DIAL.

Problem:
Termulator II is working fine, but I have lost the window border and the menu.

Solution:
Termulator II is in "full screen" mode. Press ALT+ENTER to toggle between this mode and normal "windowed" mode.

Problem:
How do I place an icon for Termulator II on my desktop?

Solution:
  1. Right click on the START button.
  2. Click OPEN.
  3. Double-click PROGRAMS.
  4. Double-click Termulator.
  5. Right click the Termulator II icon.
  6. Click SEND TO.
  7. Click DESKTOP.
Problem:
My modem connection keeps disconnecting and/or I am getting garbage characters on the screen. I have Vonage (or another VOIP) phone service.
Solution:
Most VOIP (voice over IP) phone services are designed for voice traffic only. They cannot handle the bandwidth necessary for reliable modem communications. The only solution is to use a standard phone line (land-line).
Problem:
Termulator II does not work on the 64-bit version of Microsoft Windows Vista.
Solution:
There is no known solution at this time. Microsoft Windows Vista (64-bit version) has removed support for running 16-bit Windows applications, which includes Termulator..