Date   

Re: NVDA randumly crashing?

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

Its very hard without a log set to debug of the crashing session. IE when it reboots grab the old log not the current one, but before any crashes set logging level to debug as that shows most detail.
Brian

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

----- Original Message -----
From: "Matt Turner" <meturner2214@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Sunday, March 11, 2018 12:33 PM
Subject: Re: [nvda] NVDA randumly crashing?


Hi.

I mostly use e-speak.

As for the crashing, sometimes nvda will restart on its own, and other times I have to manually restart it.


On 3/11/2018 5:25 AM, Brian's Mail list account via Groups.Io wrote:
I do not see this in Windows 7, but the other person has windows 8.1.
I'd expect all sorts of issues with 10, due to its numerous builds over its lifetime thus far.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Don H" <lmddh50@adams.net>
To: <nvda@nvda.groups.io>
Sent: Saturday, March 10, 2018 11:23 PM
Subject: Re: [nvda] NVDA randumly crashing?


I am running NVDA on a Win 10 64 bit laptop and with the last two or three versions of NVDA including 2018-1 I get NVDA crashing randomly when I hit the windows key to open the start menu. I simply restart NVDA and everything seems fine again until the next random crash.






Re: Typing Echo Change with 2018.1

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

That is probably because to stop delays in one core voices it has to be altered in windows, not nvda.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail 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: Sunday, March 11, 2018 12:27 PM
Subject: Re: [nvda] Typing Echo Change with 2018.1


Well I used ESpeak with FB cause I commented on some posts. This problem doesn’t happen with ESpeak only One Core voices. I use MSS David with NVDA.

Lino Morales

From: Gene<mailto:gsasner@ripco.com>
Sent: Sunday, March 11, 2018 8:22 AM
To: nvda@nvda.groups.io<mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] Typing Echo Change with 2018.1

It can be tried and it's unlikely CCleaner would cause problems. But I am very skeptical that it will accomplish anything. If the problem started with a new version of NVDA, why would the registry suddenly and coincidentally become corrupted at that time? And one or two other people have said they have the same problem when the new version is used. It's strains credulity that coincidentally, two or three people had the same problem when trying a new version and that the problem is caused by the registry suddenly becoming corrupted on three computers in exactly the same way when a new version is being tried.

If someone wants to try registry cleaning with CCleaner, it is unlikely to cause problems and they may want to. But I'm very skeptical.

Gene
----- Original Message -----
From: Adriani Botez<mailto:adriani.botez@gmail.com>
Sent: Sunday, March 11, 2018 7:15 AM
To: nvda@nvda.groups.io<mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] Typing Echo Change with 2018.1

I had the problem with a portable version of NVDA, where the speech did not follow the cursor movement in an application. Registry clean solved this problem. So why not trying it? I don’t see any big issues in cleaning registry with CCleaner. I didn’t hear of any issue raising after cleaning registry with that program.


Best
Adriani


Von: nvda@nvda.groups.io<mailto:nvda@nvda.groups.io> <nvda@nvda.groups.io> Im Auftrag von Gene
Gesendet: Sonntag, 11. März 2018 13:13
An: nvda@nvda.groups.io
Betreff: Re: [nvda] Typing Echo Change with 2018.1

I see no reason to do anything with the registry. Most problems do not involve the registry just as a lot of problems attributed to memory don't involve memory. The problem started with a new release of NVDA. Other people have reported this problem. Registry cleaning usually isn't necessary and accomplishes nothing meaningful if anything at all while creating a slight risk. I don't believe in taking even small risks for no benefit. is that one reason my computer runs for years without fooling around with the operating system with no additional problems or none that mean anything?

Gene
----- Original Message -----
From: Adriani Botez<mailto:adriani.botez@gmail.com>
Sent: Sunday, March 11, 2018 2:32 AM
To: nvda@nvda.groups.io<mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] Typing Echo Change with 2018.1

Garry,

Do the letters appear on the screen as fast as you type? Or are they delayed?

Please run a CCleaner and clean your registry. Does the issue still occur?

Best
Adriani

Von meinem iPhone gesendet

Am 11.03.2018 um 07:25 schrieb Joseph Lee <joseph.lee22590@gmail.com<mailto:joseph.lee22590@gmail.com>>:
Hi,
Hmmm, that’s really odd indeed. Do you have access to another computer with a similar setup where you can test these builds? Also, if you are comfortable installing beta software releases, do you mind installing 2017.4 back (and disable update checking via general settings dialog) and see if it improves things a bit? If it does improve things, then please install each of the beta builds (in sequence as described in my email) and let us know if you notice any changes.
Also, an advanced warning for people really tempted to do the following (and in order to avoid another instance of miscommunication like VS2017 runtime problem a few weeks back): just because you can’t reproduce a problem DOES NOT MEAN you can close an issue or ignore it. Who knows if the problem reported by a user might happen to you one day, or the reporter found a solution that works for him or her that might or might not apply to others. There are some in the community (who shall remain nameless) who downplay the severity of a problem when they can’t reproduce it or think their version of Windows is immune. No, a problem reported by a user is still a problem if it negatively affects productivity for them, potentially marring their NVDA experience. Some of you may think that what Gary is going through is a minor anoyance, but if this problem affects his productivity, then it should still be investigated to find out why, hence my suggestion to let him try different beta builds. I’m saying all this because I think we should change our attitudes about providing support for newcomers and/or those who are experiencing problems we can’t reproduce (easily).
Cheers,
Joseph

