|
Re: Typing Echo Change with 2018.1
brian,
whats the best and most responsive version of firefox specially for nvda users? On 3/12/18, Brian's Mail list account via Groups.Io <bglists=blueyonder.co.uk@groups.io> wrote: No me neither, but as Joseph said, the other setting allows one to use one -- By God, were I given all the seven heavens with all they contain in order that I may disobey God by depriving an ant from the husk of a grain of barley, I would not do it. imam ali
|
|||||||||||
|
|
|||||||||||
|
Please Clarify NVDA 2018?
David Russell
Hello Group members,
Two questions which "should" be simple enough to answer. - Does NVDA 2018 only work with computers and devices compatible with Windows Ten? - If NVDA works only with newer windows versions, is there an online resource that will distribute Windows Ten or other said product, and help install at a reduced cost to blind users? -- David Russell david.sonofhashem@gmail.com "chilah phanim" Make G-d smile!
|
|||||||||||
|
|
|||||||||||
|
Re: bleeps when using explorer file list
Jonathan COHN
Could this be a preview of selected files? I don't see this behavior on my systems, though I have to say I generally don't keep any folders with large amounts of files on my Windows systems.
Best Wishes, Jonathan
|
|||||||||||
|
|
|||||||||||
|
Re: Windows10 Mail and NVDA: several bugs reported
Hi,
toggle quoted messageShow quoted text
Looks like NVDA is told to use UIA directly. This is the case when traditional means of fetching information from Word and its components won't work (I need to better document this and others soon). Cheers, Joseph
-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian's Mail list account via Groups.Io Sent: Monday, March 12, 2018 4:14 AM To: nvda@nvda.groups.io Subject: Re: [nvda] Windows10 Mail and NVDA: several bugs reported I'll ask the next question which build of windows 10 is it he is using? I'm sure Joseph will ask otherwise! 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: "Iván Novegil via Groups.Io" <ivan.novegil=nvda.es@groups.io> To: <nvda@nvda.groups.io> Sent: Monday, March 12, 2018 9:59 AM Subject: [nvda] Windows10 Mail and NVDA: several bugs reported Hello all. A Spanish user asked us about the following two bugs he has with Windows10's mail app. -When opening a mail to read it, NVDA reports "page 1". -When writing a message with word echo enabled and pressing space after typing a word with accented letters or "ñ" on it NVDA doesn't report it. Can someone try to reproduce these bugs to open an issue if needed? The two ones happened after updating to 2018.1 and using either Eloquence or eSpeakNG and with WinTenApps and without it. Thanks in advance. Regards. -- Iván Novegil Cancelas Editor ivan.novegil@nvda.es <mailto:ivan.novegil@nvda.es> NVDA.es Logo Comunidad hispanohablante de NVDA | Proyecto NVDA.es - www.NVDA.es <https://nvda.es>; - @nvda_es <https://twitter.com/nvda_es>; Usuario do NVDA en galego ***Note que a anterior mensaxe e/ou os seus adxuntos pode conter información privada ou confidencial. O emprego da información desta mensaxe e/ou dos seus adxuntos está reservado ao ámbito privado do destinatario agás autorización do remitente. Se recibiu esta mensaxe por erro comuníqueo por esta mesma vía e destrúa a mensaxe.***
|
|||||||||||
|
|
|||||||||||
|
Re: URGENT HELP NEEDED
MNR. Vorster. Here's a few other links to.
toggle quoted messageShow quoted text
http://www.typefastertypingtutor.com/accversion.html http://www.yesaccessible.com/typeability.html https://www.typefastertypingtutor.com/accversion.html Hope this helps. They're the only free programs. Chantelle
On 3/12/18, Chantelle Buys <cbuys6@gmail.com> wrote:
Hi MNR. Vorster. Here's a link that you could try. --
Never give up, at any cost.
|
|||||||||||
|
|
|||||||||||
|
Re: Error while updating to NVDA 2018.1 via the NVDA update utility.
Devin Prater
This is a great message. Also, compare UAC to what Linux users have to do, typing in their whole root password when installing or updating programs sometimes. Compared to that, one keystroke is nothing.
"nvda@nvda.groups.io on behalf of Gene" wrote:
It's a minimum amount of inconvenience to respond when the UAC prompt appears. All you have to do is use the alt y command. Why are people so casual about disabling a security feature that is minimally inconvenient? You issue one command. Compare that very minor inconvenience to what you may have to doo if you are infected because UAC is off. I realize that malware can circumvent UAC, and, from what I've been told, it isn't difficult. But still, what if you could have prevented nfection by having it on at a minimum of inconvenience?
Gene
----- Original Message -----
From: Dennis L Sent: Sunday, March 11, 2018 10:52 PM Subject: Re: [nvda] Error while updating to NVDA 2018.1 via the NVDA update utility.
this is why I turn off user account control.
|
|||||||||||
|
|
|||||||||||
|
Re: Error while updating to NVDA 2018.1 via the NVDA update utility.
Brice Mijares
I've noticed of late, that I don't hear E-speak come up when UAC is triggered. I hear one core voice which I have chose as my synthesizer. Maybe this has confused this person.
toggle quoted messageShow quoted text
On 3/12/2018 3:35 AM, Gene wrote:
In what version of Windows do you not hear UAC text spoken when the screen comes up? In Windows 7 the text is spoken, from what I've read, unless you are using the portable version. If this isn't the case, we should know it and the problem should be corrected.
|
|||||||||||
|
|
|||||||||||
|
URGENT HELP NEEDED
Christo Vorster
Hi Group
We ar in need of a Talking Typing Tutor, compatible with Windows 10.
Can anybody please assist us with information, or rather, a website where can download such material.
Please assist.
Christo Vorster (South Africa)
|
|||||||||||
|
|
|||||||||||
|
Re: espeak and pronunciation of some words
Peter Beasley
I don't use Espeak, but if words are pronounced wrongly, change the pronunciation in the voice dictionary.
toggle quoted messageShow quoted text
-----Original Message-----
From: Brian's Mail list account via Groups.Io Sent: Monday, March 12, 2018 9:19 AM To: nvda@nvda.groups.io Subject: Re: [nvda] espeak and pronunciation of some words Yes I really think for the record often should have an audible T as well as for still being 'FOR' Brian! 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: "Dejan Ristic" <r.dejan83@gmail.com> To: <nvda@nvda.groups.io> Sent: Sunday, March 11, 2018 7:01 PM 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.
|
|||||||||||
|
|
|||||||||||
|
Re: Question about transferring espeak data between NVDA & Braillenote touch version
Jessica D <jldail13@...>
Hi
toggle quoted messageShow quoted text
I'm not sure.Can you please tell me where to check, for both versions?Thanks,Jessica
On Mar 12, 2018, at 5:29 AM, Brian's Mail list account via Groups.Io <bglists=blueyonder.co.uk@groups.io> wrote:
|
|||||||||||
|
|
|||||||||||
|
Webbie pdf to text new version with ocr
Brian's Mail list account <bglists@...>
I know not much about it but picked this up on another account and as there have been discussions about such things here, I thought I'd mention it.
If you put webbie into a search you should find the site. 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.
|
|||||||||||
|
|
|||||||||||
|
Re: Windows10 Mail and NVDA: several bugs reported
Brian's Mail list account <bglists@...>
I'll ask the next question which build of windows 10 is it he is using? I'm sure Joseph will ask otherwise!
toggle quoted messageShow quoted text
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: "Iván Novegil via Groups.Io" <ivan.novegil=nvda.es@groups.io> To: <nvda@nvda.groups.io> Sent: Monday, March 12, 2018 9:59 AM Subject: [nvda] Windows10 Mail and NVDA: several bugs reported Hello all. A Spanish user asked us about the following two bugs he has with Windows10's mail app. -When opening a mail to read it, NVDA reports "page 1". -When writing a message with word echo enabled and pressing space after typing a word with accented letters or "ñ" on it NVDA doesn't report it. Can someone try to reproduce these bugs to open an issue if needed? The two ones happened after updating to 2018.1 and using either Eloquence or eSpeakNG and with WinTenApps and without it. Thanks in advance. Regards. -- Iván Novegil Cancelas Editor ivan.novegil@nvda.es <mailto:ivan.novegil@nvda.es> NVDA.es Logo Comunidad hispanohablante de NVDA | Proyecto NVDA.es - www.NVDA.es <https://nvda.es>; - @nvda_es <https://twitter.com/nvda_es>; Usuario do NVDA en galego ***Note que a anterior mensaxe e/ou os seus adxuntos pode conter información privada ou confidencial. O emprego da información desta mensaxe e/ou dos seus adxuntos está reservado ao ámbito privado do destinatario agás autorización do remitente. Se recibiu esta mensaxe por erro comuníqueo por esta mesma vía e destrúa a mensaxe.***
|
|||||||||||
|
|
|||||||||||
|
Registry fixing tool in nvda
Brian's Mail list account <bglists@...>
I know a number of people here have had serious issues with browsers not reading word not working right with nvda and other associated problems.
For some time now this has been known to be due to registry issues due to uninstallers of other software not correctly registering important files. The latest next snapshot has a tool to fix this, rather predictably in its tool menu, so if you are having such issues, it may well be a good idea to try this version of nvda and use the tool. it should do no harm, but do remember that next snaps are bleeding edge code and will need to be used with caution. Always back up your previous version and set a restore point before doing any work on registry files. Note the account that its used on has to have admin access or it won't work. Here is what the entry says. commit 8793a65c7aa65949a9043aafc932627ff158c90a Author: Michael Curran <mick@nvaccess.org> Date: Thu 08 Mar 2018 09:41:04 +1000 Installer: re-register some common COM interfaces which commonly get broken by bad uninstallers. Raw diff commit d3a9795e75cdbe9241d11eecb9a98fbe774a17f7 Author: Michael Curran <mick@nvaccess.org> Date: Mon 12 Mar 2018 12:06:37 +1000 COMRegistrationFixes tool: add a backslash to the systemDrive. Also deremove some unused functions. Raw diff commit 3a5abd72a307fbe02779111dfee3bc5f5371345d Author: Michael Curran <mick@nvaccess.org> Date: Mon 12 Mar 2018 12:07:19 +1000 Add the COM Registrations Fixing tool to NVDA's Tools menu. Raw diff commit e1d79784de5f0b77343992e61b1fb811a9dc826e Author: Michael Curran <mick@nvaccess.org> Date: Mon 12 Mar 2018 15:43:05 +1000 Add a warning dialog to the COM Registration Fixing tool when run manually from the Tools menu. Raw diff commit 7c2e945533f7386b4b3142281e23009997f5d801 Author: Michael Curran <mick@nvaccess.org> Date: Mon 12 Mar 2018 17:44:10 +1000 Add copyright header Raw diff commit 877362bde2e108fae69c067cb26bdd797843caa8 Author: Michael Curran <mick@nvaccess.org> Date: Mon 12 Mar 2018 17:48:11 +1000 Add a module docstring Raw diff commit e550d32924b55272e05254eada58c9bb04fd1ae7 Author: Michael Curran <mick@nvaccess.org> Date: Mon 12 Mar 2018 17:55:53 +1000 Incubates #8075 Raw diff ------------------------------------------------------------------------------ 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.
|
|||||||||||
|
|
|||||||||||
|
Re: Error while updating to NVDA 2018.1 via the NVDA update utility.
Gene
I don't know if turning up the volume of system
sounds would make it louder, nor do I know if the sound can be changed.
But there is a sound. also, when using the portable version of NVDA, when
UAC comes on, you hear the phrase, secure desktop. I don't know what, if
anything, you hear with the installed version. But it isn't as though,
when using the default setting, UAC comes on often. I don't see a good
reason to disable a Windows security feature to eliminate a minimum amount of
inconvenience.
Gene
----- Original Message -----
Sent: Monday, March 12, 2018 5:57 AM
Subject: Re: [nvda] Error while updating to NVDA 2018.1 via the NVDA
update utility. on windows 7 I have its not, maybe one can change it. Brian bglists@... Sent via blueyonder. Please address personal E-mail to:- briang1@..., putting 'Brian Gaff' in the display name field. ----- Original Message ----- From: "Gene" <gsasner@...> To: <nvda@nvda.groups.io> Sent: Monday, March 12, 2018 10:37 AM Subject: Re: [nvda] Error while updating to NVDA 2018.1 via the NVDA update utility. There already is a UAC sound. Gene ----- Original Message ----- From: Chris via Groups.Io Sent: Monday, March 12, 2018 5:01 AM To: nvda@nvda.groups.io Subject: Re: [nvda] Error while updating to NVDA 2018.1 via the NVDA update utility. A sound can be associated in sounds in control panel Whether it has a sound by default or not i cannot tell you but there is the option to do so if one can be bothered that is From: Brian's Mail list account via Groups.Io Sent: 12 March 2018 09:35 To: nvda@nvda.groups.io Subject: Re: [nvda] Error while updating to NVDA 2018.1 via the NVDA update utility. Yes because for some reason only known to Microsoft this screen does not have any text that can be spoken by a screenreader. It would be nice if it made a sound so you knew it was there. If you are the only user, then having uac on seems completely pointless. Brian bglists@... Sent via blueyonder. Please address personal E-mail to:- briang1@..., putting 'Brian Gaff' in the display name field. ----- Original Message ----- From: "Dennis L" <dennisl1982@...> To: <nvda@nvda.groups.io> Sent: Monday, March 12, 2018 3:52 AM Subject: Re: [nvda] Error while updating to NVDA 2018.1 via the NVDA update utility. > 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 > > > > > > > > >
|
|||||||||||
|
|
|||||||||||
|
Re: Error while updating to NVDA 2018.1 via the NVDA update utility.
Brian's Mail list account <bglists@...>
But its not really a sound that shouts out a different thing. At least not on windows 7 I have its not, maybe one can change it.
toggle quoted messageShow quoted text
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: Monday, March 12, 2018 10:37 AM Subject: Re: [nvda] Error while updating to NVDA 2018.1 via the NVDA update utility. There already is a UAC sound. Gene ----- Original Message ----- From: Chris via Groups.Io Sent: Monday, March 12, 2018 5:01 AM To: nvda@nvda.groups.io Subject: Re: [nvda] Error while updating to NVDA 2018.1 via the NVDA update utility. A sound can be associated in sounds in control panel Whether it has a sound by default or not i cannot tell you but there is the option to do so if one can be bothered that is From: Brian's Mail list account via Groups.Io Sent: 12 March 2018 09:35 To: nvda@nvda.groups.io Subject: Re: [nvda] Error while updating to NVDA 2018.1 via the NVDA update utility. Yes because for some reason only known to Microsoft this screen does not have any text that can be spoken by a screenreader. It would be nice if it made a sound so you knew it was there. If you are the only user, then having uac on seems completely pointless. 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: "Dennis L" <dennisl1982@gmail.com> To: <nvda@nvda.groups.io> Sent: Monday, March 12, 2018 3:52 AM Subject: Re: [nvda] Error while updating to NVDA 2018.1 via the NVDA update utility. 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.
Gene
There already is a UAC sound.
Gene
----- Original Message -----
From: Chris via Groups.Io
Sent: Monday, March 12, 2018 5:01 AM
Subject: Re: [nvda] Error while updating to NVDA 2018.1 via the NVDA
update utility. A sound can be associated in sounds in control panel
Whether it has a sound by default or not i cannot tell you but there is the option to do so if one can be bothered that is
From: Brian's Mail list account via
Groups.Io
Yes because for some reason only known to Microsoft this screen does not have any text that can be spoken by a screenreader. It would be nice if it made a sound so you knew it was there. If you are the only user, then having uac on seems completely pointless. Brian
bglists@... Sent via blueyonder. Please address personal E-mail to:- briang1@..., putting 'Brian Gaff' in the display name field. ----- Original Message ----- From: "Dennis L" <dennisl1982@...> To: <nvda@nvda.groups.io> Sent: Monday, March 12, 2018 3:52 AM Subject: Re: [nvda] Error while updating to NVDA 2018.1 via the NVDA update utility.
> 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 > > > > > > > > >
|
|||||||||||
|
|
|||||||||||
|
Re: Error while updating to NVDA 2018.1 via the NVDA update utility.
Gene
In what version of Windows do you not hear UAC text
spoken when the screen comes up? In Windows 7 the text is spoken, from
what I've read, unless you are using the portable version. If this isn't
the case, we should know it and the problem should be corrected.
Gene
----- Original Message -----
Sent: Monday, March 12, 2018 4:35 AM
Subject: Re: [nvda] Error while updating to NVDA 2018.1 via the NVDA
update utility. have any text that can be spoken by a screenreader. It would be nice if it made a sound so you knew it was there. If you are the only user, then having uac on seems completely pointless. Brian bglists@... Sent via blueyonder. Please address personal E-mail to:- briang1@..., putting 'Brian Gaff' in the display name field. ----- Original Message ----- From: "Dennis L" <dennisl1982@...> To: <nvda@nvda.groups.io> Sent: Monday, March 12, 2018 3:52 AM Subject: Re: [nvda] Error while updating to NVDA 2018.1 via the NVDA update utility. > 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 > > > > > > > > >
|
|||||||||||
|
|
|||||||||||
|
Re: Error while updating to NVDA 2018.1 via the NVDA update utility.
Gene
It's a minimum amount of inconvenience to respond
when the UAC prompt appears. All you have to do is use the alt y
command. Why are people so casual about disabling a security feature that
is minimally inconvenient? You issue one command. Compare that
very minor inconvenience to what you may have to doo if you are infected because
UAC is off. I realize that malware can circumvent UAC, and, from what I've
been told, it isn't difficult. But still, what if you could have prevented
nfection by having it on at a minimum of inconvenience?
Gene
----- Original Message -----
From: Dennis L
Sent: Sunday, March 11, 2018 10:52 PM
Subject: Re: [nvda] Error while updating to NVDA 2018.1 via the NVDA
update utility. ----- 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
|
|||||||||||
|
|
|||||||||||
|
Re: Error while updating to NVDA 2018.1 via the NVDA update utility.
Chris
A sound can be associated in sounds in control panel
Whether it has a sound by default or not i cannot tell you but there is the option to do so if one can be bothered that is
From: Brian's Mail list account via Groups.Io
Sent: 12 March 2018 09:35 To: nvda@nvda.groups.io Subject: Re: [nvda] Error while updating to NVDA 2018.1 via the NVDA update utility.
Yes because for some reason only known to Microsoft this screen does not have any text that can be spoken by a screenreader. It would be nice if it made a sound so you knew it was there. If you are the only user, then having uac on seems completely pointless. Brian
bglists@... Sent via blueyonder. Please address personal E-mail to:- briang1@..., putting 'Brian Gaff' in the display name field. ----- Original Message ----- From: "Dennis L" <dennisl1982@...> To: <nvda@nvda.groups.io> Sent: Monday, March 12, 2018 3:52 AM Subject: Re: [nvda] Error while updating to NVDA 2018.1 via the NVDA update utility.
> 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 > > > > > > > > >
|
|||||||||||
|
|
|||||||||||
|
Windows10 Mail and NVDA: several bugs reported
Iván Novegil
Hello all.
A Spanish user asked us about the following two bugs he has with Windows10's mail app. -When opening a mail to read it, NVDA reports "page 1". -When writing a message with word echo enabled and pressing space after typing a word with accented letters or "ñ" on it NVDA doesn't report it.
Can someone try to reproduce these bugs to open an issue if
needed? The two ones happened after updating to 2018.1 and using
either Eloquence or eSpeakNG and with WinTenApps and without it.
Thanks in advance. Regards. --
Iván Novegil Cancelas
|
|||||||||||
|
|
|||||||||||
