Date   

Re: Chatty infty and math with nvda

hbentley@...
 

HI Erik, 

I've used nvda and chattyinfty for math, but it won't help you that much without inftyreader.  You need to convert the documents to a format that chattyinfty can read, for it the latter to be of any use.  This is what InftyReader does, (very well).

The setup I use now is I convert the documents from the pdf with embedded text set inftyreader, and set the output to .xml, which can be opened by microsoft word.  You need to purchase MathType, and install it in Microsoft word, then download a free toolbar, in addition, called Central Access Toolbar, or CAT for short.., here's the link.. while you're there, download central access reader... Google Link to Central Access Toolbar, (I Couldn't Find it online anymore, but I'm sure its out there somewhere): https://drive.google.com/open?id=1utQC3vuq1GqgsRUJo6yfoZM_mVf44df0 and Central Access Reader:    
http://archive.org/download/CARSetup64/CAR_Setup_64.exe


CAT has to be installed in Microsoft Word, and what you do is recognize your pdf file with infty reader => export as .xml => open with MS Word=> click the "play" icon in the CAT toolbar under the "CAT" Tab, select "Recognized with InftyReader" from the drop down list on the right side of the screen, deselect "linearalize all equations", "unlinearize all equations", "highlight Equations", and "Convert OMML to Mathtype" - (we do the last step next, seperately), and hit the play button.  The plugin will transform your document into a well formatted version.

Next Hit the Mathtype Tab, (purchase here: https://store.wiris.com/en), click "convert equations" and make the following selections: 


Then wait for Mathtype to process your document, (much better to install Mathtype on a drive with as much space as possible, as it is kind of a memory hog).  

Wait for mathtype to finish converting, save document as .docx format, (you can do this before converting as well).

The open Central Access Reader, click the "plus" icon near the top left, and upload the .docx document you just saved... It will load to CAR and you can read it beautifully in this free application, much better than chattyinfty.

Let me know if you run into any trouble!!

Ben






On 25 May 2018 at 10:32, erik burggraaf <erik@...> wrote:
Hi all,

I would like to get a head start on next semester's math.  I have chatty infty and nvda.  Do I need any add-ons?  Is any one else using this setup who can give me some insider tips?

I haven't even got my computer set up.  It's a weekend project and I just haven't gotten around to it.

Thanks for any advice.

Best,

Erik








--
Ben Humphries


Re: sounds ?

Gene
 

Do other sounds work?  I think the sound you are describing is one Windows sound, which isn't working.  This sounds to me like the kind of problem that should be solved by running a restore point.  If you don't have one, I'm not sure how you might solve the problem.  In future, please describe the problem in detail as you did in this message.  Based on your current description, most of my previous message appears not to apply.  This isn't that Windows sounds aren't working in general.  One Windows sound may not be and I addressed that in this message.
 
Gene

----- Original Message -----
From: Danni
Sent: Friday, May 25, 2018 2:25 PM
Subject: Re: [nvda] sounds ?

NVDA is speaking fine now yesterday it kept double talking so shut it down for a couple hours since a reboot did no good but sounds lost are the ping it makes when am at the top or bottom of a document as well as the sound it makes if  try to do something it doesn't want me to do!
 
----- Original Message -----
Sent: Friday, May 25, 2018 12:23 PM
Subject: Re: [nvda] sounds ?

Hi


Is there any sounds at all on the computer? or are you getting Window sounds but not having nvda speaking?


Gene nz



On 5/26/2018 6:00 AM, Danni wrote:
 
I had to reboot several times yesterday because NVDA was not reading documents and realized this morning that I lost my sounds where do I find them to turn them back  on?
 


Re: sounds ?

Gene
 

You said you had to reboot a number of times yesterday.  Why?  Did you have freezes?  If you suddenly lose Windows sounds, and everything else works properly, you can look in the volume control settings to see what the volume level is for those sounds and, if there is a mute check box, that it is unchecked.  But this may be a problem, if you had an improper shutdown, caused by something else like a registry proboem.  You may want to check the volume control settings first.  If they are correct, if you have a system restore point or a you run a registry backup program, running a backup or a system restore point from before the problem may well be the easiest solution.  if you don't have something like this available, you should.  It's very important.  You never know when it may save you a lot of work and annoyance.
 
Regarding volume control settings, the easiest thing to do is probably to hold the Windows key, type r then release both keys.  Type sndvol in the run dialog, and press enter.  When the volume control opens, tab around and see what you see for Windows sounds.
 
Gene

----- Original Message -----
From: Danni
Sent: Friday, May 25, 2018 2:24 PM
Subject: Re: [nvda] sounds ?

The only question I can answer is windows 7! am guessing with those questions it's not nvda that had the sounds but my computer? if that's the case I'll ask my computer guy about it!
 
----- Original Message -----
Sent: Friday, May 25, 2018 12:17 PM
Subject: Re: [nvda] sounds ?

What generation of Windows are you using.  It may be slightly different on Windows 7 than Windows 10, for instance.

Also, what is the make/model of your computer and did it come with function keys that were mapped to doing things like muting, increasing/decreasing volume, increasing/decreasing screen brightness, etc.  You may be able to exploit those, but you'd have to know which are which for your specific make/model.

--

Brian - Windows 10 Home, 64-Bit, Version 1803, Build 17134  

     After all, a democracy based solely on the values of the majority, with no overriding ethical principles and processes, is nothing more than clubhouse democracy, great for those on the inside and a tyranny for those who fail to see eye to eye with the majority.

         ~ Paul Noeldner, May 16, 2007 

 

 


Re: sounds ?

Danni
 


Thanks Brian I will definitely do that!

----- Original Message -----
Sent: Friday, May 25, 2018 12:40 PM
Subject: Re: [nvda] sounds ?

Danni,

         If it turns out that your Windows sound output has been muted, be certain to ask your computer guy if there is a key or key sequence on your keyboard you can hit to unmute it (or to try to unmute it).

         On my HP laptop, where I've turned off the "Quick Function Keys" feature so that I have access to the F keys "as God intended," the F6 key is the mute/unmute toggle.  F7 is decrease volume and F8 is increase volume.  All of these only serve those functions if I'm holding down the Fn key plus the previously noted key together.  What's nice is even if the sound is muted, if you attempt to either increase or decrease volume it will unmute the sound as part of that.

--

Brian - Windows 10 Home, 64-Bit, Version 1803, Build 17134  

     After all, a democracy based solely on the values of the majority, with no overriding ethical principles and processes, is nothing more than clubhouse democracy, great for those on the inside and a tyranny for those who fail to see eye to eye with the majority.

         ~ Paul Noeldner, May 16, 2007 

 

 


Re: sounds ?

 

Danni,

         If it turns out that your Windows sound output has been muted, be certain to ask your computer guy if there is a key or key sequence on your keyboard you can hit to unmute it (or to try to unmute it).

         On my HP laptop, where I've turned off the "Quick Function Keys" feature so that I have access to the F keys "as God intended," the F6 key is the mute/unmute toggle.  F7 is decrease volume and F8 is increase volume.  All of these only serve those functions if I'm holding down the Fn key plus the previously noted key together.  What's nice is even if the sound is muted, if you attempt to either increase or decrease volume it will unmute the sound as part of that.

--

Brian - Windows 10 Home, 64-Bit, Version 1803, Build 17134  

     After all, a democracy based solely on the values of the majority, with no overriding ethical principles and processes, is nothing more than clubhouse democracy, great for those on the inside and a tyranny for those who fail to see eye to eye with the majority.

         ~ Paul Noeldner, May 16, 2007 

 

 


Re: sounds ?

Danni
 


I've not had this happen before so I have no clue if I have that specific key or not so I'll ask my computer guy about it or check my settings on the computer!

----- Original Message -----
Sent: Friday, May 25, 2018 12:33 PM
Subject: Re: [nvda] sounds ?

On Fri, May 25, 2018 at 12:30 pm, Danni wrote:
am guessing with those questions it's not nvda that had the sounds but my computer?
That's the presumption I'm operating on, too.   I have a friend who's an avid NVDA user and who's accidentally muted her Windows sound output in the past.  Luckily the keyboard she has actually has a dedicated button for mute/unmute that toggles the sound on if its off and off if its on.

Many computers can do this via hitting the Fn key along with the correct F key across the top.
 
--

Brian - Windows 10 Home, 64-Bit, Version 1803, Build 17134  

     After all, a democracy based solely on the values of the majority, with no overriding ethical principles and processes, is nothing more than clubhouse democracy, great for those on the inside and a tyranny for those who fail to see eye to eye with the majority.

         ~ Paul Noeldner, May 16, 2007 

 

 


Re: sounds ?

 

On Fri, May 25, 2018 at 12:30 pm, Danni wrote:
am guessing with those questions it's not nvda that had the sounds but my computer?
That's the presumption I'm operating on, too.   I have a friend who's an avid NVDA user and who's accidentally muted her Windows sound output in the past.  Luckily the keyboard she has actually has a dedicated button for mute/unmute that toggles the sound on if its off and off if its on.

Many computers can do this via hitting the Fn key along with the correct F key across the top.
 
--

Brian - Windows 10 Home, 64-Bit, Version 1803, Build 17134  

     After all, a democracy based solely on the values of the majority, with no overriding ethical principles and processes, is nothing more than clubhouse democracy, great for those on the inside and a tyranny for those who fail to see eye to eye with the majority.

         ~ Paul Noeldner, May 16, 2007 

 

 


Re: sounds ?

Danni
 

NVDA is speaking fine now yesterday it kept double talking so shut it down for a couple hours since a reboot did no good but sounds lost are the ping it makes when am at the top or bottom of a document as well as the sound it makes if  try to do something it doesn't want me to do!
 

----- Original Message -----
Sent: Friday, May 25, 2018 12:23 PM
Subject: Re: [nvda] sounds ?

Hi


Is there any sounds at all on the computer? or are you getting Window sounds but not having nvda speaking?


Gene nz



On 5/26/2018 6:00 AM, Danni wrote:
 
I had to reboot several times yesterday because NVDA was not reading documents and realized this morning that I lost my sounds where do I find them to turn them back  on?
 


Re: File explorer (maybe)

 

On Fri, May 25, 2018 at 10:20 am, slery wrote:
When I am in the windows menu and use the applications key that is not one of the options that comes up
My apologies, I misread in that it's the file location you're trying to find.

Are you using a standard account or an account with admin privileges?   I always use my account which has admin privileges, and if I'm on an item in a list of search results that is a file, and hit the menu/applications key or SHIFT+F10, the "Open file location" option is always there.  I'm speculating it might not be for a standard user.
 
--

Brian - Windows 10 Home, 64-Bit, Version 1803, Build 17134  

     After all, a democracy based solely on the values of the majority, with no overriding ethical principles and processes, is nothing more than clubhouse democracy, great for those on the inside and a tyranny for those who fail to see eye to eye with the majority.

         ~ Paul Noeldner, May 16, 2007 

 

 


Re: sounds ?

Danni
 


The only question I can answer is windows 7! am guessing with those questions it's not nvda that had the sounds but my computer? if that's the case I'll ask my computer guy about it!
 

----- Original Message -----
Sent: Friday, May 25, 2018 12:17 PM
Subject: Re: [nvda] sounds ?

What generation of Windows are you using.  It may be slightly different on Windows 7 than Windows 10, for instance.

Also, what is the make/model of your computer and did it come with function keys that were mapped to doing things like muting, increasing/decreasing volume, increasing/decreasing screen brightness, etc.  You may be able to exploit those, but you'd have to know which are which for your specific make/model.

--

Brian - Windows 10 Home, 64-Bit, Version 1803, Build 17134  

     After all, a democracy based solely on the values of the majority, with no overriding ethical principles and processes, is nothing more than clubhouse democracy, great for those on the inside and a tyranny for those who fail to see eye to eye with the majority.

         ~ Paul Noeldner, May 16, 2007 

 

 


Re: File explorer (maybe)

 

On Fri, May 25, 2018 at 10:20 am, slery wrote:
When I am in the windows menu and use the applications key that is not one of the options that comes up
That's not what he said to do.   You simply hit the Windows Key and immediately type in the two word phrase, "task scheduler."  The search results will have Task Scheduler, Desktop App as the first item unless you have done something very weird on your system and have something else named "task scheduler."  All you have to do after entering the search phrase is wait about half a second for the search to complete and hit Enter.  Task Manager then opens.
 
--

Brian - Windows 10 Home, 64-Bit, Version 1803, Build 17134  

     After all, a democracy based solely on the values of the majority, with no overriding ethical principles and processes, is nothing more than clubhouse democracy, great for those on the inside and a tyranny for those who fail to see eye to eye with the majority.

         ~ Paul Noeldner, May 16, 2007 

 

 


Re: File explorer (maybe)

 

I am trying to get clear about what's being asked here.

If it's how to get the path to a file you can do a Cortana/Windows search for the file, then when it shows up in the results and you have focus on it hit the menu/applications key or SHIFT+F10 and select "Open File location" from the pop up menu.  You'll open file explorer for the folder in which that file is located, with focus on that file, and can get the full path, including the file name, using the Copy Path button in the Home tab [or just hit ALT+H,CP].  You can then paste this where you need it.  One word of warning, though, it encloses the entire path in quotation marks, an example of which is:

"C:\Users\Public\Documents\BriTechGuy\Toolbox\Carry_With_Programs\Search_Everything\Everything-1.4.1.877.x64-Setup.exe"

You may need to remove those.

If you're trying to find task scheduler using Quentin's windows search method is the fastest way directly to it.

--

Brian - Windows 10 Home, 64-Bit, Version 1803, Build 17134  

     After all, a democracy based solely on the values of the majority, with no overriding ethical principles and processes, is nothing more than clubhouse democracy, great for those on the inside and a tyranny for those who fail to see eye to eye with the majority.

         ~ Paul Noeldner, May 16, 2007 

 

 


Re: sounds ?

Gene New Zealand <hurrikennyandopo@...>
 

Hi


Is there any sounds at all on the computer? or are you getting Window sounds but not having nvda speaking?


Gene nz



On 5/26/2018 6:00 AM, Danni wrote:
 
I had to reboot several times yesterday because NVDA was not reading documents and realized this morning that I lost my sounds where do I find them to turn them back  on?
 


Re: sounds ?

 

What generation of Windows are you using.  It may be slightly different on Windows 7 than Windows 10, for instance.

Also, what is the make/model of your computer and did it come with function keys that were mapped to doing things like muting, increasing/decreasing volume, increasing/decreasing screen brightness, etc.  You may be able to exploit those, but you'd have to know which are which for your specific make/model.

--

Brian - Windows 10 Home, 64-Bit, Version 1803, Build 17134  

     After all, a democracy based solely on the values of the majority, with no overriding ethical principles and processes, is nothing more than clubhouse democracy, great for those on the inside and a tyranny for those who fail to see eye to eye with the majority.

         ~ Paul Noeldner, May 16, 2007 

 

 


sounds ?

Danni
 

 
I had to reboot several times yesterday because NVDA was not reading documents and realized this morning that I lost my sounds where do I find them to turn them back  on?
 


Re: File explorer (maybe)

slery <slerythema@...>
 


When I am in the windows menu and use the applications key that is not one of the options that comes up I only get pin to task bar and a couple of other Advanced options that is what I tried first and there was no way to get a file location I am running the latest Windows 10 with the April 2018 update. Cindy

Get Outlook for Android


From: nvda@nvda.groups.io<nvda@nvda.groups.io> on behalf of Quentin Christensen <quentin@...>
Sent: Friday, May 25, 2018 2:46:48 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] File explorer (maybe)

 