From: nvda@nvda.groups.io<mailto:nvda@nvda.groups.io> <nvda@nvda.groups.io<mailto:nvda@nvda.groups.io>> On Behalf Of Gary
Sent: Saturday, March 10, 2018 10:09 PM
To: nvda@nvda.groups.io<mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] Typing Echo Change with 2018.1

Ok, that's really odd. All of them were slow on the typing echo, including 2017.4, which is what I was running previously without issue. I'm confused to how that could be possible. :/


Re: Typing Echo Change with 2018.1

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

Remember Espeak being horrid is just your opinion, many people like myself like it a lot aas it is.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail 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: Sunday, March 11, 2018 12:19 PM
Subject: Re: [nvda] Typing Echo Change with 2018.1


Actually I’ve noticed this problem myself in NVDA 2017.4 and 2017.3. I’m using horrid Espeak right now cause I’ll be checking my Facebook before church.

Lino Morales

From: Gene<mailto:gsasner@ripco.com>
Sent: Sunday, March 11, 2018 8:12 AM
To: nvda@nvda.groups.io<mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] Typing Echo Change with 2018.1

I see no reason to do anything with the registry. Most problems do not involve the registry just as a lot of problems attributed to memory don't involve memory. The problem started with a new release of NVDA. Other people have reported this problem. Registry cleaning usually isn't necessary and accomplishes nothing meaningful if anything at all while creating a slight risk. I don't believe in taking even small risks for no benefit. is that one reason my computer runs for years without fooling around with the operating system with no additional problems or none that mean anything?

Gene
----- Original Message -----
From: Adriani Botez<mailto:adriani.botez@gmail.com>
Sent: Sunday, March 11, 2018 2:32 AM
To: nvda@nvda.groups.io<mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] Typing Echo Change with 2018.1

Garry,

Do the letters appear on the screen as fast as you type? Or are they delayed?

Please run a CCleaner and clean your registry. Does the issue still occur?

Best
Adriani

Von meinem iPhone gesendet

Am 11.03.2018 um 07:25 schrieb Joseph Lee <joseph.lee22590@gmail.com<mailto:joseph.lee22590@gmail.com>>:
Hi,
Hmmm, that’s really odd indeed. Do you have access to another computer with a similar setup where you can test these builds? Also, if you are comfortable installing beta software releases, do you mind installing 2017.4 back (and disable update checking via general settings dialog) and see if it improves things a bit? If it does improve things, then please install each of the beta builds (in sequence as described in my email) and let us know if you notice any changes.
Also, an advanced warning for people really tempted to do the following (and in order to avoid another instance of miscommunication like VS2017 runtime problem a few weeks back): just because you can’t reproduce a problem DOES NOT MEAN you can close an issue or ignore it. Who knows if the problem reported by a user might happen to you one day, or the reporter found a solution that works for him or her that might or might not apply to others. There are some in the community (who shall remain nameless) who downplay the severity of a problem when they can’t reproduce it or think their version of Windows is immune. No, a problem reported by a user is still a problem if it negatively affects productivity for them, potentially marring their NVDA experience. Some of you may think that what Gary is going through is a minor anoyance, but if this problem affects his productivity, then it should still be investigated to find out why, hence my suggestion to let him try different beta builds. I’m saying all this because I think we should change our attitudes about providing support for newcomers and/or those who are experiencing problems we can’t reproduce (easily).
Cheers,
Joseph

From: nvda@nvda.groups.io<mailto:nvda@nvda.groups.io> <nvda@nvda.groups.io<mailto:nvda@nvda.groups.io>> On Behalf Of Gary
Sent: Saturday, March 10, 2018 10:09 PM
To: nvda@nvda.groups.io<mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] Typing Echo Change with 2018.1

Ok, that's really odd. All of them were slow on the typing echo, including 2017.4, which is what I was running previously without issue. I'm confused to how that could be possible. :/


Re: Typing Echo Change with 2018.1

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

I think because it can have its risks and in the main, although it can speed some stuff up it is seldom the underlying cause.
For example. For those countries who have the Amazon Echo dot, the app that runs on the pc has a terrible character echo delay issue, and it has always had it. No amount of messing about with access software is going to fix it.
You just have to put up with double spoken characters or nothing at all.

I also remember a problem recently when a Braille display driver was changed and this slugged the actual speech as well, so its not always a problem caused by new code just updated drivers.
Brian

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

----- Original Message -----
From: "Adriani Botez" <adriani.botez@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Sunday, March 11, 2018 12:15 PM
Subject: Re: [nvda] Typing Echo Change with 2018.1


I had the problem with a portable version of NVDA, where the speech did not follow the cursor movement in an application. Registry clean solved this problem. So why not trying it? I don’t see any big issues in cleaning registry with CCleaner. I didn’t hear of any issue raising after cleaning registry with that program.





Best

Adriani





Von: nvda@nvda.groups.io <nvda@nvda.groups.io> Im Auftrag von Gene
Gesendet: Sonntag, 11. März 2018 13:13
An: nvda@nvda.groups.io
Betreff: Re: [nvda] Typing Echo Change with 2018.1



