Hello!

You have Vocalizer SAPI5 by KobaSpeech and by LetsTalk, a israelian company.
Tiflotecnia solds its own Vocalizer for NVDA, and also Eloquence SAPI5 from CodeFactory.


Regards,

Rui Fontes
Tiflotecnia, Lda.


-----Mensagem Original-----
De: Isaac
Data: segunda-feira, 2 de maio de 2016 09:16
Para: nvda@nvda.groups.io
Assunto: [nvda] codefactory eloquence and vocalizer


Hi, anyone recommend this addon, is the vocalizer as good as the other vocalizer, and is codefactory offering a sapi of just eloquence or vocalizer as well.
Thanks

In ny opinion, remove all addons and then removethat version of NVDA.
Install the version 2016.1 or the last Next or Master version of NVDA
without any addons, and see if the problem still exist...

Rui


-----Mensagem Original-----
De: Sharni-Lee Ward
Data: segunda-feira, 2 de maio de 2016 17:17
Para: nvda@nvda.groups.io
Assunto: Re: [nvda] NVDA still freezing, don't know what the deal is

It just happened AGAIN. This time, with no Braille Display plugged in,
but still in Word. My sister described what she saw as "It's circling
and the screen is foggy," so I'm assuming it was hanging. It took longer
than normal to shut down, and longer than normal to start up properly,
and apparently Windows Explorer lagged for a few seconds. I don't know
how to recover my writing (I tried one of the previous times this
happened by restoring the auto recovery file from the Recycle bin but it
didn't work...).


Anyways, here's the log. I hope this time I can get an answer for why
this is happening. I'm getting seriously concerned at this point.


INFO - __main__ (00:26:15):
Starting NVDA
INFO - core.main (00:26:19):
Config dir: C:\Users\pc\AppData\Roaming\nvda
INFO - core.main (00:26:20):
NVDA version brltbl20160315
INFO - core.main (00:26:20):
Using Windows version 6.1.7601 service pack 1 workstation
INFO - core.main (00:26:20):
Using Python version 2.7.11 (v2.7.11:6d1b6a68f775, Dec 5 2015,
20:32:19) [MSC v.1500 32 bit (Intel)]
INFO - core.main (00:26:20):
Using comtypes version 0.6.2
INFO - external:synthDrivers.ptenglish.SynthDriver.__init__ (00:26:24):
Using eSpeak version 1.48.03 04.Mar.14
INFO - synthDriverHandler.setSynth (00:26:24):
Loaded synthDriver ptenglish
INFO - core.main (00:26:24):
Using wx version 3.0.2.0 msw (classic)
INFO - braille.initialize (00:26:24):
Using liblouis version 2.6.5
INFO - braille.BrailleHandler.setDisplayByName (00:26:24):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - brailleInput.initialize (00:26:24):
Braille input initialized
INFO - core.main (00:26:25):
NVDA initialized
INFO - braille.BrailleHandler.setDisplayByName (00:27:25):
Loaded braille display driver freedomScientific, current display has 40
cells.
ERROR - queueHandler.flushQueue (00:33:30):
Error in func _handleUpdate from eventQueue
Traceback (most recent call last):
File "queueHandler.pyc", line 50, in flushQueue
File "virtualBuffers\__init__.pyc", line 674, in _handleUpdate
File "braille.pyc", line 1645, in handleUpdate
File "braille.pyc", line 906, in update
File "textInfos\offsets.pyc", line 346, in expand
File "virtualBuffers\__init__.pyc", line 314, in _getUnitOffsets
File "textInfos\offsets.pyc", line 328, in _getUnitOffsets
File "virtualBuffers\__init__.pyc", line 256, in _getParagraphOffsets
WindowsError: [Error 1775] A null context handle was passed from the
client to the host during a remote procedure call


On 3/05/2016 12:15 AM, Sharni-Lee Ward wrote:

Just tried another thing that consistently got NVDA to hang recently,
namely, opening the sounds manager in Control Panel and then arrowing to
the Sound Scheme tab. I thought it only did this because of the Braille
Display but I wanted to test it to make sure. This time, once the window
was closed, NVDA started responding again. I also tried to activate
Narrator but it didn't work, though as I said, that didn't end up
mattering. Here's the log for that session, though I warn you, the
warning repeats itself several times. In case each warning was subtly
different, I copied the whole thing. Don't worry about the Braille error
that shows up first—that's about me starting up the computer and by
extension NVDA without my display plugged in and then saving the
configuration with default as No Braille.


INFO - __main__ (18:51:56):
Starting NVDA
INFO - core.main (18:51:59):
Config dir: C:\Users\pc\AppData\Roaming\nvda
INFO - core.main (18:52:00):
NVDA version 2016.1
INFO - core.main (18:52:00):
Using Windows version 6.1.7601 service pack 1 workstation
INFO - core.main (18:52:00):
Using Python version 2.7.11 (v2.7.11:6d1b6a68f775, Dec 5 2015,
20:32:19) [MSC v.1500 32 bit (Intel)]
INFO - core.main (18:52:00):
Using comtypes version 0.6.2
INFO - external:synthDrivers.ptenglish.SynthDriver.__init__ (18:52:10):
Using eSpeak version 1.48.03 04.Mar.14
INFO - synthDriverHandler.setSynth (18:52:11):
Loaded synthDriver ptenglish
INFO - core.main (18:52:11):
Using wx version 3.0.2.0 msw (classic)
INFO - braille.initialize (18:52:11):
Using liblouis version 2.6.5
ERROR - braille.BrailleHandler.setDisplayByName (18:52:11):
Error initializing display driver
Traceback (most recent call last):
File "braille.pyo", line 1447, in setDisplayByName
File "brailleDisplayDrivers\freedomScientific.pyo", line 179, in
__init__
RuntimeError: No display found
INFO - braille.BrailleHandler.setDisplayByName (18:52:11):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - brailleInput.initialize (18:52:11):
Braille input initialized
INFO - core.main (18:52:12):
NVDA initialized
INFO - braille.BrailleHandler.setDisplayByName (19:30:34):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - config.ConfigManager.save (19:30:39):
Base configuration saved
WARNING - watchdog._watcher (23:47:35):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_espeak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

WARNING - watchdog._watcher (23:47:50):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_espeak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

WARNING - watchdog._watcher (23:48:05):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_espeak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

WARNING - watchdog._watcher (23:48:20):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_espeak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

WARNING - watchdog._watcher (23:48:35):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_espeak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

WARNING - watchdog._watcher (23:48:50):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_espeak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

WARNING - watchdog._watcher (23:49:05):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_espeak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

WARNING - watchdog._watcher (23:49:20):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_espeak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

INFO - core.onEndSession (23:54:04):
Windows session ending


On 2/05/2016 7:29 PM, Sharni-Lee Ward wrote:

If the master snapshots fixed it, does this mean the next release (which
is hopefully coming sometime this month or next) will have the fix?
Because if so, I can just change the configuration so I have to connect
it manually when I want to use it, which isn't a problem as I usually
have to re-activate the Braille settings if I have to disconnect the
display for one reason or another, or if the computer's put to sleep. If
the fix is implemented next release, I'll adjust the configuration
again. If it does happen again despite this measure, I will try Gene's
method, although I suspect it will be fine. Thank you everyone for all
your help and tips, and at least I know how to retrieve old log messages
now! :D


On 2/05/2016 7:02 PM, Brian's Mail list account wrote:

I don't think its malware, reading the thread it sounds like the
braill table part of nvda and the master snapshots are supposed to
have now fixed it. Its been a while since I had a computer with one of
those displays. fartoo expensive for the low usage I have.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Arlene" <nedster66@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Monday, May 02, 2016 4:15 AM
Subject: Re: [nvda] NVDA still freezing, don't know what the deal is

Hi there: Do you think your computer could have mellwhere to cause this
freezing?

-----Original Message-----
From: Rob [mailto:captinlogic@gmail.com]
Sent: May-01-16 6:31 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA still freezing, don't know what the deal is

Gene <gsasner@ripco.com> wrote:

Why wouldn't my workaround accomplish the same end but more easily.

Because most of the keyboard is frozen when this freeze happens. The
only
thing that works is the windows key and some function keys.

Just tried another thing that consistently got NVDA to hang recently,
namely, opening the sounds manager in Control Panel and then arrowing to
the Sound Scheme tab. I thought it only did this because of the Braille
Display but I wanted to test it to make sure. This time, once the window
was closed, NVDA started responding again. I also tried to activate
Narrator but it didn't work, though as I said, that didn't end up
mattering. Here's the log for that session, though I warn you, the
warning repeats itself several times. In case each warning was subtly
different, I copied the whole thing. Don't worry about the Braille error
that shows up first�that's about me starting up the computer and by
extension NVDA without my display plugged in and then saving the
configuration with default as No Braille.


INFO - __main__ (18:51:56):
Starting NVDA
INFO - core.main (18:51:59):
Config dir: C:\Users\pc\AppData\Roaming\nvda
INFO - core.main (18:52:00):
NVDA version 2016.1
INFO - core.main (18:52:00):
Using Windows version 6.1.7601 service pack 1 workstation
INFO - core.main (18:52:00):
Using Python version 2.7.11 (v2.7.11:6d1b6a68f775, Dec 5 2015,
20:32:19) [MSC v.1500 32 bit (Intel)]
INFO - core.main (18:52:00):
Using comtypes version 0.6.2
INFO - external:synthDrivers.ptenglish.SynthDriver.__init__ (18:52:10):
Using eSpeak version 1.48.03 04.Mar.14
INFO - synthDriverHandler.setSynth (18:52:11):
Loaded synthDriver ptenglish
INFO - core.main (18:52:11):
Using wx version 3.0.2.0 msw (classic)
INFO - braille.initialize (18:52:11):
Using liblouis version 2.6.5
ERROR - braille.BrailleHandler.setDisplayByName (18:52:11):
Error initializing display driver
Traceback (most recent call last):
File "braille.pyo", line 1447, in setDisplayByName
File "brailleDisplayDrivers\freedomScientific.pyo", line 179, in
__init__
RuntimeError: No display found
INFO - braille.BrailleHandler.setDisplayByName (18:52:11):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - brailleInput.initialize (18:52:11):
Braille input initialized
INFO - core.main (18:52:12):
NVDA initialized
INFO - braille.BrailleHandler.setDisplayByName (19:30:34):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - config.ConfigManager.save (19:30:39):
Base configuration saved
WARNING - watchdog._watcher (23:47:35):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_espeak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

WARNING - watchdog._watcher (23:47:50):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_espeak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

WARNING - watchdog._watcher (23:48:05):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_espeak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

WARNING - watchdog._watcher (23:48:20):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_espeak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

WARNING - watchdog._watcher (23:48:35):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_espeak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

WARNING - watchdog._watcher (23:48:50):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_espeak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

WARNING - watchdog._watcher (23:49:05):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_espeak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

WARNING - watchdog._watcher (23:49:20):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_espeak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

INFO - core.onEndSession (23:54:04):
Windows session ending


On 2/05/2016 7:29 PM, Sharni-Lee Ward wrote:

If the master snapshots fixed it, does this mean the next release (which
is hopefully coming sometime this month or next) will have the fix?
Because if so, I can just change the configuration so I have to connect
it manually when I want to use it, which isn't a problem as I usually
have to re-activate the Braille settings if I have to disconnect the
display for one reason or another, or if the computer's put to sleep. If
the fix is implemented next release, I'll adjust the configuration
again. If it does happen again despite this measure, I will try Gene's
method, although I suspect it will be fine. Thank you everyone for all
your help and tips, and at least I know how to retrieve old log messages
now! :D


On 2/05/2016 7:02 PM, Brian's Mail list account wrote:

I don't think its malware, reading the thread it sounds like the
braill table part of nvda and the master snapshots are supposed to
have now fixed it. Its been a while since I had a computer with one of
those displays. fartoo expensive for the low usage I have.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Arlene" <nedster66@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Monday, May 02, 2016 4:15 AM
Subject: Re: [nvda] NVDA still freezing, don't know what the deal is

Hi there: Do you think your computer could have mellwhere to cause this
freezing?

-----Original Message-----
From: Rob [mailto:captinlogic@gmail.com]
Sent: May-01-16 6:31 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA still freezing, don't know what the deal is

Gene <gsasner@ripco.com> wrote:

Why wouldn't my workaround accomplish the same end but more easily.

Because most of the keyboard is frozen when this freeze happens. The
only
thing that works is the windows key and some function keys.

Just tried another thing that consistently got NVDA to hang recently,
namely, opening the sounds manager in Control Panel and then arrowing to
the Sound Scheme tab. I thought it only did this because of the Braille
Display but I wanted to test it to make sure. This time, once the window
was closed, NVDA started responding again. I also tried to activate
Narrator but it didn't work, though as I said, that didn't end up
mattering. Here's the log for that session, though I warn you, the
warning repeats itself several times. In case each warning was subtly
different, I copied the whole thing. Don't worry about the Braille error
that shows up first—that's about me starting up the computer and by
extension NVDA without my display plugged in and then saving the
configuration with default as No Braille.


INFO - __main__ (18:51:56):
Starting NVDA
INFO - core.main (18:51:59):
Config dir: C:\Users\pc\AppData\Roaming\nvda
INFO - core.main (18:52:00):
NVDA version 2016.1
INFO - core.main (18:52:00):
Using Windows version 6.1.7601 service pack 1 workstation
INFO - core.main (18:52:00):
Using Python version 2.7.11 (v2.7.11:6d1b6a68f775, Dec 5 2015,
20:32:19) [MSC v.1500 32 bit (Intel)]
INFO - core.main (18:52:00):
Using comtypes version 0.6.2
INFO - external:synthDrivers.ptenglish.SynthDriver.__init__ (18:52:10):
Using eSpeak version 1.48.03 04.Mar.14
INFO - synthDriverHandler.setSynth (18:52:11):
Loaded synthDriver ptenglish
INFO - core.main (18:52:11):
Using wx version 3.0.2.0 msw (classic)
INFO - braille.initialize (18:52:11):
Using liblouis version 2.6.5
ERROR - braille.BrailleHandler.setDisplayByName (18:52:11):
Error initializing display driver
Traceback (most recent call last):
File "braille.pyo", line 1447, in setDisplayByName
File "brailleDisplayDrivers\freedomScientific.pyo", line 179, in __init__
RuntimeError: No display found
INFO - braille.BrailleHandler.setDisplayByName (18:52:11):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - brailleInput.initialize (18:52:11):
Braille input initialized
INFO - core.main (18:52:12):
NVDA initialized
INFO - braille.BrailleHandler.setDisplayByName (19:30:34):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - config.ConfigManager.save (19:30:39):
Base configuration saved
WARNING - watchdog._watcher (23:47:35):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_espeak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

WARNING - watchdog._watcher (23:47:50):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_espeak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

WARNING - watchdog._watcher (23:48:05):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_espeak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

WARNING - watchdog._watcher (23:48:20):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_espeak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

WARNING - watchdog._watcher (23:48:35):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_espeak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

WARNING - watchdog._watcher (23:48:50):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_espeak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

WARNING - watchdog._watcher (23:49:05):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_espeak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

WARNING - watchdog._watcher (23:49:20):
Core frozen in stack:
File "nvda.pyw", line 190, in <module>
File "core.pyo", line 382, in main
File "wx\_core.pyo", line 8657, in MainLoop
File "wx\_core.pyo", line 7952, in MainLoop
File "core.pyo", line 353, in Notify
File "queueHandler.pyo", line 83, in pumpAll
File "queueHandler.pyo", line 50, in flushQueue
File "eventHandler.pyo", line 61, in _queueEventCallback
File "eventHandler.pyo", line 138, in executeEvent
File "eventHandler.pyo", line 162, in doPreGainFocus
File "eventHandler.pyo", line 143, in executeEvent
File "eventHandler.pyo", line 91, in __init__
File "eventHandler.pyo", line 98, in next
File "NVDAObjects\__init__.pyo", line 868, in event_foreground
File "speech.pyo", line 107, in cancelSpeech
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\__init__.py",
line 117, in cancel
File
"C:\Users\pc\AppData\Roaming\nvda\addons\protalker\synthDrivers\ptenglish\_espeak.py",
line 224, in stop
File "nvwave.pyo", line 244, in stop
File "threading.pyo", line 174, in acquire

INFO - core.onEndSession (23:54:04):
Windows session ending


On 2/05/2016 7:29 PM, Sharni-Lee Ward wrote:

If the master snapshots fixed it, does this mean the next release (which
is hopefully coming sometime this month or next) will have the fix?
Because if so, I can just change the configuration so I have to connect
it manually when I want to use it, which isn't a problem as I usually
have to re-activate the Braille settings if I have to disconnect the
display for one reason or another, or if the computer's put to sleep. If
the fix is implemented next release, I'll adjust the configuration
again. If it does happen again despite this measure, I will try Gene's
method, although I suspect it will be fine. Thank you everyone for all
your help and tips, and at least I know how to retrieve old log messages
now! :D


On 2/05/2016 7:02 PM, Brian's Mail list account wrote:

I don't think its malware, reading the thread it sounds like the
braill table part of nvda and the master snapshots are supposed to
have now fixed it. Its been a while since I had a computer with one of
those displays. fartoo expensive for the low usage I have.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Arlene" <nedster66@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Monday, May 02, 2016 4:15 AM
Subject: Re: [nvda] NVDA still freezing, don't know what the deal is

Hi there: Do you think your computer could have mellwhere to cause this
freezing?

-----Original Message-----
From: Rob [mailto:captinlogic@gmail.com]
Sent: May-01-16 6:31 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA still freezing, don't know what the deal is

Gene <gsasner@ripco.com> wrote:

Why wouldn't my workaround accomplish the same end but more easily.

Because most of the keyboard is frozen when this freeze happens. The
only
thing that works is the windows key and some function keys.

To be honest though I realise its not possible I'd like a conference
held in new zealand or close to my country australia maybe.
While there is this online one my only hate if you will is that while I
do like the archives and such due to timezone I always then have to
catch up and then end up skipping things.
Today was supposed to be archive day but due to the fact I had some work
to do it just never happened.
I am not sure if I would actually attend one live or not but it would be
good to get one that was not sounding digital.



On 2/05/2016 8:37 p.m., Bhavya shah wrote:

Dear all,
The below integrated survey seeks to determine the amount of interest
in introducing a version of the NVDACon International Users and
Developers Conferences and regional NVDACons which are currently held
in places such as United States of America, Japan, Korea etc. For South
Asian regions. Created originally by a fellow NVDA enthusiast (a friend
of mine too), and I myself being a passionate NVDA enthusiast, would
like to sincerely request all of you to fill this form carefully and
spread the word about it to other NVDA users in South Asia, preferably
online at
https://docs.google.com/forms/d/1P7xL7wPKHjN3GZs2Z1qBs_xZ7NEKnmWCywVk_pdBCr0/viewform?c=0&w=1

or by filling the fields and sending it to me privately at
Bhavya.shah125@gmail.com
Sincerely looking forward to receiving many responses!
Thanks.




NVDA, having been founded in the year 2006 by a fascinated Australian
blind programmer named Michael Curren, is now officialy ten years old
today. As NVDA communities across the world celebrate this massive
screen reading milestone, inspired from NVDACon International 2016
Users and Developers Conference 10th Anniversary edition, a group of
people who are avid NVDA users, supporters and enthusiasts from India
and Pakistan are willing to organize an NVDA conference for South Asia,
where users, developers and even those simply interested in NVDA are
given an opportunity to network with fellow NVDA residents, and share,
discuss, learn more about and shape the future of NVDA. This survey has
been authored by these NVDA loyallists and seeks to understand and
ascertain the amount of interest in South Asian countries (like India,
Pakistan etc.) in an NVDACon South Asia. We sincerely hope that you may
take out a few minutes of your invaluable time in filling this survey
questionairre carefully, to bring NVDACon South Asia to life.


I've invited you to fill out the form NVDACon Non Visual Desktop Access
screen reader Users and Developers Conference for South Asian regions.
To fill it out, visit:
https://docs.google.com/forms/d/1P7xL7wPKHjN3GZs2Z1qBs_xZ7NEKnmWCywVk_pdBCr0/viewform?c=0&w=1&usp=mail_form_link

If the master snapshots fixed it, does this mean the next release (which
is hopefully coming sometime this month or next) will have the fix?
Because if so, I can just change the configuration so I have to connect
it manually when I want to use it, which isn't a problem as I usually
have to re-activate the Braille settings if I have to disconnect the
display for one reason or another, or if the computer's put to sleep. If
the fix is implemented next release, I'll adjust the configuration
again. If it does happen again despite this measure, I will try Gene's
method, although I suspect it will be fine. Thank you everyone for all
your help and tips, and at least I know how to retrieve old log messages
now! :D


On 2/05/2016 7:02 PM, Brian's Mail list account wrote:

I don't think its malware, reading the thread it sounds like the
braill table part of nvda and the master snapshots are supposed to
have now fixed it. Its been a while since I had a computer with one of
those displays. fartoo expensive for the low usage I have.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Arlene" <nedster66@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Monday, May 02, 2016 4:15 AM
Subject: Re: [nvda] NVDA still freezing, don't know what the deal is

Hi there: Do you think your computer could have mellwhere to cause this
freezing?

-----Original Message-----
From: Rob [mailto:captinlogic@gmail.com]
Sent: May-01-16 6:31 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA still freezing, don't know what the deal is

Gene <gsasner@ripco.com> wrote:

Why wouldn't my workaround accomplish the same end but more easily.

Because most of the keyboard is frozen when this freeze happens. The
only
thing that works is the windows key and some function keys.

Hi Brian,


That does seem to match up with my mother's description of what was
going on on the screen. I'm going to start connecting it manually
instead of having it be connected at startup and NVDA configured to use
it automatically. I may simply have been typing too fast in Word for the
code to keep up (although as I said this doesn't happen just in Word).


Also, That fix sounds horrible and unnatural. I wish there were ways to
make words be emphasised the way you want them to be, and that the
method worked across the board instead of in just one synth, but you
can't have everything...


On 2/05/2016 6:33 PM, Brian's Mail list account wrote:

Obviously if you are certain that the problem does not occur whenits
not connected you have proved the issue is that. Next you need to see
if there is a newer version of the driver perhaps?
Not having tried this display, I'm a bit useless on this aspect.
Are there any other bits ofsoftware on the computer that can use the
display that might be able to test f its just nvda or if its a more
general problem. It sounds like a hang not exactly a crash, ie its
going around in circles and not getting out of a loop.
If it happens at a non critical time, what happens if you do the short
tap on the power button which in my case seems to break out of a
crashed piece of software back to a a working condition again.
Too long of course will shut the machine down. I think Word saves its
file in the background and tells you next time you staart of any
rescued documents it may have you might need to get into.
Incidentally did my fix for your name in speech platform work?

shar-nee-Lee.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Sharni-Lee Ward"
<sharni-lee.ward@hotmail.com>
To: <nvda@nvda.groups.io>
Sent: Monday, May 02, 2016 12:00 AM
Subject: Re: [nvda] NVDA still freezing, don't know what the deal is

It just happened again, again while I was writing. My mother came to
help me again and tried to save my work. Word wouldn't respond. She
tried to exit NVDA mannually, but it wouldn't allow her to do that. She
scanned NVDA with Microsoft Security Essentials but nothing came up. I'm
now using the computer without my Braille Display. I don't understand
why it's doing this to me, but I can't think of any other culprit. It's
brand new. We bought it in February and I've barely used it, partly
because of this issue and partly because of the MUD I've been playing.
But I've had it plugged into my computer via USB almost constantly since
I got it and installed the driver. The computer usually starts up with
it plugged in.


Please, someone, help! I want to solve this problem as soon as possible!
I've had about enough of this and I don't want to sacrifice my Braille
Display just because this is happening!


On 2/05/2016 7:10 AM, Sharni-Lee Ward wrote:

I've mentioned this before, but it's been weeks and I don't know if I
got any more useful help after Joseph said to submit a log entry. Which
given the nature of my problem, I doubt would work.


Since I got my Braille Display in February, NVDA has frozen with
alarming regularity. It hasn't been like previous experiences of the
phenomenon either. I used to occasionally have NVDA freeze, but I could
restart the screen reader with alt+ctrl+n. With this situation, I
can't.
NVDA completely stops working. It says nothing. The Braille display's
display remains frozen on whatever was last spoken. I can't restart
NVDA, and sometimes can't even shut down the computer without sighted
help. That's the only way to get things working again—shut down and
restart the computer. I used to only experience this soon after
startup,
especially when I tried to activate the snapshot with the experimental
UEB table in it, but now I'm having it happen after the computer's been
going for a while, and it happens on both the normal installation and
the brltbl snapshot. Just now, I had it happen while I was writing in a
document. I was typing merrily away when NVDA stopped reporting letters
and the Braille Display, when I checked it, was only displaying the
first two words I'd typed on that line.


This is getting seriously annoying both for me and my mother, who is my
carer. I don't know what's causing this problem but I have a horrible
feeling it's to do with my Focus 40 Blue, as it didn't happen before I
got it. Can anyone shed some light on this? I want it to stop so my
writing and other activities don't keep getting interrupted.

Hi Brian,


That does seem to match up with my mother's description of what was
going on on the screen. I'm going to start connecting it manually
instead of having it be connected at startup and NVDA configured to use
it automatically. I may simply have been typing too fast in Word for the
code to keep up (although as I said this doesn't happen just in Word).


Also, That fix sounds horrible and unnatural. I wish there were ways to
make words be emphasised the way you want them to be, and that the
method worked across the board instead of in just one synth, but you
can't have everything...


On 2/05/2016 6:33 PM, Brian's Mail list account wrote:

Obviously if you are certain that the problem does not occur whenits
not connected you have proved the issue is that. Next you need to see
if there is a newer version of the driver perhaps?
Not having tried this display, I'm a bit useless on this aspect.
Are there any other bits ofsoftware on the computer that can use the
display that might be able to test f its just nvda or if its a more
general problem. It sounds like a hang not exactly a crash, ie its
going around in circles and not getting out of a loop.
If it happens at a non critical time, what happens if you do the short
tap on the power button which in my case seems to break out of a
crashed piece of software back to a a working condition again.
Too long of course will shut the machine down. I think Word saves its
file in the background and tells you next time you staart of any
rescued documents it may have you might need to get into.
Incidentally did my fix for your name in speech platform work?

shar-nee-Lee.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Sharni-Lee Ward"
<sharni-lee.ward@hotmail.com>
To: <nvda@nvda.groups.io>
Sent: Monday, May 02, 2016 12:00 AM
Subject: Re: [nvda] NVDA still freezing, don't know what the deal is

It just happened again, again while I was writing. My mother came to
help me again and tried to save my work. Word wouldn't respond. She
tried to exit NVDA mannually, but it wouldn't allow her to do that. She
scanned NVDA with Microsoft Security Essentials but nothing came up. I'm
now using the computer without my Braille Display. I don't understand
why it's doing this to me, but I can't think of any other culprit. It's
brand new. We bought it in February and I've barely used it, partly
because of this issue and partly because of the MUD I've been playing.
But I've had it plugged into my computer via USB almost constantly since
I got it and installed the driver. The computer usually starts up with
it plugged in.


Please, someone, help! I want to solve this problem as soon as possible!
I've had about enough of this and I don't want to sacrifice my Braille
Display just because this is happening!


On 2/05/2016 7:10 AM, Sharni-Lee Ward wrote:

I've mentioned this before, but it's been weeks and I don't know if I
got any more useful help after Joseph said to submit a log entry. Which
given the nature of my problem, I doubt would work.


Since I got my Braille Display in February, NVDA has frozen with
alarming regularity. It hasn't been like previous experiences of the
phenomenon either. I used to occasionally have NVDA freeze, but I could
restart the screen reader with alt+ctrl+n. With this situation, I
can't.
NVDA completely stops working. It says nothing. The Braille display's
display remains frozen on whatever was last spoken. I can't restart
NVDA, and sometimes can't even shut down the computer without sighted
help. That's the only way to get things working again—shut down and
restart the computer. I used to only experience this soon after
startup,
especially when I tried to activate the snapshot with the experimental
UEB table in it, but now I'm having it happen after the computer's been
going for a while, and it happens on both the normal installation and
the brltbl snapshot. Just now, I had it happen while I was writing in a
document. I was typing merrily away when NVDA stopped reporting letters
and the Braille Display, when I checked it, was only displaying the
first two words I'd typed on that line.


This is getting seriously annoying both for me and my mother, who is my
carer. I don't know what's causing this problem but I have a horrible
feeling it's to do with my Focus 40 Blue, as it didn't happen before I
got it. Can anyone shed some light on this? I want it to stop so my
writing and other activities don't keep getting interrupted.

I don't think its malware, reading the thread it sounds like the
braill table part of nvda and the master snapshots are supposed to
have now fixed it. Its been a while since I had a computer with one of
those displays. fartoo expensive for the low usage I have.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Arlene" <nedster66@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Monday, May 02, 2016 4:15 AM
Subject: Re: [nvda] NVDA still freezing, don't know what the deal is

Hi there: Do you think your computer could have mellwhere to cause this
freezing?

-----Original Message-----
From: Rob [mailto:captinlogic@gmail.com]
Sent: May-01-16 6:31 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA still freezing, don't know what the deal is

Gene <gsasner@ripco.com> wrote:

Why wouldn't my workaround accomplish the same end but more easily.

Because most of the keyboard is frozen when this freeze happens. The
only
thing that works is the windows key and some function keys.

Hello,

I recently bought this add on and the Vocalizer voices work well. However, when I am trying to use the Eloquence voice I hear a very annoying crackling or popping noise. Multiple people have heard the crackling noise so I know its not just my machine.


Regards,

Greg WOcher


On 5/2/2016 4:21 AM, Pawel Urbanski wrote:

Hi,
Have been using this add-on for 4 months. The libraries used are the
same as for other screen readers. NVDA's dictionary is rather good and
prenunciatin is also good.
I use Eloquence as my speech engine after switching from using JAWS.
NVDA is very responsive, has no lags and works more than well.

On 5/2/16, Isaac <bigikemusic@gmail.com> wrote:

Hi, anyone recommend this addon, is the vocalizer as good as the other
vocalizer, and is codefactory offering a sapi of just eloquence or vocalizer
as well.
Thanks

To be honest I am waiting for this orbit portable something thats supposed to come out but to be honest I graduated from braille to querty ages ago.
The only reason I would want braille is that if I could get a display for 1-200 bucks or something I would probably get one, saying that my desk is to full of stuff to put much on it.
Every time I do any recording of reviews etc like today I got in trouble with cables getting snared.
I know I could go to wireless but batteries are not my thing either.



On 2/05/2016 9:02 p.m., Brian's Mail list account wrote:

I don't think its malware, reading the thread it sounds like the braill
table part of nvda and the master snapshots are supposed to have now
fixed it. Its been a while since I had a computer with one of those
displays. fartoo expensive for the low usage I have.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Arlene" <nedster66@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Monday, May 02, 2016 4:15 AM
Subject: Re: [nvda] NVDA still freezing, don't know what the deal is

Hi there: Do you think your computer could have mellwhere to cause this
freezing?

-----Original Message-----
From: Rob [mailto:captinlogic@gmail.com]
Sent: May-01-16 6:31 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA still freezing, don't know what the deal is

Gene <gsasner@ripco.com> wrote:

Why wouldn't my workaround accomplish the same end but more easily.

Because most of the keyboard is frozen when this freeze happens. The only
thing that works is the windows key and some function keys.

.

Dear all,
The below integrated survey seeks to determine the amount of interest
in introducing a version of the NVDACon International Users and
Developers Conferences and regional NVDACons which are currently held
in places such as United States of America, Japan, Korea etc. For South
Asian regions. Created originally by a fellow NVDA enthusiast (a friend
of mine too), and I myself being a passionate NVDA enthusiast, would
like to sincerely request all of you to fill this form carefully and
spread the word about it to other NVDA users in South Asia, preferably
online at
https://docs.google.com/forms/d/1P7xL7wPKHjN3GZs2Z1qBs_xZ7NEKnmWCywVk_pdBCr0/viewform?c=0&w=1

or by filling the fields and sending it to me privately at
Bhavya.shah125@gmail.com
Sincerely looking forward to receiving many responses!
Thanks.




NVDA, having been founded in the year 2006 by a fascinated Australian
blind programmer named Michael Curren, is now officialy ten years old
today. As NVDA communities across the world celebrate this massive
screen reading milestone, inspired from NVDACon International 2016
Users and Developers Conference 10th Anniversary edition, a group of
people who are avid NVDA users, supporters and enthusiasts from India
and Pakistan are willing to organize an NVDA conference for South Asia,
where users, developers and even those simply interested in NVDA are
given an opportunity to network with fellow NVDA residents, and share,
discuss, learn more about and shape the future of NVDA. This survey has
been authored by these NVDA loyallists and seeks to understand and
ascertain the amount of interest in South Asian countries (like India,
Pakistan etc.) in an NVDACon South Asia. We sincerely hope that you may
take out a few minutes of your invaluable time in filling this survey
questionairre carefully, to bring NVDACon South Asia to life.


I've invited you to fill out the form NVDACon Non Visual Desktop Access
screen reader Users and Developers Conference for South Asian regions.
To fill it out, visit:
https://docs.google.com/forms/d/1P7xL7wPKHjN3GZs2Z1qBs_xZ7NEKnmWCywVk_pdBCr0/viewform?c=0&w=1&usp=mail_form_link

I don't think its malware, reading the thread it sounds like the braill
table part of nvda and the master snapshots are supposed to have now
fixed it. Its been a while since I had a computer with one of those
displays. fartoo expensive for the low usage I have.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Arlene" <nedster66@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Monday, May 02, 2016 4:15 AM
Subject: Re: [nvda] NVDA still freezing, don't know what the deal is

Hi there: Do you think your computer could have mellwhere to cause this
freezing?

-----Original Message-----
From: Rob [mailto:captinlogic@gmail.com]
Sent: May-01-16 6:31 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA still freezing, don't know what the deal is

Gene <gsasner@ripco.com> wrote:

Why wouldn't my workaround accomplish the same end but more easily.

Because most of the keyboard is frozen when this freeze happens. The only
thing that works is the windows key and some function keys.

.

I think originally it was proffered that it was due to nvda missing an
item, due to timing issues, but it is so flaky that nobody seemed to be
able to get a definitive answer.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Arianna Sepulveda"
<englishrider91@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Monday, May 02, 2016 3:01 AM
Subject: Re: [nvda] NVDA and tab


Wow! I use Firefox, and I don't think I've ever had this problem.


Thanks,
Ari

On May 1, 2016, at 1:26 PM, Gene <gsasner@ripco.com> wrote:

But the problem here is that when you are in the proper part of the
Window and have opened a page, you have to tab once at times to be
able to move in and read the page. I haven't paid much attention to
this. In my case, using firefox, it is a problem that occurs off and
on but that doesn't occur nearly every time I load a page. I believe
I've seen the same problem when using Google, though I don't use
google much.

I haven't tested to see if the problem exists in other screen-readers.
Gene
----- Original Message -----
From: Jacob Kruger
Sent: Sunday, May 01, 2016 2:19 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA and tab

I generally use ctrl + F6 keystroke to focus on webpage contents after
typing in an address, etc. - think this works in both IE11 and firefox.

Stay well

Jacob Kruger
Blind Biker
Skype: BlindZA
"Roger Wilco wants to welcome you...to the space janitor's closet..."

On 2016-05-01 9:08 PM, Nevzat Adil wrote:

Hello all,
I encounter an issue when trying to get on to the Internet which I am
not sure whether it is n NVDA issue or something else.
For instance, when I try to get to my home page, google, the page does
not seem to load and read by NVDA unless I press tab. It is only then
that NVDA begins reading the page. The same issue occurs when trying
to get onto other pages, as well.
My operating system is Windows 10 64 bit. NVDA is the most recent.
I would appreciate your comments.
Nevzat

Obviously if you are certain that the problem does not occur whenits not
connected you have proved the issue is that. Next you need to see if
there is a newer version of the driver perhaps?
Not having tried this display, I'm a bit useless on this aspect.
Are there any other bits ofsoftware on the computer that can use the
display that might be able to test f its just nvda or if its a more
general problem. It sounds like a hang not exactly a crash, ie its going
around in circles and not getting out of a loop.
If it happens at a non critical time, what happens if you do the short
tap on the power button which in my case seems to break out of a crashed
piece of software back to a a working condition again.
Too long of course will shut the machine down. I think Word saves its
file in the background and tells you next time you staart of any rescued
documents it may have you might need to get into.
Incidentally did my fix for your name in speech platform work?

shar-nee-Lee.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Sharni-Lee Ward"
<sharni-lee.ward@hotmail.com>
To: <nvda@nvda.groups.io>
Sent: Monday, May 02, 2016 12:00 AM
Subject: Re: [nvda] NVDA still freezing, don't know what the deal is

It just happened again, again while I was writing. My mother came to
help me again and tried to save my work. Word wouldn't respond. She
tried to exit NVDA mannually, but it wouldn't allow her to do that. She
scanned NVDA with Microsoft Security Essentials but nothing came up. I'm
now using the computer without my Braille Display. I don't understand
why it's doing this to me, but I can't think of any other culprit. It's
brand new. We bought it in February and I've barely used it, partly
because of this issue and partly because of the MUD I've been playing.
But I've had it plugged into my computer via USB almost constantly since
I got it and installed the driver. The computer usually starts up with
it plugged in.


Please, someone, help! I want to solve this problem as soon as possible!
I've had about enough of this and I don't want to sacrifice my Braille
Display just because this is happening!


On 2/05/2016 7:10 AM, Sharni-Lee Ward wrote:

I've mentioned this before, but it's been weeks and I don't know if I
got any more useful help after Joseph said to submit a log entry. Which
given the nature of my problem, I doubt would work.


Since I got my Braille Display in February, NVDA has frozen with
alarming regularity. It hasn't been like previous experiences of the
phenomenon either. I used to occasionally have NVDA freeze, but I could
restart the screen reader with alt+ctrl+n. With this situation, I can't.
NVDA completely stops working. It says nothing. The Braille display's
display remains frozen on whatever was last spoken. I can't restart
NVDA, and sometimes can't even shut down the computer without sighted
help. That's the only way to get things working again—shut down and
restart the computer. I used to only experience this soon after startup,
especially when I tried to activate the snapshot with the experimental
UEB table in it, but now I'm having it happen after the computer's been
going for a while, and it happens on both the normal installation and
the brltbl snapshot. Just now, I had it happen while I was writing in a
document. I was typing merrily away when NVDA stopped reporting letters
and the Braille Display, when I checked it, was only displaying the
first two words I'd typed on that line.


This is getting seriously annoying both for me and my mother, who is my
carer. I don't know what's causing this problem but I have a horrible
feeling it's to do with my Focus 40 Blue, as it didn't happen before I
got it. Can anyone shed some light on this? I want it to stop so my
writing and other activities don't keep getting interrupted.

Hi,
Have been using this add-on for 4 months. The libraries used are the
same as for other screen readers. NVDA's dictionary is rather good and
prenunciatin is also good.
I use Eloquence as my speech engine after switching from using JAWS.
NVDA is very responsive, has no lags and works more than well.

On 5/2/16, Isaac <bigikemusic@gmail.com> wrote:

Hi, anyone recommend this addon, is the vocalizer as good as the other
vocalizer, and is codefactory offering a sapi of just eloquence or vocalizer
as well.
Thanks