Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!hplabs!pyramid!cal
From: cal@pyrtech.pyramid.com (Craig Alan Levin)
Newsgroups: comp.sys.pyramid
Subject: Re: Targon/35: talk and sysline dont run correct / not
Message-ID: <142844@pyramid.pyramid.com>
Date: 29 Jan 91 19:47:53 GMT
Sender: daemon@pyramid.pyramid.com
Reply-To: cal@pyrtech.pyramid.com (Craig Alan Levin)
Distribution: comp
Organization: Pyramid Technology Corp., Customer Support, San Diego Yacht Racing
Lines: 25

In article <tc14bot.664816154@snimuc> 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 <term> and exits.
>     I tried TERM=ba80-08, dap4x, vt100; no one worked.
>     Is there a special termcap entry (which) ?

Only certain terminals have an addressable 25th row that can be used
by sysline.  Sysline has a few different options that do not require
the 25th row.  Please see the UCB man page.  It definitely works with
Wyse terminals.

>2)   talk user (or ucb talk user) says:
>     [Your Party is not logged on]
>     and exits
>     (of course the user is logged on!)
>
>     what to do ?

This sounds like a system administration problem.  Check to insure
that your /etc/inittab and /etc/ttys files agree as to the numbers and
designations of terminals.  ie.  if you are running ATT
init-getty-login and the user is on a port not specified in the
/etc/ttys file, the port information  will not be available to UCB
commands.