Using TinyTERM 3.3 on Windows 95, it hangs when clicking the Modem button in the communications setup screen. This will happen if the modem is not configured correctly in Windows. You can do that through Control Panel.

If the modem looks like it’s set up correctly, but TinyTERM still hangs when trying to configure it, delete the modem from Windows. Reboot the PC and re-add it. That will refresh the modem driver.

Using TinyTERM Plus Edition 4.02 on Windows 98, a modem session connects properly. However, once connected the keyboard response is extremely slow, and it seems like it is using all the laptop’s system resources.

This happens when the baud rate for the modem is set too high; i.e., 115,000. Lower the baud rate in Control Panel to match the remote host’s maximum speed. If there is no exact match, use the baud rate that is just higher than the host’s.

This happens on Windows 95 when the modem is listed twice in Control Panel. HyperTerminal can ignore the second modem, but TinyTERM 3.3. and earlier versions can’t. Deleting the duplicate modem will solve the problem.

In TinyTERM versions through 4.21, and TERM versions through 7.2, the maximum scrollback buffer size is 999 lines. This was extended to thousands of lines in version 4.30.

Century Software, Inc., has also had a request to make the scrollback buffer infinite, removing the size limitation altogether. For practical purposes the buffer will always be limited by system memory, whether or not this is ever implemented.

CR 613, increase buffer
Cr 761, infinite buffer

If you need to map a non-printable character such as Escape or Tab to a key, there are a couple of ways to do this. On Windows versions of TERM or TinyTERM, do one of the following:

• In the keyboard mapper, drag the desired key into the Clipboard in the bottom left. You can then drag it from that clipboard to any other key on the keyboard.
• Click on the key you want to remap. Change the Action drop-down to MACRO. In the Value, enter the ASCII value of the key between angle brackets <>. For example, Ctrl-T is ASCII value 20, so it would be entered as <20>.
  You can also enter the control character somewhat literally, again inside the angle brackets. In that case, you’d put the caret ^ in front of the appropriate letter. For example, Ctrl-T would be entered as <^T>.

For DOS or UNIX products, you would use the SETKEY command. You can put the character in quotes directly, preceded by a ^ character:

setkey F5 “^X”

For a complete list of ASCII values, see www.robelle.com.

The SETKEY command redefines a key on the keyboard. The key then sends a different character of string of characters when pressed. SETKEY can also be used to cause a key to run a TinyTERM script or call one of TinyTERM’s internal functions.

The syntax for SETKEY is:

setkey keyname value

The keyname may be any of the following:

• F1 – F12 (Function keys 1 – 12)
• AF1 – AF12 (Alt-Function keys: hold the Alt key and hit F1 – F12)
• SF1 – SF12 (Shift-Function keys)
• CF1 – CF12 (Ctrl-Function keys)
• CSF1 – CSF12 (Ctrl-Shift-Function keys)
• “a” – “z” (Lower-case letters a-z, must be in quotation marks)
• “A” – “Z” (Capital letters A-Z)
• “^a” – “^z” (Ctrl- keys a-z)
• AltA – AltZ (Alt keys a-z, Windows may override)
• “0” – “9” (Top row number keys)
• kp0 – kp9, kp+, … (keypad number and symbol keys, NumLock must be on)
• c-kp0 – c-kp9, … (Ctrl-keypad number and symbol keys)
• “#”, “$”, … (Any symbol)
• up, home, end, … (Named keys)
• c-up, c-right, … (Named Ctrl-keys)

Only the letter keys are case-sensitive. The other keys can be typed upper- or lower-case for the SETKEY command.

The value may be one of the following:

• A single character or string of characters in quotation marks. This may include:
  • a special string character
  • \x42 – a hex value preceded by \x
  • \072 – an octal value preceded by \
  • ^M – a control character
  • or any other valid TERM string sequence
• the name of a pre-defined TERM function key such as PRINT or BREAK
• “@@command” – A valid TERM Script Language command

Examples

