In the standalone TN3270 emulator, the Keyboard Mapper is not the same as the mapper in TinyTERM. Instead, it shows a 3270 Protocol Keys section at the top, and a PC Keyboard at the bottom.

The PC keys are in red and yellow. Pointing to any red key with the mouse causes an “Unmapped” message to appear at the bottom.

To the left of the 3270 Protocol Keys 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, use the left mouse button to drag the desired key from the 3270 Protocol Keys. Drop it on the red key you want mapped. The key will list its new assignment in black.

To save the mapping, exit the Keyboard Mapper. It will prompt you for a profile name, then save it. The next time you start 3270 emulation, select the desired profile to return to that key mapping.

To make changes to the key mappings under the any profile, open that profile. Go to the Keyboard Mapper to see and change that profile’s mappings.

In 1995 Century Software, Inc., produced a white paper on code pages. It includes information on what a code page is, and how code pages are used by TERM and TinyTERM.

Some of the information was later incorporated into TinyTERM documentation and help files. You can now download the original in Microsoft Word format here.

When you get the error “modem not responding,” there are several steps you can take:

1. Check to see that the modem is connected and turned on.
2. Check the modem initialization string in the modem setup:
   1. Make sure that the init string is correct for your modem. Check your modem documentation for details.
   2. If there is a “^M” at the first of that string, remove it.
   3. Make sure that there is a carriage return or line feed character at the end of that string: “^M” in DOS or Windows, or “\r” in UNIX.
3. Try using a slower baud rate.
4. Ensure the modem is functioning by using HyperTerminal in Windows, cu in UNIX, or by typing echo ath1>comx (where “x” is the COM port that the modem resides on) at the command prompt in DOS.

There is also one known issue with TERM for UNIX, documented here.

Many problems can occur if Pathway is not properly configured. Here are some things to check in case of errors, slowness and lockups. Please be aware that some specific files may not be used; i.e., ODI installation does not use protocol.ini.

Installing

• ODI: lsl.com and a *.com network card driver must be loaded.
• NDIS: Use either the *.mac or *.dos driver and the protocol.ini supplied by the network card manufacturer.
• PDS: This is a packet driver. It’s often unstable in Windows, so not recommended.
• Dedicated: Only use a dedicated driver for one of the listed network cards. Even so, we recommend ODI or NDIS instead.
• ASI: This is used by token ring networks. It is similar to a normal NDIS installation and just as easy to troubleshoot.

Winsock.dll
There should be only one. Any others will need to be renamed. Make sure the winsock.dll you use belongs to the TCP/IP or transport layer in use.

The -I: option is the interrupt of the network card or COM port
Run the network card setup utility to verify the interrupt of the card. Also, verify that there are no conflicts with this IRQ and other hardware.

pwconfig.exe -N: should be different than the network card
This is an interrupt vector or software interrupt. The default for Wollongong is 65. Valid numbers are 60-66. Most network cards are on 60 or 61. Recommended numbers are 63, 65 and 66.

Check for errors on boot. Concentrate on the error description, not the number. The brief description tells more than the number. If a technician can find the error number, chances are it will be the same description. Do not worry if there are two error numbers and one description. They will be related.

NET.CFG syntax
Order and spacing are critical. In general, the order should be: “Wollongong” group, “Link driver” section, “Wollongong” group, and then extra additions such as buffers, Novell DOS requesters, etc. Make sure the frames are correct.

PROTOCOL.INI
Verify the ndis.exe -d: argument is pointing to the right [driver] section. You may also need to verify the protocol.ini file being used. You may find copies in multiple places: C:\Windows, C:\Pathway\Lanman, etc.

In Windows for Workgroups, make sure Windows has loaded the right network driver and that NetBEUI is running correctly.

IP addresses
Check to see if it is a duplicate or otherwise incorrect. Errors that occur from this are PC lockups, lost connection, and read/write errors.

A simple way to check for duplicate IP addresses is to change the PC’s address, then ping the old address.

Subnet mask bits
Make sure they are the same as other computers on the subnet. This will also cause PC lockups, lost connections and read/write errors.

STAT.EXE
Run this at a DOS prompt. Three parameters need to be checked:

• stat 2: Physical address of the network card. If it’s all zeroes, Pathway is not loaded or not loaded properly. Pathway needs to see the card, unless you are using PPP or SLIP.
• stat 3: Resolved IP addresses. If this reports no resolved addresses, the TCP stack could still be the problem. If there is a resolved address and there is still no reply from the ping, the problem is on the other end of the connection, not the PC.
• stat 4: This gives the local IP address and subnet mask bits.

Patch
Download the updated PCHRUN.EXE. Replace the existing copy on the PC with the new file.

