Incomplete Termcap Entry

[db1]

My ISP is using Cobalt Raq2.&nbsp;&nbsp;I have been having problems in Telnetting.&nbsp;&nbsp;Once I login to the server and I am trying to use Pico it will give me an error &quot;Incomplete Termcap Entry&quot;.&nbsp;&nbsp;When I call the ISP and tell them about it, they saying that it is working fine on their end.&nbsp;&nbsp;I get this error like 75% of the time sometimes it would work.<br><br>Anyone has any ideas or solutions?

 

[AndyBo]

When you log in, what is TERM set to?&nbsp;&nbsp;(<FONT FACE=monospace>echo $TERM</font>)&nbsp;&nbsp;You may find it's set to something like &quot;unknown&quot;.&nbsp;&nbsp;If that's the case, check what your TERM is set to in the shell your running telnet from, and set it to be the same when you log in to your ISP.<br><br>If you want to make this permanent you can then put it into your .profile in your home directory.

 

[frtillman]

When you log in, what is TERM set to? <br><br>@ the prompt type in <br><br>&quot;set&quot; AND THEN &quot;env&quot;<br><br>NOTICE THE VALUE OF &quot;TERM=&quot;<br><br>you can then make sure that the tlnet session is using the correct termtype<br><br>if you match them up you should have no problem IF by chance you system is using W3.11 or DOS6.22 or LOWER make sure the ansi.sys driver is loaded in the config.sys But if you r using W3x or DOS6.2 Why r u even computing? forget the statement I am just typing out loud some old stuff I remembered.<br><br><br>

 

[mikeadams]

Pine complains about an incomplete termcap entry whenever $TERM is set to something it doesn't know about - It's sort of lame. An easy way to get around this is to do this when starting pine<br><br>export TERM=vt100 ¦ pine filename<br><br>this will set the TERM variable to the default vt100 term (which every telnet program known to man supports), and pine should work fine from there.. If not, try vt102, instead of vt100..<br>