I see no reason to do anything with the registry. Most problems do not involve the registry just as a lot of problems attributed to memory don't involve memory. The problem started with a new release of NVDA. Other people have reported this problem. Registry cleaning usually isn't necessary and accomplishes nothing meaningful if anything at all while creating a slight risk. I don't believe in taking even small risks for no benefit. is that one reason my computer runs for years without fooling around with the operating system with no additional problems or none that mean anything?



Gene

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

From: Adriani Botez <mailto:adriani.botez@gmail.com>

Sent: Sunday, March 11, 2018 2:32 AM

To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>

Subject: Re: [nvda] Typing Echo Change with 2018.1



Garry,



Do the letters appear on the screen as fast as you type? Or are they delayed?



Please run a CCleaner and clean your registry. Does the issue still occur?



Best

Adriani



Von meinem iPhone gesendet


Am 11.03.2018 um 07:25 schrieb Joseph Lee <joseph.lee22590@gmail.com <mailto:joseph.lee22590@gmail.com> >:

Hi,

Hmmm, that’s really odd indeed. Do you have access to another computer with a similar setup where you can test these builds? Also, if you are comfortable installing beta software releases, do you mind installing 2017.4 back (and disable update checking via general settings dialog) and see if it improves things a bit? If it does improve things, then please install each of the beta builds (in sequence as described in my email) and let us know if you notice any changes.

Also, an advanced warning for people really tempted to do the following (and in order to avoid another instance of miscommunication like VS2017 runtime problem a few weeks back): just because you can’t reproduce a problem DOES NOT MEAN you can close an issue or ignore it. Who knows if the problem reported by a user might happen to you one day, or the reporter found a solution that works for him or her that might or might not apply to others. There are some in the community (who shall remain nameless) who downplay the severity of a problem when they can’t reproduce it or think their version of Windows is immune. No, a problem reported by a user is still a problem if it negatively affects productivity for them, potentially marring their NVDA experience. Some of you may think that what Gary is going through is a minor anoyance, but if this problem affects his productivity, then it should still be investigated to find out why, hence my suggestion to let him try different beta builds. I’m saying all this because I think we should change our attitudes about providing support for newcomers and/or those who are experiencing problems we can’t reproduce (easily).

Cheers,

Joseph



From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> <nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> > On Behalf Of Gary
Sent: Saturday, March 10, 2018 10:09 PM
To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] Typing Echo Change with 2018.1



Ok, that's really odd. All of them were slow on the typing echo, including 2017.4, which is what I was running previously without issue. I'm confused to how that could be possible. :/


Re: Typing Echo Change with 2018.1

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

Yes and anything you do, you need to be sure you do one thing at a time and have a way back if things get worse, ie a restore point before you start to fiddle. I to have never had to reinstall windows as I only change one thing at a time.
its standard diagnostic practice.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail 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: Sunday, March 11, 2018 12:12 PM
Subject: Re: [nvda] Typing Echo Change with 2018.1


I see no reason to do anything with the registry. Most problems do not involve the registry just as a lot of problems attributed to memory don't involve memory. The problem started with a new release of NVDA. Other people have reported this problem. Registry cleaning usually isn't necessary and accomplishes nothing meaningful if anything at all while creating a slight risk. I don't believe in taking even small risks for no benefit. is that one reason my computer runs for years without fooling around with the operating system with no additional problems or none that mean anything?

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

From: Adriani Botez
Sent: Sunday, March 11, 2018 2:32 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Typing Echo Change with 2018.1


Garry,


Do the letters appear on the screen as fast as you type? Or are they delayed?


Please run a CCleaner and clean your registry. Does the issue still occur?


Best
Adriani



Von meinem iPhone gesendet

Am 11.03.2018 um 07:25 schrieb Joseph Lee <joseph.lee22590@gmail.com>:


Hi,

Hmmm, that’s really odd indeed. Do you have access to another computer with a similar setup where you can test these builds? Also, if you are comfortable installing beta software releases, do you mind installing 2017.4 back (and disable update checking via general settings dialog) and see if it improves things a bit? If it does improve things, then please install each of the beta builds (in sequence as described in my email) and let us know if you notice any changes.

Also, an advanced warning for people really tempted to do the following (and in order to avoid another instance of miscommunication like VS2017 runtime problem a few weeks back): just because you can’t reproduce a problem DOES NOT MEAN you can close an issue or ignore it. Who knows if the problem reported by a user might happen to you one day, or the reporter found a solution that works for him or her that might or might not apply to others. There are some in the community (who shall remain nameless) who downplay the severity of a problem when they can’t reproduce it or think their version of Windows is immune. No, a problem reported by a user is still a problem if it negatively affects productivity for them, potentially marring their NVDA experience. Some of you may think that what Gary is going through is a minor anoyance, but if this problem affects his productivity, then it should still be investigated to find out why, hence my suggestion to let him try different beta builds. I’m saying all this because I think we should change our attitudes about providing support for newcomers and/or those who are experiencing problems we can’t reproduce (easily).

Cheers,

Joseph



From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary
Sent: Saturday, March 10, 2018 10:09 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Typing Echo Change with 2018.1



