Date   

Re: GMail, PDF and NVDA

 

The answer to this question depends on a number of factors, including the word processing program you're using.

Libre Office Writer can open a PDF file without the need for any copy and paste.  I'm not sure it can save it as a PDF, but I do know it can open one from its native format.  More recent versions of MS-Office can do this, too.

If you're using a word processor that can do this then the easiest thing is to simply save the PDF attachment to your drive and then open it within the word processor itself.

Brian
-- 

Never underestimate the difficulty of changing false beliefs by facts. 
   ~ Henry Rosovsky

    



nvda line number for deaf and blind

ilanvpnina@...
 
Edited

hello i am deaf and blind

and using nvda

i tried  all shortcuts and also

changed

the pref. document  fromatting to include line nmuber

but i dont see the braille number in my braille dispaly

any idea or help?

thanks

#HELP #BUG #DEAF



Those using Outlook expres with multiple identities

Brian's Mail list account BY <bglists@...>
 

Now that we have a version of Outlook Express that works on windows 7 to 10, I thought it might be a good idea to repeat this little batch file here.
As many have found when switching identities a lot O-E can get confused if nvda is running and refuse to display messages or indeed allow entry of messages. The reasons for this are unclear but have been going on even in windows xp at times even when the preview pane is disabled.
My quick and dirty fix is not really a fix but reboots Outlook express into the same identity that has stopped working properly. You put this batch file in the working directory of Outlook Express. the one with the exe file in it, and call the batch file from a desktop shortcut instead of its normal entry shortcut.
Here is the batch file.

@echo off

taskkill /f /im msimn.exe
ping -n 5 127.0.0.1>nul

start MSIMN.EXE
exit



This then reboots or runs Outlook Express either in its default identity if its the first time you ran it, or in the current one if its stopped working correctly as above.
For the curious, it forcibly terminates Outlook Express and everything else it has running, then waits for the dust to settle, and reboots it in the same identity.

Hope it helps.
I'm sure this is due to an interaction with nvda, but nobody seems to have found the culprit in some years now, so at least this is a work around.
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: voices again

Brian's Mail list account BY <bglists@...>
 

Which is what I was attempting to find an answer to, as in theory, both should sound the same in my view, but did not when i tested them, admitedly on a bit of a slow computer.
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: "Rui Fontes" <rui.fontes@tiflotecnia.com>
To: <nvda@nvda.groups.io>
Sent: Tuesday, May 03, 2016 11:33 AM
Subject: Re: [nvda] voices again


The vocalizer voices, from Tiflotecnia and Code Factory, are not SAPI5.
Eloquence addon from Code Factory, is not SAPI5.
Eloquence for Windows, from Code Factory, and sold by Tiflotecnia, is SAPI5.

Best regards,

Rui Fontes
Tiflotecnia, Lda.


-----Mensagem Original-----
De: Brian's Mail list account
Data: terça-feira, 3 de maio de 2016 09:33
Para: nvda@nvda.groups.io
Assunto: Re: [nvda] voices again

That simply should not happen after all, lots of sappi 5 voices coexist.
Could the drivers be different, is one maybe newer than the other?

I think this is a question to ask the codefactory people.
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: "Isaac" <bigikemusic@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Tuesday, May 03, 2016 8:34 AM
Subject: [nvda] voices again


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







Re: voices again

Brian's Mail list account BY <bglists@...>
 

Yes but apparently not on that machine.
for no obvious reason.
Have neither as I really have too many synths and voices already, unless you have one that sounds sexy that is, I don't think any of them can claim to sound like that...yet...:-)

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: "Rui Fontes" <rui.fontes@tiflotecnia.com>
To: <nvda@nvda.groups.io>
Sent: Tuesday, May 03, 2016 11:31 AM
Subject: Re: [nvda] voices again


It is possible to use both...

Regards,

Rui Fontes
Tiflotecnia, Lda.

-----Mensagem Original-----
De: Isaac
Data: terça-feira, 3 de maio de 2016 08:34
Para: nvda@nvda.groups.io
Assunto: [nvda] voices again


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





Re: voices again

Brian's Mail list account BY <bglists@...>
 

