[Time-saving (?) information by Zube, January 17, 2000.] Below are two termcap entries for use with informix. The first one, vt100, works very well using teraterm/ttssh on a PC; F1-F10 all work. The second one, wvt100, works well using a wyse (wy-55) terminal in vt100 emulation. To get this to work on (for example), a Solaris 7 box running informix (and the user is using /bin/csh or /usr/local/bin/tcsh), you must have a line that points to the file. To wit, if you save the second entry into /usr/local/etc/mytermcap, you'll do setenv TERMCAP /usr/local/etc/mytermcap somewhere (perhaps in your .login) before your tset line: set noglob; eval `tset - - -kb -Q -s -m 'dialup:vt100' -m 'network:vt100' 'vt100'`; unset noglob Note that I did not have to hack any of the terminfo files to get this to work with informix. Also note that they are both called vt100. This is by design. If you wish to use both, save both entries to separate files and point each TERMCAP variable to each file as needed. Anyway, without further ado: # # PC vt100 (teraterm/ttssh) with F1-F10 function key support # Zube@stat.colostate.edu modified the informix termcap # v1|vt100|vt-100|DEC vt100:\ :bs:am:xn:xv:pt:cd=\E[J:ce=2\E[K:cl=45\E[H\E[J:\ :cs=%i\E[%d;%dr:cm=%i\E[%d;%dH:co#80:li#24:\ :Hi=\E=:Hf=\E>:HI=^|:Po=\E1:Pe=\E2:\ :bc=\E[D:do=\E[B:nd=\E[C:sr=\EM:up=\E[A:so=\E[7m:se=\E[m:\ :ku=\E[A:kd=\E[B:kr=\E[C:kl=\E[D:kh=\E[H:us=\E[4m:ue=\E[0m:\ :k0=\E[11~:k1=\E[12~:k2=\E[13~:k3=\E[14~:\ :k4=\E[15~:k5=\E[17~:k6=\E[18~:k7=\E[19~:k8=\E[20~:k9=\E[21~:\ :KA=\EOu:KU=\EOM:KB=\EOv:KC=\EOt:\ :Ki=\EOr:KT=\EOl:KY=\EOS:KZ=\EOq:\ :Kd=\EOm:k6=\EOs: \ :sc=\E7:rc=\E8: \ :gs=\E(0:ge=\E(B:gb=lmkjqxntuvw: # # Wyse-55 in vt100 emulation mode with F1-F10 function key support # Zube@stat.colostate.edu modified the informix termcap # v1|vt100|vt-100|DEC vt100:\ :bs:am:xn:xv:pt:cd=\E[J:ce=2\E[K:cl=45\E[H\E[J:\ :cs=%i\E[%d;%dr:cm=%i\E[%d;%dH:co#80:li#24:\ :Hi=\E=:Hf=\E>:HI=^|:Po=\E1:Pe=\E2:\ :bc=\E[D:do=\E[B:nd=\E[C:sr=\EM:up=\E[A:so=\E[7m:se=\E[m:\ :ku=\E[A:kd=\E[B:kr=\E[C:kl=\E[D:kh=\E[H:us=\E[4m:ue=\E[0m:\ :k0=\EOP:k1=\EOQ:k2=\EOR:k3=\EOS:\ :k4=\E[M:k5=\E[17~:k6=\E[18~:k7=\E[19~:k8=\E[20~:k9=\E[21~:\ :KA=\EOu:KU=\EOM:KB=\EOv:KC=\EOt:\ :Ki=\EOr:KT=\EOl:KY=\EOS:KZ=\EOq:\ :Kd=\EOm:k6=\EOs: \ :sc=\E7:rc=\E8: \ :gs=\E(0:ge=\E(B:gb=lmkjqxntuvw: ####################################################################### A few random notes: 1) I expunged all the color bits from the vt100 entry because otherwise it comes up as something like "bright eggshell" on "light eggshell." 2) For the record, real honest-to-goodness vt100s had neither color nor function keys F1-F10. They did, however, have PF1-PF4 (four keys above the keypad) that acted as function keys. Sometimes termcaps will define F1-F4 as PF1-PF4 (this is how the second entry above does it) and leave the rest out, which is why I saw instances where keys above F4 would not work, but F1-F4 worked fine. 3) Link MC-5 terminals turn out to be (almost) completely useless under vt100 emulation because the F1-F5 keys *cannot* (to the best of my knowledge) be redefined when using a vt emulation. Instead, these keys do exactly as labeled on the keyboard, i.e. setup, break, etc. Indeed, when one tries to redefine these keys in the setup, the first key available is F6. The keys can be redefined under other emulations, i.e. tvi925. 4) Note that different wyse-55 terminals *seem* (I can't stress that enough) to emulate vt100 differently. For example, I had one terminal that worked fine and another that left garbage everywhere even though the two were the same model with the same firmware. After much head banging, if I compared *all* (I mean every single one, including the tab ) settings and set the bad one to the settings of the good, all was well. But I'm not kidding about the *all* part.