Ok, that's really odd. All of them were slow on the typing echo, including 2017.4, which is what I was running previously without issue. I'm confused to how that could be possible. :/


Re: Error while updating to NVDA 2018.1 via the NVDA update utility.

Gene New Zealand <hurrikennyandopo@...>
 

Hi


Do the following


Press the windows key and in the search box type uac it should come with a result like change user account 

settings.

Press the enter key on that result.


Tab down until you get to the slider and then use the down  arrow key to make it go to nought


Then either tab down to if i remember either apply if it is there if so apply it then tab to ok then press the enter key on it.


After you press the enter key the UAC screen will come up just tab to yes then press the enter key on it and it should be done.


Hopefully after that it will not come up again until the next big windows update.


Gene nz




On 3/12/2018 5:56 PM, richard kurlander wrote:
how do you turn off user account control?At 11:52 PM 3/11/2018, you wrote:
this is why I turn off user account control.
----- Original Message ----- From: "Joseph Lee" <joseph.lee22590@...>
To: <nvda@nvda.groups.io>
Sent: Sunday, March 11, 2018 9:45 PM
Subject: Re: [nvda] Error while updating to NVDA 2018.1 via the NVDA update utility.


Hi,
Yes, but this time, say "yes" when UAC (User Account Control) screen appears.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Arianna Sepulveda
Sent: Sunday, March 11, 2018 6:44 PM
To: nvda@nvda.groups.io
Subject: [nvda] Error while updating to NVDA 2018.1 via the NVDA update utility.

Hello, All,


I just tried installing the NVDA 2018.1 update via the NVDA update utility, and got the following error. I'm not sure what is relevant, so I just coppied the entire output of the log viewer.

INFO - __main__ (18:37:12.331):
Starting NVDA
INFO - core.main (18:37:12.667):
Config dir: C:\Users\englishrider91\AppData\Roaming\nvda
INFO - config.ConfigManager._loadConfig (18:37:12.667):
Loading config: C:\Users\englishrider91\AppData\Roaming\nvda\nvda.ini
INFO - core.main (18:37:12.684):
NVDA version 2018.1
INFO - core.main (18:37:12.684):
Using Windows version 10.0.15063 workstation INFO - core.main (18:37:12.684):
Using Python version 2.7.14 (v2.7.14:84471935ed, Sep 16 2017,
20:19:30) [MSC v.1500 32 bit (Intel)]
INFO - core.main (18:37:12.684):
Using comtypes version 1.1.3
INFO - synthDriverHandler.setSynth (18:37:13.601):
Loaded synthDriver eloquence
INFO - core.main (18:37:13.601):
Using wx version 3.0.2.0 msw (classic)
INFO - brailleInput.initialize (18:37:13.601):
Braille input initialized
INFO - braille.initialize (18:37:13.601):
Using liblouis version 3.3.0
INFO - braille.BrailleHandler.setDisplayByName (18:37:13.601):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (18:37:13.753):
UIAutomation: IUIAutomation3
INFO - core.main (18:37:14.687):
NVDA initialized
ERROR - gui.installerGui.doInstall (18:37:46.061):
Failed to execute installer
Traceback (most recent call last):
 File "gui\installerGui.pyo", line 32, in doInstall
 File "config\__init__.pyo", line 192, in execElevated
 File "shellapi.pyo", line 42, in ShellExecuteEx
WindowsError: [Error 1223] The operation was canceled by the user.
ERROR - gui.installerGui.doInstall (18:37:46.061):
Installation failed: [Error 1223] The operation was canceled by the user.

Should I try updating again?


Thanks,
Ari













--
Check out my website for NVDA tutorials and other blindness related material at http://www.accessibilitycentral.net Regardless of where you are in New Zealand if you are near one of the APNK sites you can use a copy of the NVDA screen reader on one of their computers. To find out which locations (or location) is near to you please visit http://www.aotearoapeoplesnetwork.org/content/partner-libraries (Aotearoa People's Network Kaharoa). To find an NVDA certified expert near you, please visit the following link https://certification.nvaccess.org/. The certification page contains the official list of NVDA certified individuals from around the world, who have sat and successfully passed the NVDA expert exam.


Re: Error while updating to NVDA 2018.1 via the NVDA update utility.

richard kurlander <r.kurlander@...>
 

how do you turn off user account control?At 11:52 PM 3/11/2018, you wrote:

this is why I turn off user account control.
----- Original Message ----- From: "Joseph Lee" <joseph.lee22590@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Sunday, March 11, 2018 9:45 PM
Subject: Re: [nvda] Error while updating to NVDA 2018.1 via the NVDA update utility.


Hi,
Yes, but this time, say "yes" when UAC (User Account Control) screen appears.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Arianna Sepulveda
Sent: Sunday, March 11, 2018 6:44 PM
To: nvda@nvda.groups.io
Subject: [nvda] Error while updating to NVDA 2018.1 via the NVDA update utility.

Hello, All,


I just tried installing the NVDA 2018.1 update via the NVDA update utility, and got the following error. I'm not sure what is relevant, so I just coppied the entire output of the log viewer.