If you press the windows key and then start typing "Task scheduler" it should come up. If you want to find out where it is, you can always press the applications / context menu key on the item instead of enter, and choose "Open file location" which will open it in File Explorer and you can check the address bar to see where it is.


Regards

Quentin.


On Fri, May 25, 2018 at 4:44 PM, slery <slerythema@...> wrote:


Okay, I am trying to use task scheduler but I need to find the file path to start the program. I did a search for grover.exe (assuming this is what I need for a windows app) but it only came up with a file called grover.exe.temp.DMP.



Can someone help me? Do the new window apps (an app downloaded from the windows store) follow a typical structure such as using a *.exe file or should I be looking for something else?



Cindy


Get Outlook for Android





-- 

Quentin Christensen
Training and Support Manager


Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/


Twitter: @NVAccess 


Re: A recurring error with the latest master snapshot

Marcia Yale
 

Thank you, Joseph! Restarting my computer seems to have fixed the problem!

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph
Lee
Sent: Friday, May 25, 2018 12:14 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] A recurring error with the latest master snapshot

Hi Marcia,
Ah, something I have experienced before. This dialog usually means that NVDA
cannot work well with certain applications or might not behave correctly
under some circumstances. Usually restarting your computer fixes this
problem.
Technical: somehow, NVDA Helper is unable to hook into deeper event
processing routines. I think numerous issues were raised on GitHub regarding
this problem.
Cheers,
Joseph


-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Marcia Yale
Sent: Friday, May 25, 2018 6:57 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] A recurring error with the latest master snapshot

Okay, here's the log with the control set to debug. I still have no clue
what I'm reading so I hope someone out there can figure out what is
happening.


