From owner-freebsd-questions Tue Jan 2 10:45:35 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA02885 for questions-outgoing; Tue, 2 Jan 1996 10:45:35 -0800 (PST) Received: from ncc-1701-d.starfleet.gov (root@ix-sb1-13.ix.netcom.com [204.32.201.45]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA02877 for ; Tue, 2 Jan 1996 10:45:31 -0800 (PST) Received: (from d_burr@localhost) by ncc-1701-d.starfleet.gov (8.6.11/8.6.9) id KAA00421; Tue, 2 Jan 1996 10:49:35 -0800 Date: Tue, 2 Jan 1996 10:49:34 -0800 (PST) From: Donald Burr X-Sender: d_burr@ncc-1701-d To: Stephen Couchman , questions@freebsd.org Subject: Re: iijpp STILL cannot talk to my modem :-(( In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org Precedence: bulk On Tue, 2 Jan 1996, Donald Burr wrote: > [...my solution...] To further elaborate, when you used tip and cu to access your modem, it worked, because AFAIK tip/cu don't indiscriminately set crtscts on the port they're accessing. In fact, most programs don't. This is why /etc/rc.serial exists, so that default parameters for each serial port can be set. If you had a high speed modem and tried using it with tip/cu, CRTSCTS would not be enabled, and because the modems weren't handshaking, you'd end up with a lot of lost data and other nastiness due to the high modem speed.