INFO - __main__ (18:37:12.331):
Starting NVDA
INFO - core.main (18:37:12.667):
Config dir: C:\Users\englishrider91\AppData\Roaming\nvda
INFO - config.ConfigManager._loadConfig (18:37:12.667):
Loading config: C:\Users\englishrider91\AppData\Roaming\nvda\nvda.ini
INFO - core.main (18:37:12.684):
NVDA version 2018.1
INFO - core.main (18:37:12.684):
Using Windows version 10.0.15063 workstation INFO - core.main (18:37:12.684):
Using Python version 2.7.14 (v2.7.14:84471935ed, Sep 16 2017,
20:19:30) [MSC v.1500 32 bit (Intel)]
INFO - core.main (18:37:12.684):
Using comtypes version 1.1.3
INFO - synthDriverHandler.setSynth (18:37:13.601):
Loaded synthDriver eloquence
INFO - core.main (18:37:13.601):
Using wx version 3.0.2.0 msw (classic)
INFO - brailleInput.initialize (18:37:13.601):
Braille input initialized
INFO - braille.initialize (18:37:13.601):
Using liblouis version 3.3.0
INFO - braille.BrailleHandler.setDisplayByName (18:37:13.601):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (18:37:13.753):
UIAutomation: IUIAutomation3
INFO - core.main (18:37:14.687):
NVDA initialized
ERROR - gui.installerGui.doInstall (18:37:46.061):
Failed to execute installer
Traceback (most recent call last):
File "gui\installerGui.pyo", line 32, in doInstall
File "config\__init__.pyo", line 192, in execElevated
File "shellapi.pyo", line 42, in ShellExecuteEx
WindowsError: [Error 1223] The operation was canceled by the user.
ERROR - gui.installerGui.doInstall (18:37:46.061):
Installation failed: [Error 1223] The operation was canceled by the user.

Should I try updating again?


Thanks,
Ari








Re: Error while updating to NVDA 2018.1 via the NVDA update utility.

Dennis L <dennisl1982@...>
 

this is why I turn off user account control.

----- Original Message -----
From: "Joseph Lee" <joseph.lee22590@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Sunday, March 11, 2018 9:45 PM
Subject: Re: [nvda] Error while updating to NVDA 2018.1 via the NVDA update utility.


Hi,
Yes, but this time, say "yes" when UAC (User Account Control) screen appears.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Arianna Sepulveda
Sent: Sunday, March 11, 2018 6:44 PM
To: nvda@nvda.groups.io
Subject: [nvda] Error while updating to NVDA 2018.1 via the NVDA update utility.

Hello, All,


I just tried installing the NVDA 2018.1 update via the NVDA update utility, and got the following error. I'm not sure what is relevant, so I just coppied the entire output of the log viewer.

INFO - __main__ (18:37:12.331):
Starting NVDA
INFO - core.main (18:37:12.667):
Config dir: C:\Users\englishrider91\AppData\Roaming\nvda
INFO - config.ConfigManager._loadConfig (18:37:12.667):
Loading config: C:\Users\englishrider91\AppData\Roaming\nvda\nvda.ini
INFO - core.main (18:37:12.684):
NVDA version 2018.1
INFO - core.main (18:37:12.684):
Using Windows version 10.0.15063 workstation INFO - core.main (18:37:12.684):
Using Python version 2.7.14 (v2.7.14:84471935ed, Sep 16 2017,
20:19:30) [MSC v.1500 32 bit (Intel)]
INFO - core.main (18:37:12.684):
Using comtypes version 1.1.3
INFO - synthDriverHandler.setSynth (18:37:13.601):
Loaded synthDriver eloquence
INFO - core.main (18:37:13.601):
Using wx version 3.0.2.0 msw (classic)
INFO - brailleInput.initialize (18:37:13.601):
Braille input initialized
INFO - braille.initialize (18:37:13.601):
Using liblouis version 3.3.0
INFO - braille.BrailleHandler.setDisplayByName (18:37:13.601):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (18:37:13.753):
UIAutomation: IUIAutomation3
INFO - core.main (18:37:14.687):
NVDA initialized
ERROR - gui.installerGui.doInstall (18:37:46.061):
Failed to execute installer
Traceback (most recent call last):
File "gui\installerGui.pyo", line 32, in doInstall
File "config\__init__.pyo", line 192, in execElevated
File "shellapi.pyo", line 42, in ShellExecuteEx
WindowsError: [Error 1223] The operation was canceled by the user.
ERROR - gui.installerGui.doInstall (18:37:46.061):
Installation failed: [Error 1223] The operation was canceled by the user.

Should I try updating again?


Thanks,
Ari


Re: Typing Echo Change with 2018.1

Daniel Wolak <danielwolak97@...>
 

Hi,

I can also reproduce this. Running latest master of nvda 14940 e78,e72f9 on windows10 ver1709.

HTH,


Daniel


On 12/03/2018 00:18, Rosemarie Chavarria wrote:

Hi, Joseph,

 

I tested it and unchecking speech interrupt does cause NVDA to lag for me so I checked it again.

 

Rosemarie

 

 

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Sunday, March 11, 2018 9:15 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Typing Echo Change with 2018.1

 

Hi,

Huh? That’s new for me. So you’re saying turning this off fixed this for you? Can others test this theory?

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary
Sent: Sunday, March 11, 2018 8:21 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Typing Echo Change with 2018.1

 

