i have a dectalk pc nullmodem com2 decpc emulated com3 dont think anythings on com1 it works if i type directory from dos directly At 01:04 PM 10/26/00 +1100, you wrote: >If the ports are on the isa bus they can't share an interrupt without the risc >of burning the bus driver. >Some synths _require_ the irq to show up and require to receive, but some dos >screen >readers do not use the interrupts, speakup needs to read from the synth. >On Wed, Oct 25, 2000 at 08:51:26PM -0500, Kirk Wood wrote: > > 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 at 1tree.net > > > > > > > > _______________________________________________ > > Speakup mailing list > > Speakup at braille.uwo.ca > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > >-- >-- >Kerry Hoath: kerry at gotss.eu.org >Alternates: kerry at emusys.com.au kerry at gotss.spice.net.au or khoath at lis.net.au >ICQ UIN: 62823451 > > >_______________________________________________ >Speakup mailing list >Speakup at braille.uwo.ca >http://speech.braille.uwo.ca/mailman/listinfo/speakup