OK so are they both the same kind or are they different, ie do you need to switch synth to use them. I cannot really see how a sappi 5 installation can affect another type of synth.
Do you see these voices and their synth still after installing the new one?
If you do but they just do not work, might be worth removing them and reinstalling.
I had a similar issue with a couple of Sappi 4 voices some time ago. Turned out to be an updated synth package.
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: "Isaac" <bigikemusic@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Tuesday, May 03, 2016 9:37 AM
Subject: Re: [nvda] voices again


these aren't sapi 5 voices, nvda addons
----- Original Message -----
From: "Brian's Mail list account" <bglists@blueyonder.co.uk>
To: <nvda@nvda.groups.io>
Sent: Tuesday, May 3, 2016 3:33 AM
Subject: Re: [nvda] voices again


That simply should not happen after all, lots of sappi 5 voices coexist. Could the drivers be different, is one maybe newer than the other?

I think this is a question to ask the codefactory people.
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: "Isaac" <bigikemusic@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Tuesday, May 03, 2016 8:34 AM
Subject: [nvda] voices again


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





Re: Navigational sounds

Brian's Mail list account BY <bglists@...>
 

I need to do that next. Its interesting though as the latest firefox on xp still works perfectly.
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: "Gene" <gsasner@ripco.com>
To: <nvda@nvda.groups.io>
Sent: Tuesday, May 03, 2016 10:50 AM
Subject: Re: [nvda] Navigational sounds


have you tested with an earlier version of firefox to see if the sounds still work? You can easily get an earlier version of firefox portable and check.

Gene
----- Original Message -----


From: Brian's Mail list account
Sent: Tuesday, May 03, 2016 3:15 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Navigational sounds


Well I have got the end of download back but cannot get the click to work
any more. Its Firefox 47 beta, amaybe it needs a downdate.
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: "Lino Morales" <linomorales001@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Monday, May 02, 2016 7:54 PM
Subject: Re: [nvda] Navigational sounds


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: voices again

Rui Fontes
 

The vocalizer voices, from Tiflotecnia and Code Factory, are not SAPI5.
Eloquence addon from Code Factory, is not SAPI5.
Eloquence for Windows, from Code Factory, and sold by Tiflotecnia, is SAPI5.

Best regards,

Rui Fontes
Tiflotecnia, Lda.


-----Mensagem Original-----
De: Brian's Mail list account
Data: tera-feira, 3 de maio de 2016 09:33
Para: nvda@nvda.groups.io
Assunto: Re: [nvda] voices again

That simply should not happen after all, lots of sappi 5 voices coexist.
Could the drivers be different, is one maybe newer than the other?

I think this is a question to ask the codefactory people.
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: "Isaac" <bigikemusic@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Tuesday, May 03, 2016 8:34 AM
Subject: [nvda] voices again


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


Re: voices again

Rui Fontes
 

It is possible to use both...

Regards,

Rui Fontes
Tiflotecnia, Lda.

-----Mensagem Original-----
De: Isaac
Data: tera-feira, 3 de maio de 2016 08:34
Para: nvda@nvda.groups.io
Assunto: [nvda] voices again


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


Re: big problem with voices

Rui Fontes
 

Hello!
One set of voices should not make problems on the other...

If you want, contact us in private.

Best regards,

Rui Fontes
Tiflotecnia, Lda.


-----Mensagem Original-----
De: Isaac
Data: tera-feira, 3 de maio de 2016 06:56
Para: nvda@nvda.groups.io
Assunto: [nvda] big problem with voices


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?


Re: codefactory eloquence and vocalizer

Rui Fontes
 

Hello!

Tiflotecnia is making a new version of Vocalizer for NVDA. It is based in
the newest version of Vocalizer Expressive voices, 2.0, and should be
released in end of May or June...

Best regards,

Rui Fontes
Tiflotecnia, Lda.



-----Mensagem Original-----
De: Kelly Sapergia
Data: tera-feira, 3 de maio de 2016 02:43
Para: nvda@nvda.groups.io
Assunto: Re: [nvda] codefactory eloquence and vocalizer

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: Navigational sounds

Gene
 

have you tested with an earlier version of firefox to see if the sounds still work?  You can easily get an earlier version of firefox portable and check. 
 
Gene

----- Original Message -----

Sent: Tuesday, May 03, 2016 3:15 AM
Subject: Re: [nvda] Navigational sounds

Well I have got the end of download back but cannot get the  click to work
any more. Its Firefox 47 beta, amaybe it needs a  downdate.
 Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Lino Morales" <linomorales001@...>
