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.

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.

To setup Pathway 2.0 on Windows 95, with or without Novell installed, do the following:

1. In the Windows 95 Control Panel, double-click Network.
2. Add your network card if it is not already in place. It does not matter if you select the real-mode NDIS driver or the enhanced mode 32-bit NDIS driver, unless you add Novell IPX/ODI support. Then you must use the 16-bit real mode driver.
3. Client for Microsoft Networks and NetBEUI will automatically be added. Click OK and reboot the PC when asked.
4. During reboot hit the F8 function key. Choose Command prompt from the boot menu.
5. Install Pathway from the diskettes. Choose Ethernet|NDIS as the install type.
6. The directory containing the protocol.ini file is C:\Windows.
7. Choose the section of the protocol.ini that references your card driver name; for example, ms2000$.
   (Note: In one case the protocol.ini called for an ms2000$, but the driver that Windows 95 installed was ne2000.dos. To solve this problem, copy the ne2000.dos file to ms2000.dos.)
8. Let Pathway alter the AUTOEXEC.BAT file, but not the CONFIG.SYS.
9. Make the following changes to AUTOEXEC.BAT:
   1. Windows 95 adds the line NET START to the beginning of the file. Type “REM ” before it to comment out this line.
   2. After the line pwconfig -n:x add C:\Windows\net init.
   3. The next line reads ndis -i:x -d:x. After this line add C:\Windows\net start netbind.
   4. The next line should read pwtcp.
10. Reboot the computer and hit the F8 function key during boot-up. Choose Line by line confirmation from the boot menu. Load each line and make sure there are no errors during the Pathway load sequence. If you get an error in C:\Windows\net start netbind, change it to C:\Pathway\netbind.
11. Answer No to the Load Windows? prompt.
12. Ping in DOS to verify the install. If this works, enter Windows and use the winping.exe utility in the Pathway directory to test the stack in Windows.

If your machine can’t read the media TERM came on, there are a few things to check:

