[nvda] Re: Possible Bug
- From: Lukas Loehrer <listaddr1@xxxxxxx>
- To: nvda@xxxxxxxxxxxxx
- Date: Sat, 27 Jan 2007 07:49:15 +0100
Storm Dragon writes ("[nvda] Possible Bug"):
> I am using the latest version of NVDA Binary posted to the site. When I went
> into the voice settings menu, the first time when I started arrowing around
> my computer froze and I had to restart to get it back. I tried it again, and
> this time, it froze as soon as I got into the dialog.
I am seeing the same problem here, even with the latest svn
version. All the nvda preferences dialogs work except for the voice
settings. I have espeak and eflite voices installed aside from the
three Microsoft voices and assumed so far the problem was due to none
of the additional voices. What SAPI 5 voices do you have installed?
Waht happens here is that nvda freezes as soon as I try to enter its
voices dialog. I also have the demos of jfw and window eyes installed.
There is some strange interaction with those two and this nvda
problem: After the freezing, only window eyes can start, jfw fails for
some reason. also narrator acts strangely afterwards. If I keep jfw
running while using nvda and then inter the voices dialog, jfw keeps
working after nvda freezes and I can ckill nvda via the task manager.
Best rgards, Lukas
To post messages to the list send email to
nvda@xxxxxxxxxxxxx
To unsubscribe from the list send a blank message to:
nvda-request@xxxxxxxxxxxxx
with 'unsubscribe' in the Subject field.
Thank you for your continued support of Nonvisual Desktop Access, an open
source free screen reader for Microsoft Windows:
http://www.kulgan.net/nvda/
- Follow-Ups:
- [nvda] Re: Possible Bug
- From: Michael Curran
- References:
- [nvda] Possible Bug
- From: Storm Dragon
Other related posts:
- » [nvda] Possible Bug
- » [nvda] Re: Possible Bug
- » [nvda] Re: Possible Bug
- » [nvda] Re: Possible Bug
- » [nvda] Re: Possible Bug
- » [nvda] Possible Bug
- » [nvda] Re: Possible Bug
- » [nvda] Re: Possible Bug
- [nvda] Re: Possible Bug
- From: Michael Curran
- [nvda] Possible Bug
- From: Storm Dragon