Xref: utzoo comp.dcom.modems:1805 unix-pc.general:634 unix-pc.uucp:15 Path: utzoo!utgpu!water!watmath!clyde!mtune!bakerst!cgh!amanue!jr From: jr@amanue.UUCP (Jim Rosenberg) Newsgroups: comp.dcom.modems,unix-pc.general,unix-pc.uucp Subject: Re: UNIX PC modem autobaud detect by uugetty Keywords: modem, unixpc, uugetty Message-ID: <279@amanue.UUCP> Date: 30 Apr 88 04:08:59 GMT References: <716@rush.cts.com> Reply-To: jr@amanue.UUCP (Jim Rosenberg) Organization: Amanuensis Inc., Grindstone, PA Lines: 29 In article <716@rush.cts.com> bob@rush.cts.com (Bob "Rush" Ames) writes: >I've been trying to get my 2400 Baud external modem to work on >my 3B1. It dials out OK, but when answering the phone, I can't >seem to figure out how to get my uugetty to change baud rate from >2400 to 1200. As Ken Brassler noted, there is definitely a bug in the 3.51 tty000 driver that eats the very null uugetty needs to tell it to change baud rates. You may or may not have your switch settings right, but that's probably not the problem. I haven't gotten the Fixdisk, but I gather from unix-pc traffic that the Fixdisk for 3.51 fixes this. You might be able to toggle from 2400 -> 1200 with luck if your gettydefs entry is exactly right -- be sure you're stripping parity. It seems to me that in trying to nail down the tty000 bug I determined that if the talker is at 1200 and the listener is at 2400, an \r sent by the talker will be heard as two characters by the listener, one of which just happens, by the luck of the draw, to be 0x80. If your uugetty is stripping parity correctly \r should cause it to toggle from 2400 -> 1200. But once you land at 1200 you're stuck without the driver fix. I reported the tty000 problem to the hotline, and they sent me a new kernel, months before the fixdisk came out. I've been running it quite happily ever since. -- Jim Rosenberg CIS: 71515,124 decvax!idis! \ WELL: jer allegra! ---- pitt!amanue!jr BIX: jrosenberg uunet!cmcl2!cadre! /