Century Software, Inc., has received a report in reference to Windows Vista Business Edition running in VMware, with an Agere OCM Serial Modem installed. Any attempt to configure a TAPI connection in that environment causes TinyTERM to crash with:

CSL Run Engine has encountered a problem and needs to close.

The same configuration works fine when using Windows XP in the same environment. Century Software has not been able to duplicate this error.

CR 881

On a widescreen monitor, if TinyTERM is maximized to fill the screen, the letters will probably be spaced far enough apart to be distracting and hard to read. Widescreen monitors use a 16:9 or similar aspect ratio intended to be like a movie screen. The dedicated terminals TinyTERM emulates all used a 4:3 aspect ratio, similar to a standard television. That makes a widescreen monitor about 1/3 wider than an equivalent terminal, so the letters are spaced that much farther apart. There are two ways to compensate for this in TinyTERM.

The preferred method is to run TinyTERM in a window, rather than full screen. You can resize the window to use the full height of the screen, widening it until it looks correct to the user.

The alternate method is to change the number of columns TinyTERM displays. To do that, open the Session Properties. In the lower right of the Session tab, check the “Use custom emulation size” box. Change the number of columns to 132. Leave the number of lines as-is. This will cause TinyTERM to display the maximum number of letters it can support in each line. However, it will cause display oddities for text longer than the terminal standard of 80 characters.

Once you have either resized TinyTERM to match your preference or increased the number of columns, go to the File menu and select Save Session to save your settings. This will ensure that the spacing does not automatically reset.

Century Software, Inc., has had several reports that the TinyTERM cursor does not blink when used over a thin client connection. When used at the terminal server console, the cursor does blink. We have not been able to duplicate this issue in-house.

CR 853

Using TERM-to-TERM server mode transfer, download a file to your Linux PC. Nothing transfers. The same is true for uploading to TERM in server mode using term -1x or term -2x. Both manual and scripted file transfers fail. This works using TinyTERM connecting to Linux.

CR 852

The following tables summarize the various versions of TinyTERM and TERM, for both DOS and Windows platforms. They show which operating systems each version was originally supported on, the basic format of the serial number, and whether or not that version of TinyTERM is still eligible for telephone and email support. The table is organized from most current products to oldest.

Support information for all versions is available in this Knowledge Base.

Version	Year	Product	Activation Key	Currently Supported?	OSes
4.12.0-4.12.4	2017-present	TinyTERM TinyTERM Plus	ADHSX-FH2C7-VVFF7-CHLRA-5EZRP	Yes	Windows XP and newer
4.9.0-4.11.0	2015-2017	TinyTERM TinyTERM Plus TinyTERM AX for Web	ADHSX-FH2C7-VVFF7-CHLRA-5EZRP	No	Windows XP and newer
4.8.0-4.8.6	2013-2015	TinyTERM TinyTERM Plus TinyTERM AX for Web	ADHSX-FH2C7-VVFF7-CHLRA-5EZRP	No	Windows XP, Vista, Windows 7, Windows 8
4.7.6	2013	TinyTERM AX for Web (initial release)	ADHSX-FH2C7-VVFF7-CHLRA-5EZRP (Registered Name required)	No	Windows XP, Vista, Windows 7, Windows 8
4.7.0-4.7.4	2011-2013	TinyTERM TinyTERM Plus TinyTERM AX for Web	ADHSX-FH2C7-VVFF7-CHLRA-5EZRP	No	Windows XP, Vista and Windows 7

Support for TinyTERM version 4.65 ended in August 2013. Support for TinyTERM versions 4.60-4.64 ended in February 2013.

Beginning with version 4.60, all products share the same 25-character activation key format.

Version	Year	Product	Activation Key	Currently Supported?	OSes
4.65	2011	TinyTERM TinyTERM Plus	ADHSX-FH2C7-VVFF7-CHLRA-5EZRP	No	Windows XP, Vista and Windows 7
4.60-4.64	2009-2011	TinyTERM TinyTERM Plus TinyTERM SHA	ADHSX-FH2C7-VVFF7-CHLRA-5EZRP	No	Windows XP, Vista and Windows 7

Support for TinyTERM versions 4.40-4.52 ended in May 2010.

TinyTERM Web Server was removed from the TinyTERM product line in version 4.60. Support for TinyTERM Web Server in all versions was also ended at that point.

Version	Year	Product	Serial Number	Curently Supported?	OSes
4.53	2007-2009	TinyTERM	E53777777EM	No	Windows 98se, Me, NT 4.0, 2000, XP and Vista
		TinyTERM Plus	P53777777EM		Windows 98se, Me, NT 4.0, 2000, XP, 2003 and Vista
		TinyTERM Web Server	S53777777EM	No
