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 <mailto: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<mailto:dennisl1982@gmail.com>
*Sent:*Sunday, March 11, 2018 10:52 PM
*To:*nvda@nvda.groups.io<mailto:nvda@nvda.groups.io>
*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<mailto:joseph.lee22590@gmail.com>>
To: <nvda@nvda.groups.io<mailto: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<mailto:nvda@nvda.groups.io><nvda@nvda.groups.io<mailto:nvda@nvda.groups.io>> On Behalf Of Arianna
Sepulveda
Sent: Sunday, March 11, 2018 6:44 PM
To: nvda@nvda.groups.io<mailto: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

Question from a long time Window Eyes user. At present Windows can’t update to the latest version as it thinks there is an incompatible program installed on my computer. That program is Window Eyes. I have correctly uninstalled WE and have done multiple searches to try and find remnants. My best guess is that it is lurking still in my registry. I am not foolish enough to try editing my registry, and Leary of using any of the “registry cleaners.” Any chance that this addon would find such a lingering registry entry. When I read “other programs” I assume other access software. I am not having the issues described in this thread, but. . . .

Any advice out there?

Rick

 

Dr. Rick Ely

TVI, Vision Consultant

451 Rocky Hill Road

Florence, MA 01062

&413()  727-3038

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gene New Zealand
Sent: Monday, March 12, 2018 3:53 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Registry fixing tool in nvda

 

Hi

 

Just had a quick look is this a snapshot to fix the unknown and pane problems that some people have had in the past? if it is and it works it would be far easier than the other way which i have been posting from time to time.

 

Gene nz

 

 

On 3/13/2018 12:10 AM, Brian's Mail list account via Groups.Io wrote:

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@...>
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@...>
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@...>
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@...>
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@...>
Date: Mon 12 Mar 2018 17:44:10 +1000
Add copyright header
Raw diff
commit 877362bde2e108fae69c067cb26bdd797843caa8
Author: Michael Curran <mick@...>
Date: Mon 12 Mar 2018 17:48:11 +1000
Add a module docstring
Raw diff
commit e550d32924b55272e05254eada58c9bb04fd1ae7
Author: Michael Curran <mick@...>
Date: Mon 12 Mar 2018 17:55:53 +1000
Incubates #8075
Raw diff

------------------------------------------------------------------------------

Brian

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

 

--

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.

Hi

Just had a quick look is this a snapshot to fix the unknown and pane problems that some people have had in the past? if it is and it works it would be far easier than the other way which i have been posting from time to time.

Gene nz

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@...>
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@...>
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@...>
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@...>
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@...>
Date: Mon 12 Mar 2018 17:44:10 +1000
Add copyright header
Raw diff
commit 877362bde2e108fae69c067cb26bdd797843caa8
Author: Michael Curran <mick@...>
Date: Mon 12 Mar 2018 17:48:11 +1000
Add a module docstring
Raw diff
commit e550d32924b55272e05254eada58c9bb04fd1ae7
Author: Michael Curran <mick@...>
Date: Mon 12 Mar 2018 17:55:53 +1000
Incubates #8075
Raw diff

------------------------------------------------------------------------------

Brian

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

Hi

Just had a quick look is this a snapshot to fix the unknown and pane problems that some people have had in the past? if it is and it works it would be far easier than the other way which i have been posting from time to time.

Gene nz

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@...>
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@...>
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@...>
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@...>
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@...>
Date: Mon 12 Mar 2018 17:44:10 +1000
Add copyright header
Raw diff
commit 877362bde2e108fae69c067cb26bdd797843caa8
Author: Michael Curran <mick@...>
Date: Mon 12 Mar 2018 17:48:11 +1000
Add a module docstring
Raw diff
commit e550d32924b55272e05254eada58c9bb04fd1ae7
Author: Michael Curran <mick@...>
Date: Mon 12 Mar 2018 17:55:53 +1000
Incubates #8075
Raw diff

------------------------------------------------------------------------------

