Date   

voices again

Isaac <bigikemusic@...>
 

So, if I bought the codefactory voices will I never be able to use the tiflatechnia voices again with out uninstalling the codefactory ones?


big problem with voices

Isaac <bigikemusic@...>
 

Hi, I purchased the codefactory eloquence and vocalizer, and several problems arrise.  The first is that it knocked out my other vocalizer voices from tiflatechnia.  Second of all, I can switch to eloquence, but when I switch to vocalizer, there is no voice playing, and I have turned on narrator and nothing.  I need this working or I need to dispute this charge with my credit card company, so please guys, why is one set of voices knocking out another set of voices?


GMail, PDF and NVDA

David Russell
 

Hi NVDA Group,
First, happy 10th anniversary to NVDA! It is about my fourth year for
using NVDA and hooked!

My question is this: Are their hot key tutorials online, for opening
and copying a PDF attachment to a Word Processing program?
Unfortunately, the "view as HTML" appears as an error message when
trying to utilize that option.
Thanks in advance for help with this.

-- Cheers,
David Russell
david.sonofhashem@gmail.com
"Confront the dark parts of yourself, and work to banish them with
illumination and forgiveness. Your willingness to wrestle with your
demons will cause your angels to sing." Writer, Frederick Kittel


Re: codefactory eloquence and vocalizer

Kelly Sapergia
 

Hi,

Shortly after trying the Eloquence add-on from Code Factory on one of my systems a couple weeks ago, I wrote to the company to let them know about the problem. I eventually got an email later in the week basically asking me to send them a sound file demoing the voice's choppiness. Unfortunately, my trial period had expired by then, so I couldn't do it. Personally, I'm not going to bother with this add-on, as I already have the Vocalizer voices from Tiflotecnia (though I'm surprised they don't have the other voices included with the Code Factory add-on). I'm also enjoying using the Acapela voices add-on, and the Edward voice in the free Speech Player and eSpeak add-on.

Thanks.

Yours Sincerely,
Kelly John Sapergia
Show Host and Production Director
The Global Voice Internet Radio
http://www.theglobalvoice.info

Personal Website: http://www.ksapergia.net
Business Website (KJS Productions): http://www.kjsproductions.com
Follow me on Twitter at: kjsapergia


Re: NVDA still freezing, don't know what the deal is

Gene
 

I doubt any of those maintenance utilities will solve the problem.  There is no harm in running them but what might be far more useful than just doing routine maintenance because maybe it will help, is to get more information from NVDA logs and if that is inadequate, from the Reliability history.  And I consider BIOS settings to be a very unlikely cause of the problem. 
 
Gene

From: Arlene
Sent: Monday, May 02, 2016 5:32 PM
Subject: Re: [nvda] NVDA still freezing, don't know what the deal is

Oh,then I'd run chkdsk before you have to format. Then try disk defragment and disk clean up. If it still freezes then maybe you have to get a sighted person to go into the bios and see what can be the problem. Before you have to format. Cause if you did format it. You may still end up with that problem.

-----Original Message-----
From: Sharni-Lee Ward [mailto:sharni-lee.ward@...]
Sent: May-02-16 2:11 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA still freezing, don't know what the deal is

No, I do not have a backup screen reader. NVDA is the only free one I
know of and I am happy with it. I considered getting a Braille Display
more beneficial than Jaws, which I would have to pay $500 per year to
keep updated. And I don't have the bandwidth to even download the demo.
I don't like Jaws anyway. I was never taught how to properly use most
Jaws specific commands when I did use it in school. That was ten years
ago now, so it likely wouldn't help me much anyways.


