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

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.

The keyboard may be remapped to suit specific needs for each user. In addition, more than one keyboard mapping may be set up, and keyboard mappings may be distributed to other PCs. This document addresses keyboard mapping in Windows versions of TERM and TinyTERM.

To change the keyboard scheme
From the TinyTERM 3.x or TERM 7.x Configure menu, select Keyboard. The Keyboard Select dialog box is then displayed.

In TinyTERM 4.x, from the Edit menu select Session Properties, then the Keyboard tab.

From the drop-down list, select the keyboard scheme to load. To have the selected scheme take effect, click the OK button. To leave the keyboard scheme as is, click the Cancel button.

Edit
To edit an existing keyboard scheme, select it and click the Edit button. In TinyTERM 3.x or TERM 7.x, it will be saved under the same name automatically. In TinyTERM 4.x, click the Save As button when done editing, then give the same name it had before.

After clicking the Edit button, the Keyboard Editor dialog box comes up. Some of the buttons in this dialog box are described below. The more obvious buttons — such as Cancel — are not described in the interest of document length.

Create a new keyboard scheme
To create a new keyboard mapping scheme in TinyTERM 3.x or TERM 7.x, type a description in the Keyboard Scheme edit field and click the Edit button. In TinyTERM 4.x, click the Save As button and give the scheme a new name.

The keyboard editor
All the keys in the keyboard edit window accept several actions:

• Any key can be dragged and dropped on any other key to change the destination key to send the sequence of the source key. The label on the destination key will change to the new value, and the font will be bold to show that the key has been changed.
• Any key can be clicked on and the key name will appear in the Keyname list box for manual editing.
• When the Alt, Shift or Ctrl key is clicked, the keyboard will redraw to display the keys modified by the selected key. Shift and Ctrl may be combined, but Alt is used alone. Keys that do not display a value are generally not mappable, except for the space bar.

The key chart
Clicking the Chart Open button opens the TCS chart. Characters from the chart can be dragged to keys in the keyboard editor. The target key will be set to the value of the character dragged and dropped. Each page of the TCS chart can be viewed by clicking the buttons labeled 1, 2, 3 and 4 on the right side of the chart.

The functions chart can be displayed by clicking the F Button. TinyTERM functions can be dragged from this chart to any key.

Set button
This button can be used to set or apply the contents of the Value Viewer text box to the selected key.

The Reset button
Clicking this button resets the selected key to its default value.

The Clipboard
The Clipboard is a temporary holding area for keys and values. Use the clipboard to drag keys and values from modified keys to unmodified keys and to drag keys and values from unmodified keys to modified keys. More information is available here.

Copy keyboard mappings
To copy keyboard mappings to other PCs running TinyTERM 3.x or TERM 7.x, simply copy the current .tap file and the keyboard.dat file to a network or floppy drive. The files can then be copied onto the other PCs.

For TinyTERM 4.x, simply copy the keyboard.dat file. No other files are needed for the keyboard schemes.

Common macro values

Macro	Meaning	Keyboard
\E or ^[	Escape	Esc
^M or \r	Enter or carriage return	Enter
\n or ^J	line feed	Ctrl-J
^	control	Ctrl
\x##	hex string	(n/a)

Example
Typing Ctrl-E in TinyTERM 3.x executes the internal command ECMD by default. To remap Ctrl-E to the value ^E, do the following:

1. Open the Keyboard Editor.
2. After selecting the correct keyboard scheme, click the Edit button.
3. Click the CTRL key on the keyboard map.
4. Click the key labeled FN1 where the E key should be.
5. Notice under Keyname that “^E” is displayed, and in Value is shown “<ECMD>”.
6. Remove <ECMD> in the Value box.
7. Click the Chart Open button.
8. Click on the club symbol in the chart (5th symbol on the first row), then drag the symbol to the Value Viewer box. The club symbol on an ASCII chart is the same as ^E.
9. The club symbol will be displayed in the Value Viewer box. The Value will display “<517>”, which is the internal TCS value.
10. Click the Set button, then click OK. Typing Ctrl-E will now send ^E.

You can also view this information in a screencast by clicking here.

Windows Vista no longer supports Microsoft Help files. Opening the Help file in TinyTERM produces a message to that effect.

There is a Help compatibility module for Vista, available for download from Microsoft. But it doesn’t seem to work with TinyTERM. Installing it does not change the “not supported” message from TinyTERM’s Help.

CR 845

Using Windows XP, SecureFT reads zip files as directories. Uploading a zip file causes a new directory to be created on the host, and the individual files in the zip are uploaded into that directory. This is directly related to XP’s ability to show the contents of a zip as a virtual directory.

CR 806, fixed in TinyTERM Plus 4.53

Change the default dialog color in Windows. In TinyTERM, open the Session Properties and go to the Keyboard tab. Click the Edit button to bring up the keyboard map. Most of the keys shift to match the new dialog color. However, the background stays gray, as do the Ctrl, Shift and Alt keys.

CR 8

TinyTERM is a 32-bit application. However, it will install properly on 64-bit versions of Windows. You do not need to do anything special to install TinyTERM in these environments.

To run TinyTERM on a 64-bit Windows system, 32-bit compatibility must be installed in the OS. This is automatic in Windows 7 and later versions. No changes need to be made for TinyTERM to work properly in those environments.

For 64-bit versions of Windows XP or Vista, after installing TinyTERM test it for functionality. If there are any errors, close TinyTERM. Right-click on the TinyTERM shortcut and select Properties from the popup menu. Go to the Compatibility tab. On that tab, select a 32-bit compatibility mode. The “Windows XP service pack 2” option generally works well. TinyTERM will run normally with that option.

Century Software, Inc., has had a request to compile TinyTERM as a 64-bit application for that environment. To date this has not been done.

CR 795

Century Software, Inc., has had a request to make TinyTERM run as a service in Windows, rather than as a standard application. This has not been implemented thus far.

CR 699

You can disable the splash screen in TinyTERM 4.x with the -nosplash command-line parameter. Century Software, Inc., has received requests to make this available in the user interface as well. That has not been implemented thus far.

CR 27