INFO - __main__ (09:54:32.895):
Starting NVDA
INFO - core.main (09:54:33.145):
Config dir: C:\Users\Marcia\AppData\Roaming\nvda
INFO - config.ConfigManager._loadConfig (09:54:33.145):
Loading config: C:\Users\Marcia\AppData\Roaming\nvda\nvda.ini
INFO - config.ConfigManager._loadConfig (09:54:33.161):
Config loaded (after upgrade, and in the state it will be used by NVDA):
{u'schemaVersion': u'2', u'upgrade': {}, u'update': {u'autoCheck': u'True',
u'startupNotification': u'True'}, u'general': {u'language': u'en',
u'saveConfigurationOnExit': u'True', u'askToExit': u'False',
u'playStartAndExitSounds': u'True', u'loggingLevel': u'DEBUG',
u'showWelcomeDialogAtStartup': u'False'}, u'speech': {u'synth': u'espeak',
u'autoLanguageSwitching': u'False', u'outputDevice': u'Microsoft Sound
Mapper', u'symbolLevel': u'300', u'espeak': {u'voice': u'en-gb-x-rp',
u'variant': u'max', u'rate': u'80', u'pitch': u'43', u'inflection': u'75',
u'volume': u'100', u'beepForCapitals': u'True', u'sayCapForCapitals':
u'False'}}, u'braille': {u'display': u'noBraille', u'translationTable':
u'en-us-g2.ctb', u'inputTable': u'en-us-g2.ctb', u'expandAtCursor':
u'False', u'showCursor': u'False', u'messageTimeout': u'2', u'noBraille':
{u'port': u''}, u'freedomScientific': {u'port': u'auto'}}, u'keyboard':
{u'useCapsLockAsNVDAModifierKey': u'True', u'speakTypedCharacters':
u'False'}, u'documentFormatting': {u'reportRevisions': u'False',
u'reportSpellingErrors': u'False', u'reportTableHeaders': u'False',
u'reportTableCellCoords': u'True', u'reportLists': u'False',
u'reportBlockQuotes': u'False', u'reportFrames': u'False',
u'autoLanguageSwitching': u'False', u'reportClickable': u'False'}} DEBUG -
core.main (09:54:33.239):
setting language to en
INFO - core.main (09:54:33.239):
NVDA version master-15137,1cd171de
INFO - core.main (09:54:33.239):
Using Windows version 6.1.7601 service pack 1 workstation INFO - core.main
(09:54:33.239):
Using Python version 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018, 16:22:17) [MSC
v.1500 32 bit (Intel)]
INFO - core.main (09:54:33.239):
Using comtypes version 1.1.3
DEBUG - core.main (09:54:33.239):
Initializing add-ons system
DEBUG - addonHandler._getAvailableAddonsFromPath (09:54:33.255):
Listing add-ons from C:\Users\Marcia\AppData\Roaming\nvda\addons
DEBUGWARNING - touchHandler.touchSupported (09:54:33.282):
Touch only supported on Windows 8 and higher DEBUG - core.main
(09:54:33.371):
Initializing appModule Handler
DEBUG - core.main (09:54:33.371):
Initializing NVDAHelper
ERROR - RPC process 60284 (nvda.exe) (09:54:33.381):
Thread 59768, build\x86\remote\injection.cpp, inprocMgrThreadFunc, 168:
SetWinEventHook failed

DEBUG - core.main (09:54:33.421):
Speech Dictionary processing
DEBUG - speechDictHandler.SpeechDict.load (09:54:33.421):
Loading speech dictionary
'C:\Users\Marcia\AppData\Roaming\nvda\speechDicts\default.dic'...
DEBUG - speechDictHandler.SpeechDict.load (09:54:33.421):
1 loaded records.
DEBUG - speechDictHandler.SpeechDict.load (09:54:33.421):
Loading speech dictionary 'builtin.dic'...
DEBUG - speechDictHandler.SpeechDict.load (09:54:33.421):
3 loaded records.
DEBUG - core.main (09:54:33.421):
Initializing speech
INFO - synthDrivers.espeak.SynthDriver.__init__ (09:54:33.441):
Using eSpeak NG version 1.49.1 dev
DEBUG - speechDictHandler.SpeechDict.load (09:54:33.482):
Loading speech dictionary
'C:\Users\Marcia\AppData\Roaming\nvda\speechDicts\voiceDicts.v1\espeak\espea
k-English (Received Pronunciation).dic'...
DEBUG - speechDictHandler.SpeechDict.load (09:54:33.482):
file
'C:\Users\Marcia\AppData\Roaming\nvda\speechDicts\voiceDicts.v1\espeak\espea
k-English (Received Pronunciation).dic' not found.
INFO - synthDriverHandler.setSynth (09:54:33.482):
Loaded synthDriver espeak
INFO - core.main (09:54:33.482):
Using wx version 3.0.2.0 msw (classic)
DEBUG - core.main (09:54:33.482):
Initializing braille input
INFO - brailleInput.initialize (09:54:33.482):
Braille input initialized
DEBUG - core.main (09:54:33.482):
Initializing braille
INFO - braille.initialize (09:54:33.482):
Using liblouis version 3.5.0
INFO - braille.BrailleHandler.setDisplayByName (09:54:33.492):
Loaded braille display driver noBraille, current display has 0 cells.
DEBUG - core.main (09:54:33.492):
Initializing displayModel
DEBUG - core.main (09:54:33.492):
Initializing GUI
DEBUG - core.main (09:54:33.502):
initializing Java Access Bridge support
DEBUG - core.main (09:54:33.552):
Initializing winConsole support
DEBUG - core.main (09:54:33.552):
Initializing UIA support
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (09:54:33.552):
UIAutomation: IUIAutomation
DEBUG - core.main (09:54:34.151):
Initializing IAccessible support
DEBUG - core.main (09:54:34.151):
Initializing input core
DEBUGWARNING - inputCore.InputManager.loadLocaleGestureMap (09:54:34.151):
No locale gesture map for language en
DEBUGWARNING - inputCore.InputManager.loadUserGestureMap (09:54:34.151):
No user gesture map
DEBUG - core.main (09:54:34.151):
Initializing keyboard handler
DEBUG - core.main (09:54:34.151):
initializing mouse handler
DEBUG - core.main (09:54:34.161):
Initializing touchHandler
DEBUGWARNING - touchHandler.touchSupported (09:54:34.161):
Touch only supported on Windows 8 and higher DEBUG - core.main
(09:54:34.161):
Initializing global plugin handler
DEBUG - core.main (09:54:34.161):
Initializing core pump
DEBUG - core.main (09:54:34.161):
Initializing watchdog
DEBUG - core.main (09:54:34.161):
initializing updateCheck
INFO - core.main (09:54:34.161):
NVDA initialized
DEBUG - core.main (09:54:34.161):
entering wx application main loop
IO - speech.speak (09:54:34.181):
Speaking [u'nvdaHelperRemote (outprocMgrThreadFunc) dialog Error
registering focus winEvent hook'] IO - speech.speak (09:54:34.191):
Speaking [u'OK button']
IO - inputCore.InputManager.executeGesture (09:54:40.007):
Input: kb(desktop):space
IO - speech.speak (09:54:40.028):
Speaking [u'pressed']
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (09:54:40.197):
oleacc.AccessibleObjectFromEvent with window 16452220, objectID -4 and
childID 0: [Error -2147467259] Unspecified error DEBUGWARNING -
NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole
(09:54:40.237):
accRole failed: (-2147024809, 'The parameter is incorrect.', (None, None,
None, 0, None)) IO - speech.speak (09:54:40.257):
Speaking [u'Taskbar']
IO - inputCore.InputManager.executeGesture (09:54:42.266):
Input: kb(desktop):NVDA+n
IO - speech.speak (09:54:42.336):
Speaking [u'NVDA menu']
IO - inputCore.InputManager.executeGesture (09:54:43.677):
Input: kb(desktop):downArrow
IO - speech.speak (09:54:43.697):
Speaking [u'Preferences subMenu p']
IO - inputCore.InputManager.executeGesture (09:54:45.049):
Input: kb(desktop):downArrow
IO - speech.speak (09:54:45.078):
Speaking [u'Tools subMenu t']
IO - inputCore.InputManager.executeGesture (09:54:45.532):
Input: kb(desktop):rightArrow
IO - speech.speak (09:54:45.582):
Speaking [u'View log v']
IO - inputCore.InputManager.executeGesture (09:54:46.229):
Input: kb(desktop):enter
-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Brian's
Mail list account via Groups.Io
Sent: Friday, May 25, 2018 3:16 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] A recurring error with the latest master snapshot

Firstly have a look at it with the logging level set to debug, as this may
well show up more detail. I certainly get no such error here on the latest
master installed copy The windows internal number is correct though, as
this is just an internal designation.

If you are bored easily stop reading now as I'm pasting my debug log with no
errors and the add ons listed for comparison.