1. Verify that the correct extraction command is being used. Double-check your release notes for that information.
2. Verify that the correct device name is being used for the media being read. If you are unsure of the device name and it is not listed in the “Installation and Set up of TERM” section in the manual, you can search for the correct device name by inserting the release media in the appropriate drive and typing the following at a system prompt:
   

   # for x `ls /dev/rfd”
   > do
   > echo “Device: $x ”
   > tar xvf $x
   > done
   #

   This will cause the tar command to be used on all the selected devices until the correct one is found. In order for this to work correctly, you must loop through the right files and directory. An example of some directory specifications are as follows:

   Interactive UNIX system V/386 : /dev/rdsk/* (disks)
   SCO XENIX/UNlX : /dev/rfd* (disks)
   Sun Microsystems : /dev/rst/* (cartridge tape)
   ICL DRS : /dev/rmt/* (cartridge tape)

   Century Software, Inc., has provided TERM for UNIX releases in the following formats:

   Tan 5.25 Diskette: 36OK
   Black 5.25 Diskette: 1.2M
   Black 3.5- Diskette: 720K
   Black 3.5- Diskette: 1.44M
   Cartridge Tape: Low density
   CD-ROM: ISO 9660

3. Remove the media, reinsert it and try again.
4. If the release has multiple diskettes, try executing the extraction command on each diskette received. If all diskettes fail, reboot the system and repeat steps 1 through 4. Occasionally, UNIX drives can get messed up and require rebooting to correct. If only one diskette fails, it is an indication that the diskette is bad. Call Century Software technical support.
5. If all diskettes fail again, try using a non-Century Software diskette. If it fails to read, the diskette drive probably requires cleaning. If the non-Century Software disk works, the TERM product diskettes are damaged. Call Century Software technical support.

Cartridge Tapes
lf you are having problems reading a cartridge tape, follow the steps above. lf the above steps fall, be sure to use the blocking option with the tar command. Century Software’s tapes are usually written with a block size of 20. For example:

tar xvfb /dev/rctO 20

lf adding the block size option doesn’t help, try using the dd command as follows:

dd if = /dev/ < device > | tar xvf –

lf this command doesn’t work, try:

dd if = /dev/ < device > conv = swab | tar xvf –

Network Installation (DOS and Windows 3.x)
To install TERM or TinyTERM on a network file server, run the SETUP (Windows) or INSTALL (DOS) program. When prompted for the drive on which to install TERM, specify the desired network drive; i.e., G:\apps\century.

The number of network users authorized to use TERM or TinyTERM is enforced within the software. Each user will be informed of their status with the licensing agreement. When TERM or TinyTERM loads, it will display a message similar to the following:

User 1 of 1

When users encounter the error message:

TOO MANY USERS
WAITING FOR OPENING

they must wait for a license to become available. It is important that users of a network installed version of TERM or TinyTERM exit the program gracefully. If the computer is turned off or re-booted while in TERM or TinyTERM, authorized licensees will “lose” their network license. They may then have to wait for a license the next time they attempt to access TERM or TinyTERM.

When TERM or TinyTERM are installed on a network, the sub-directory \SER installed under the TERM directory must allow all users read and write permissions to its files. Any users with insufficient rights will receive an error message and will be returned to the Program Manager or a DOS prompt.

If it becomes impossible to recover lost licenses in the manner explained above, the file TERM.SER or TT.SER may have become corrupt. Should this occur, you will need to replace the file with a fresh copy. This may be done by either installing TERM or TinyTERM again, or the file may be copied from a backup.

Adding Individual User Licenses
Use ISETUP for Windows or INSTUSER for DOS systems to install files (and a program icon on a Windows system) to user workstations. It will also brand TERM or TinyTERM with additional licenses. The serial number and activation key will be required.

Note: Century TCP/IP must be installed on each individual workstation. Install only the emulator on the network server when using Windows.

Branding
The file brand.exe is a DOS executable, so it must be run from a DOS prompt. Change to the directory where brand.exe is located, then tell “brand” which file to add new licenses to. For example, if the TinyTERM executable file is wtt.exe, the command might be:

G:\apps\century>brand wtt.exe

If you get a message that it cannot locate the file to brand, add a specific path to the file:

G:\apps\century>brand g:\apps\century\plus\wtt.exe

The serial number and activation key will then be requested. A message will then be displayed that TinyTERM has been branded.

1. Make sure that Windows for Workgroups is installed correctly and can connect to other Windows for Workgroups PCs using the NetBEUI protocol.
2. Ensure that Windows for Workgroups is installed for ODI drivers.
3. Now install PathWay Runtime using PWSETUP, specifying C:\Windows as the directory containing the driver and related files.
4. PWSETUP will prompt you for a modification of net.cfg. Respond with Yes.

Sample Files for Windows for Workgroups 3.11 and Novell 3.11

*************************AUTOEXEC.BAT*********************************

@ECHO OFF
cd \novell
lsl
smcplus
ipxodi
netx ;(or VLM for 4.x)
E:\WINWORK\SMARTDRV.EXE
PROMPT $P$G
PATH E:\NFS20\PATHWAY;E:\UTILS\UNIX;e:\norton
SET TEMP=E:\WINWORK\TEMP
SET TMP=E:\TMP
LOADHIGH DOSKEY
COPY C:\DOS\COMMAND.COM C:\ > NUL
rem #—————– The Wollongong Group ——————–#
rem # The following lines are for PathWay Runtime setup. Please DO NOT #
rem # modify or remove any of them. If you DO want to, please run the #
rem # setup program to modify or deinstall PathWay for DOS. #
PATH E:\PATHWAY;%PATH%
PWCONFIG -N:65
ODI -i:5
PWTCP
rem #——————- The Wollongong Group ——————#
NFS
mount g: \phaedra\/home/sm sm
C:\DOS\SHARE.EXE /F:4096 /L:400

**********************END OF AUTOEXEC.BAT*****************************

The -I: parameter on the ODI line refers to the IRQ level of your network card. Please verify your card setting and make sure the Pathway setting matches. Remember to use the hex value for 10 and above. Symptoms of an IRQ mismatch include slow connection speed, intermittent hanging or loss of connection, and kernel initialization failure.

Once you have installed Pathway, reboot your PC. Watch for any errors. If no errors occur, first try to ping from a DOS prompt, then make sure Windows for Workgroups loads successfully. You should then be able to use FTP, telnet or NFS to connect to your host.

***********************CONFIG.SYS************************************

DEVICE=E:\WINWORK\HIMEM.SYS
DEVICE=E:\WINWORK\EMM386.EXE noems x=d000-d3ff
DOS=HIGH,umb
files = 70
stacks=9,256
buffers = 40
lastdrive=P
DEVICE=C:\DOS\SETVER.EXE
SHELL=c:\dos\command.com /p /e:600
DEVICE=E:\WINWORK\IFSHLP.SYS

*********************END OF CONFIG.SYS********************************

**************************NET.CFG*************************************

#—————- The Wollongong Group —————-#
# The following lines are inserted for PathWay driver #
# interface setup for ODI. Please DO NOT remove them. #
Protocol IP
Bind SMCPLUS

Protocol ARP
Bind SMCPLUS
#—————- The Wollongong Group —————-#

Link Driver SMCPLUS
Port #1 300
Mem #1 000d8000
Int #1 5
Frame Ethernet_802.3
Frame Ethernet_SNAP
Protocol IPX 0 Ethernet_802.3
#—————- The Wollongong Group —————-#
# The following lines are inserted for PathWay driver #
# interface setup for ODI. Please DO NOT remove them. #
frame ETHERNET_II
PROTOCOL IP 000000000800 ETHERNET_II
PROTOCOL ARP 000000000806 ETHERNET_II
#—————- The Wollongong Group —————-#

#For 4.x Novell the Novell DOS requestors will go here.

LINK SUPPORT
Max Boards 4
Buffers 8 1514

**************************END OF NET.CFG******************************

***************************PROTOCOL.INI*******************************

[network.setup]
version=0x3110
netcard=ms$w13ep,1,MS$W13EP,4
transport=ms$nwlinknb,NWLINK
transport=ms$netbeui,NETBEUI
lana0=ms$w13ep,1,ms$netbeui
lana1=ms$w13ep,1,ms$nwlinknb

[MS$W13EP]

[NWLINK]
BINDINGS=SMCPLUS

[NETBEUI]
BINDINGS=SMCPLUS
LANABASE=0

[net.cfg]
PATH=E:\NOVELL\NET.CFG

[Link Driver SMCPLUS]
data= Frame Ethernet_SNAP
data= Frame Ethernet_802.2
data= Frame Ethernet_II
data= Frame Ethernet_802.3
data=Link Driver SMCPLUS

**************************END OF PROTOCOL.INI*************************

1. Make sure that Windows for Workgroups is installed correctly and that a connection can be made to other Windows for Workgroup machines using the NetBEUI protocol.
2. Ensure that Windows for Workgroups is installed for Real and/or Enhanced mode NDIS.
3. Check the CONFIG.SYS file. No Protocol Manager or MAC driver should be included.
4. Now install PathWay Runtime using PWSETUP, specifying C:\Windows as the directory containing the driver and related files.
5. PWSETUP will prompt you for a modification of CONFIG.SYS. Respond with No. This will avoid having to modify it later. If this was missed for some reason, remark out or delete the Wollongong Group section of that file.
6. In AUTOEXEC.BAT add the bolded lines to the Wollongong section as indicated:

SET PATH=C:\PATHWAY;%PATH%
PWCONFIG -N:65
C:\WFW3.11\NET INIT ;this loads the device driver
NDIS -I:X -D:Y ;this loads the NDIS driver interface
C:\WFW3.11\NET START NETBIND ;this completes the binding process
PWTCP

Make sure that the NET START command is not executed at the beginning of AUTOEXEC.BAT.

The -I: parameter on the NDIS line refers to the IRQ level of the network card. Please verify your card setting and make sure the Pathway setting matches. Remember to use the hex value for 10 and above. Symptoms of an IRQ mismatch include slow connection speed, intermittent hanging or loss of connection, and kernel initialization failure.

The -D: parameter on the NDIS line refers to the bracketed section in your protocol.ini file which contains your card name and settings. For example, if the sixth section in your protocol.ini contains this information, the NDIS line should read -D:6. Errors which indicate “unable to bind” or “incomplete binding” can be resolved by double-checking this value and/or verifying that the protocol.ini contains the proper information for your network card.

Once you have installed Pathway, reboot the machine. Watch for any errors. If no errors occur, first try to ping at a DOS prompt, then make sure Windows for Workgroups loads successfully. You should then be able to use FTP, telnet or NFS to connect to your host.

Century Software, Inc., has had requests for two enhancements to the TinyTERM uninstall:

1. Combine TinyTERM and NetUtils into a single entry in Add/Remove Programs. This is problematic, as TinyTERM, TinyTERM Plus, TinyTERM Web Server and TinyTERM Web Server Client all share a single install. NetUtils is a separate install process spawned when TinyTERM Plus is selected.
2. Create an uninstall shortcut on the Windows Start menu.

CR 817

This error from the TinyTERM install means that the attempt to write the license to the registry failed. In most cases you can add the license through License Manager immediately after install completes.

If that also fails, verify that you are logged in as a local PC administrator. You must have administrator rights to install TinyTERM.

TinyTERM 4.50 gives this error for an evaluation install, regardless of the user rights or version of Windows. That was fixed in TinyTERM 4.52.

TinyTERM Web Server Client also gives this error on install. When that happens, start the TinyTERM Emulator from the Start menu. You’ll get a “product not licensed” error. Click the 30-day Eval button. Select TinyTERM Web Server from the list, then click OK. TinyTERM Web Server Client will run normally after that, and will not expire.

CR 790, TinyTERM 4.50
CR 812, TinyTERM Web Server Client