4.52	2006-2007	TinyTERM	E52777777EM	No	Windows 98se, Me, NT 4.0, 2000 and XP
		TinyTERM Plus	P52777777EM		Windows 98se, Me, NT 4.0, 2000, XP and 2003
		TinyTERM Web Server	S52777777EM
4.50	2005-2006	TinyTERM	E50777777EM	No	Windows 98se, Me, NT 4.0, 2000 and XP
		TinyTERM Plus	P50777777EM		Windows 98se, Me, NT 4.0, 2000, XP and 2003
		TinyTERM Web Server	S50777777EM
4.43	2005	TinyTERM	E43777777EM	No	Windows 98se, Me, NT 4.0, 2000 and XP
		TinyTERM Plus	P43777777EM		Windows 98se, Me, NT 4.0, 2000, XP and 2003
		TinyTERM Web Server	S43777777EM
4.42	2004-2005	TinyTERM	E42777777EM	No	Windows 98se, Me, NT 4.0, 2000 and XP
		TinyTERM Plus	P42777777EM		Windows 98se, Me, NT 4.0, 2000, XP and 2003
		TinyTERM Web Server	S42777777EM
4.41	2004	TinyTERM	E41777777EM	No	Windows 98se, Me, NT 4.0, 2000 and XP
		TinyTERM Plus	P41777777EM		Windows 98se, Me, NT 4.0, 2000, XP and 2003
		TinyTERM Web Server	S41777777EM
4.40	2004	TinyTERM	EV4777777EM	No	Windows 98se, Me, NT 4.0, 2000 and XP
		TinyTERM Plus	PL4777777EM		Windows 98se, Me, NT 4.0, 2000, XP and 2003
		TinyTERM Web Server	WS4777777EM

TinyTERM Thin Client was made an install option of TinyTERM Plus in version 4.40.

Support for TinyTERM versions 4.30-4.52 ended in May 2010.

Support for TinyTERM versions 4.00-4.21 ended in March 2007.

Version	Year	Product	Serial Number	Currently Supported?	OSes
4.30-4.33	2002-2004	TinyTERM	EV3777777EM	No	Windows 98se, Me, NT 4.0, 2000 and XP
		TinyTERM Plus	PL3777777EM
		TinyTERM Web Server	WS3777777EM		Windows 98se, Me, NT 4.0, 2000, XP and 2003
		TinyTERM Thin Client	TC3777777EM		Windows NT 4.0 Terminal Server, 2000 Server and 2003 Advanced Server
4.20-4.21	2001-2002	TinyTERM	EV2777777EM	No	Windows 95, 98, Me, NT 4.0, 2000 and XP
		TinyTERM Plus Edition	PL2777777EM
		TinyTERM Web Server Edition	WS2777777EM
		TinyTERM Thin Client Edition	TC2777777EM		Windows NT 4.0 Terminal Server, and 2000 Server
4.12-4.13	2000-2001	TinyTERM	EV1777777EM	No	Windows 95, 98, Me, NT 4.0 and 2000
		TinyTERM Plus Edition	PL1777777EM
		TinyTERM Web Server Edition	WS1777777EM
		TinyTERM Thin Client Edition	TC1777777EM		Windows NT 4.0 Terminal Server and 2000 Server
4.10-4.11	2000	TinyTERM	TTE777777EM	No	Windows 95, 98, Me, NT 4.0 and 2000
		TinyTERM Plus Edition	WPL777777EM
		TinyTERM Web Server Edition	WWS777777EM
		TinyTERM Thin Client Edition	WTC777777EM		Windows NT 4.0 Terminal Server and 2000 Server
4.02-4.05	1999	TinyTERM Plus Edition	WPL777777EM	No	Windows 95, 98 and NT 4.0
		TinyTERM Web Server Edition	WWS777777EM
		TinyTERM Thin Client Edition	WTC777777EM		Windows NT 4.0 Terminal Server
4.00-4.01	1998	TinyTERM Web Edition	TWE777777EM	No	Windows 95, 98 and NT 4.0

Version 3.3 combined the TinyTERM and TERM for Windows product lines, including ending the serial number in the letters EM. (No serial number ends in the letters OEM. Any serial number in that format actually uses the number zero, not the letter O.)

All products were released on CD from this point on.

Support for TinyTERM 3.3 and earlier Windows products ended in July 1999.

Version	Year	Product	Serial Number	Currently Supported?	OSes
3.3	1997-1998	TinyTERM	WTE777777EM	No	Windows 3.1, 95, NT 3.51 and NT 4.0
		TinyTERM Plus	WTP777777EM
		TERM Professional	WPN777777EM

All versions prior to 3.3 shipped on diskettes.