• setkey f1 “MyLoginName”
  causes the F1 key to send MyLoginName down the comm line.
  
• setkey “b” “MyPassword”
  causes the lower-case b key to send MyPassword down the comm line.
• setkey kp* abort
  causes the keypad * key to send the standard abort, usually ^C.
• setkey pgup “@@cls”
  causes the PageUp key to run TERM’s cls (clear screen) command.
• setkey SF1 “@@do myfile”
  causes the Shift-F1 key to run the TERM script myfile.cmd.
• setkey F11 “@@do wtermus@w_file_quit
  causes the F11 key to run the w_file_quit procedure within the TERM script wtermus.cmd.

To install TERM for UNIX manually, login as root or a user with equivalent permissions. Then do the following:

1. Create the directory where TERM will reside:
   

   md /usr/term

2. Copy the install files into this directory.
3. Extract (untar) the files. For example:
   

   tar xvf cmdfile1.tar
tar xvf cmdfile2.tar
tar xvf cmdfile3.tar
tar xvf termi6.tar

   Replace termi6.tar with the correct install file. You may not have the separate cmdfile#.tar files either, depending on your flavor of UNIX.

4. Move the term, callin and callout files to /usr/bin:
   

   mv term callin callout /usr/bin

5. Change permissions on the moved files:
   

   chmod 555 /usr/bin/term
chmod 4755 /usr/bin/callin /usr/bin/callout

6. Brand the TERM executable with the command:
   

   ./brand /usr/bin/term

   Enter your serial number and activation key when prompted to do so. Please remember that both are case-sensitive.

The install will be complete at this point.

On a PC with no hard drive, you can make a boot disk that also runs TinyTERM for DOS. To do that, insert a floppy into a system already running DOS, one that has TinyTERM installed as well. From the DOS prompt, execute this command:

format /s

This will make the diskette bootable. Next, copy the following files from the root of C: to the floppy:

COMMAND.COM (may already be in place)
AUTOEXEC.BAT
CONFIG.SYS

Edit the AUTOEXEC.BAT and CONFIG.SYS files on the floppy to remove all information relating to the C: drive. You want it stripped to the bare minimum required to use DOS.

Finally, copy the following files from the TinyTERM directory to the floppy:

default.con
tt.exe (the main executable, not the stub)
tt.ini
tt.sys
langus.str
ttsetup.exe
comnul.kdl
vidram.kdl
emansi.kdl
comasy.kdl

The files comnul.kdl and vidram.kdl are required .kdl files.

Next, copy the *.kdl file for the emulation you will be using. For example, if you are using ANSI or SCOANSI emulation, get the emansi.kdl file listed above. For WYSE60 emulation, get the emwy60.kdl file. Similar files exist for other emulations.

Finally, copy the *.kdl file for the kind of connection you will make. These files will begin with “COM.” For example, the comasy.kdl file listed above is for asynchronous connections, serial or RS232. For the Wollongong TCP/IP, get the comwol.kdl file.

Space permitting, copy over any other *.kdl files you may use in the future.

This error comes up from TinyTERM Plus 3.2 on Windows 98 when installing LPD. It happens despite the directory C:\Century clearly containing the necessary information.

To get rid of the error, do the following:

1. Remove the Marlpd icon from the system tray by right-clicking it and selecting Exit.
2. Type Ctrl-Alt-Del and end all marlpd tasks that show.
3. Go into the Century directory and run marlpd manually.

Using TinyTERM Plus or TERM Professional in Windows 95 or Windows 98, if the LPD server will not start, do the following:

1. Right-click on the hammer-and-wrench icon in the system tray, next to the clock on the Start bar.
2. Select Exit from the pop-up menu.
3. Right-click on Network Neighborhood.
4. Select Properties.
5. Select Century Internet Services.
6. Click on the Properties button.
7. Click on the Options tab.
8. Remove the check from the box in front of “Start Internet Services at Windows startup.”
9. Click OK and OK again.

You will now be able to configure the LPD server and use it.