[gui-talk] Double Talk problem
Mike Freeman
k7uij at panix.com
Sat Dec 29 22:24:39 CST 2007
I think that one had SSIL drivers, i.e., one of the synth choices was
DoubleTalk external with SSIL drivers.
Mike
----- Original Message -----
From: Cindy Handel
To: NFBnet GUI Talk Mailing List
Sent: Saturday, December 29, 2007 7:07 PM
Subject: Re: [gui-talk] Double Talk problem
Mike,
That's one of the first things I did. But, it still doesn't work.
I'm
about to give up. I don't know what else to try. It works perfectly
on my
neighbor's computer. He's using an older version of JAWS, 6.1, but I
can't
see why that would make a difference.
Cindy
----- Original Message -----
From: "Mike Arrigo" <n0oxy at charter.net>
To: "NFBnet GUI Talk Mailing List" <gui-talk at nfbnet.org>
Sent: Saturday, December 29, 2007 11:14 AM
Subject: Re: [gui-talk] Double Talk problem
You might need to disable the buffering on your port, some times that
can
cause problems. Go in to your device manager, and go down to the ports
option. Press the right arrow key to expand it, then select com 1. Now
press
alt+enter to open the properties. Go to the port settings tab, make
sure
it's set for 9600 baud, now tab to advanced, then uncheck the option
to use
buffering. Select ok as many times as needed to close everything and
see if
that makes a difference.
----- Original Message -----
From: "Cindy Handel" <cindy425 at verizon.net>
To: "NFBnet GUI Talk Mailing List" <gui-talk at nfbnet.org>
Sent: Friday, December 28, 2007 8:35 PM
Subject: Re: [gui-talk] Double Talk problem
> Hi,
>
> The Doubletalk doesn't say any of the garbage when disconnected from
the
> computer. I did try to connect my cell phone to transfer
information
> between it and the computer, using Bitpim, this past summer. But, I
> couldn't get Bitpim to work, and I believe it was trying to use com
1. I
> uninstalled the program, but maybe it did something to the port? I
just
> don't know how to fix it. I've tried everything people have
suggested and
> it still doesn't work.
>
> Cindy
> ----- Original Message -----
> From: "Mike Arrigo" <n0oxy at charter.net>
> To: "NFBnet GUI Talk Mailing List" <gui-talk at nfbnet.org>
> Sent: Friday, December 28, 2007 7:34 PM
> Subject: Re: [gui-talk] Double Talk problem
>
>
> If you unplug the doubletalk from the computer, then turn it on,
does it
> still speak the garbage? It probably won't, but it's worth checking.
Did
you
> install anything recently that uses a com port? It sounds like
another
> program has taken over the port. Programs such as microsoft active
sync,
and
> other programs for p d a devices will some times do this.
> ----- Original Message -----
> From: "Cindy Handel" <cindy425 at verizon.net>
> To: "NFBnet GUI Talk Mailing List" <gui-talk at nfbnet.org>
> Sent: Friday, December 28, 2007 11:42 AM
> Subject: Re: [gui-talk] Double Talk problem
>
>
> > Hi Steve,
> >
> > I did select the port through JAWS, originally. It has always
been set
to
> > com 1, until recently. After the battery died and I replaced it,
I
turned
> > the Doubletalk on and that's when it starts the stream of
characters.
It
> > says, "Doubletalk ready", and then
> > starts --------u--------a--------o-------, etc. I can't get all
the
> > letters, and sometimes it says something like 0$. If I try to
change
> > synthesizers when it's on com 1, JAWS won't switch at
all...Eloquence
> > continues to talk. If I have it set to com 2, Eloquence stops
talking,
as
> > it should, but the Doubletalk continues with the dashes, etc.
> >
> > Cindy
> > ----- Original Message -----
> > From: "Steve Jacobson" <steve.jacobson at visi.com>
> > To: "NFBnet GUI Talk Mailing List" <gui-talk at nfbnet.org>
> > Sent: Friday, December 28, 2007 12:04 PM
> > Subject: Re: [gui-talk] Double Talk problem
> >
> >
> > Cindy,
> >
> > Usually, if you have one serial connector, it is assigned to COM1.
This
> > isn't always the case, though, so if that doesn't
> > work, other options will have to be tried. If you have an
internal
modem,
> > even though it is not physically connected to a
> > port, it uses a "COM" address.
> >
> > In your original note, you mentioned that the DoubleTalk spoke a
string
of
> > characters that didn't seem to mean anything.
> > Which port was it assigned to then, and what caused the speech to
start?
> > For example, did reading the current line in
> > JFW result in garbage being spoken, or did it seem to be random?
If any
> > activity of JFW seemed to result in characters
> > being spoken, you probably chose the correct port number.
> >
> > However, please explain where you are setting the port number?
You
> > mentioned a DoubleTalk CD. Do you also select
> > the port through JFW as well? You might need someone who has more
> > experience with the DoubleTalk in particular
> > than do I, but if the DoubleTalk was already used once on your
computer,
> I'm
> > not certain what the role of the
> > DoubleTalk CD is. If there are no answers here, someone on NFBCS
might
> > know.
> >
> > On Fri, 28 Dec 2007 09:35:10 -0500, Cindy Handel wrote:
> >
> > >Hi Steve,
> >
> > >It's an external synthesizer. I'll check the settings and make
sure
the
> > >port and Doubletalk match. I just don't know how I determine
what port
> > >number it's actually plugged into. It seems like it should be
one,
> because
> > >that's the only one I have. There is the printer port, but
that's
> > >different. Internally, I guess the modem is connected to
something,
but
> I
> > >don't know if that's specified as a port.
> >
> > >Cindy
> > >----- Original Message -----
> > >From: "Steve Jacobson" <steve.jacobson at visi.com>
> > >To: "NFBnet GUI Talk Mailing List" <gui-talk at nfbnet.org>
> > >Sent: Thursday, December 27, 2007 11:55 PM
> > >Subject: Re: [gui-talk] Double Talk problem
> >
> >
> > >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
> >
> >
> >
> >
> > >_______________________________________________
> > >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
> >
> >
> > _______________________________________________
> > 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
>
_______________________________________________
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
-------------- next part --------------
I think that one had SSIL drivers, i.e., one of the synth choices was DoubleTalk external with SSIL drivers.
Mike
----- Original Message -----
From:
mailto:cindy425 at verizon.net Cindy Handel
To:
mailto:gui-talk at nfbnet.org NFBnet GUI Talk Mailing List
Sent:
Saturday, December 29, 2007 7:07 PM
Subject:
Re: [gui-talk] Double Talk problem
Mike,
That's one of the first things I did. But, it still doesn't work. I'm
about to give up. I don't know what else to try. It works perfectly on my
neighbor's computer. He's using an older version of JAWS, 6.1, but I can't
see why that would make a difference.
Cindy
----- Original Message -----
From: "Mike Arrigo" < mailto:n0oxy at charter.net n0oxy at charter.net
>
To: "NFBnet GUI Talk Mailing List" < mailto:gui-talk at nfbnet.org gui-talk at nfbnet.org
>
Sent: Saturday, December 29, 2007 11:14 AM
Subject: Re: [gui-talk] Double Talk problem
You might need to disable the buffering on your port, some times that can
cause problems. Go in to your device manager, and go down to the ports
option. Press the right arrow key to expand it, then select com 1. Now press
alt+enter to open the properties. Go to the port settings tab, make sure
it's set for 9600 baud, now tab to advanced, then uncheck the option to use
buffering. Select ok as many times as needed to close everything and see if
that makes a difference.
----- Original Message -----
From: "Cindy Handel" < mailto:cindy425 at verizon.net cindy425 at verizon.net
>
To: "NFBnet GUI Talk Mailing List" < mailto:gui-talk at nfbnet.org gui-talk at nfbnet.org
>
Sent: Friday, December 28, 2007 8:35 PM
Subject: Re: [gui-talk] Double Talk problem
> Hi,
>
> The Doubletalk doesn't say any of the garbage when disconnected from the
> computer. I did try to connect my cell phone to transfer information
> between it and the computer, using Bitpim, this past summer. But, I
> couldn't get Bitpim to work, and I believe it was trying to use com 1. I
> uninstalled the program, but maybe it did something to the port? I just
> don't know how to fix it. I've tried everything people have suggested and
> it still doesn't work.
>
> Cindy
> ----- Original Message -----
> From: "Mike Arrigo" < mailto:n0oxy at charter.net n0oxy at charter.net
>
> To: "NFBnet GUI Talk Mailing List" < mailto:gui-talk at nfbnet.org gui-talk at nfbnet.org
>
> Sent: Friday, December 28, 2007 7:34 PM
> Subject: Re: [gui-talk] Double Talk problem
>
>
> If you unplug the doubletalk from the computer, then turn it on, does it
> still speak the garbage? It probably won't, but it's worth checking. Did
you
> install anything recently that uses a com port? It sounds like another
> program has taken over the port. Programs such as microsoft active sync,
and
> other programs for p d a devices will some times do this.
> ----- Original Message -----
> From: "Cindy Handel" < mailto:cindy425 at verizon.net cindy425 at verizon.net
>
> To: "NFBnet GUI Talk Mailing List" < mailto:gui-talk at nfbnet.org gui-talk at nfbnet.org
>
> Sent: Friday, December 28, 2007 11:42 AM
> Subject: Re: [gui-talk] Double Talk problem
>
>
> > Hi Steve,
> >
> > I did select the port through JAWS, originally. It has always been set
to
> > com 1, until recently. After the battery died and I replaced it, I
turned
> > the Doubletalk on and that's when it starts the stream of characters.
It
> > says, "Doubletalk ready", and then
> > starts --------u--------a--------o-------, etc. I can't get all the
> > letters, and sometimes it says something like 0$. If I try to change
> > synthesizers when it's on com 1, JAWS won't switch at all...Eloquence
> > continues to talk. If I have it set to com 2, Eloquence stops talking,
as
> > it should, but the Doubletalk continues with the dashes, etc.
> >
> > Cindy
> > ----- Original Message -----
> > From: "Steve Jacobson" < mailto:steve.jacobson at visi.com steve.jacobson at visi.com
>
> > To: "NFBnet GUI Talk Mailing List" < mailto:gui-talk at nfbnet.org gui-talk at nfbnet.org
>
> > Sent: Friday, December 28, 2007 12:04 PM
> > Subject: Re: [gui-talk] Double Talk problem
> >
> >
> > Cindy,
> >
> > Usually, if you have one serial connector, it is assigned to COM1. This
> > isn't always the case, though, so if that doesn't
> > work, other options will have to be tried. If you have an internal
modem,
> > even though it is not physically connected to a
> > port, it uses a "COM" address.
> >
> > In your original note, you mentioned that the DoubleTalk spoke a string
of
> > characters that didn't seem to mean anything.
> > Which port was it assigned to then, and what caused the speech to start?
> > For example, did reading the current line in
> > JFW result in garbage being spoken, or did it seem to be random? If any
> > activity of JFW seemed to result in characters
> > being spoken, you probably chose the correct port number.
> >
> > However, please explain where you are setting the port number? You
> > mentioned a DoubleTalk CD. Do you also select
> > the port through JFW as well? You might need someone who has more
> > experience with the DoubleTalk in particular
> > than do I, but if the DoubleTalk was already used once on your computer,
> I'm
> > not certain what the role of the
> > DoubleTalk CD is. If there are no answers here, someone on NFBCS might
> > know.
> >
> > On Fri, 28 Dec 2007 09:35:10 -0500, Cindy Handel wrote:
> >
> > >Hi Steve,
> >
> > >It's an external synthesizer. I'll check the settings and make sure
the
> > >port and Doubletalk match. I just don't know how I determine what port
> > >number it's actually plugged into. It seems like it should be one,
> because
> > >that's the only one I have. There is the printer port, but that's
> > >different. Internally, I guess the modem is connected to something,
but
> I
> > >don't know if that's specified as a port.
> >
> > >Cindy
> > >----- Original Message -----
> > >From: "Steve Jacobson" < mailto:steve.jacobson at visi.com steve.jacobson at visi.com
>
> > >To: "NFBnet GUI Talk Mailing List" < mailto:gui-talk at nfbnet.org gui-talk at nfbnet.org
>
> > >Sent: Thursday, December 27, 2007 11:55 PM
> > >Subject: Re: [gui-talk] Double Talk problem
> >
> >
> > >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" < mailto:k7uij at panix.com k7uij at panix.com
>
> > >>To: "NFBnet GUI Talk Mailing List" < mailto:gui-talk at nfbnet.org 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
> > >> mailto:gui-talk at nfbnet.org gui-talk at nfbnet.org
> > >> http://www.nfbnet.org/mailman/listinfo/gui-talk 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
> >
> >
> >
> >
> > >_______________________________________________
> > >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
> > mailto:gui-talk at nfbnet.org gui-talk at nfbnet.org
> > http://www.nfbnet.org/mailman/listinfo/gui-talk http://www.nfbnet.org/mailman/listinfo/gui-talk
> >
> >
> > _______________________________________________
> > gui-talk mailing list
> > mailto:gui-talk at nfbnet.org gui-talk at nfbnet.org
> > http://www.nfbnet.org/mailman/listinfo/gui-talk http://www.nfbnet.org/mailman/listinfo/gui-talk
>
> _______________________________________________
> gui-talk mailing list
> mailto:gui-talk at nfbnet.org gui-talk at nfbnet.org
> http://www.nfbnet.org/mailman/listinfo/gui-talk http://www.nfbnet.org/mailman/listinfo/gui-talk
>
>
> _______________________________________________
> gui-talk mailing list
> mailto:gui-talk at nfbnet.org gui-talk at nfbnet.org
> http://www.nfbnet.org/mailman/listinfo/gui-talk http://www.nfbnet.org/mailman/listinfo/gui-talk
>
_______________________________________________
gui-talk mailing list
mailto:gui-talk at nfbnet.org gui-talk at nfbnet.org
http://www.nfbnet.org/mailman/listinfo/gui-talk http://www.nfbnet.org/mailman/listinfo/gui-talk
_______________________________________________
gui-talk mailing list
mailto:gui-talk at nfbnet.org gui-talk at nfbnet.org
http://www.nfbnet.org/mailman/listinfo/gui-talk http://www.nfbnet.org/mailman/listinfo/gui-talk
More information about the gui-talk
mailing list