Version	Year	Product	Serial Number	Currently Supported?	OSes
7.2	1995-1996	TERM for Windows	WPE777777IW	No	Windows 3.1, 95 and NT 3.51
		TERM Professional	WPN777777IW
	1995-1999	TERM for DOS	DPE777777IB	No	DOS
3.2	1995-1996	TinyTERM Plus DOS	DTP777777TT	No	DOS
		TinyTERM Plus NFS DOS	DTN777777TT
		TinyTERM	WTE777777TT	No	Windows 3.1, 95 and NT 3.51
		TinyTERM Plus	WTP777777TT
		Plus[NFS]	WTN777777TT
		Simply[NFS]	WSN107107US
Pre 3.2 and 7.2	Up to 1995	TinyTERM	CSU777777TT	No	DOS
		TERM for DOS	CSU777777IB
		TERM for Windows	CSU777777IW	No	Windows 3.x

In a previous entry, we posted information on reading the serial number and activation key from the registry. This only works if your PC will boot, of course. If the hard drive has crashed, you’ll need to read its registry on another PC. Windows XP and Vista both have the capability to do this.

First, install the failed hard drive as a slave drive in a Windows XP or Vista PC. Make sure you can read the drive in My Computer before continuing. If you can’t read the drive at all, there is no way to recover the license from it.

Next, backup the PC’s registry. This is a vital safety step when making changes.

While still in the Registry Editor, click on HKEY_LOCAL_MACHINE to highlight it. From the File menu, select Load Hive. In the window that opens, browse to \Windows\System32\Config on the slave drive. Open SOFTWARE.SAV.

A message window will come up, asking you to name the key. There is already a key named “SOFTWARE,” so name the new key “CENSOFT.” When “CENSOFT” opens, extract the license according to our previous instructions.

Once you have your license written down, click on “CENSOFT” to highlight it. From the Registry Editor’s File menu, select Unload Hive. This removes the extra registry entries, restoring your system to its prior condition. You should not need the registry backup.

The Century LPD Server does not automatically start on Windows Vista. There’s a runtime error, then the status monitor CenLPDstatus.exe closes.

This is due to security settings in Windows Vista. To bypass the problem, run CenLPDstatus.exe as an administrator:

1. Click on the Start button and select All Programs, then Startup.
2. Right-click on Cenlpdstatus.exe.
3. Select Properties from the pop-up menu.
4. Go to the Compatibility tab.
5. Check the box labeled, “Run this program as an administrator.”

The next time CenLPDstatus.exe tries to load, you will see an “Allow/Deny” message window. Allow the program to run. It can then be configured normally.

CR 847

Before you can install TERM for UNIX from CD-ROM, you must mount the CD. Most UNIX platforms support SCSI or ISO 9660 CD-ROM drives. To find out whether or not the drive is recognized on the system, change directories to the /dev or /dev/dsk directory and type:

ls -l cd*

The permissions and device names will be displayed out, similar to the following example:

brw-rw-rw 1 root sys 51, Oct 28 08:16 cd0

In this case the CD-ROM device is cd0. Determine which device corresponds to your drive.

Mount the TERM for UNIX CD from the root directory by typing:

mount /dev/cd0 /mnt

Use the correct path for the CD-ROM device and the mount directory you prefer to use if not /mnt. Then change directories to /mnt/termunix and type ls to list the files and directories on the CD. Change directories again, this time to the directory that contains files for your platform:

Directory	Platform	TERM Version
ai	IBM PS/2 (AIX)	6.2.2
av	Data General 4000	6.2.3
h8	HP 9000 Series 700, 8×7	6.2.5
i6/3.x	IBM RS6000 (AIX 3.x)	6.2.3
i6/4.1	IBM RS6000 (AIX 4.1)	6.2.5
i6/4.2	IBM RS6000 (AIX 4.2 and higher)	6.2.5
ia	Altos Series 686, 886, 1086 SCO Xenix 286 Unisys IT, PW2 (XENIX)	6.1
m8	Motorola Delta Series 3000	6.2.5
mr	Motorola Delta Serives 8000, MPC	6.1
n4	NCR 3000	6.2.3
s4/solaris	Solaris	6.2.5
s4/sunos	SunOS	6.2.5
tu	Texas Instruments TI 1500	6.1
u3	Altos Series 500, 1000, 2000 Coherent 386 UNIX Convergent Tech Server (SPC 386) Intel 320 Interactive UNIX System V/386 SCO UNIX 5.x and higher	6.28
u3/old	SCO XENIX 386 Unisys 6000/3x, 6000/5x, 6000/6x Univel UnixWare	6.2.5b
u6	Sequent Series (PTX) Unisys 6000/70	6.2.2

For example, if your platform is SCO OpenServer 6, you would change to the u3 directory.

Next, copy the files from your chosen directory to the /tmp directory. Then change to the /tmp directory and extract each *.tar file separately with tar xvf:

tar xvf termu3.tar

