🚀 go-pugleaf

pete@extro.ucc.su.OZ.AU (Peter Alexander Merel) writes:

 >I`ve been trying for some time (since term 107 - I just tried term 111, to
 >no avail) to get term to connect between a Solaris 1.1 box and my Solaris
 >2.3 sparcclassic at home, with no success. Term works okay on the remote
 >end from a linux box, so I know that ain't the problem. 

 >From the 2.3 box I connect using cu. I then run term remotely, and then try
 >to run it locally using term < /dev/cua/a > /dev/cua/a. Both ends tell me

 >Term version: 1.11

 >Then, in another local window, I type trsh. At this point, all hell breaks 
 >loose:

 >On the remote end I see:

 >Term version: 1.11

 >~c`f<160><226>`$<170>"f<225><231><160><222><189><232>q<225>`$<184><243>"c`f<160>
 ><226>`$<170><243>"f<225><231><160><222><189><232>q<225>`$<184><243>"c`f<160><226
 >>`$<170><243>"f<225><231><160><222><189><232>q<225>`$<184><243>"c`f<160><226>`$<
 >170><243>"f<225>

 >and so on. On the local end:

 >:timed out at 53 trans 1
 >:timed out at 53 trans 1
 >:timed out at 54 trans 2
 >:timed out at 53 trans 2
 >:timed out at 53 trans 3
 >:timed out at 53 trans 3
 >:timed out at 53 trans 4
 >:timed out at 53 trans 4

 >and so on. A friend of mine was able to get term to run under Solaris 2.0, but
 >since he upgraded to 2.3 he has the same problem. Has anyone been able to run
 >term under Solaris 2.3? How? What am I doing wrong? Any and all help deeply
 >appreciated, and many many thanks in advance.

 >-- 
 >Internet: pete@extro.su.oz.au          |         Accept Everything.            |
 >UUCP: {uunet,mcvax}!munnari!extro!pete |         Reject Nothing.               |

I am running exactly the same setup successfully.  The binaries I ran on
Solaris 2.1 ran just fine with Solaris 2.3.  I am now running 1.11.  First
of all, I establish the connection with tip and use the <CR>~Cterm sequence
to launch the local term after I have launched the remote term in my console
window.  Here is my remote entry:

#
# the two zs (built-in) serial ports
#       38.4K bps, hardware flow control
#
cuaa:\
        :dv=/dev/cua/a:br#38400:el=^C^S^Q^U^D:ie=%$:oe=^D:nt:hf:
cuab:\
        :dv=/dev/cua/b:br#38400:el=^C^S^Q^U^D:ie=%$:oe=^D:nt:hf:


It is difficult to tell which side is entering the error messages.  Start
term on both ends with output redirected to a log file.  You may have to
start from ksh and use stderr redirection as well.

If you have not run linecheck, you need to do so to make sure something is
not eating characters somewhere in between.  I am running with nothing
escaped or ignored except for ^X for exit.


-- 
  R.Stewart(Stew) Ellis, Assoc.Prof., (Off)313-762-9765   ___________________
  Humanities & Social Science,  GMI Eng.& Mgmt. Inst.    /   _____  ______ 
  Flint, MI 48504      ellis@nova.gmi.edu               /        / /  /  / /
  Gopher,News and  modem   maintainer, all around hack /________/ /  /  / /