Path: utzoo!censor!geac!torsqnt!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!cs.utexas.edu!uunet!rbj From: rbj@uunet.UU.NET (Root Boy Jim) Newsgroups: comp.sys.pyramid Subject: Re: Targon/35: talk and sysline dont run correct / not Message-ID: <120570@uunet.UU.NET> Date: 30 Jan 91 01:56:24 GMT References: <142844@pyramid.pyramid.com> Distribution: comp Organization: UUNET Communications Services, Falls Church, VA Lines: 26 In article <142844@pyramid.pyramid.com> cal@pyrtech.pyramid.com (Craig Alan Levin) writes: >In article tc14bot@snimuc.tc14.stm.sni.de (Richard Bothe) writes: >>on our Targon/35 TOS 3.3.08 talk and sysline dont run well. >> >>1) sysline says: No status capability for and exits. >> I tried TERM=ba80-08, dap4x, vt100; no one worked. >> Is there a special termcap entry (which) ? > I've never heard of a ba80-08 or dap4x. The vt100 has a settable scrolling region and two termcap entrys which use the top and bottom line for a status line. You only get 23 lines left over. Unless Pyramid is different, TERM should be one word, not three. >>2) talk user (or ucb talk user) says: >> [Your Party is not logged on] >> and exits >> (of course the user is logged on!) You may also have to use ntalk for different machines, and you may want to use it even for local talking. -- Root Boy Jim Cottrell Close the gap of the dark year in between