Installing TERM Professional 3.3 on Window NT 4.0, you may see the error “Sesman.exe unable to locate rasapi32.dll.” This happens when RAS is not installed in Windows NT. To bypass the error, either uncheck the Desktop Manager option in the TERM Professional install, or install the RAS option on Windows before installing TERM Professional.

Using TERM on AIX 3.2.5, you may have problems using modems. In particular, you may need to power the modem off and on after starting TERM for it to connect.  Setup strings are the same (ATZ\r) for all three Motorola modems. To resolve this, apply the most recent AIX 3.2.5.5 service pack.

When TERM for UNIX returns a “device busy” error, but there are no lockfiles, there is a permission problem.  Verify the following:

• Permissions on /usr/bin/callin and /usr/bin/callout must be 4755 (-rwsr-xr-x).
• Permissions on the full structure of /usr/spool/uucp or /var/spool/uucp (Linux) must be at least 666 (-rw-rw-rw-). The directory itself, plus every directory and file within it, must have those permissions or higher. Lockfiles are placed in this directory.
• Permissions on the tty port itself must be at least 666 (-rw-rw-rw-).

Using TinyTERM on Windows NT 4.0, installing a Windows service packmay cause registry errors. Uninstalling and reinstalling TinyTERM should fix this. If you still have problems after that, do the following:

1. Uninstall TinyTERM and NetUtils through Control Panel.
2. Click the Start button.
3. Select Run.
4. Type in regedit and click OK
5. Click the + sign next to HKEY_Current_User.
6. Click the + sign next to Software.
7. Delete any “Century Software” or “NCD Software” folders.
8. Click the + sign next to HKEY_Local_Machine
9. Click the + sign next to Software.
10. Delete any “Century Software” or “NCD Software” folders.
11. Close the Registry Editor.
12. Open Windows Explorer or My Computer.
13. Delete any Century folders from C:\ and C:\Program Files.
14. Go to the Windows folder.
15. Delete any marathon.* or marsetup.* files listed there.
16. Reboot the PC.
17. Now install TinyTERM.

Using TinyTERM 3.3 with Citrix Winframe on Windows NT 3.51, it works properly on a client until it logs out. At this point the session on the Unix server is closed, but the TinyTERM window stays open. The only way to get rid of the window is through Task Manager.

Century Software, Inc., has never supported TinyTERM 3.3 or earlier versions in a terminal services environment. However, it may help to uninstall TinyTERM and run Scandisk on the hard drive. When that’s done, reboot and reinstall Tiny Term.

When TERM for UNIX gives the error, “Non-expired lockfile lck..inittab,” make sure the permissions on the whole structure of /usr/spool/uucp are at least 666 (-rw-rw-rw-).

For TERM for Linux, the directory path is normally /var/spool/uucp. If TERM for Linux is configured for /usr/spool/uucp instead, this error will result even if permissions are correct on /var/spool/uucp.

CR 277
CR 573, Linux spool directory fixed in TERM 6.28

TinyTERM version 4.x will run on Windows 95 or 98 if no Web browser is installed. It will run as a standalone application.

On such a system you may see error 1810 when installing TinyTERM. This is a cosmetic error that will not affect its functionality.

Using TinyTERM or TERM for Windows, Alt keys are ignored in the emulator by default, even if you’ve remapped them. Under the keyboard configuration there is a check box labeled, “Use Alt keys in emulation.” That needs to be set; otherwise, Windows uses the Alt keys.

Note that in TinyTERM versions prior to 4.0, and by extension all versions of TERM for Windows, that Alt-F4 can be remapped, but Windows will still read it. This will of course close the emulator, no matter what mapping you may have set for it.

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.