On 2/05/2016 1:30 PM, Arlene wrote:
> Hi, What other screen reader do you have on your computer? If you have a back up screen reader besides NVDA why not try it to make sure it's not your Braille Display? It sounds like you might have botched up a setting while setting it up for it to run on NVDA.  If it works on your back up screen reader, then there's something up with a setting for NVDA.
>
> -----Original Message-----
> From: Sharni-Lee Ward [mailto:sharni-lee.ward@...]
> Sent: May-01-16 4:01 PM
> To: nvda@nvda.groups.io
> 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.
>>
>>
>>
>>
>
>
>
>
>
>
>









Re: NVDA still freezing, don't know what the deal is

 

Actually the only thing you can check is the smart info in bios that may not be much you can do there.

On 3/05/2016 10:32 a.m., Arlene wrote:
Oh,then I'd run chkdsk before you have to format. Then try disk defragment and disk clean up. If it still freezes then maybe you have to get a sighted person to go into the bios and see what can be the problem. Before you have to format. Cause if you did format it. You may still end up with that problem.

-----Original Message-----
From: Sharni-Lee Ward [mailto:sharni-lee.ward@hotmail.com]
Sent: May-02-16 2:11 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA still freezing, don't know what the deal is

No, I do not have a backup screen reader. NVDA is the only free one I
know of and I am happy with it. I considered getting a Braille Display
more beneficial than Jaws, which I would have to pay $500 per year to
keep updated. And I don't have the bandwidth to even download the demo.
I don't like Jaws anyway. I was never taught how to properly use most
Jaws specific commands when I did use it in school. That was ten years
ago now, so it likely wouldn't help me much anyways.


On 2/05/2016 1:30 PM, Arlene wrote:
Hi, What other screen reader do you have on your computer? If you have a back up screen reader besides NVDA why not try it to make sure it's not your Braille Display? It sounds like you might have botched up a setting while setting it up for it to run on NVDA. If it works on your back up screen reader, then there's something up with a setting for NVDA.

-----Original Message-----
From: Sharni-Lee Ward [mailto:sharni-lee.ward@hotmail.com]
Sent: May-01-16 4:01 PM
To: nvda@nvda.groups.io
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.















Re: NVDA still freezing, don't know what the deal is

 

Hmmm well if it is your display updating the firmware etc.
Maybe the driver is not compatible, my suggestion is you restore the computer to a point before you installed the display, try it without the display for a while and see if it still goes nuts.
If it does, I'd look at getting your system repaired if its truely got something wrong.
It may need a dusting or something worse.
I had to deal with a server replacement, where one of the primary supplies had burned out and was on fire.
I never knew that and tried to start it.
It didn't want to start the hard drive or get any data to load because it detected it was dammaged.
A new system was procured and the old one was due for salvage of bits.
However aparently its all burned inside so no salvage.
The data was on raid backup but you do actually need the unit working to get that off.
Otherwise it just takes a while to recover.
From what I heard, progress has been made on getting that sorted.
I would do a system restore to a day or a month before you got that display loaded and see what it does.
I would then download the latest software and drivers and firmware for your display and try that.
I'd try your display in another system and see if it crashes out.
I'd check the usb cables of the display to.
The only time I have had other issues similar to this was when I was working on a friend's system, it kept crashing and getting really hot.
We dusted it out and found one of the fans had gotten so clogged it had actually been dammaged and had to be replaced.

On 3/05/2016 9:21 a.m., Sharni-Lee Ward wrote:
...I don't even know what you mean by half of what you said and all of
it sounds terrifying. All I can say is that since this wasn't happening
before I got my Braille Display, and that NVDA updated to 2016.1 only a
few days before I got said Braille Display, that I can only imagine it
is the culprit somehow. I don't have the bandwidth to chase down
software currently and the prospect of spending hours and hours doing
things that have me on edge the entire time and possibly not solving my
problem in any way (like when Firefox was acting up last year) makes me
very uncomfortable. I don't think this warrants such an extreme. It's
probably the driver for my Braille Display, as I had it plugged in for a
little while in conjunction with the snapshot, so I could read some
things in Braille, and then I disconnected it before I went to write. It
lasted a lot longer than it did previously, though it was at times slow
to respond. I'm a pretty fast typer when I get going so I thought it was
possible the system wasn't keeping up with my typing for some reason,
although Thunderbird's fine with it.


