From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ignatious.1tree.com(c716099-a.rchdsn1.tx.home.com[24.7.105.70]) (1478 bytes) by braille.uwo.ca via smail with P:esmtp/D:aliases/T:pipe (sender: ) id for ; Wed, 25 Oct 2000 21:45:49 -0400 (EDT) (Smail-3.2.0.102 1998-Aug-2 #2 built 1999-Sep-5) Received: from cpt.kirk (helo=localhost) by ignatious.1tree.com with local-esmtp (Exim 3.12 #1 (Debian)) id 13ocCU-0000Aj-00 for ; Wed, 25 Oct 2000 20:51:26 -0500 Date: Wed, 25 Oct 2000 20:51:26 -0500 (CDT) From: Kirk Wood X-Sender: cpt.kirk@ignatious.1tree.com To: speakup@braille.uwo.ca Subject: Re: partial success - still need help In-Reply-To: <5.0.0.25.0.20001025201144.009e09b0@wapvi.bc.ca> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII List-Id: On Wed, 25 Oct 2000, tyler spivey wrote: > ok, i can make speakup probe for my decpc, i set speakup for decext. > i am using commo term prog, i set capture to com3 mode raw. > when i use say line or shut up, it takes several minutes to process the data. > what could cause this? would dectalk express driver cause a better delay? I am guessing your synth is on what DOS would call com1. As such it would be sharing an IRQ with com3. Since they share an IRQ when you issue a command for the synth, it must wait in line for the activity on com3 to subside. The answer isn't drivers. The answer is reconfigure your hardware. In dos you can actually make continous use of com1 com2 and com5. Skip 3 and 4. ======= Kirk Wood Cpt.Kirk@1tree.net