The typing interrupt toggle under keyboard settings fixed it!?

I have never touched that setting...ever.  Is there a chance 2018.1 changed this setting somehow?  Sorry for the trouble.



Re: Error while updating to NVDA 2018.1 via the NVDA updateutility.

Kevin <kleeva5@...>
 

I downloaded NVDA 2018.1 from the NVDA site, downloaded to my download folder and ran it from there.  The installer recognized I had the previous version and updated.  No problems what so ever!

 

E-mail is golden!!!
Kevin Lee

 

From: Arianna Sepulveda
Sent: Sunday, March 11, 2018 6:43 PM
To: nvda@nvda.groups.io
Subject: [nvda] Error while updating to NVDA 2018.1 via the NVDA updateutility.

 

Hello, All,

 

 

I just tried installing the NVDA 2018.1 update via the NVDA update

utility, and got the following error. I'm not sure what is relevant,

so I just coppied the entire output of the log viewer.

 

INFO - __main__ (18:37:12.331):

Starting NVDA

INFO - core.main (18:37:12.667):

Config dir: C:\Users\englishrider91\AppData\Roaming\nvda

INFO - config.ConfigManager._loadConfig (18:37:12.667):

Loading config: C:\Users\englishrider91\AppData\Roaming\nvda\nvda.ini

INFO - core.main (18:37:12.684):

NVDA version 2018.1

INFO - core.main (18:37:12.684):

Using Windows version 10.0.15063 workstation

INFO - core.main (18:37:12.684):

Using Python version 2.7.14 (v2.7.14:84471935ed, Sep 16 2017,

20:19:30) [MSC v.1500 32 bit (Intel)]

INFO - core.main (18:37:12.684):

Using comtypes version 1.1.3

INFO - synthDriverHandler.setSynth (18:37:13.601):

Loaded synthDriver eloquence

INFO - core.main (18:37:13.601):

Using wx version 3.0.2.0 msw (classic)

INFO - brailleInput.initialize (18:37:13.601):

Braille input initialized

INFO - braille.initialize (18:37:13.601):

Using liblouis version 3.3.0

INFO - braille.BrailleHandler.setDisplayByName (18:37:13.601):

Loaded braille display driver noBraille, current display has 0 cells.

INFO - _UIAHandler.UIAHandler.MTAThreadFunc (18:37:13.753):

UIAutomation: IUIAutomation3

INFO - core.main (18:37:14.687):

NVDA initialized

ERROR - gui.installerGui.doInstall (18:37:46.061):

Failed to execute installer

Traceback (most recent call last):

  File "gui\installerGui.pyo", line 32, in doInstall

  File "config\__init__.pyo", line 192, in execElevated

  File "shellapi.pyo", line 42, in ShellExecuteEx

WindowsError: [Error 1223] The operation was canceled by the user.

ERROR - gui.installerGui.doInstall (18:37:46.061):

Installation failed: [Error 1223] The operation was canceled by the user.

 

Should I try updating again?

 

 

Thanks,

Ari

 

 

 


Re: Error while updating to NVDA 2018.1 via the NVDA update utility.

 

Hi,
Yes, but this time, say "yes" when UAC (User Account Control) screen appears.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Arianna Sepulveda
Sent: Sunday, March 11, 2018 6:44 PM
To: nvda@nvda.groups.io
Subject: [nvda] Error while updating to NVDA 2018.1 via the NVDA update utility.

Hello, All,


I just tried installing the NVDA 2018.1 update via the NVDA update utility, and got the following error. I'm not sure what is relevant, so I just coppied the entire output of the log viewer.

INFO - __main__ (18:37:12.331):
Starting NVDA
INFO - core.main (18:37:12.667):
Config dir: C:\Users\englishrider91\AppData\Roaming\nvda
INFO - config.ConfigManager._loadConfig (18:37:12.667):
Loading config: C:\Users\englishrider91\AppData\Roaming\nvda\nvda.ini
INFO - core.main (18:37:12.684):
NVDA version 2018.1
INFO - core.main (18:37:12.684):
Using Windows version 10.0.15063 workstation INFO - core.main (18:37:12.684):
Using Python version 2.7.14 (v2.7.14:84471935ed, Sep 16 2017,
20:19:30) [MSC v.1500 32 bit (Intel)]
INFO - core.main (18:37:12.684):
Using comtypes version 1.1.3
INFO - synthDriverHandler.setSynth (18:37:13.601):
Loaded synthDriver eloquence
INFO - core.main (18:37:13.601):
Using wx version 3.0.2.0 msw (classic)
INFO - brailleInput.initialize (18:37:13.601):
Braille input initialized
INFO - braille.initialize (18:37:13.601):
Using liblouis version 3.3.0
INFO - braille.BrailleHandler.setDisplayByName (18:37:13.601):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (18:37:13.753):
UIAutomation: IUIAutomation3
INFO - core.main (18:37:14.687):
NVDA initialized
ERROR - gui.installerGui.doInstall (18:37:46.061):
Failed to execute installer
Traceback (most recent call last):
File "gui\installerGui.pyo", line 32, in doInstall
File "config\__init__.pyo", line 192, in execElevated
File "shellapi.pyo", line 42, in ShellExecuteEx
WindowsError: [Error 1223] The operation was canceled by the user.
ERROR - gui.installerGui.doInstall (18:37:46.061):
Installation failed: [Error 1223] The operation was canceled by the user.