On 3/05/2016 6:51 AM, Shaun Everiss wrote:
Hmmm well this is getting stranger and stranger.
Right now it could be anything from your braille display drivers to
hardware.
Firstly I'd tackle the os.
Since I don't know what is going on I suggest you just reformat.
Next I'd like you to do a chkdsk on the hard drive.
I'd also like you to do a hdd analisis with speedfan which you can get
online.
It almost looks like malware got in, or a bad drive or something like
that.
I have not had things like this on my systems but when I have it has
been dust in the system or a blocked fan.
I did a clearout of a system and replaced the power supply, and
regreased the heat sink and it got rid of that sucker.
Another thing you can do I guess is to get ccleaner go to the tools
and startup pain and save a text file of the startup programs and also
go to brouser cleanup and save the text files of that.
Anyway send me those files off list and maybe I can help you.
We need to establish if it freezes with nvda loaded.
I'd also like you to get a boot cd or one of them and get a sightling
actually run a memmory diagnostic for you.
I'd like a malware and virus scan to be run though it sounds like
hardware.
I'd also do a stress test with pcpitstop.
While pcpitstop is sensitive and wrigged for you to buy their software
and also while its got some adds in it, it is still a good tool in
telling you what could be the problem.
Next I'd also like to get updated drivers for your hardware
intel and amd have driver updaters intel driver update and amd drive
autodetect are what come to mind.
I'd also like to get a bios upgrade.
Out of all these it sounds like a bad power supply, busted fan or
overheating unit.
However if a sightling can do things without it locking well this is
getting a bit hard to diagnose now.



On 3/05/2016 4:17 a.m., Sharni-Lee Ward wrote:
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.









.




Re: NVDA still freezing, don't know what the deal is

Arlene
 

Oh,then I'd run chkdsk before you have to format. Then try disk defragment and disk clean up. If it still freezes then maybe you have to get a sighted person to go into the bios and see what can be the problem. Before you have to format. Cause if you did format it. You may still end up with that problem.

-----Original Message-----
From: Sharni-Lee Ward [mailto:sharni-lee.ward@hotmail.com]
Sent: May-02-16 2:11 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA still freezing, don't know what the deal is

No, I do not have a backup screen reader. NVDA is the only free one I
know of and I am happy with it. I considered getting a Braille Display
more beneficial than Jaws, which I would have to pay $500 per year to
keep updated. And I don't have the bandwidth to even download the demo.
I don't like Jaws anyway. I was never taught how to properly use most
Jaws specific commands when I did use it in school. That was ten years
ago now, so it likely wouldn't help me much anyways.


On 2/05/2016 1:30 PM, Arlene wrote:
Hi, What other screen reader do you have on your computer? If you have a back up screen reader besides NVDA why not try it to make sure it's not your Braille Display? It sounds like you might have botched up a setting while setting it up for it to run on NVDA. If it works on your back up screen reader, then there's something up with a setting for NVDA.

-----Original Message-----
From: Sharni-Lee Ward [mailto:sharni-lee.ward@hotmail.com]
Sent: May-01-16 4:01 PM
To: nvda@nvda.groups.io
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.









Re: NVDA still freezing, don't know what the deal is

Arlene
 

Hey, before you have to format the computer. Why not run chkdsk and then go
into the bios and see what can be the problem. I'd use format as the last
resort. Or if you just want to do it and get it over with. then go ahead and
do one. Good luck!

-----Original Message-----
From: Sharni-Lee Ward [mailto:sharni-lee.ward@hotmail.com]
Sent: May-02-16 9:17 AM
To: nvda@nvda.groups.io
Subject: 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\_e
speak.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\_e
speak.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\_e
speak.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\_e
speak.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\_e
speak.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\_e
speak.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\_e
speak.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\_e
speak.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.







