Free 14-Day Evaluations    
Product Downloads    

Sign in     


DESKTOP MOBILE DOWNLOAD PURCHASE SUPPORT INFO COMPANY
 Home  >>  Support  >>  Knowledge Base

Archive for the 'Connect' Category

Ishare Modem Server Errors

Tuesday, April 10th, 2007

You may see sporadic Winsock errors in TinyTERM when connecting to an Ishare modem server. This happens when the Ishare modem server conflicts with the TCP/IP settings for the local network. You will need to redirect Ishare to look at the modem server only, and redirect the local network to look at the network configuration only. This may require a hosts file on the PC.

Can’t Save Address in .tap File

Tuesday, April 10th, 2007

Occasionally TinyTERM 3.3 will not save a change to the IP address or phone number it’s using. When that happens, open the .tap file in Notepad or another text editor. Make the change there, then save the file. It will be in effect the next time you start TinyTERM.

Netscape Winsock Causes TinyTERM to Dial Modem

Tuesday, April 10th, 2007

Using TinyTERM 3.2 on Windows 3.1, Netscape will not load pages if the Marathon Winsock.dll is in place. However, using Netscape’s Winsock.dll causes TinyTERM to dial the modem, rather than connecting to an ISP.

To bypass this, use the Century Internet Dialer to connect to the ISP before starting Netscape or TinyTERM. This will allow the use of Netscape’s Winsock.dll, while TinyTERM will still recognize the ISP connection.

Install Without Marathon Stack

Tuesday, April 10th, 2007

TinyTERM Plus 3.2 comes with a Marathon TCP/IP stack for Windows 3.1. If you want to install without it, edit the PC’s AUTOEXEC.BAT and CONFIG.SYS files.

In the AUTOEXEC.BAT, REM out everything except ECHO, PROMPT and PATH commands. In the CONFIG.SYS, REM out everything except FILES, BUFFER, HIMEM.SYS and EMM386.EXE.

Restart your PC after this. When you install TinyTERM, you will be able to bypass the Marathon portion.

Wrong Version of Windows

Monday, April 9th, 2007

This error comes up when installing TinyTERM 3.2 on Windows 3.1. It’s caused by one of two things:

  1. Multiple Winsocks are installed on the PC. Remove them and reinstall only one.
  2. No Winsock is installed on the PC. Install one before installing TinyTERM.

Install Asks for IP Address

Monday, April 9th, 2007

Installing TinyTERM on Windows 3.1, it may ask for an IP address, even if you plan a serial connection. When this happens, click the Back button and deselect the network installation.

Error 502 Missing Network Driver

Monday, April 9th, 2007

Error 502 means that TinyTERM has no network driver selected. To select a network driver, do the following:

  1. Open the ICONect or .tap file.
  2. Go to the Configure menu and select Communications.
  3. Select Network Login for the port.
  4. Click the Network button and choose Generic Winsock as the network type.

Cannot Find Syslog.DLL

Monday, April 9th, 2007

TinyTERM Plus or TERM Professional 3.3 installed in Windows 3.x. After the install, when Windows starts you may get two errors:

Cannot find syslog.dll
Cannot find file winsock.dll

Both of these files should be in the C:\Windows and C:\Windows\System directories. Copy them from their current location to both directories.

To get the winsock.dll file, you may need uninstall and reinstall TinyTERM. When you get to the screen that allows you to select which components you want to install, select the Century TCP/IP. You may be asked about installing a secondary network. This is what you want to select.

Before you start the install check your System.ini file. Search or Find the word “network” and take note of what is there. You will want to put these settings back in after the install if they change in any way.

Mar_Com and Mar_TCP Errors from Modem Connection

Monday, April 9th, 2007

If TinyTERM gives errors when trying to use the dialer or on boot, it usually means the PC does not have networking installed. To fix the errors, uninstall TinyTERM and reboot the PC. When you reinstall TinyTERM, uncheck Network Utilities and any other network option.

Error Creating Socket

Monday, April 9th, 2007

This error means that either TCP/IP is not installed, or there is a problem with the Winsock.dll file. It may be corrupted, or missing.

You may also have too many Winsock.dll files on the PC. This occurs when TCP/IP has been reinstalled multiple times. Remove it entirely in this case, then delete all copies of Winsock.dll. Restart Windows and reinstall TCP/IP at that point.

  Copyright © 2024 Century Software, Inc. All Rights Reserved999 TERMS OF USE PRIVACY POLICY EULA