Path: utzoo!attcan!uunet!wuarchive!mit-eddie!uw-beaver!sumax!ole!thebes!happym!irv
From: irv@happym.wa.com (Irving Wolfe)
Newsgroups: comp.sys.next
Subject: Re: Incorrect interpretation of "RETURN" key from TIP
Message-ID: <1143@happym.wa.com>
Date: 2 Nov 90 07:07:53 GMT
References: <1124@happym.wa.com>
Organization: Happy Man Corp., Seattle
Lines: 31

In <1124@happym.wa.com> pat@happym.wa.com (Patrick Tate) writes:

>The problem we are seeing is that the shell running on the Motorola system
>will not interpret the "RETURN KEY" from the NeXT terminal as a signal to
>execute the entered command. We can force the execution by sending out a cntl-J
>and are then are able to login and execute commands on the Motorola system. We
>can type return then cntl-J and see that the shell is attempting to execute
>the cntl-M entered by hitting return.

We got the solution with help from NeXT technical support.  The problem was
that outgoing characters from both tip and uucico were being generated with
parity bits.  These are the tricks to turning off parity:

For tip, insert the following additional parameter into /etc/remote for the
line being used --
 pa=none
(This will be delimited with : like the other parameters.)

For uucico, insert the following fragment into the chat script at its
beginning, right after ABORT BUSY if you use that --
 "" P_ZERO

I hope this saves someone else some trouble.  

Thank you, readers who tried to help Pat by mail, and thank you, NeXT, for
providing the solution that worked.
-- 
 Irving Wolfe    Happy Man Corp.   irv@happym.wa.com    206/463-9399 ext.101
 4410 SW Point Robinson Road,  Vashon Island, WA  98070-7399     fax ext.116
 SOLID VALUE, the investment letter for Benj. Graham's intelligent investors
Information free (sample $20 check or credit card): email patty@happym.wa.com