Re: File recovery tool

mr. Chikodinaka Oguledo&mrs. AdonnihHappiness Obima Oguledo
 

go to https://www.grc.com purchis spin ritetht. Use it to recover your
files & so so much much much more! Good luck

On 5/2/16, Tony James <megatronjames@gmail.com> wrote:
Ok thx. No, this is just a simple undelete. The drive is fine, it's just I
want to see if I can get a file back

Tony JAmes, untouched and alive!

On May 2, 2016, at 4:40 PM, Shaun Everiss <sm.everiss@gmail.com> wrote:

recuva should handle stuff its on piriform.com
Its free
However just a warning I had an flash drive go bad on me.
If it does you may not be able to get anything back.
It happened to me once.
Saying that I have flash disks that have lasted longer than my magnetic
drives.



On 3/05/2016 4:20 a.m., Tony James wrote:
Hi, I am wondering if there is a program out there for recovering files
that have been deleted that is also accessible for NVDA. Specifically, I
want to see if I can recover files from an SD card. Thx

Tony JAmes, untouched and alive!



--
• Watch your thoughts, for they become words.
Watch your words, for they become actions.
Watch your actions, for they become habits.
Watch your habits, for they become character.
Watch your character, for it becomes your destiny.


Re: File recovery tool

Tony James <megatronjames@...>
 

Ok thx. No, this is just a simple undelete. The drive is fine, it's just I want to see if I can get a file back

Tony JAmes, untouched and alive!

On May 2, 2016, at 4:40 PM, Shaun Everiss <sm.everiss@gmail.com> wrote:

recuva should handle stuff its on piriform.com
Its free
However just a warning I had an flash drive go bad on me.
If it does you may not be able to get anything back.
It happened to me once.
Saying that I have flash disks that have lasted longer than my magnetic drives.



On 3/05/2016 4:20 a.m., Tony James wrote:
Hi, I am wondering if there is a program out there for recovering files that have been deleted that is also accessible for NVDA. Specifically, I want to see if I can recover files from an SD card. Thx

Tony JAmes, untouched and alive!


Re: NVDA still freezing, don't know what the deal is

Kenny Peyatt jr. <p.wildcat1234@...>
 

Hi if you want i can forward the log you sent over to the nvda developers li9st.
Kenny Peyatt jr.

On 5/2/2016 3:15 PM, Sharni-Lee Ward wrote:
I forgot to mention that last log was made in the old snapshot I have,
not the official installation. But I would still like a translation of
those errors from someone who understands them better than I do.


On 3/05/2016 2:17 AM, Sharni-Lee Ward wrote:
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.






Re: NVDA still freezing, don't know what the deal is

Sharni-Lee Ward
 

...I don't even know what you mean by half of what you said and all of
it sounds terrifying. All I can say is that since this wasn't happening
before I got my Braille Display, and that NVDA updated to 2016.1 only a
few days before I got said Braille Display, that I can only imagine it
is the culprit somehow. I don't have the bandwidth to chase down
software currently and the prospect of spending hours and hours doing
things that have me on edge the entire time and possibly not solving my
problem in any way (like when Firefox was acting up last year) makes me
very uncomfortable. I don't think this warrants such an extreme. It's
probably the driver for my Braille Display, as I had it plugged in for a
little while in conjunction with the snapshot, so I could read some
things in Braille, and then I disconnected it before I went to write. It
lasted a lot longer than it did previously, though it was at times slow
to respond. I'm a pretty fast typer when I get going so I thought it was
possible the system wasn't keeping up with my typing for some reason,
although Thunderbird's fine with it.

