To make a telnet connection in TinyTERM 4.x, do the following:

1. From TinyTERM’s Edit menu, select Session Properties.
2. Under Connection type, select Telnet.
3. In the Emulation drop-down list, select the terminal emulation required by your host.
4. In the Host name, IP address, or phone number box, enter the hostname or IP address of the server.
5. Click OK to close the Session Properties dialog.
6. From TinyTERM’s File menu, select Save Session.
7. Click the Connect button.

To make a modem connection in TinyTERM 4.x, do the following:

1. From TinyTERM’s Edit menu, select Session Properties.
2. Under Connection type, select Modem.
3. From the Available Devices drop-down list, select the correct modem for this connection.
4. Next to Available Devices, click the Setup button. The Modem Setup dialog box appears.
5. Click the Configure button. The Modem Properties dialog box appears.
6. Set the Maximum Speed to match the speed the host modem supports.
7. Click OK to close the Modem Properties dialog.
8. Click OK to close the Modem Setup dialog.
9. In the Emulation drop-down list, select the terminal emulation required by your host.
10. In the Host name, IP address, or phone number box, enter the host’s phone number, including any dial-out prefix and area code.
11. Click OK to close the Session Properties dialog.
12. From TinyTERM’s File menu, select Save Session.
13. Click Connect to dial.

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

March 26, 1997

Dear Century Customer/Partner:

Subject: Year 2000 Compliance

The Year 2000 Problem:
The Year 2000 problem is the result of the common practice of using two digits instead of four to represent years in dates.  Many computer applications written in the last three decades did not provide for the fact that the century would change during the lifetime of the application.  Many installed computer applications (including those in client/server environments) that use two digits (YY) instead of four digits (CCYY) to represent year values in programs, may cause incorrect results in arithmetic operations, comparisons, and data sorting

Year 2000 compliant applications are capable of correct identification, manipulation, and calculation using dates outside of the 1900-1999 year range.

Century Software’s Year 2000 Compliance Performance Warranty:

Century Software warrants and represents that it’s product’s beginning with the April 15, 1997 release are and will continue to be Year 2000 compliant.  All date processing by our products will include four digit year codes.  Additionally, all date sorting by Century’s products that includes a “year category” shall be done based on the four digit year code.

In the event that a Century product released after April 15, 1997 is not Year 2000 compliant Century Software will upgrade that product to a Year 2000 compliant Century product at no cost to the customer.

Sincerely,

Michael Feaster
Director of Product Development,
Century Software Inc.

CVF

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.

Some versions of TERM and TinyTERM for Windows include the EMAIL file transfer protocol. This allows you to send files via email.

To set up an email transfer, open the Transfer File(s) dialog. In the File Name field, enter the full path to the file you want to send, or click the folder button next to this line to open a browse window.

Once the file is selected, enter the recipient’s email address in the Destination field. Set the Transfer Protocol to EMAIL.

If you set the Transfer Type to ASCII, carriage return/line feed pairs will be converted to single line feeds. This will happen whether you’re sending a text or binary file, so choose the type according to the file you’re sending.

Click the Email button next. In the Email Server line, enter the hostname or IP address of the outgoing email server. Set the Username and Password to your username and password on that server. Set the Email Address to your return address. The Subject line should be self-explanatory.

Click OK to return to Transfer File(s). Click the Send File button to send the email. Any replies will go to the email address specified above.

The standalone 5250 Keyboard Mapper is similar to the mapper in the standalone 3270 emulator. However, some of the keys are already mapped. In the PC Keyboard section, red keys are standard Windows keys. Black keys are already mapped to 5250 protocol keys. Yellow keys cannot be changed.

To the left of the tn5250 Keymap section is a Show Map button. This will give a more detailed list of the key abbreviations. It also allows you to change the keys in a list format, rather than a map format.

To map a PC Keyboard key, drag the desired key from the tn5250 Keymap section and drop it on the PC key you want configured. The new key mapping will display in black.

To save the mapping, exit 5250 emulation. The program will prompt you for a profile name. Save the profile. When starting 5250 emulation, select the desired profile to restore the keyboard mapping.