[gui-talk] FW: Important: Kurzweil 1000 and WindowEyes

[W. Nick Dotson]

SAPI is a protocol, not a reference to a specific speech engine or synthesizer.  It refers to Version 5.x of Eloquence Eloquence that ships with WindowEyes, 
and Version 6.x which ships with Kurzweil 1000.  It is pretty clearly explained in Stephen Baum's message, so I'd encourage a rereading.

W. Nick Dotson

On Tue, 19 Dec 2006 19:22:40 -0500, slery wrote:

 Does this problem exist if you are using Sapi 5 in Kurzweil and Eloquence in
 WindowEyes?

 Cindy

 -----Original Message-----
 From: gui-talk-bounces at nfbnet.org [mailto:gui-talk-bounces at nfbnet.org]On
 Behalf Of Steve Pattison
 Sent: Tuesday, December 19, 2006 5:59 PM
 To: GUI Talk; Access-L
 Subject: [gui-talk] FW: Important: Kurzweil 1000 and WindowEyes



 >[mailto:k1000-owner at listserv.kurzweiledu.com] On Behalf Of Stephen Baum
 >To: k1000 at listserv.kurzweiledu.com
 >
 >Hello everyone.
 >
 >WindowEyes ships with version 5.0 of Eloquence. Kurzweil 1000, beginning
 >with version 11, ships with version 6.1 of Eloquence.
 >Unfortunately, since the company that makes Eloquence changed its name,
 >and hence its install folder, installation programs for one aren't aware
 >of the existance of the other. Even more unfortunately, the two versions
 >do not peacefully coexist on the same machine.
 >
 >If someone installs Kurzweil 1000 version 11 on a system that has
 >WindowEyes, or, for that matter, if they install WindowEyes on a system
 >that contains Kurzweil 1000 version 11, both copies of Eloquence will be
 >on the system, and both will be unstable. If the WindowEyes copy was
 >installed first, Kurzweil 1000 would probably not see either copy of
 >Eloquence. WindowEyes, if Eloquence is selected as the speech engine,
 >would see only its copy, but several error message boxes would be
 >displayed if attempts were made to access that engine.
 >Note, though, that WindowEyes does eventually succeed at using
 >Eloquence.
 >
 >If someone is in that situation, they should switch to a different
 >speech synthesizer in WindowEyes, and then uninstall the WindowEyes
 >version of Eloquence using the Add/Remove programs applet from the
 >control panel. Note that there will multiple uninstalls - one for
 >Eloquence common modules, and another for each language that was
 >installed. WindowEyes has no problem using the newer version of
 >Eloquence - at least none that we've found.
 >
 >If someone has WindowEyes and uses the Eloquence engine as their
 >synthesizer in WindowEyes, they have two choices to avoid this problem
 >before installing Kurzweil 1000.
 >
 >One choice - probably the preferred one - is to do what we recommended
 >above - switch to another synthesizer in WindowEyes temporarily, and
 >then uninstall Eloquence. Once that has been done, they can reboot and
 >install Kurzweil 1000. After the installation, they can switch to the
 >new version of Eloquence in WindowEyes if they wish.
 >
 >A second choice is to keep using the old version of Eloquence, and do a
 >custom installation of Kurzweil 1000, making sure that you do NOT
 >install Eloquence.
 >
 >Its worth noting, by the way, that if you keep Eloquence as your TTS
 >engine in WindowEyes and uninstall Eloquence, WindowEyes will come up
 >silently. Until you switch synthesizers (either by knowing the
 >keystrokes or using sighted assistance), your screen reader won't be
 >talking to you.
 >
 >Stephen

 Regards Steve
 Email:  srp at internode.on.net
 Skype:  steve1963
 MSN Messenger:  internetuser383 at hotmail.com
 _______________________________________________
 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



W. Nick Dotson
Technical Support Group
Senior Support Engineer for Kurzweil 1000
and K_NFB Reader
kurzweil1000support at kurzweiledu.com for e-mail and 800-894-5374
(followed by Option 5, then Option 2) for telephone.