segedy@cspi.com (Cathy Segedy) (07/31/89)
hello. I just acquired a MACIIcx with AUX 1.1 and am having a bit of trouble with tip. Basically, if I call a non-MAC site, it refuses to recognize my <CR> (^M) as such. Now I am aware that the AUX by default maps all <crtl-M> to <crtl-J>, but I cannot seem to get it to recognize it just in tip, without wrecking havoc on my normal work. I have tried setting eol in my .tiprc file, and I have tried setting the eol characters in the /etc/remote file, and I have tried various combinations of settings to stty right before the tip. All to no avail. Has anyone solved this problem (or even seen it, for that matter?). Also, I have tried to change the modem type to hayes or ventel, but it doesn't like that at all. I feel I am doing something seriously wrong, but I've tried everything I can think of. hhhheeeelllllppppp.......!!!!! thanks in advance, cathy segedy PS- probably it would be best to send replies directly to me, and I will summerize to the net if/when I get it to work. decvax!cspi!segedy apollo!cspi!segedy
cander@unisoft.UUCP (Charles Anderson) (08/02/89)
From article <374@cspi.cspi.com>, by segedy@cspi.com (Cathy Segedy): > I just acquired a MACIIcx with AUX 1.1 and am having a bit of trouble > with tip. Basically, if I call a non-MAC site, it refuses to recognize my > <CR> (^M) as such. Now I am aware that the AUX by default maps all <crtl-M> > to <crtl-J>, but I cannot seem to get it to recognize it just in tip, without > wrecking havoc on my normal work. I have tried setting eol in my .tiprc > file, and I have tried setting the eol characters in the /etc/remote file, > and I have tried various combinations of settings to stty right before > the tip. All to no avail. Has anyone solved this problem (or even seen it, > for that matter?). Also, I have tried to change the modem type to hayes > or ventel, but it doesn't like that at all. I feel I am doing something > seriously wrong, but I've tried everything I can think of. The A/UX version of tip has a few "features" that are not present in the BSD version. Most of them that I've noticed are related to port configuration and can be worked-around using stty. It works best if you're running from a multi-window system such as X or term. You can run tip in one window and use stty from the other. Unfortunately, there are two sets of terminal configurations you need to worry about: tip's stdin (/dev/ttypx) and the output port (/dev/tty[01]). I've encountered your problem before, but I can't remember what the cause was. It was either the ICRNL flag on stdin or the OCRNL flag on the output port, or both (I hacked both in my version of tip). From the other window, after tip is running, you can run "stty -n /dev/ttypx -icrnl" or "stty -n /dev/tty[01] -ocrnl". If you do muck with icrnl, you'll have to set "el=\r" in /etc/remote, or you'll never be able to exit tip, because it never sees "<EOL>~.". You can use this technique to achieve any arbitrary port configuration on either the input or the output. Regardless of the options you use, you don't need to reverse them when you quit tip, as it should restore your tty to the state it was in when it started, before either you or tip screwed with the ports. -- Charles. {sun, amdahl, ucbvax, pyramid, uunet}!unisoft!cander
michael@xanadu.COM (Michael McClary) (08/04/89)
In article <374@cspi.cspi.com> segedy@cspi.com (Cathy Segedy) writes: > >hello. > I just acquired a MACIIcx with AUX 1.1 and am having a bit of trouble >with tip. Basically, if I call a non-MAC site, it refuses to recognize my ><CR> (^M) as such. This sounds to me like the mac tip is exhibiting correct behavior (forwarding the keys as struck) and the remote site is rejecting carriage return. This sometimes happens because parity detection is enabled at the remote site. Try specifying the partity ("pa=none", "pa=even", "pa=odd", "pa=one", or "pa=zero") in the /etc/remote entry for the troublesome sites.