On 3/05/2016 6:51 AM, Shaun Everiss wrote:
Hmmm well this is getting stranger and stranger.
Right now it could be anything from your braille display drivers to
hardware.
Firstly I'd tackle the os.
Since I don't know what is going on I suggest you just reformat.
Next I'd like you to do a chkdsk on the hard drive.
I'd also like you to do a hdd analisis with speedfan which you can get
online.
It almost looks like malware got in, or a bad drive or something like
that.
I have not had things like this on my systems but when I have it has
been dust in the system or a blocked fan.
I did a clearout of a system and replaced the power supply, and
regreased the heat sink and it got rid of that sucker.
Another thing you can do I guess is to get ccleaner go to the tools
and startup pain and save a text file of the startup programs and also
go to brouser cleanup and save the text files of that.
Anyway send me those files off list and maybe I can help you.
We need to establish if it freezes with nvda loaded.
I'd also like you to get a boot cd or one of them and get a sightling
actually run a memmory diagnostic for you.
I'd like a malware and virus scan to be run though it sounds like
hardware.
I'd also do a stress test with pcpitstop.
While pcpitstop is sensitive and wrigged for you to buy their software
and also while its got some adds in it, it is still a good tool in
telling you what could be the problem.
Next I'd also like to get updated drivers for your hardware
intel and amd have driver updaters intel driver update and amd drive
autodetect are what come to mind.
I'd also like to get a bios upgrade.
Out of all these it sounds like a bad power supply, busted fan or
overheating unit.
However if a sightling can do things without it locking well this is
getting a bit hard to diagnose now.



On 3/05/2016 4:17 a.m., Sharni-Lee Ward wrote:
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.









.


Re: Survey: NVDACon Non Visual Desktop Access Users and Developers Conference for South Asia

 

Hmmm.
I have never seen actual communities sites for either country.

That is there is no central place, everyone comes here, etc.
I am unsure how big our's actually is, etc.

On 3/05/2016 3:02 a.m., Bhavya shah wrote:
Hi Shaun,
For that, NVDA user communities in Australia and New Zealand will need
to proactively engage in attending and learning organisation of such
conferences, and either a physical gathering or an online event could
be organized. Regional and language communities need to take charge of
their respective audiences.
Thanks.

On 5/2/16, Shaun Everiss <sm.everiss@gmail.com> wrote:
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




Re: NVDA still freezing, don't know what the deal is

 

Hmmm well this is getting stranger and stranger.
Right now it could be anything from your braille display drivers to hardware.
Firstly I'd tackle the os.
Since I don't know what is going on I suggest you just reformat.
Next I'd like you to do a chkdsk on the hard drive.
I'd also like you to do a hdd analisis with speedfan which you can get online.
It almost looks like malware got in, or a bad drive or something like that.
I have not had things like this on my systems but when I have it has been dust in the system or a blocked fan.
I did a clearout of a system and replaced the power supply, and regreased the heat sink and it got rid of that sucker.
Another thing you can do I guess is to get ccleaner go to the tools and startup pain and save a text file of the startup programs and also go to brouser cleanup and save the text files of that.
Anyway send me those files off list and maybe I can help you.
We need to establish if it freezes with nvda loaded.
I'd also like you to get a boot cd or one of them and get a sightling actually run a memmory diagnostic for you.
I'd like a malware and virus scan to be run though it sounds like hardware.
I'd also do a stress test with pcpitstop.
While pcpitstop is sensitive and wrigged for you to buy their software and also while its got some adds in it, it is still a good tool in telling you what could be the problem.
Next I'd also like to get updated drivers for your hardware
intel and amd have driver updaters intel driver update and amd drive autodetect are what come to mind.
I'd also like to get a bios upgrade.
Out of all these it sounds like a bad power supply, busted fan or overheating unit.
However if a sightling can do things without it locking well this is getting a bit hard to diagnose now.

On 3/05/2016 4:17 a.m., Sharni-Lee Ward wrote:
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.








.


Re: File recovery tool

 