Should I try updating again?


Thanks,
Ari


Error while updating to NVDA 2018.1 via the NVDA update utility.

Arianna Sepulveda
 

Hello, All,


I just tried installing the NVDA 2018.1 update via the NVDA update
utility, and got the following error. I'm not sure what is relevant,
so I just coppied the entire output of the log viewer.

INFO - __main__ (18:37:12.331):
Starting NVDA
INFO - core.main (18:37:12.667):
Config dir: C:\Users\englishrider91\AppData\Roaming\nvda
INFO - config.ConfigManager._loadConfig (18:37:12.667):
Loading config: C:\Users\englishrider91\AppData\Roaming\nvda\nvda.ini
INFO - core.main (18:37:12.684):
NVDA version 2018.1
INFO - core.main (18:37:12.684):
Using Windows version 10.0.15063 workstation
INFO - core.main (18:37:12.684):
Using Python version 2.7.14 (v2.7.14:84471935ed, Sep 16 2017,
20:19:30) [MSC v.1500 32 bit (Intel)]
INFO - core.main (18:37:12.684):
Using comtypes version 1.1.3
INFO - synthDriverHandler.setSynth (18:37:13.601):
Loaded synthDriver eloquence
INFO - core.main (18:37:13.601):
Using wx version 3.0.2.0 msw (classic)
INFO - brailleInput.initialize (18:37:13.601):
Braille input initialized
INFO - braille.initialize (18:37:13.601):
Using liblouis version 3.3.0
INFO - braille.BrailleHandler.setDisplayByName (18:37:13.601):
Loaded braille display driver noBraille, current display has 0 cells.
INFO - _UIAHandler.UIAHandler.MTAThreadFunc (18:37:13.753):
UIAutomation: IUIAutomation3
INFO - core.main (18:37:14.687):
NVDA initialized
ERROR - gui.installerGui.doInstall (18:37:46.061):
Failed to execute installer
Traceback (most recent call last):
File "gui\installerGui.pyo", line 32, in doInstall
File "config\__init__.pyo", line 192, in execElevated
File "shellapi.pyo", line 42, in ShellExecuteEx
WindowsError: [Error 1223] The operation was canceled by the user.
ERROR - gui.installerGui.doInstall (18:37:46.061):
Installation failed: [Error 1223] The operation was canceled by the user.

Should I try updating again?


Thanks,
Ari


Re: Typing Echo Change with 2018.1

Robert Mendoza
 

Hi Joseph,

Sorry for the late in my respond. I went again to double-check the keyboard settings then I noticed that the option for Speech interrupt for typed characters is uncheck though in my recollection I never altered this even before. and now I am back again in using the 2018.1 fine for now -the lag in typing were solved. Thanks again.


Robert Mendoza
On 3/11/2018 12:06 PM, Joseph Lee wrote:

Hi,

Does running NVDA in “safe mode” aka add-ons disabled help?

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Robert Mendoza
Sent: Saturday, March 10, 2018 7:50 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Typing Echo Change with 2018.1

 

Yes! I noticed it here so I decided to go back to older version and use my flash drive. Not specifically  for the mobile facebook but as well with typing to notepad that some kinda delay or what. I even tried to adjust the keyboard settings but got the same results. I think I will be working for now and use 2017.4 version.

 

Robert Mendoza

On 3/11/2018 11:36 AM, Lino Morales wrote:

Que pasa Gary. Yeah I’ve noticed this too. When I’m writing a status or replying to someone in the FB mobile site that’s when it happens.

 

Lino Morales

 

From: Gary
Sent: Saturday, March 10, 2018 10:34 PM
To: nvda@nvda.groups.io
Subject: [nvda] Typing Echo Change with 2018.1

 

I upgraded to the latest release of NVDA today and right away I noticed a change that is, well, quite annoying to me.

I am a fast typist who prefers to have typed characters repeated.  Since upgrading NVDA today, the letters I type are read back to me extremely slowly, where as previously, i was hearing the key I typed instantly.

Similarly, in a web browser when I use NVDA+F7 to jump to a link, there is also a delay.  For example, if I know the link I want is "Search", I could hit the S and NVDA would immediately say "Search" and I could then hit enter.  Now, NVDA says "S", there is a delay, then it says "Search".  Is this a new feature that has a setting I can't find to change it, a bug, or am I the only person noticing this?

 

 



Question about transferring espeak data between NVDA & Braillenote touch version

Jessica D
 

Hi,

Yesterday, I bought eSpeak for my Braillenote touch.

I’m really enjoying it, and its totally boosted my productivity.

I’m now using eSpeak with NVDA, and was wondering if it was possible to transfer my settings and other data between the 2 versions?

 

Thanks,

Jessica

 

 

Sent from Mail for Windows 10

 


Re: Typing Echo Change with 2018.1

Rosemarie Chavarria
 

I don't have a braille display. Can't afford one.

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Brian's Mail list account via Groups.Io
Sent: Sunday, March 11, 2018 1:31 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Typing Echo Change with 2018.1

