From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by listman.back-rdu.redhat.com (8.11.6/8.11.6) with ESMTP id hB8DTvR10398 for ; Mon, 8 Dec 2003 08:29:57 -0500 Received: (from mail@localhost) by int-mx1.corp.redhat.com (8.11.6/8.11.6) id hB8DawW25961 for blinux-list@listman.back-rdu.redhat.com; Mon, 8 Dec 2003 08:36:58 -0500 Received: from mx1.redhat.com (mx1.redhat.com [172.16.48.31]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with SMTP id hB8Dav225956 for ; Mon, 8 Dec 2003 08:36:57 -0500 Received: from mirapointmr3.wayne.edu (IDENT:mirapoint@mirapointmr3.wayne.edu [141.217.1.113]) by mx1.redhat.com (8.11.6/8.11.6) with SMTP id hB8Dav208358 for ; Mon, 8 Dec 2003 08:36:57 -0500 Received: from lmaschm.cit.wayne.edu (lmaschm.cit.wayne.edu [141.217.4.24]) by mirapointmr3.wayne.edu (Mirapoint Messaging Server MOS 3.3.2-CR) with ESMTP id APH86423; Mon, 8 Dec 2003 08:36:56 -0500 (EST) Received: (from lmaschm@localhost) by lmaschm.cit.wayne.edu (8.12.10/8.12.10/Submit) id hB8DaAsg008030 for blinux-list@redhat.com; Mon, 8 Dec 2003 08:36:10 -0500 Date: Mon, 8 Dec 2003 08:36:10 -0500 From: Lee_Maschmeyer@wayne.edu To: blinux-list@redhat.com Subject: Re: debian install issue solved Message-ID: <20031208133610.GA7995@wayne.edu> Mail-Followup-To: blinux-list@redhat.com References: <6.0.0.22.2.20031205094828.01b1dda0@wiscmail.wisc.edu> <16336.45197.4719.348717@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <16336.45197.4719.348717@localhost.localdomain> User-Agent: Mutt/1.4.1i X-Loop: blinux-list@redhat.com Sender: blinux-list-admin@redhat.com Errors-To: blinux-list-admin@redhat.com X-BeenThere: blinux-list@redhat.com X-Mailman-Version: 2.0.13 Precedence: junk Reply-To: blinux-list@redhat.com List-Help: List-Post: List-Subscribe: , List-Id: Linux for blind general discussion List-Unsubscribe: , List-Archive: But what's the operative principle here? Apparently the VT100 was sending an inappropriate response, but I don't see how the terminal version can in and of itself make a difference - waiting for input is waiting for input. Could it be something in end-of-line or echo or something? Lee On Fri, Dec 05, 2003 at 11:21:33AM -0500, Dave Hunt wrote: > Thanks for sharing your solution to this. I find it timely, as I'm > considering a Debian install, using either Speakup or an external > terminal as a serial console. If I go with Speakup, my external > doubletalk would be the synthesizer. For the serial console option, > I'd run a terminal emulator on my braillenspeak 640. This box now has an old version of RH, > but, I may want to try another distro, and, Debian looks like a worthy > candidate. > > > -Dave > > > > > > John> I've been stuck since last weekend on a debian install via a > John> serial console. > > John> I'm using Hyperterminal on a Windows PC as the terminal. And > John> I found that the problem went away if I switched the > John> emulation from VT100 to ANSI. So it didn't have anything to > John> do with the baud rate or the flow control. When I left it > John> last night it was downloading packages so by now I may have > John> a functioning system. > > > _______________________________________________ > Blinux-list mailing list > Blinux-list@redhat.com > https://www.redhat.com/mailman/listinfo/blinux-list