recuva should handle stuff its on piriform.com
Its free
However just a warning I had an flash drive go bad on me.
If it does you may not be able to get anything back.
It happened to me once.
Saying that I have flash disks that have lasted longer than my magnetic drives.

On 3/05/2016 4:20 a.m., Tony James wrote:
Hi, I am wondering if there is a program out there for recovering files that have been deleted that is also accessible for NVDA. Specifically, I want to see if I can recover files from an SD card. Thx

Tony JAmes, untouched and alive!


Re: NVDA still freezing, don't know what the deal is

Sharni-Lee Ward
 

I forgot to mention that last log was made in the old snapshot I have,
not the official installation. But I would still like a translation of
those errors from someone who understands them better than I do.

On 3/05/2016 2:17 AM, Sharni-Lee Ward wrote:
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.







Re: Navigational sounds

Lino Morales
 

Its working here just fine Brian and I'm running Firefox V 46 64 bit and WIN 10

On 5/2/2016 4:53 AM, Brian's Mail list account wrote:
No I don't want it to duck in this case but as I say, if anyone out there still has the clicking, end of download etc still working on Firefox with navigational sounds add in, do let me know.
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: "David Moore" <jesusloves1966@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Monday, May 02, 2016 2:04 AM
Subject: Re: [nvda] Navigational sounds


Windows 8 and above is correct! There's a reason to upgrade to win10 LOL!

-----Original Message----- From: Chris Mullins
Sent: Sunday, May 1, 2016 2:04 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Navigational sounds

I think audio ducking only works on windows 8 and above.

Cheers
Chris

-----Original Message-----
From: Jacob Kruger [mailto:jacob@blindza.co.za]
Sent: 01 May 2016 14:51
To: nvda@nvda.groups.io
Subject: Re: [nvda] Navigational sounds

Sound ducking?

As in, if remember correctly, it won't work on XP, but, will work on later
versions of windows if activated/turned on?

Stay well

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

On 2016-05-01 12:36 PM, Brian's Mail list account wrote:
Rather strangely, the click sound amongst others seems not to be being
played any more in IE or Firefox even though the start navigation
sound is still selected and plays from the control panel dialogue fine
on both
Windows7 and 10. anyone else noticed this. One is using a usb sound
card the other the built in realtek one so i doubt if that is the issue.
It seems to be working on xp though, which is, as someone once said,
illogical.

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.













Re: codefactory eloquence and vocalizer

Isaac <bigikemusic@...>
 

thanks

----- Original Message -----
From: "Rui Fontes" <rui.fontes@tiflotecnia.com>
To: <nvda@nvda.groups.io>
Sent: Monday, May 2, 2016 5:59 AM
Subject: Re: [nvda] codefactory eloquence and vocalizer


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





NVDACon 2016: Closing remarks from the outgoing chair, regional NVDACon plan, Derek Riemer appointed next international NVDACon organizers chair

 

Dear members of the NVDA community:

 

Thank you for taking part in NVDACon International 2016 (Tenth Anniversary Edition). I still can’t believe how successful this gathering was: reflecting upon NVDA’s history, looking at its potential and launching NVDA movement campaign.

 

I’d like to take this time to thank those who’ve helped out with NVDACon:

·         NVDACon group: for your amazing assistance with organizing, promoting and participating in NVDACon 2016.

·         Presenters: Lucy Greco, Pranav Lal, Dave Williams, Sean Randall, Fernando, Sina Bahram, Davy Kager, Mick and Jamie from NV Access and others. Also I’d like to thank Marco Zehe from Mozilla for showing interest in participating in this conference.

·         Engineers: Michael Hansen (Applevis) for audio editing.

·         NVDA translators for spreading the news about this conference to various language communities.

·         All NVDA community members.

 

Second, there is a famous Korean saying that translates to, “it takes a decade to change a mountainous landscape”. I believe that, as we continue to celebrate NVDA’s tenth anniversary (throughout 2016), we need a fresher face of NVDACon leadership. As you may know by now, it takes dedication to lead an effort like this, and being the chair of NVDACon organizers means you are answerable to the community and will need to collaborate with many people.

 