INFO - __main__ (08:06:41.973):
Starting NVDA
INFO - core.main (08:06:42.223):
Config dir: C:\Users\Brian\AppData\Roaming\nvda
INFO - config.ConfigManager._loadConfig (08:06:42.223):
Loading config: C:\Users\Brian\AppData\Roaming\nvda\nvda.ini
INFO - config.ConfigManager._loadConfig (08:06:42.255):
Config loaded (after upgrade, and in the state it will be used by NVDA):
{u'schemaVersion': u'2', u'upgrade': {}, u'update': {u'autoCheck': u'True',
u'startupNotification': u'True'}, u'general':
{u'showWelcomeDialogAtStartup': u'False', u'language': u'Windows',
u'saveConfigurationOnExit': u'True', u'askToExit': u'True',
u'playStartAndExitSounds': u'True', u'loggingLevel': u'DEBUG'}, u'speech':
{u'synth': u'speechPlayerInEspeak', u'outputDevice': u'Speakers (3-
BEHRINGER USB WDM ', u'symbolLevel': u'100', u'espeak': {u'voice': u'en',
u'variant': u'quincy', u'rate': u'40', u'pitch': u'40', u'inflection':
u'75', u'volume': u'86'}, u'sapi5': {u'voice':
u'HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Speech\\Voices\\Tokens\\ScanSoftD
aniel_Full_22kHz',
u'volume': u'100', u'rate': u'90'}, u'mssp': {u'voice':
u'HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Speech
Server\\v11.0\\Voices\\Tokens\\TTS_MS_en-GB_Hazel_11.0', u'volume': u'90',
u'rate': u'60'}, u'silence': {}, u'sapi4': {u'voice':
u'{BF5EAD40-9F65-11CF-8FC8-0020AF14F271}', u'rate': u'38', u'pitch': u'20',
u'volume': u'41'}, u'speechPlayerInEspeak': {u'voice': u'en', u'variant':
u'quincy', u'rate': u'40', u'pitch': u'40', u'inflection': u'75', u'volume':

u'99'}, u'pico': {u'voice': u'en-gb', u'volume': u'80', u'rate': u'55',
u'pitch': u'40'}, u'dectalk': {u'voice': u'Frank', u'rate': u'38', u'pitch':

u'19', u'inflection': u'40'}}, u'braille': {u'noBraille': {u'port': u''}},
u'presentation': {u'reportTooltips': u'True',
u'guessObjectPositionInformationWhenUnavailable': u'True',
u'reportObjectDescriptions': u'True', u'progressBarUpdates':
{u'progressBarOutputMode': u'both'}}, u'virtualBuffers':
{u'autoPassThroughOnCaretMove': u'True'}, u'documentFormatting':
{u'reportRevisions': u'False', u'reportSpellingErrors': u'False',
u'reportLineIndentation': u'True', u'reportBlockQuotes': u'False',
u'autoLanguageSwitching': u'True', u'detectFormatAfterCursor': u'False',
u'reportFontName': u'False', u'reportFontSize': u'False',
u'reportAlignment': u'True', u'reportStyle': u'False',
u'reportFontAttributes': u'False', u'reportEmphasis': u'False',
u'reportLineIndentationWithTones': u'False'}, u'keyboard':
{u'speakTypedCharacters': u'True', u'useCapsLockAsNVDAModifierKey':
u'False', u'keyboardLayout': u'desktop'}} DEBUG - core.main (08:06:42.270):
setting language to Windows
INFO - core.main (08:06:42.270):
NVDA version master-15137,1cd171de
INFO - core.main (08:06:42.270):
Using Windows version 6.1.7601 service pack 1 workstation INFO - core.main
(08:06:42.270):
Using Python version 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018, 16:22:17) [MSC

v.1500 32 bit (Intel)]
INFO - core.main (08:06:42.270):
Using comtypes version 1.1.3
DEBUG - core.main (08:06:42.302):
Initializing add-ons system
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.303):
Listing add-ons from C:\Users\Brian\AppData\Roaming\nvda\addons
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.303):
Loading add-on from C:\Users\Brian\AppData\Roaming\nvda\addons\DECTalk
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.305):
Found add-on DECTalk
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.305):
Loading add-on from C:\Users\Brian\AppData\Roaming\nvda\addons\dropbox
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.306):
Found add-on dropbox
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.306):
Loading add-on from
C:\Users\Brian\AppData\Roaming\nvda\addons\extendedWinamp
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.308):
Found add-on extendedWinamp
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.308):
Loading add-on from
C:\Users\Brian\AppData\Roaming\nvda\addons\fakeClipboardAnouncement
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.309):
Found add-on fakeClipboardAnouncement
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.309):
Loading add-on from
C:\Users\Brian\AppData\Roaming\nvda\addons\focusHighlight
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.312):
Found add-on focusHighlight
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.312):
Loading add-on from C:\Users\Brian\AppData\Roaming\nvda\addons\goldenCursor
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.315):
Found add-on goldenCursor
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.315):
Loading add-on from C:\Users\Brian\AppData\Roaming\nvda\addons\goldwave
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.316):
Found add-on goldwave
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.316):
Loading add-on from C:\Users\Brian\AppData\Roaming\nvda\addons\mp3DirectCut
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.318):
Found add-on mp3DirectCut
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.318):
Loading add-on from C:\Users\Brian\AppData\Roaming\nvda\addons\OpenLinkWith
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.319):
Found add-on OpenLinkWith
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.319):
Loading add-on from C:\Users\Brian\AppData\Roaming\nvda\addons\pico
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.319):
Found add-on pico
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.319):
Loading add-on from C:\Users\Brian\AppData\Roaming\nvda\addons\readFeeds
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.321):
Found add-on readFeeds
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.321):
Disabling add-on readFeeds
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.321):
Loading add-on from
C:\Users\Brian\AppData\Roaming\nvda\addons\resourceMonitor
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.322):
Found add-on resourceMonitor
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.322):
Loading add-on from C:\Users\Brian\AppData\Roaming\nvda\addons\SentenceNav
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.325):
Found add-on SentenceNav
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.325):
Disabling add-on SentenceNav
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.325):
Loading add-on from
C:\Users\Brian\AppData\Roaming\nvda\addons\speechPlayerInEspeak
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.326):
Found add-on speechPlayerInEspeak
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.326):
Loading add-on from
C:\Users\Brian\AppData\Roaming\nvda\addons\virtualRevision
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.329):
Found add-on virtualRevision
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.329):
Disabling add-on virtualRevision
DEBUGWARNING - touchHandler.touchSupported (08:06:42.565):
Touch only supported on Windows 8 and higher DEBUG - core.main
(08:06:42.651):
Initializing appModule Handler
DEBUG - addonHandler.Addon.addToPackagePath (08:06:42.651):
Addon dropbox added to appModules package path DEBUG -
addonHandler.Addon.addToPackagePath (08:06:42.651):
Addon extendedWinamp added to appModules package path DEBUG -
addonHandler.Addon.addToPackagePath (08:06:42.651):
Addon goldwave added to appModules package path DEBUG -
addonHandler.Addon.addToPackagePath (08:06:42.651):
Addon mp3DirectCut added to appModules package path DEBUG - core.main
(08:06:42.653):
Initializing NVDAHelper
DEBUG - core.main (08:06:42.710):
Speech Dictionary processing
DEBUG - speechDictHandler.SpeechDict.load (08:06:42.711):
Loading speech dictionary
'C:\Users\Brian\AppData\Roaming\nvda\speechDicts\default.dic'...
DEBUG - speechDictHandler.SpeechDict.load (08:06:42.711):
file 'C:\Users\Brian\AppData\Roaming\nvda\speechDicts\default.dic' not
found.
DEBUG - speechDictHandler.SpeechDict.load (08:06:42.711):
Loading speech dictionary 'builtin.dic'...
DEBUG - speechDictHandler.SpeechDict.load (08:06:42.717):
3 loaded records.
DEBUG - core.main (08:06:42.717):
Initializing speech
DEBUG - addonHandler.Addon.addToPackagePath (08:06:42.717):
Addon DECTalk added to synthDrivers package path DEBUG -
addonHandler.Addon.addToPackagePath (08:06:42.717):
Addon pico added to synthDrivers package path DEBUG -
addonHandler.Addon.addToPackagePath (08:06:42.717):
Addon speechPlayerInEspeak added to synthDrivers package path INFO -
external:synthDrivers.speechPlayerInEspeak.SynthDriver.__init__
(08:06:42.782):
Using eSpeak NG version 1.49.1 dev
DEBUG - speechDictHandler.SpeechDict.load (08:06:42.976):
Loading speech dictionary
'C:\Users\Brian\AppData\Roaming\nvda\speechDicts\voiceDicts.v1\speechPlayerI
nEspeak\speechPlayerInEspeak-english.dic'...
DEBUG - speechDictHandler.SpeechDict.load (08:06:42.977):
6 loaded records.
INFO - synthDriverHandler.setSynth (08:06:42.979):
Loaded synthDriver speechPlayerInEspeak
INFO - core.main (08:06:42.979):
Using wx version 3.0.2.0 msw (classic)
DEBUG - core.main (08:06:42.980):
Initializing braille input
INFO - brailleInput.initialize (08:06:42.980):
Braille input initialized
DEBUG - core.main (08:06:42.980):
Initializing braille
INFO - braille.initialize (08:06:42.980):
Using liblouis version 3.5.0
INFO - braille.BrailleHandler.setDisplayByName (08:06:42.982):
Loaded braille display driver noBraille, current display has 0 cells.
DEBUG - core.main (08:06:42.982):
Initializing displayModel
DEBUG - core.main (08:06:42.982):
Initializing GUI
DEBUG - core.main (08:06:42.994):
initializing Java Access Bridge support
WARNING - core.main (08:06:42.994):
Java Access Bridge not available
DEBUG - core.main (08:06:42.996):
Initializing winConsole support
DEBUG - core.main (08:06:42.996):
Initializing UIA support
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (08:06:42.997):
UIAutomation: IUIAutomation
DEBUG - core.main (08:06:43.260):
Initializing IAccessible support
DEBUG - core.main (08:06:43.262):
Initializing input core
DEBUGWARNING - inputCore.InputManager.loadLocaleGestureMap (08:06:43.262):
No locale gesture map for language en
DEBUG - core.main (08:06:43.263):
Initializing keyboard handler
DEBUG - core.main (08:06:43.265):
initializing mouse handler
DEBUG - core.main (08:06:43.282):
Initializing touchHandler
DEBUGWARNING - touchHandler.touchSupported (08:06:43.282):
Touch only supported on Windows 8 and higher DEBUG - core.main
(08:06:43.282):
Initializing global plugin handler
DEBUG - addonHandler.Addon.addToPackagePath (08:06:43.282):
Addon dropbox added to globalPlugins package path DEBUG -
addonHandler.Addon.addToPackagePath (08:06:43.282):
Addon fakeClipboardAnouncement added to globalPlugins package path DEBUG -
addonHandler.Addon.addToPackagePath (08:06:43.282):
Addon focusHighlight added to globalPlugins package path DEBUG -
addonHandler.Addon.addToPackagePath (08:06:43.283):
Addon goldenCursor added to globalPlugins package path DEBUG -
addonHandler.Addon.addToPackagePath (08:06:43.283):
Addon mp3DirectCut added to globalPlugins package path DEBUG -
addonHandler.Addon.addToPackagePath (08:06:43.283):
Addon OpenLinkWith added to globalPlugins package path DEBUG -
addonHandler.Addon.addToPackagePath (08:06:43.283):
Addon resourceMonitor added to globalPlugins package path DEBUG - core.main
(08:06:43.494):
Initializing core pump
DEBUG - core.main (08:06:43.494):
Initializing watchdog
DEBUG - core.main (08:06:43.496):
initializing updateCheck
INFO - core.main (08:06:43.497):
NVDA initialized
DEBUG - core.main (08:06:43.499):
entering wx application main loop
DEBUG - external:globalPlugins.focusHighlight.startThread (08:06:43.499):
focusHighlight started
IO - speech.speak (08:06:43.523):
Speaking [LangChangeCommand ('en_GB'), u'Taskbar'] IO -
inputCore.InputManager.executeGesture (08:06:50.809):
Input: kb(desktop):control+alt+r
IO - speech.speak (08:06:50.900):
Speaking [LangChangeCommand ('en_GB'), u'reboot nvda with log terminal'] IO
- speech.speak (08:06:50.903):
Speaking [LangChangeCommand ('en_GB'), u'80 space', u'blank'] INFO -
core.main (08:06:50.970):
Exiting


bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Marcia Yale" <dragoncatmc@...>
To: <nvda@nvda.groups.io>
Sent: Friday, May 25, 2018 3:13 AM
Subject: [nvda] A recurring error with the latest master snapshot


I will paste my log below, but the issue here is that every time NVDA
is started it gives an error and an "ok" dialog comes up with a
corresponding sound. Not sure what the error means. It's strange that
it shows me using Windows 6.1--I'm using 7. Didn't know there was even
such a thing as Windows 6!


Starting NVDA
INFO - core.main (22:08:35.072):
Config dir: C:\Users\Marcia\AppData\Roaming\nvda
INFO - config.ConfigManager._loadConfig (22:08:35.072):
Loading config: C:\Users\Marcia\AppData\Roaming\nvda\nvda.ini
INFO - core.main (22:08:35.181):
NVDA version master-15137,1cd171de
INFO - core.main (22:08:35.181):
Using Windows version 6.1.7601 service pack 1 workstation INFO -
core.main (22:08:35.181):
Using Python version 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018,
16:22:17) [MSC
v.1500 32 bit (Intel)]
INFO - core.main (22:08:35.181):
Using comtypes version 1.1.3
ERROR - RPC process 57604 (nvda.exe) (22:08:35.329):
Thread 48112, build\x86\remote\injection.cpp, inprocMgrThreadFunc, 168:
SetWinEventHook failed

INFO - synthDrivers.espeak.SynthDriver.__init__ (22:08:35.380):
Using eSpeak NG version 1.49.1 dev
INFO - synthDriverHandler.setSynth (22:08:35.420):
Loaded synthDriver espeak
INFO - core.main (22:08:35.420):
Using wx version 3.0.2.0 msw (classic) INFO - brailleInput.initialize
(22:08:35.420):
Braille input initialized
INFO - braille.initialize (22:08:35.420):
Using liblouis version 3.5.0
INFO - braille.BrailleHandler.setDisplayByName (22:08:35.430):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (22:08:35.490):
UIAutomation: IUIAutomation
INFO - core.main (22:08:36.089):
NVDA initialized
Marcia Yale
It is not our differences that divide us. It is our inability to
recognize, accept, and celebrate those differences.
Audre Lorde







Re: A recurring error with the latest master snapshot

 

Hi Marcia,
Ah, something I have experienced before. This dialog usually means that NVDA
cannot work well with certain applications or might not behave correctly
under some circumstances. Usually restarting your computer fixes this
problem.
Technical: somehow, NVDA Helper is unable to hook into deeper event
processing routines. I think numerous issues were raised on GitHub regarding
this problem.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Marcia Yale
Sent: Friday, May 25, 2018 6:57 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] A recurring error with the latest master snapshot

Okay, here's the log with the control set to debug. I still have no clue
what I'm reading so I hope someone out there can figure out what is
happening.


INFO - __main__ (09:54:32.895):
Starting NVDA
INFO - core.main (09:54:33.145):
Config dir: C:\Users\Marcia\AppData\Roaming\nvda
INFO - config.ConfigManager._loadConfig (09:54:33.145):
Loading config: C:\Users\Marcia\AppData\Roaming\nvda\nvda.ini
INFO - config.ConfigManager._loadConfig (09:54:33.161):
Config loaded (after upgrade, and in the state it will be used by NVDA):
{u'schemaVersion': u'2', u'upgrade': {}, u'update': {u'autoCheck': u'True',
u'startupNotification': u'True'}, u'general': {u'language': u'en',
u'saveConfigurationOnExit': u'True', u'askToExit': u'False',
u'playStartAndExitSounds': u'True', u'loggingLevel': u'DEBUG',
u'showWelcomeDialogAtStartup': u'False'}, u'speech': {u'synth': u'espeak',
u'autoLanguageSwitching': u'False', u'outputDevice': u'Microsoft Sound
Mapper', u'symbolLevel': u'300', u'espeak': {u'voice': u'en-gb-x-rp',
u'variant': u'max', u'rate': u'80', u'pitch': u'43', u'inflection': u'75',
u'volume': u'100', u'beepForCapitals': u'True', u'sayCapForCapitals':
u'False'}}, u'braille': {u'display': u'noBraille', u'translationTable':
u'en-us-g2.ctb', u'inputTable': u'en-us-g2.ctb', u'expandAtCursor':
u'False', u'showCursor': u'False', u'messageTimeout': u'2', u'noBraille':
{u'port': u''}, u'freedomScientific': {u'port': u'auto'}}, u'keyboard':
{u'useCapsLockAsNVDAModifierKey': u'True', u'speakTypedCharacters':
u'False'}, u'documentFormatting': {u'reportRevisions': u'False',
u'reportSpellingErrors': u'False', u'reportTableHeaders': u'False',
u'reportTableCellCoords': u'True', u'reportLists': u'False',
u'reportBlockQuotes': u'False', u'reportFrames': u'False',
u'autoLanguageSwitching': u'False', u'reportClickable': u'False'}} DEBUG -
core.main (09:54:33.239):
setting language to en
INFO - core.main (09:54:33.239):
NVDA version master-15137,1cd171de
INFO - core.main (09:54:33.239):
Using Windows version 6.1.7601 service pack 1 workstation INFO - core.main
(09:54:33.239):
Using Python version 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018, 16:22:17) [MSC
v.1500 32 bit (Intel)]
INFO - core.main (09:54:33.239):
Using comtypes version 1.1.3
DEBUG - core.main (09:54:33.239):
Initializing add-ons system
DEBUG - addonHandler._getAvailableAddonsFromPath (09:54:33.255):
Listing add-ons from C:\Users\Marcia\AppData\Roaming\nvda\addons
DEBUGWARNING - touchHandler.touchSupported (09:54:33.282):
Touch only supported on Windows 8 and higher DEBUG - core.main
(09:54:33.371):
Initializing appModule Handler
DEBUG - core.main (09:54:33.371):
Initializing NVDAHelper
ERROR - RPC process 60284 (nvda.exe) (09:54:33.381):
Thread 59768, build\x86\remote\injection.cpp, inprocMgrThreadFunc, 168:
SetWinEventHook failed