Brian

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

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@...>
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@...>
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@...>
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@...>
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@...>
Date: Mon 12 Mar 2018 17:44:10 +1000
Add copyright header
Raw diff
commit 877362bde2e108fae69c067cb26bdd797843caa8
Author: Michael Curran <mick@...>
Date: Mon 12 Mar 2018 17:48:11 +1000
Add a module docstring
Raw diff
commit e550d32924b55272e05254eada58c9bb04fd1ae7
Author: Michael Curran <mick@...>
Date: Mon 12 Mar 2018 17:55:53 +1000
Incubates #8075
Raw diff

------------------------------------------------------------------------------

Brian

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

Hi,
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@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Iván Novegil via Groups.Io" <ivan.novegil@...>
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.

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@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Iván Novegil via Groups.Io" <ivan.novegil@...>
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.

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.

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!

I just tried thunderbird and the same problem occurred so I'm staying with outlook.
*From:* nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] *On Behalf Of *Bobby Vinton
*Sent:* Monday, March 12, 2018 8:20 AM
*To:* nvda@nvda.groups.io
*Subject:* Re: [nvda] problems with the mail app in nvda
Well if you try the mail app for with nvda it works very well butt when you close the mail app after reading a message you always have to restart nvda.
Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
*From: *Rosemarie Chavarria <mailto:knitqueen2007@gmail.com>
*Sent: *Monday, March 12, 2018 11:11 AM
*To: *nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
*Subject: *Re: [nvda] problems with the mail app in nvda
I haven't tried the mail app with the latest version of NVDA.
On 3/12/2018 8:09 AM, Bobby Vinton wrote:
Hay when I am using the mail app with nvda nvda crashes every time I
close the mail app after reading a message.  This just started last
week when I updated to nvda 2018.1.  I was wondering if any else has
this problem?
Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for
Windows 10

Well if you try the mail app for with nvda it works very well butt when you close the mail app after reading a message you always have to restart nvda.

Sent from Mail for Windows 10

I haven't tried the mail app with the latest version of NVDA.

Hay when I am using the mail app with nvda nvda crashes every time I close the mail app after reading a message.  This just started last week when I updated to nvda 2018.1.  I was wondering if any else has this problem?

 

Sent from Mail for Windows 10

 

I haven't tried the mail app with the latest version of NVDA.

Hay when I am using the mail app with nvda nvda crashes every time I close the mail app after reading a message.  This just started last week when I updated to nvda 2018.1.  I was wondering if any else has this problem?

 

Sent from Mail for Windows 10

 

Actually the original Espeak did a fine job. Too much tweaking recently has broken things that were good compromises before.
I certainly cannot stand Eloquence, I'd rather listen to a voice based on George W Bush than that!
However, as I say synths are intensely personal things.
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 7:15 PM
Subject: Re: [nvda] espeak and pronunciation of some words


Dear all,


I think eSpeak has to be adjusted from scratch. It is very hard to get to a point where every word is being pronounced correctly. This is a matter of accent and phonemes which are very limited in eSpeak development.

If we begin to assess every word in eSpeak, we will find thousants and thousants of words which are mispronounced. Don't forget eSpeak supports more than 50 languages. So, developing this synthesizer word by word is not a long term solution.

So, in my view, if another speech synthesizer becomes free (i.e. eloquence or vocalizer), every user will change to it unless eSpeak is being vastly improved from scratch.


Best
Adriani

-----Ursprüngliche Nachricht-----
Von: nvda@nvda.groups.io <nvda@nvda.groups.io> Im Auftrag von Dejan
Ristic
Gesendet: Sonntag, 11. März 2018 20:01
An: nvda@nvda.groups.io
Betreff: 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?




.

Hay when I am using the mail app with nvda nvda crashes every time I close the mail app after reading a message.  This just started last week when I updated to nvda 2018.1.  I was wondering if any else has this problem?

 

Sent from Mail for Windows 10

 

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@...
"chilah phanim" Make G-d smile!