As I was thinking about who’ll take this operation to the next level, one person stood out the most: a student who have shown potential to become the next Mick and Jamie, the next leader in promoting screen reading excellence, an influential member of this community with NVDACon presentation experience, and a born leader who understands the challenges associated with this role and is ready to embark on this journey. And I found this person in Derek Riemer (University of Colorado at Boulder), thus I hereby appoint him as the next chair of international NVDACon organizers. He’ll also be in charge of NVDACon US, which will take place later this year.

 

In regards to regional gatherings, they can range in scope from a single meeting (like NVDACon Korea) to one or two day event featuring well-known speakers. When formulating this plan, NVDACon organizers agreed that the international gathering (to be held annually from now on to reduce burden on NV Access) shall have precedence over others (mostly in terms of length), and that the chair of the international NVDACon organizers shall serve as first among equals in the group of regional NVDACon leaders. The chair of the international NVDACon organizers can also serve as a member of the organizing committee for one or more regional conferences.

 

Few guidelines for regional gatherings:

·         If a multinational NVDACon or a meeting with wide geographic impact (including international one) is to be held, it should be organized by a committee, with NVDA community members, presenters, engineers and others serving as members lead by one or more chairs (if in doubt, take NVDACon 2016 organizing committee (NVDACon group) as an example).

·         Unless an exception is granted, archives of regional gatherings and presentations thereof should be made available to members of the public.

·         Organizing committees for regional gatherings should have regular planning meetings to discuss various topics, including presentations, schedule, promotion and others.

·         If a gathering will feature multiple presentations, the committee should organize a “speakers luncheon” or a similar event to meet with presenters two weeks to a month before conference is due to begin. The purpose of such a meeting is to meet presenters and hear about their topics and to finalize the conference schedule (in case of Lightning Talks, to negotiate speaking order).

·         Organizing committee members should be willing to serve, listen to feedback, and be ready to answer questions from members of the public regarding their conferences.

·         Most importantly, have fun.

 

Lastly, as I’m stepping down from chairmanship of international NVDACon organizers (not the Tenth Anniversary Planning Committee, which I’ll continue to lead until end of this year), I’d like to talk about one important topic brought up throughout NVDACon 2016:

 

NonVisual Desktop Access is more than a screen reader now. NVDA is more than a free, open-source, community-driven assistive software package for Microsoft Windows. NVDA is more than a tool used by thousands of people around the world.

 

Rather, NVDA is a global phenomenon. NVDA is a global thing. NonVisual Desktop Access is a movement: access to information by those who couldn’t enjoy this gift, a group of people taking the initiative to serve others rather than be served, a group of enthusiasts willing to open the doors to employment, education and more to other people, and an initiative to show that blind folks can make a difference by utilizing their talents. And this movement has been in the making for the last ten years, and I believe it is time to move this momentum forward. Let NVDACon International 2016 serve as a Launchpad for this movement for years to come.

 

In closing, I’d like to evoke a quote from Jesus of Nazareth which summarizes the core message of NVDA, NVDA movement, NVDACon 2016 and other tenth anniversary events:` “I did not come to the world to be served, but to serve and to lay down my life for all. Whoever wishes to be greatest among you must become a servant of all.”

 

Thank you. Please help Derek and his team as they organize the next big adventure in NVDA’s history: NVDACon International 2017 and other gatherings.

 

Sincerely,

Joseph s. Lee

Translator, code contributor and community add-ons reviewer, NVDA screen reader project

Chair, NVDA Tenth Anniversary Planning Committee

Former chair, NVDACon International organizing committee

Chief organizer, NVDACon Korea

 

P.S. The NVDACon group will continue to serve as a discussion venue for other tenth anniversary events, and will serve as a committee room for NVDACon 2017 during its planning phase.