DEBUG - core.main (09:54:33.421):
Speech Dictionary processing
DEBUG - speechDictHandler.SpeechDict.load (09:54:33.421):
Loading speech dictionary
'C:\Users\Marcia\AppData\Roaming\nvda\speechDicts\default.dic'...
DEBUG - speechDictHandler.SpeechDict.load (09:54:33.421):
1 loaded records.
DEBUG - speechDictHandler.SpeechDict.load (09:54:33.421):
Loading speech dictionary 'builtin.dic'...
DEBUG - speechDictHandler.SpeechDict.load (09:54:33.421):
3 loaded records.
DEBUG - core.main (09:54:33.421):
Initializing speech
INFO - synthDrivers.espeak.SynthDriver.__init__ (09:54:33.441):
Using eSpeak NG version 1.49.1 dev
DEBUG - speechDictHandler.SpeechDict.load (09:54:33.482):
Loading speech dictionary
'C:\Users\Marcia\AppData\Roaming\nvda\speechDicts\voiceDicts.v1\espeak\espea
k-English (Received Pronunciation).dic'...
DEBUG - speechDictHandler.SpeechDict.load (09:54:33.482):
file
'C:\Users\Marcia\AppData\Roaming\nvda\speechDicts\voiceDicts.v1\espeak\espea
k-English (Received Pronunciation).dic' not found.
INFO - synthDriverHandler.setSynth (09:54:33.482):
Loaded synthDriver espeak
INFO - core.main (09:54:33.482):
Using wx version 3.0.2.0 msw (classic)
DEBUG - core.main (09:54:33.482):
Initializing braille input
INFO - brailleInput.initialize (09:54:33.482):
Braille input initialized
DEBUG - core.main (09:54:33.482):
Initializing braille
INFO - braille.initialize (09:54:33.482):
Using liblouis version 3.5.0
INFO - braille.BrailleHandler.setDisplayByName (09:54:33.492):
Loaded braille display driver noBraille, current display has 0 cells.
DEBUG - core.main (09:54:33.492):
Initializing displayModel
DEBUG - core.main (09:54:33.492):
Initializing GUI
DEBUG - core.main (09:54:33.502):
initializing Java Access Bridge support
DEBUG - core.main (09:54:33.552):
Initializing winConsole support
DEBUG - core.main (09:54:33.552):
Initializing UIA support
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (09:54:33.552):
UIAutomation: IUIAutomation
DEBUG - core.main (09:54:34.151):
Initializing IAccessible support
DEBUG - core.main (09:54:34.151):
Initializing input core
DEBUGWARNING - inputCore.InputManager.loadLocaleGestureMap (09:54:34.151):
No locale gesture map for language en
DEBUGWARNING - inputCore.InputManager.loadUserGestureMap (09:54:34.151):
No user gesture map
DEBUG - core.main (09:54:34.151):
Initializing keyboard handler
DEBUG - core.main (09:54:34.151):
initializing mouse handler
DEBUG - core.main (09:54:34.161):
Initializing touchHandler
DEBUGWARNING - touchHandler.touchSupported (09:54:34.161):
Touch only supported on Windows 8 and higher DEBUG - core.main
(09:54:34.161):
Initializing global plugin handler
DEBUG - core.main (09:54:34.161):
Initializing core pump
DEBUG - core.main (09:54:34.161):
Initializing watchdog
DEBUG - core.main (09:54:34.161):
initializing updateCheck
INFO - core.main (09:54:34.161):
NVDA initialized
DEBUG - core.main (09:54:34.161):
entering wx application main loop
IO - speech.speak (09:54:34.181):
Speaking [u'nvdaHelperRemote (outprocMgrThreadFunc) dialog Error
registering focus winEvent hook'] IO - speech.speak (09:54:34.191):
Speaking [u'OK button']
IO - inputCore.InputManager.executeGesture (09:54:40.007):
Input: kb(desktop):space
IO - speech.speak (09:54:40.028):
Speaking [u'pressed']
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (09:54:40.197):
oleacc.AccessibleObjectFromEvent with window 16452220, objectID -4 and
childID 0: [Error -2147467259] Unspecified error DEBUGWARNING -
NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole
(09:54:40.237):
accRole failed: (-2147024809, 'The parameter is incorrect.', (None, None,
None, 0, None)) IO - speech.speak (09:54:40.257):
Speaking [u'Taskbar']
IO - inputCore.InputManager.executeGesture (09:54:42.266):
Input: kb(desktop):NVDA+n
IO - speech.speak (09:54:42.336):
Speaking [u'NVDA menu']
IO - inputCore.InputManager.executeGesture (09:54:43.677):
Input: kb(desktop):downArrow
IO - speech.speak (09:54:43.697):
Speaking [u'Preferences subMenu p']
IO - inputCore.InputManager.executeGesture (09:54:45.049):
Input: kb(desktop):downArrow
IO - speech.speak (09:54:45.078):
Speaking [u'Tools subMenu t']
IO - inputCore.InputManager.executeGesture (09:54:45.532):
Input: kb(desktop):rightArrow
IO - speech.speak (09:54:45.582):
Speaking [u'View log v']
IO - inputCore.InputManager.executeGesture (09:54:46.229):
Input: kb(desktop):enter
-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Brian's
Mail list account via Groups.Io
Sent: Friday, May 25, 2018 3:16 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] A recurring error with the latest master snapshot

Firstly have a look at it with the logging level set to debug, as this may
well show up more detail. I certainly get no such error here on the latest
master installed copy The windows internal number is correct though, as
this is just an internal designation.

If you are bored easily stop reading now as I'm pasting my debug log with no
errors and the add ons listed for comparison.