To: <nvda@nvda.groups.io>
Sent: Monday, May 02, 2016 7:54 PM
Subject: Re: [nvda] Navigational sounds


> 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@...
>> Sent via blueyonder.
>> Please address personal email to:-
>> briang1@..., putting 'Brian Gaff'
>> in the display name field.
>> ----- Original Message ----- From: "David Moore"
>> <jesusloves1966@...>
>> 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@...]
>>> 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@...
>>>> Sent via blueyonder.
>>>> Please address personal email to:-
>>>> briang1@..., putting 'Brian Gaff'
>>>> in the display name field.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>
>
>
>




Re: voices again

Isaac <bigikemusic@...>
 

these aren't sapi 5 voices, nvda addons

----- Original Message -----
From: "Brian's Mail list account" <bglists@blueyonder.co.uk>
To: <nvda@nvda.groups.io>
Sent: Tuesday, May 3, 2016 3:33 AM
Subject: Re: [nvda] voices again


That simply should not happen after all, lots of sappi 5 voices coexist. Could the drivers be different, is one maybe newer than the other?

I think this is a question to ask the codefactory people.
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: "Isaac" <bigikemusic@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Tuesday, May 03, 2016 8:34 AM
Subject: [nvda] voices again


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



Re: voices again

Brian's Mail list account BY <bglists@...>
 

That simply should not happen after all, lots of sappi 5 voices coexist. Could the drivers be different, is one maybe newer than the other?

I think this is a question to ask the codefactory people.
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: "Isaac" <bigikemusic@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Tuesday, May 03, 2016 8:34 AM
Subject: [nvda] voices again


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


Re: GMail, PDF and NVDA

Brian's Mail list account BY <bglists@...>
 

Is this an online pdf then?
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 Russell" <david.sonofhashem@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Tuesday, May 03, 2016 3:37 AM
Subject: [nvda] GMail, PDF and NVDA


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: NVDA still freezing, don't know what the deal is

Brian's Mail list account BY <bglists@...>
 

No, to me unless there has been some significant malware or crash from a bit of software, then the registry can be repaired automatically by windows.

Beware however, as next week is update week.
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 11:25 PM
Subject: Re: [nvda] NVDA still freezing, don't know what the deal is


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: NVDA still freezing, don't know what the deal is

Brian's Mail list account BY <bglists@...>
 

Exactly. Just do one thing at a time and test as I say disable to driver or remove it then test a lot. However I'd test with the master snapshot first before doing anything if you have not done so.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Sharni-Lee Ward" <sharni-lee.ward@hotmail.com>
To: <nvda@nvda.groups.io>
Sent: Monday, May 02, 2016 10:21 PM
Subject: Re: [nvda] NVDA still freezing, don't know what the deal is


...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

Brian's Mail list account BY <bglists@...>
 

I agree about chkdsk, but not reformatting and reinstalling. I never solved anything permanently by doing this, at least not after Windows 98!
I'd remove the driver next or at least disable it in the device manager.

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: "Shaun Everiss" <sm.everiss@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Monday, May 02, 2016 9:51 PM
Subject: Re: [nvda] 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: NVDA still freezing, don't know what the deal is

Brian's Mail list account BY <bglists@...>
 

I see by this log that the driver for the display is still being seen. Is it possible to uninstall it and then set no Braille and see what happens.
The error seems to be saying that the display is trying to do something that it cannot, ie its out of range or something and if the driver is doing this it should go away if its a completely clean system.
I'd warn agains reinstalling the operating system or whatever, as all that achieves is mega hassle and a ticking time bomb until the problem starts again. Best to try to find the smoking gun, or at least that has been my experience of such things in the past.


Might be worth airing this on the dev list.

Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Sharni-Lee Ward" <sharni-lee.ward@hotmail.com>
To: <nvda@nvda.groups.io>
Sent: Monday, May 02, 2016 8:15 PM
Subject: Re: [nvda] NVDA still freezing, don't know what the deal is


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

Brian's Mail list account BY <bglists@...>
 

Well I have got the end of download back but cannot get the click to work any more. Its Firefox 47 beta, amaybe it needs a downdate.
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: "Lino Morales" <linomorales001@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Monday, May 02, 2016 7:54 PM
Subject: Re: [nvda] Navigational sounds


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.