Update the network card driver
Get latest drivers for network card from the manufacturer. Generally, the manufacturer’s website will have the files to download.

Watch for cards that do not support multiple protocols
Some older network cards only support one protocol at a time; e.g., IPX or NDIS. This is not common. If either protocol loads and connects properly when run alone, but combined one or the other fails, then it does not support multiple protocols.

Adjust Windows
See our other documents on NDIS, ODI and Windows 95 configuration.

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.

Flow control issues in file transfer can manifest several different ways in a TERM-to-TERM environment. CRC errors typically occur. Often a file can only be transferred one direction. Only a portion of the file transfers, or perhaps none at all. There are several troubleshooting steps:

1. Make sure you have selected the same protocol on both sides.
2. Login to the remote system and put it in the server mode appropriate to the protocol. Server mode is invoked with term -1x for WTERMCRC, or term -x for TERMCRC.
3. Initiate the file transfer by doing an XFER or GET. Enter the complete path in the source or destination directory, or use a period . for the default directory. Transfers from UNIX to DOS require that file conversion be turned on as well.
4. If you still cannot transfer the file, you may have flow control problems. You may have to turn flow control off, location by location, beginning with your modem if possible. Flow control is turned off in each modem differently, so see your modem documentation.
5. The next location to turn flow control off is in TERM itself. This is done by editing the .termsys file in the user’s home directory or the C:\Term directory. Add the following entry in the “!file transfer” section:
   

   protocol NONE

   This must be done in TERM on both sides.

6. If the file will still not transfer, try turning flow control off at the unix ports themselves. The UNIX command stty -a display the “ixon,” “ixany” and “ixoff” flow control parameter settings. The command stty -ixany will turn off “ixany,” and the command stty ixany will turn it on. You will need to experiment with various combinations of these flow control parameters.

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.

With TinyTERM for DOS set for SCOANSI emulation, the UNIX TERM environment variable set to ansi or ansic, and the WPTERM environment variable set to either term or termcolor, the following lines can be added to the tt.rc file to allow TinyTERM to work with WordPerfect 5.0 for UNIX.

setkey sf10 reset
setkey f10 reset
setkey cf10 reset
setkey kp- "\E[-" !keypad -
setkey kp+ "\E[+" !keypad +
setkey c-home "\E[E" !Ctrl-Home
setkey c-pgup "\E[J" !Ctrl-PgUp
setkey c-pgdn "\E[K" !Ctrl-PgDn
setkey c-end "\E[0" !Ctrl-End
setkey c-left "\E[1" !Ctrl-LeftArrow
setkey c-right "\E[2" !Ctrl-RightArrow
setkey c-enter "\E[3" !Ctrl-Enter
setkey c-bs "\E[4" !Ctrl-BackSpace
setkey s-tab "\E[5" !Shift-Tab
setkey "^H" "\E{h" !Ctrl-H
setkey "^Q" "\E{q" !Ctrl-Q
setkey "^S" "\E{s" !Ctrl-S
setkey af1 "\E[w" !Map Ctrl-Shift-Fkeys to Alt-Fkeys
setkey af2 "\E[x"
setkey af3 "\E[y"
setkey af4 "\E[z"
setkey af5 "\E[@"
setkey af6 "\E[["
setkey af7 "\E["
setkey af8 "\E[]"
setkey af9 "\E[\^"
setkey af10 "\E[_"
setkey alta "\E|a" !Assign sequences to Alt-A through Alt-Z
!setkey altb "\E|b" ! Not mapped for default break key.
!setkey altc "\E|c" ! Not mapped for default compose key.
setkey altd "\E|d"
setkey alte "\E|e"
setkey altf "\E|f"
setkey altg "\E|g"
!setkey alth "\E|h" ! Not mapped for hot key.
setkey alti "\E|i"
setkey altj "\E|j"
setkey altk "\E|k"
setkey altl "\E|l"
setkey altm "\E|m"
setkey altn "\E|n"
setkey alto "\E|o"
!setkey altp "\E|p" ! Not mapped so we can print.
setkey altq "\E|q"
setkey altr "\E|r"
!setkey alts "\E|s" ! Not mapped so we can run setup.
setkey altt "\E|t"
setkey altu "\E|u"
setkey altv "\E|v"
setkey altw "\E|w"
!setkey altx "\E|x" ! Not mapped so we can exit.
setkey alty "\E|y"
setkey altz "\E|z"

You may want to comment out different lines than those selected above. The ones commented out are the default keys used by TinyTERM.

