[gui-talk] Double Talk problem

Mike Freeman k7uij at panix.com
Fri Dec 28 11:51:41 CST 2007 

I also wonder whether the connection speeds on the DoubleTalk and port 
match.

And several years ago when I used an external DoubleTalk (I still have 
it), it worked better with a SSIL driver and JAWS than it did with the 
straight port connection. Ah well.

Mike

  ----- Original Message ----- 
  From: Steve Jacobson
  To: NFBnet GUI Talk Mailing List
  Sent: Friday, December 28, 2007 9:04 AM
  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
-------------- next part --------------
I also wonder whether the connection speeds on the DoubleTalk and port match.
 
And several years ago when I used an external DoubleTalk (I still have it), it worked better with a SSIL driver and JAWS than it did with the straight port connection. Ah well.
 
Mike
 
----- Original Message -----
From:
mailto:steve.jacobson at visi.com Steve Jacobson
To:
mailto:gui-talk at nfbnet.org NFBnet GUI Talk Mailing List
Sent:
Friday, December 28, 2007 9:04 AM
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

More information about the gui-talk mailing list