Do all of you have Braille displays?
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Gary" <ironmangary@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Sunday, March 11, 2018 6:08 AM
Subject: Re: [nvda] Typing Echo Change with 2018.1


Ok, that's really odd. All of them were slow on the typing echo, including
2017.4, which is what I was running previously without issue. I'm confused
to how that could be possible. :/


Re: espeak and pronunciation of some words

Rosemarie Chavarria
 

I've used the one-core voices and they're really great.

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Devin Prater
Sent: Sunday, March 11, 2018 5:14 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] espeak and pronunciation of some words

I agree, eSpeak needs lots of work, still. But the worst part of Open Source is that we all talk about it, but nothing gets done, we all wish, but never act, and there is only one person working on eSpeak. I know, we can't all program. But, with Windows 10, there are the OneCore voices, created by Microsoft which we can use, so we are no longer limited to eSpeak.

On 3/11/18, 7:05 PM, "nvda@nvda.groups.io on behalf of Rosemarie Chavarria" <nvda@nvda.groups.io on behalf of knitqueen2007@gmail.com> wrote:

I've noticed that about e-speak too. The word "for" when with other words soundlike "fer".



-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Dejan Ristic
Sent: Sunday, March 11, 2018 12:01 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] espeak and pronunciation of some words

Let me remind you of the word for, which, if followed by another word, seems to sound like fur.


For example: for the time being.


It is very interesting to here it pronounced quite correctly when it is
a stand alone word, as is the case in the first line of my message.


On 11/03/2018 07:54, Governor staten wrote:
> I'll try to describe this as best I can. Take the word "content". The
> stress in this word is wrong, or, very much off. This is the case with
> other words too. Nazarene should sound like Nazareen. I'm sure there
> are other words like this I, and others, could think of.
>
>
> Any word with the letter "o" is likely to have the stress wrong.
> Monster is another example. This could just be me. Does anyone else
> hear what I'm hearing?
>
>
>
>
> .
>


Re: Typing Echo Change with 2018.1

Rosemarie Chavarria
 

Hi, Joseph,

 

I tested it and unchecking speech interrupt does cause NVDA to lag for me so I checked it again.

 

Rosemarie

 

 

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Sunday, March 11, 2018 9:15 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Typing Echo Change with 2018.1

 

Hi,

Huh? That’s new for me. So you’re saying turning this off fixed this for you? Can others test this theory?

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary
Sent: Sunday, March 11, 2018 8:21 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Typing Echo Change with 2018.1

 

The typing interrupt toggle under keyboard settings fixed it!?

I have never touched that setting...ever.  Is there a chance 2018.1 changed this setting somehow?  Sorry for the trouble.


Re: espeak and pronunciation of some words

Devin Prater
 

I agree, eSpeak needs lots of work, still. But the worst part of Open Source is that we all talk about it, but nothing gets done, we all wish, but never act, and there is only one person working on eSpeak. I know, we can't all program. But, with Windows 10, there are the OneCore voices, created by Microsoft which we can use, so we are no longer limited to eSpeak.

On 3/11/18, 7:05 PM, "nvda@nvda.groups.io on behalf of Rosemarie Chavarria" <nvda@nvda.groups.io on behalf of knitqueen2007@gmail.com> wrote:

I've noticed that about e-speak too. The word "for" when with other words soundlike "fer".

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Dejan Ristic
Sent: Sunday, March 11, 2018 12:01 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] espeak and pronunciation of some words

Let me remind you of the word for, which, if followed by another word, seems to sound like fur.


For example: for the time being.


It is very interesting to here it pronounced quite correctly when it is
a stand alone word, as is the case in the first line of my message.


On 11/03/2018 07:54, Governor staten wrote:
> I'll try to describe this as best I can. Take the word "content". The
> stress in this word is wrong, or, very much off. This is the case with
> other words too. Nazarene should sound like Nazareen. I'm sure there
> are other words like this I, and others, could think of.
>
>
> Any word with the letter "o" is likely to have the stress wrong.
> Monster is another example. This could just be me. Does anyone else
> hear what I'm hearing?
>
>
>
>
> .
>


Re: outlook 2016 calendar

Rosemarie Chavarria
 

I have the outlook 2013 calendar buthaven't tried it yet.

 

 

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Angelo Sonnesso
Sent: Sunday, March 11, 2018 11:17 AM
To: nvda@nvda.groups.io
Subject: [nvda] outlook 2016 calendar

 

Has anyone had success with the outlook 2016 calendar?

I never had a problem with older versions of outlook, but now I can only read the dates.

Thanks

 

73 N2DYN Angelo


Re: Typing Echo Change with 2018.1

Roger Stewart
 

Interesting!  I just checked, and mine is checked but I have no typing echo delays at all!  As snappy and responsive as ever.

Roger









On 3/11/2018 6:56 PM, Gene wrote:
Did you check or uncheck it?  It should be unchecked by default and when unchecked, I don't have the problem.  I'm not using the newest NVDA version but it has been unchecked whenever I've used a new version.
 
Gene
----- Original Message -----
From: Gary
Sent: Sunday, March 11, 2018 11:28 AM
Subject: Re: [nvda] Typing Echo Change with 2018.1

I checked "speech interrupt for typed characters."  It was unchecked, although I never touched it previously, so I can't say how it was set prior to 2018.1.