The Wollongong TCP/IP stack included with TinyTERM Plus NFS for DOS includes an NFS client that allows a DOS PC to use UNIX printers. To print using NFS, Wollongong TCP/IP must be running. It then requires the following steps:

1. At the DOS prompt type NFS, then press Enter. If NFS has been installed correctly, the following screen will be displayed:
   

   Century Client NFS for DOS (Version 2.0)
   Copyright (C) 1990,1993 The Wollongong Group.

   If the above lines are not displayed or an error message is received, check the NFS installation guide and try again.

2. The host system must be running version 2 of the pcnfsd daemon. To confirm this, log into the host and run the following command:
   

   rpcinfo -p

   This program can usually be found in the /usr/etc directory. If you can not run this program, you may not have permissions. Talk to your system administrator to use this program. Assuming you can run the above command, you will see a screen similar to the following:

   program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
150001 1 udp 1028 pcnfsd
150001 2 udp 1028 pcnfsd
150001 1 tcp 1024 pcnfsd
150001 2 tcp 1024 pcnfsd
100003 2 udp 2049 nfs
100005 1 udp 1027 mountd
100024 1 udp 1042 status
100024 1 tcp 1025 status
100020 1 udp 1050 llockmgr
100020 1 tcp 1026 llockmgr
100021 2 tcp 1028 nlockmgr
100017 1 tcp 1027 rexd
100021 1 tcp 1029 nlockmgr
100021 1 udp 1062 nlockmgr


   Under the program column you will be looking for the number 150001. Under the vers column you will need the number 2. You must have pcnfsd version 2 in order for the NFS services to work. Versions 1 and 2 can run in conjunction. If you only have version 1 running, you will have to upgrade to version 2 on your host.

3. Determine which hosts on your network are running NFS services. To do this, type the following:
   

   mount /n

   This command may take a few seconds to process, depending on the number of servers available and the current network traffic. It will return a screen similar to the following:

   NFS SERVERS
(192.168.0.25) century
(192.168.0.13) sconfs
(192.168.0.12) scoodt
(192.168.0.10) rs6000
4 servers available on your subnet.

   If no servers are available, talk with your network administrator.

4. Next you will need to see which servers, if any, have print services available. To do this, use the /l option along with the hostname in question. For example:
   

   mount /l century

   A screen similar to the following will be displayed:

   NAME DEVICE LOCATION
---------- ------------ ---------------
sunprint Local
epson1 /dev/lp0 Local

   Note that the sunprint line above doesn’t show a device. On some systems this is normal.

5. You are now ready to mount an NFS printer. In the example above, you might enter the following at the DOS prompt:
   

   mount lpt1 century:/sunprint user passwd

   In the above example the host is century, the printer is sunprint device, the username is user, and the password is passwd. If auth had been run, it would not be necessary to add the username or password, although doing so would not cause any problems.

   If all went well, you will see a line similar to the following:

   Device lpt1 redirected to \century\/sunprint successfully

Troubleshooting Tips
If you get “permission denied” or “invalid path” when mounting the printer:

1. Using the rpcinfo command outlined above, verify that pcnfsd version 2 is up and running on the NFS server.
2. Verify that the spool directory has been exported by looking for /usr/spool/pcnfs (or higher) in the /etc/exports file.
3. From the DOS prompt, type mount /e servername. You should see /usr/spool or higher directory exported.
4. Verify that you can mount /usr/spool and that you have permissions of 777 by copying a file to /usr/spool. On some systems the directory will be /var/spool instead.
5. From the DOS prompt execute PWSETUP and select View Current Settings. Make a note of the PC’s IP address, the user id and hostname of the PC. On the server, verify that the PC’s hostname is in the /etc/hosts file.
6. Finally, if you have any logical links to /usr/spool, verify that the linked file as well as /usr/spool is also exported.

cron allows users and administrators to run unattended jobs at any time. Although this document provides examples, you should refer to your UNIX documentation for details specific to your environment.

On older versions of UNIX (pre-System V or Berkeley), cron was only accessible to the system administrator with root or superuser capabilities. If you are using a newer version of UNIX, you should have access to cron. If not, consult with the system administrator.

To run TERM as a background application using cron, do the following:

1. Set the PATH environment variable to include the directory where the TERM executable is installed, normally /usr/bin.
2. Set the TERM environment variable to the correct terminal emulation.
3. Set the HOME environment variable to your home directory. This is normally done by default.
4. Export the above three environment variables.
5. Have CRON run the shell script in background mode as follows:
   

term -q &

You must use the -q option and the ampersand &. If you do not use the -q option, you will see multiple copies of the error, “EOF error on console”.To have TERM run a TSL script when the system is rebooted, you must have a shell in the /etc/rc2.d directory that invokes TERM.