At this point you can install TERM by running the install shell script:

/bin/sh ./install

Please note that on some CD releases, the files are in upper case. Any commands must refer to files in the correct case, upper or lower.

This information is also available in a screencast.

TinyTERM Application Developer 3.3 has a server mode. When that’s running, TinyTERM monitors a given port or modem, waiting for an inbound connection. This allows you to dial into your PC and use it as a file transfer server.

To use server mode, you must first select the connection type. Go to the Configure menu and select Communications. Select either MODEM or NETWORK LOGIN, then click OK.

Next, you’ll need to set up the server itself. Go to the Configure menu and select Server. You have a choice of Hostmode Server, WTERMCRC Server, Zmodem Server or FTP. The latter three allow you to connect for file transfers only, using the specified protocol. For purposes of this document, select Hostmode Server. This allows you to connect and communicate from any terminal emulation software.

Set the hostmode options you need. You must choose either Async for modem connections or Network for telnet connections. Once this is configured, click OK. Hostmode is now configured.

To start TinyTERM’s hostmode, go to the Action menu and select Server Mode. A server dialog will come up, noting that TinyTERM Application Developer is waiting for a connection of the specified type. That dialog will disappear while a user is logged in, then reappear when that user logs out. Only one user can login to hostmode at a time.

When you want to end hostmode, type Ctrl-C to close the dialog box. TinyTERM will return to terminal mode.

Many problems can occur if Pathway is not properly configured. Here are some things to check in case of errors, slowness and lockups. Please be aware that some specific files may not be used; i.e., ODI installation does not use protocol.ini.

Installing

• ODI: lsl.com and a *.com network card driver must be loaded.
• NDIS: Use either the *.mac or *.dos driver and the protocol.ini supplied by the network card manufacturer.
• PDS: This is a packet driver. It’s often unstable in Windows, so not recommended.
• Dedicated: Only use a dedicated driver for one of the listed network cards. Even so, we recommend ODI or NDIS instead.
• ASI: This is used by token ring networks. It is similar to a normal NDIS installation and just as easy to troubleshoot.

Winsock.dll
There should be only one. Any others will need to be renamed. Make sure the winsock.dll you use belongs to the TCP/IP or transport layer in use.

The -I: option is the interrupt of the network card or COM port
Run the network card setup utility to verify the interrupt of the card. Also, verify that there are no conflicts with this IRQ and other hardware.

pwconfig.exe -N: should be different than the network card
This is an interrupt vector or software interrupt. The default for Wollongong is 65. Valid numbers are 60-66. Most network cards are on 60 or 61. Recommended numbers are 63, 65 and 66.

Check for errors on boot. Concentrate on the error description, not the number. The brief description tells more than the number. If a technician can find the error number, chances are it will be the same description. Do not worry if there are two error numbers and one description. They will be related.

NET.CFG syntax
Order and spacing are critical. In general, the order should be: “Wollongong” group, “Link driver” section, “Wollongong” group, and then extra additions such as buffers, Novell DOS requesters, etc. Make sure the frames are correct.

PROTOCOL.INI
Verify the ndis.exe -d: argument is pointing to the right [driver] section. You may also need to verify the protocol.ini file being used. You may find copies in multiple places: C:\Windows, C:\Pathway\Lanman, etc.

In Windows for Workgroups, make sure Windows has loaded the right network driver and that NetBEUI is running correctly.

IP addresses
Check to see if it is a duplicate or otherwise incorrect. Errors that occur from this are PC lockups, lost connection, and read/write errors.

A simple way to check for duplicate IP addresses is to change the PC’s address, then ping the old address.

Subnet mask bits
Make sure they are the same as other computers on the subnet. This will also cause PC lockups, lost connections and read/write errors.

STAT.EXE
Run this at a DOS prompt. Three parameters need to be checked:

• stat 2: Physical address of the network card. If it’s all zeroes, Pathway is not loaded or not loaded properly. Pathway needs to see the card, unless you are using PPP or SLIP.
• stat 3: Resolved IP addresses. If this reports no resolved addresses, the TCP stack could still be the problem. If there is a resolved address and there is still no reply from the ping, the problem is on the other end of the connection, not the PC.
• stat 4: This gives the local IP address and subnet mask bits.

Patch
Download the updated PCHRUN.EXE. Replace the existing copy on the PC with the new file.

Update the network card driver
Get latest drivers for network card from the manufacturer. Generally, the manufacturer’s website will have the files to download.

Watch for cards that do not support multiple protocols
Some older network cards only support one protocol at a time; e.g., IPX or NDIS. This is not common. If either protocol loads and connects properly when run alone, but combined one or the other fails, then it does not support multiple protocols.

Adjust Windows
See our other documents on NDIS, ODI and Windows 95 configuration.