INFO - __main__ (08:06:41.973):
Starting NVDA
INFO - core.main (08:06:42.223):
Config dir: C:\Users\Brian\AppData\Roaming\nvda
INFO - config.ConfigManager._loadConfig (08:06:42.223):
Loading config: C:\Users\Brian\AppData\Roaming\nvda\nvda.ini
INFO - config.ConfigManager._loadConfig (08:06:42.255):
Config loaded (after upgrade, and in the state it will be used by NVDA):
{u'schemaVersion': u'2', u'upgrade': {}, u'update': {u'autoCheck': u'True',
u'startupNotification': u'True'}, u'general':
{u'showWelcomeDialogAtStartup': u'False', u'language': u'Windows',
u'saveConfigurationOnExit': u'True', u'askToExit': u'True',
u'playStartAndExitSounds': u'True', u'loggingLevel': u'DEBUG'}, u'speech':
{u'synth': u'speechPlayerInEspeak', u'outputDevice': u'Speakers (3-
BEHRINGER USB WDM ', u'symbolLevel': u'100', u'espeak': {u'voice': u'en',
u'variant': u'quincy', u'rate': u'40', u'pitch': u'40', u'inflection':
u'75', u'volume': u'86'}, u'sapi5': {u'voice':
u'HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Speech\\Voices\\Tokens\\ScanSoftD
aniel_Full_22kHz',
u'volume': u'100', u'rate': u'90'}, u'mssp': {u'voice':
u'HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Speech
Server\\v11.0\\Voices\\Tokens\\TTS_MS_en-GB_Hazel_11.0', u'volume': u'90',
u'rate': u'60'}, u'silence': {}, u'sapi4': {u'voice':
u'{BF5EAD40-9F65-11CF-8FC8-0020AF14F271}', u'rate': u'38', u'pitch': u'20',
u'volume': u'41'}, u'speechPlayerInEspeak': {u'voice': u'en', u'variant':
u'quincy', u'rate': u'40', u'pitch': u'40', u'inflection': u'75', u'volume':

u'99'}, u'pico': {u'voice': u'en-gb', u'volume': u'80', u'rate': u'55',
u'pitch': u'40'}, u'dectalk': {u'voice': u'Frank', u'rate': u'38', u'pitch':

u'19', u'inflection': u'40'}}, u'braille': {u'noBraille': {u'port': u''}},
u'presentation': {u'reportTooltips': u'True',
u'guessObjectPositionInformationWhenUnavailable': u'True',
u'reportObjectDescriptions': u'True', u'progressBarUpdates':
{u'progressBarOutputMode': u'both'}}, u'virtualBuffers':
{u'autoPassThroughOnCaretMove': u'True'}, u'documentFormatting':
{u'reportRevisions': u'False', u'reportSpellingErrors': u'False',
u'reportLineIndentation': u'True', u'reportBlockQuotes': u'False',
u'autoLanguageSwitching': u'True', u'detectFormatAfterCursor': u'False',
u'reportFontName': u'False', u'reportFontSize': u'False',
u'reportAlignment': u'True', u'reportStyle': u'False',
u'reportFontAttributes': u'False', u'reportEmphasis': u'False',
u'reportLineIndentationWithTones': u'False'}, u'keyboard':
{u'speakTypedCharacters': u'True', u'useCapsLockAsNVDAModifierKey':
u'False', u'keyboardLayout': u'desktop'}} DEBUG - core.main (08:06:42.270):
setting language to Windows
INFO - core.main (08:06:42.270):
NVDA version master-15137,1cd171de
INFO - core.main (08:06:42.270):
Using Windows version 6.1.7601 service pack 1 workstation INFO - core.main
(08:06:42.270):
Using Python version 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018, 16:22:17) [MSC

v.1500 32 bit (Intel)]
INFO - core.main (08:06:42.270):
Using comtypes version 1.1.3
DEBUG - core.main (08:06:42.302):
Initializing add-ons system
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.303):
Listing add-ons from C:\Users\Brian\AppData\Roaming\nvda\addons
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.303):
Loading add-on from C:\Users\Brian\AppData\Roaming\nvda\addons\DECTalk
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.305):
Found add-on DECTalk
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.305):
Loading add-on from C:\Users\Brian\AppData\Roaming\nvda\addons\dropbox
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.306):
Found add-on dropbox
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.306):
Loading add-on from
C:\Users\Brian\AppData\Roaming\nvda\addons\extendedWinamp
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.308):
Found add-on extendedWinamp
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.308):
Loading add-on from
C:\Users\Brian\AppData\Roaming\nvda\addons\fakeClipboardAnouncement
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.309):
Found add-on fakeClipboardAnouncement
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.309):
Loading add-on from
C:\Users\Brian\AppData\Roaming\nvda\addons\focusHighlight
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.312):
Found add-on focusHighlight
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.312):
Loading add-on from C:\Users\Brian\AppData\Roaming\nvda\addons\goldenCursor
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.315):
Found add-on goldenCursor
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.315):
Loading add-on from C:\Users\Brian\AppData\Roaming\nvda\addons\goldwave
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.316):
Found add-on goldwave
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.316):
Loading add-on from C:\Users\Brian\AppData\Roaming\nvda\addons\mp3DirectCut
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.318):
Found add-on mp3DirectCut
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.318):
Loading add-on from C:\Users\Brian\AppData\Roaming\nvda\addons\OpenLinkWith
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.319):
Found add-on OpenLinkWith
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.319):
Loading add-on from C:\Users\Brian\AppData\Roaming\nvda\addons\pico
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.319):
Found add-on pico
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.319):
Loading add-on from C:\Users\Brian\AppData\Roaming\nvda\addons\readFeeds
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.321):
Found add-on readFeeds
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.321):
Disabling add-on readFeeds
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.321):
Loading add-on from
C:\Users\Brian\AppData\Roaming\nvda\addons\resourceMonitor
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.322):
Found add-on resourceMonitor
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.322):
Loading add-on from C:\Users\Brian\AppData\Roaming\nvda\addons\SentenceNav
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.325):
Found add-on SentenceNav
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.325):
Disabling add-on SentenceNav
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.325):
Loading add-on from
C:\Users\Brian\AppData\Roaming\nvda\addons\speechPlayerInEspeak
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.326):
Found add-on speechPlayerInEspeak
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.326):
Loading add-on from
C:\Users\Brian\AppData\Roaming\nvda\addons\virtualRevision
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.329):
Found add-on virtualRevision
DEBUG - addonHandler._getAvailableAddonsFromPath (08:06:42.329):
Disabling add-on virtualRevision
DEBUGWARNING - touchHandler.touchSupported (08:06:42.565):
Touch only supported on Windows 8 and higher DEBUG - core.main
(08:06:42.651):
Initializing appModule Handler
DEBUG - addonHandler.Addon.addToPackagePath (08:06:42.651):
Addon dropbox added to appModules package path DEBUG -
addonHandler.Addon.addToPackagePath (08:06:42.651):
Addon extendedWinamp added to appModules package path DEBUG -
addonHandler.Addon.addToPackagePath (08:06:42.651):
Addon goldwave added to appModules package path DEBUG -
addonHandler.Addon.addToPackagePath (08:06:42.651):
Addon mp3DirectCut added to appModules package path DEBUG - core.main
(08:06:42.653):
Initializing NVDAHelper
DEBUG - core.main (08:06:42.710):
Speech Dictionary processing
DEBUG - speechDictHandler.SpeechDict.load (08:06:42.711):
Loading speech dictionary
'C:\Users\Brian\AppData\Roaming\nvda\speechDicts\default.dic'...
DEBUG - speechDictHandler.SpeechDict.load (08:06:42.711):
file 'C:\Users\Brian\AppData\Roaming\nvda\speechDicts\default.dic' not
found.
DEBUG - speechDictHandler.SpeechDict.load (08:06:42.711):
Loading speech dictionary 'builtin.dic'...
DEBUG - speechDictHandler.SpeechDict.load (08:06:42.717):
3 loaded records.
DEBUG - core.main (08:06:42.717):
Initializing speech
DEBUG - addonHandler.Addon.addToPackagePath (08:06:42.717):
Addon DECTalk added to synthDrivers package path DEBUG -
addonHandler.Addon.addToPackagePath (08:06:42.717):
Addon pico added to synthDrivers package path DEBUG -
addonHandler.Addon.addToPackagePath (08:06:42.717):
Addon speechPlayerInEspeak added to synthDrivers package path INFO -
external:synthDrivers.speechPlayerInEspeak.SynthDriver.__init__
(08:06:42.782):
Using eSpeak NG version 1.49.1 dev
DEBUG - speechDictHandler.SpeechDict.load (08:06:42.976):
Loading speech dictionary
'C:\Users\Brian\AppData\Roaming\nvda\speechDicts\voiceDicts.v1\speechPlayerI
nEspeak\speechPlayerInEspeak-english.dic'...
DEBUG - speechDictHandler.SpeechDict.load (08:06:42.977):
6 loaded records.
INFO - synthDriverHandler.setSynth (08:06:42.979):
Loaded synthDriver speechPlayerInEspeak
INFO - core.main (08:06:42.979):
Using wx version 3.0.2.0 msw (classic)
DEBUG - core.main (08:06:42.980):
Initializing braille input
INFO - brailleInput.initialize (08:06:42.980):
Braille input initialized
DEBUG - core.main (08:06:42.980):
Initializing braille
INFO - braille.initialize (08:06:42.980):
Using liblouis version 3.5.0
INFO - braille.BrailleHandler.setDisplayByName (08:06:42.982):
Loaded braille display driver noBraille, current display has 0 cells.
DEBUG - core.main (08:06:42.982):
Initializing displayModel
DEBUG - core.main (08:06:42.982):
Initializing GUI
DEBUG - core.main (08:06:42.994):
initializing Java Access Bridge support
WARNING - core.main (08:06:42.994):
Java Access Bridge not available
DEBUG - core.main (08:06:42.996):
Initializing winConsole support
DEBUG - core.main (08:06:42.996):
Initializing UIA support
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (08:06:42.997):
UIAutomation: IUIAutomation
DEBUG - core.main (08:06:43.260):
Initializing IAccessible support
DEBUG - core.main (08:06:43.262):
Initializing input core
DEBUGWARNING - inputCore.InputManager.loadLocaleGestureMap (08:06:43.262):
No locale gesture map for language en
DEBUG - core.main (08:06:43.263):
Initializing keyboard handler
DEBUG - core.main (08:06:43.265):
initializing mouse handler
DEBUG - core.main (08:06:43.282):
Initializing touchHandler
DEBUGWARNING - touchHandler.touchSupported (08:06:43.282):
Touch only supported on Windows 8 and higher DEBUG - core.main
(08:06:43.282):
Initializing global plugin handler
DEBUG - addonHandler.Addon.addToPackagePath (08:06:43.282):
Addon dropbox added to globalPlugins package path DEBUG -
addonHandler.Addon.addToPackagePath (08:06:43.282):
Addon fakeClipboardAnouncement added to globalPlugins package path DEBUG -
addonHandler.Addon.addToPackagePath (08:06:43.282):
Addon focusHighlight added to globalPlugins package path DEBUG -
addonHandler.Addon.addToPackagePath (08:06:43.283):
Addon goldenCursor added to globalPlugins package path DEBUG -
addonHandler.Addon.addToPackagePath (08:06:43.283):
Addon mp3DirectCut added to globalPlugins package path DEBUG -
addonHandler.Addon.addToPackagePath (08:06:43.283):
Addon OpenLinkWith added to globalPlugins package path DEBUG -
addonHandler.Addon.addToPackagePath (08:06:43.283):
Addon resourceMonitor added to globalPlugins package path DEBUG - core.main
(08:06:43.494):
Initializing core pump
DEBUG - core.main (08:06:43.494):
Initializing watchdog
DEBUG - core.main (08:06:43.496):
initializing updateCheck
INFO - core.main (08:06:43.497):
NVDA initialized
DEBUG - core.main (08:06:43.499):
entering wx application main loop
DEBUG - external:globalPlugins.focusHighlight.startThread (08:06:43.499):
focusHighlight started
IO - speech.speak (08:06:43.523):
Speaking [LangChangeCommand ('en_GB'), u'Taskbar'] IO -
inputCore.InputManager.executeGesture (08:06:50.809):
Input: kb(desktop):control+alt+r
IO - speech.speak (08:06:50.900):
Speaking [LangChangeCommand ('en_GB'), u'reboot nvda with log terminal'] IO
- speech.speak (08:06:50.903):
Speaking [LangChangeCommand ('en_GB'), u'80 space', u'blank'] INFO -
core.main (08:06:50.970):
Exiting


bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Marcia Yale" <dragoncatmc@...>
To: <nvda@nvda.groups.io>
Sent: Friday, May 25, 2018 3:13 AM
Subject: [nvda] A recurring error with the latest master snapshot


I will paste my log below, but the issue here is that every time NVDA is
started it gives an error and an "ok" dialog comes up with a corresponding
sound. Not sure what the error means. It's strange that it shows me using
Windows 6.1--I'm using 7. Didn't know there was even such a thing as
Windows
6!


Starting NVDA
INFO - core.main (22:08:35.072):
Config dir: C:\Users\Marcia\AppData\Roaming\nvda
INFO - config.ConfigManager._loadConfig (22:08:35.072):
Loading config: C:\Users\Marcia\AppData\Roaming\nvda\nvda.ini
INFO - core.main (22:08:35.181):
NVDA version master-15137,1cd171de
INFO - core.main (22:08:35.181):
Using Windows version 6.1.7601 service pack 1 workstation
INFO - core.main (22:08:35.181):
Using Python version 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018, 16:22:17)
[MSC
v.1500 32 bit (Intel)]
INFO - core.main (22:08:35.181):
Using comtypes version 1.1.3
ERROR - RPC process 57604 (nvda.exe) (22:08:35.329):
Thread 48112, build\x86\remote\injection.cpp, inprocMgrThreadFunc, 168:
SetWinEventHook failed

INFO - synthDrivers.espeak.SynthDriver.__init__ (22:08:35.380):
Using eSpeak NG version 1.49.1 dev
INFO - synthDriverHandler.setSynth (22:08:35.420):
Loaded synthDriver espeak
INFO - core.main (22:08:35.420):
Using wx version 3.0.2.0 msw (classic)
INFO - brailleInput.initialize (22:08:35.420):
Braille input initialized
INFO - braille.initialize (22:08:35.420):
Using liblouis version 3.5.0
INFO - braille.BrailleHandler.setDisplayByName (22:08:35.430):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (22:08:35.490):
UIAutomation: IUIAutomation
INFO - core.main (22:08:36.089):
NVDA initialized
Marcia Yale
It is not our differences that divide us. It is our inability to
recognize,
accept, and celebrate those differences.
Audre Lorde







Re: Question: NVDA Starts Differently with the Windows 10 April 2018 Update

Sarah k Alawami
 

I disabled my lock screen, so I'm not having those issues, In fact I don't notice the ease of access thing coming up at all. And I do have the latest major update thingy.

On May 25, 2018, at 8:17 AM, Brian's Mail list account via Groups.Io <bglists=blueyonder.co.uk@groups.io> wrote:

Also people are reporting that as standard windows 10 now has sound in safe mode so one might also suspect this will mean sound drivers load earlier than they used to.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Nimer Jaber" <nimerjaber1@...>
To: <nvda@nvda.groups.io>
Sent: Friday, May 25, 2018 3:23 PM
Subject: Re: [nvda] Question: NVDA Starts Differently with the Windows 10 April 2018 Update


Hello,

First, did you copy your saved settings to the log-on screen?

Second, it sounds as if the ease of access menu may have gotten triggered.
Have you tried to do an alt+tab to see if that is running? Have you gone
into the access settings to see if anything is set to start at log-on?

Thanks.

On Fri, May 25, 2018 at 8:20 AM David Goldfield <david.goldfield@...>
wrote:

Hello.

I have just rejoined this list and my guess is that this question may have
already been discussed.

After updating to the April 2018 Windows 10 update I noticed two things.

1. NVDA seems to fully start with my default synthesizer of Acapela, even
on the login screen prior to the desktop being loaded. In the past, it
would default to Espeak and would then restart after entering my Pin. I am
assuming this is a deliberate change? Is this the case for other screen
readers, as well?


2. Before I press ctrl-alt-del to enter my pin at startup I am now hearing
information about various, pre-installed accessibility tools, such as a
description of Narrator, Magnifier, etc. How is this screen triggered and
is there a way to suppress it?
--
David Goldfield, Assistive Technology Specialist WWW.David-Goldfield.Com

--
Cordially,

Nimer Jaber

My mission is to bring love and peace to everyone around me with all tools
available to me.
My core values are integrity, innovation, loyalty, excellence, and 100%
personal responsibility.

The message above is intended for the recipient to whom it was
addressed. If you believe that you are not the intended recipient,
please notify me via reply email and destroy all copies of this
correspondence. Action taken as a result of this email or its contents
by anyone other than the intended recipient(s) may result in civil or
criminal charges. I have checked this email and all corresponding
attachments for security threats. However, security of your machine is
up to you. Thanks.

Registered Linux User 529141.
This is a test of typing on this.http://counter.li.org/
<http://counter.li.org/>

To find out about a free and versatile screen reader for windows XP
and above, please click here:
http://www.nvda-project.org

You can follow @nimerjaber on Twitter for the latest technology news.

To contact me, you can reply to this email or you may call me at
(218-606-0475) and I will do my best to respond to you promptly. Thank
you, and have a great day!



Re: Question: NVDA Starts Differently with the Windows 10 April 2018 Update

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

Also people are reporting that as standard windows 10 now has sound in safe mode so one might also suspect this will mean sound drivers load earlier than they used to.
Brian

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

----- Original Message -----
From: "Nimer Jaber" <nimerjaber1@...>
To: <nvda@nvda.groups.io>
Sent: Friday, May 25, 2018 3:23 PM
Subject: Re: [nvda] Question: NVDA Starts Differently with the Windows 10 April 2018 Update


Hello,

First, did you copy your saved settings to the log-on screen?

Second, it sounds as if the ease of access menu may have gotten triggered.
Have you tried to do an alt+tab to see if that is running? Have you gone
into the access settings to see if anything is set to start at log-on?

Thanks.

On Fri, May 25, 2018 at 8:20 AM David Goldfield <david.goldfield@...>
wrote:

Hello.

I have just rejoined this list and my guess is that this question may have
already been discussed.

After updating to the April 2018 Windows 10 update I noticed two things.

1. NVDA seems to fully start with my default synthesizer of Acapela, even
on the login screen prior to the desktop being loaded. In the past, it
would default to Espeak and would then restart after entering my Pin. I am
assuming this is a deliberate change? Is this the case for other screen
readers, as well?


2. Before I press ctrl-alt-del to enter my pin at startup I am now hearing
information about various, pre-installed accessibility tools, such as a
description of Narrator, Magnifier, etc. How is this screen triggered and
is there a way to suppress it?
--
David Goldfield, Assistive Technology Specialist WWW.David-Goldfield.Com

--
Cordially,

Nimer Jaber

My mission is to bring love and peace to everyone around me with all tools
available to me.
My core values are integrity, innovation, loyalty, excellence, and 100%
personal responsibility.

The message above is intended for the recipient to whom it was
addressed. If you believe that you are not the intended recipient,
please notify me via reply email and destroy all copies of this
correspondence. Action taken as a result of this email or its contents
by anyone other than the intended recipient(s) may result in civil or
criminal charges. I have checked this email and all corresponding
attachments for security threats. However, security of your machine is
up to you. Thanks.

Registered Linux User 529141.
This is a test of typing on this.http://counter.li.org/
<http://counter.li.org/>

To find out about a free and versatile screen reader for windows XP
and above, please click here:
http://www.nvda-project.org

You can follow @nimerjaber on Twitter for the latest technology news.

To contact me, you can reply to this email or you may call me at
(218-606-0475) and I will do my best to respond to you promptly. Thank
you, and have a great day!