[gui-talk] Double Talk problem
Steve Jacobson
steve.jacobson at visi.com
Thu Dec 27 22:55:35 CST 2007
Cindy,
Is your Double-Talk an external device? if so, it has to match the COM port assigned to the port into which you have it
plugged in. The fact that you already have a port assigned to COM1 probably makes it unavailable on some lists.
I believe the most likely reason for your problem is that when the Double-Talk battery went dead, you may have lost your
serial port settings. If your port is configured for 8 bits and no parity, but your Double-Talk is configured for seven bits
with even or odd parity, your computer will not identify some characters. Another computer that is set differently may
recognize the characters without a problem. Therefore be sure that your Double-Talk is set to the parity that your ports
are set to. Usually one sets both to 8 bit characters, no parity, and one stop bit. I do not own a double-talk, though, so
if another setting is suggested follow that setting, but make certain that the parameters agree. I also do not know how
port settings on the Double-Talk are changed. It is sometimes accomplished with switches but other times by going
through a setup menu.
On Thu, 27 Dec 2007 22:06:58 -0500, Cindy Handel wrote:
>Mike,
>What can I do to correct it? In looking around, when installing some
>software from the Doubletalk disk, it seems that it says port 1 isn't
>available. I don't know why. Two and three are, but I've tried those two
>ports and it's no better.
>Cindy
>----- Original Message -----
>From: "Mike Freeman" <k7uij at panix.com>
>To: "NFBnet GUI Talk Mailing List" <gui-talk at nfbnet.org>
>Sent: Thursday, December 27, 2007 9:58 PM
>Subject: Re: [gui-talk] Double Talk problem
>Most DoubleTalk sequences start with Control-E. Sounds like your port
>isn't allowing that character thru.
>Mike
> ----- Original Message -----
> From: Cindy Handel
> To: gui talk
> Sent: Thursday, December 27, 2007 2:18 PM
> Subject: [gui-talk] Double Talk problem
> I have a Double Talk connected to my com 1 port. I've used it before,
>but
> not for awhile.
> A few weeks ago, I tried to turn it on and found the battery was dead,
>so I
> replaced it. But, now, every time I turn it on, I get "Double Talk
>Ready"
> and then a string of letters and characters, along with dashes. I
>can't
> make JAWS 7.1 or 9 switch to Double Talk, even though it's checked in
>both
> versions.
> I took the Double Talk to my neighbor's house (he also uses JAWS), and
> connected and selected it as one of the synthesizer languages. It
>works
> perfectly, there.
> I don't know what the characters and dashes are all about, but I can't
>get
> it to work on my computer. As I said, It did before, but doesn't,
>now. The
> port appears to be configured correctly. If anyone has suggestions,
>I'd
> appreciate knowing what I might try.
> Thanks.
> Cindy
> "Determine that the thing can and shall be done, and then...find the
>way."
> Abraham Lincoln
> _______________________________________________
> gui-talk mailing list
> gui-talk at nfbnet.org
> http://www.nfbnet.org/mailman/listinfo/gui-talk
>--------------------------------------------------------------------------------
>_______________________________________________
>gui-talk mailing list
>gui-talk at nfbnet.org
>http://www.nfbnet.org/mailman/listinfo/gui-talk
>_______________________________________________
>gui-talk mailing list
>gui-talk at nfbnet.org
>http://www.nfbnet.org/mailman/listinfo/gui-talk
More information about the gui-talk
mailing list