Date   
Re: Question about Excel

Christopher-Mark Gilland <clgilland07@...>
 


I can't tell you how many times I've used these commands while in the ribbon. It really does speed up your workflow!
---
Christopher Gilland
Co-founder of Genuine Safe Haven Ministries
 

----- Original Message -----
From: Gene
Sent: Monday, December 04, 2017 9:36 AM
Subject: Re: [nvda] Question about Excel

Not if you know how to use the control right arrow and control left arrow commands.  They don't move through every item.  they move to each category.  If you are in Windows Live Mail, for example, you can move to the home ribbon with alt h.  then you can use control right arrow to get to a category, such as respond, where you can tab through items in the category and continue tabbing if you wish.  but if a ribbon has seven categories and there are seven or eight items in each category, you can control right arrow to the category that sounds logical to find the item.  If you want to reply to an e-mail, respond is the logical category.  If you land on a category such as respond, either by tabbing until you get there or by control right or left arrow, you will be in the category and on the first item.  You will hear the name of the category, respond, for example, and, if you wait for everything to be read, you will hear that you are on reply. 
 
Gene
----- Original Message -----
Sent: Monday, December 04, 2017 8:00 AM
Subject: Re: [nvda] Question about Excel

That‘s right. But by using object nav you can navigate much faster to functions where you usually press 20 times tab. Apart from the productivity aspect it gives you the possibility to easily explore and visualize the menu structure. Ofcourse you can combine object navigation with usual navigation to reach functions even faster.
Don‘t rely only on one navigation mode. There are always shorter ways from a to b.


Best
Adriani


Von meinem iPhone gesendet

Am 04.12.2017 um 14:23 schrieb Gene <gsasner@...>:

You don't have to use object navigation in ribbons.  Ribbons are, in essence, menus that you tab through.  I say in essence because that is an oversimplification but that's the essence of what ribbons are.  they are fully accessible from the keyboard.  If a ribbon has menus in it, you will hear things as you tab like button and if you let text read and not tab to the next item before reading is finished, you will hear if the button opens a submenu.  use space bar or enter on the button and a menu will open.  In menus, in a menu program, if you up and down arrow in a menu, if you let items read submenu will be announced if you move to one.  The same thing will happen in a ribbon.  any menu you tab to in a ribbon is announced as a submenu.  Why?  Maybe its because ribbons are, in essence, as I said, menus you tab through.
 
Gene
----- Original Message -----
Gene
----- Original Message -----

Sent: Monday, December 04, 2017 5:48 AM
Subject: Re: [nvda] Question about Excel

Press alt, then one time tab and then start exploring the menu groups by object navigation. You will see all cathegories of the ribbon start.

Best
Adriani

Von meinem iPhone gesendet

Am 04.12.2017 um 12:41 schrieb Christopher-Mark Gilland <clgilland07@...>:

Alt H is the home tab, however, where does O take me? I like knowing the hierarchy of where in the ribbon I am going. This way I better understand the workflow.

nonetheless, thank you profusely for your help!

Chris.


Sent from my iPhone

On Dec 4, 2017, at 06:32, softwarethatworks@... wrote:

Hello Chris:

 

To insert a new worksheet, press Shift+F11. You can also press Alt+H, I, S.

 

To rename a sheet, press Alt+H, O, R.

 

Hope this helps.

 

Rick

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Christopher-Mark Gilland
Sent: Monday, December 4, 2017 6:21 AM
To: nvda@nvda.groups.io
Subject: [nvda] Question about Excel

 

I have been asked to prepare an Excel document which will contain several worksheets within the one workbook.

 

I have tried and tried and tried, and cannot find a way to do the following tasks, and hope someone can give me the steps.

 

1. How do I create a new worksheet within a workbook?

 

2. I know about ctrl+tabbing to move between worksheets, but how do I focus myself on the worksheet tabs, so I can right click one of them and select the rename option?

 

Yes, I've looked in the ribbon, but don't see anything which appears obvious for either of these questions.

 

Chris.

Re: Question about Excel

Christopher-Mark Gilland <clgilland07@...>
 


You might have not been aware of this, but when in your lower ribbon on a particular tab, you don't need to press your arrows 20 gazillian times as you said. You can move group by group on the lower ribbon with ctrl+left and CTRL+right arrow.
---
Christopher Gilland
Co-founder of Genuine Safe Haven Ministries
 

----- Original Message -----
Sent: Monday, December 04, 2017 9:00 AM
Subject: Re: [nvda] Question about Excel

That‘s right. But by using object nav you can navigate much faster to functions where you usually press 20 times tab. Apart from the productivity aspect it gives you the possibility to easily explore and visualize the menu structure. Ofcourse you can combine object navigation with usual navigation to reach functions even faster.
Don‘t rely only on one navigation mode. There are always shorter ways from a to b.


Best
Adriani


Von meinem iPhone gesendet

Am 04.12.2017 um 14:23 schrieb Gene <gsasner@...>:

You don't have to use object navigation in ribbons.  Ribbons are, in essence, menus that you tab through.  I say in essence because that is an oversimplification but that's the essence of what ribbons are.  they are fully accessible from the keyboard.  If a ribbon has menus in it, you will hear things as you tab like button and if you let text read and not tab to the next item before reading is finished, you will hear if the button opens a submenu.  use space bar or enter on the button and a menu will open.  In menus, in a menu program, if you up and down arrow in a menu, if you let items read submenu will be announced if you move to one.  The same thing will happen in a ribbon.  any menu you tab to in a ribbon is announced as a submenu.  Why?  Maybe its because ribbons are, in essence, as I said, menus you tab through.
 
Gene
----- Original Message -----
Gene
----- Original Message -----

Sent: Monday, December 04, 2017 5:48 AM
Subject: Re: [nvda] Question about Excel

Press alt, then one time tab and then start exploring the menu groups by object navigation. You will see all cathegories of the ribbon start.

Best
Adriani

Von meinem iPhone gesendet

Am 04.12.2017 um 12:41 schrieb Christopher-Mark Gilland <clgilland07@...>:

Alt H is the home tab, however, where does O take me? I like knowing the hierarchy of where in the ribbon I am going. This way I better understand the workflow.

nonetheless, thank you profusely for your help!

Chris.


Sent from my iPhone

On Dec 4, 2017, at 06:32, softwarethatworks@... wrote:

Hello Chris:

To insert a new worksheet, press Shift+F11. You can also press Alt+H, I, S.

To rename a sheet, press Alt+H, O, R.

Hope this helps.

Rick

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Christopher-Mark Gilland
Sent: Monday, December 4, 2017 6:21 AM
To: nvda@nvda.groups.io
Subject: [nvda] Question about Excel

I have been asked to prepare an Excel document which will contain several worksheets within the one workbook.

I have tried and tried and tried, and cannot find a way to do the following tasks, and hope someone can give me the steps.

1. How do I create a new worksheet within a workbook?

2. I know about ctrl+tabbing to move between worksheets, but how do I focus myself on the worksheet tabs, so I can right click one of them and select the rename option?

Yes, I've looked in the ribbon, but don't see anything which appears obvious for either of these questions.

Chris.

Re: nvda 2017.3 and opening multiple applications

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

I think a little more about the hardware spec might be informative here. When you say it hangs. Does it hang or is it just very slow?
If you can tell us what applications cause this that too would be a help. It is not uncommon as has been mentioned already, for power saving to be responsible for slow downs, but usually its things like zooming up and down explorer file lists and the like that tend to get slow.
I find that not only should you select always on on any machine, but also that you may need to look at power management and see if the processor is being kept at around 10 percent of its real speed during access by nvda. Its not uncommon for Windows not to spot one of its cores is maxing out. I presume this is a limitation of Windows, but you can fix it by setting the idling speed up considerably. However all of this will use more battery, so if you run on battery a lot you might need to play around here to get an acceptable result.
another thing to bear in mind is that if your machine came from a bulk store or warehouse seller its more than likely packed with software that runs at start up and is just there as a trial and is probably best uninstalled as soon as possible. Beware though. Doing this with an Office product has caused issues with screenreaders in the past.
Also, it might be worth knowing what anti virus or malware solution is on the system. I think generally we tend to say, remove all of the third party stuff avg, avast Norton etc, and stick to Windows defender and maybe a third party run manually program like malwarebytes.

So let folk here know and in the meantime learn about Narrator as if things freeze in nvda it may well be that Narrator which is built in can shed some light on what is going on.
One last thing, do you use a Braille display?
OK lots to go on with there, but certainly the majority of people have not had the issue you report if the machine is at all capable of running windows 10.
Brian

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

----- Original Message -----
From: "Marisane Moruthanyana" <marisanem@...>
To: <nvda@nvda.groups.io>
Sent: Tuesday, December 05, 2017 6:54 AM
Subject: [nvda] nvda 2017.3 and opening multiple applications


Morning guys

I am Marisane from SA.

I use nvda as my screen reader on my win10 laptop.

I have just bought the laptop.

It came with win10.

I, before, used jaws without this problem.

I cannot open more than one application without nvda freezing.

It freezes and continuously goes unresponsive as well as even decides
to sometimes stop talking.

It is frustrating me as it is now my only screen reader to access
applications in win10.

Your assistance in this regard is appreciated in advance.


May I also ask this question?

How does one know that one's laptop has windows10 fall creators?

Please help.

Regards
Marisane
On 12/5/17, Rayn Darren <rayndarren@...> wrote:
Evening everyone,

I joined two groups today and cannot for the life of me find how to post to
them. I don't know if this is an NVDA things or and I'm missing the obvious
thing. Any help would be greatly appreciated.

Thanks,
Rayn


Re: Some misstakes in new rc NVDA version

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

What do I do to subscribe by sending an email, by the way?
I don't really want to mess around on the web for this.
brian

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

----- Original Message -----
From: "Hareth" <hareth4m@...>
To: <nvda@nvda.groups.io>
Sent: Tuesday, December 05, 2017 7:19 AM
Subject: Re: [nvda] Some misstakes in new rc NVDA version


The developer created a mailing list for that, here is the link:
https://groups.io/g/espeak-ng

On 12/5/17, Brian's Mail list account via Groups.Io
<bglists=blueyonder.co.uk@groups.io> wrote:
It would also be good to see a very clear message somewhere permanent about

somewhere we can interact with the current Espeak team and shall we say, not

be sort of ignored as noise.
Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Quentin Christensen" <quentin@...>
To: <nvda@nvda.groups.io>
Sent: Monday, December 04, 2017 9:33 PM
Subject: Re: [nvda] Some misstakes in new rc NVDA version


We changed from using eSpeak NG 1.49.1 in 2017.3 to using 1.49.2, but for
those not using the Next or Master snaps, the RC builds (or the final
2017.4 when it comes out) are likely the first time they've tried it.
So,
as Brian guessed, it's likely that the issues here are not specific to
this
RC as such, but to the change in eSpeak version, since the RCs are a bit
more widely distributed. It would be good to get confirmation from Marco
though.

Regards

Quentin.

On Tue, Dec 5, 2017 at 1:57 AM, Brian's Mail list account via Groups.Io <
bglists=blueyonder.co.uk@groups.io> wrote:

I got the impressing it was RCs in this series actually.
I have certainly noticed some strangenesses in Espeak on recent
snapshots
since the last two updates of espeak NG, none for the better
particularly
in English hence my work around mentioned in my reply.

I guess the most noticable is the way it says the word for in some
circumstances, making it into fur. Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Antony Stone" <
antony.stone@...>
To: <nvda@nvda.groups.io>
Sent: Monday, December 04, 2017 2:49 PM
Subject: Re: [nvda] Some misstakes in new rc NVDA version


Your subject line refers to the new RC version.

Is this problem something new in the latest RC version and did not
exist
in
earlier (RC or otherwise) versions, or does the same problem also exist

in
older (especially standard release) versions of NVDA?


Antony.

On Monday 04 December 2017 at 11:43:33, Marco Oros wrote:

Hi!

At the first, where can I inform about this thing of NVDA misstakes
of,
for example Espeak NG?

Because I have noticed, that new Mandarin Chinese is badly pronounced
in
NVDA in that way, that syllable and some kind of number. Maybe, this
is
problem of Espeak NG, but I am not shure.

Nextly, arabic letter meem is pronounced in Espeak, like meetar, but I
think, that It is incorrect.

Where can I issued those things?

Thank You.

Marco Oros
--
"If I've told you once, I've told you a million times - stop
exaggerating!"

Please reply to the
list;
please *don't*
CC
me.






--
Quentin Christensen
Training and Support Manager

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

www.nvaccess.org
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess



Re: Some misstakes in new rc NVDA version

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

I'm not disputing that they did, but I bet most don't know it exists.
Brian

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

----- Original Message -----
From: "Hareth" <hareth4m@...>
To: <nvda@nvda.groups.io>
Sent: Tuesday, December 05, 2017 7:19 AM
Subject: Re: [nvda] Some misstakes in new rc NVDA version


The developer created a mailing list for that, here is the link:
https://groups.io/g/espeak-ng

On 12/5/17, Brian's Mail list account via Groups.Io
<bglists=blueyonder.co.uk@groups.io> wrote:
It would also be good to see a very clear message somewhere permanent about

somewhere we can interact with the current Espeak team and shall we say, not

be sort of ignored as noise.
Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Quentin Christensen" <quentin@...>
To: <nvda@nvda.groups.io>
Sent: Monday, December 04, 2017 9:33 PM
Subject: Re: [nvda] Some misstakes in new rc NVDA version


We changed from using eSpeak NG 1.49.1 in 2017.3 to using 1.49.2, but for
those not using the Next or Master snaps, the RC builds (or the final
2017.4 when it comes out) are likely the first time they've tried it.
So,
as Brian guessed, it's likely that the issues here are not specific to
this
RC as such, but to the change in eSpeak version, since the RCs are a bit
more widely distributed. It would be good to get confirmation from Marco
though.

Regards

Quentin.

On Tue, Dec 5, 2017 at 1:57 AM, Brian's Mail list account via Groups.Io <
bglists=blueyonder.co.uk@groups.io> wrote:

I got the impressing it was RCs in this series actually.
I have certainly noticed some strangenesses in Espeak on recent
snapshots
since the last two updates of espeak NG, none for the better
particularly
in English hence my work around mentioned in my reply.

I guess the most noticable is the way it says the word for in some
circumstances, making it into fur. Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Antony Stone" <
antony.stone@...>
To: <nvda@nvda.groups.io>
Sent: Monday, December 04, 2017 2:49 PM
Subject: Re: [nvda] Some misstakes in new rc NVDA version


Your subject line refers to the new RC version.

Is this problem something new in the latest RC version and did not
exist
in
earlier (RC or otherwise) versions, or does the same problem also exist

in
older (especially standard release) versions of NVDA?


Antony.

On Monday 04 December 2017 at 11:43:33, Marco Oros wrote:

Hi!

At the first, where can I inform about this thing of NVDA misstakes
of,
for example Espeak NG?

Because I have noticed, that new Mandarin Chinese is badly pronounced
in
NVDA in that way, that syllable and some kind of number. Maybe, this
is
problem of Espeak NG, but I am not shure.

Nextly, arabic letter meem is pronounced in Espeak, like meetar, but I
think, that It is incorrect.

Where can I issued those things?

Thank You.

Marco Oros
--
"If I've told you once, I've told you a million times - stop
exaggerating!"

Please reply to the
list;
please *don't*
CC
me.






--
Quentin Christensen
Training and Support Manager

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

www.nvaccess.org
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess



Re: Posting to Google groups

Rayn Darren
 

Hi,

 

Thanks you so much! It was driving me crazy!

 

Thanks,

Rayn

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of iván Novegil
Sent: Monday, December 4, 2017 11:50 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Posting to Google groups

 

Hello.

 

Go to the group's main page and under the first two-level heading press "new topic" button. You can also post by mail to the groups that accept it by writing to groupid@... (groupid is the group's short name, obtainable from the URL groups.google.com/group/groupid).

 

Regards.

Iván Novegil Cancelas
Editor
ivan.novegil@...
 
Comunidad hispanohablante de NVDA | Proyecto NVDA.es
- www.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.***

O 05/12/2017 á(s) 5:07, Rayn Darren escribiu:

Evening everyone,

 

I joined two groups today and cannot for the life of me find how to post to them. I don’t know if this is an NVDA things or and I’m missing the obvious thing. Any help would be greatly appreciated.

 

Thanks,

Rayn

 

Virus-free. www.avast.com

 

Re: Posting to Google groups

Iván Novegil
 

Hello.


Go to the group's main page and under the first two-level heading press "new topic" button. You can also post by mail to the groups that accept it by writing to groupid@... (groupid is the group's short name, obtainable from the URL groups.google.com/group/groupid).


Regards.

Iván Novegil Cancelas
Editor
ivan.novegil@...

Comunidad hispanohablante de NVDA | Proyecto NVDA.es
- www.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.***
O 05/12/2017 á(s) 5:07, Rayn Darren escribiu:

Evening everyone,

 

I joined two groups today and cannot for the life of me find how to post to them. I don’t know if this is an NVDA things or and I’m missing the obvious thing. Any help would be greatly appreciated.

 

Thanks,

Rayn


Virus-free. www.avast.com

Re: nvda 2017.3 and opening multiple applications

Quentin Christensen
 

Hi Marisane,

Firstly, welcome to the NVDA community and to this group in particular.

The problem you are describing shouldn't be normal.  One thing to check is whether your laptop is using any power control settings.  The always on one seems to be the best.  Any of the others often throttle the CPU back, ignoring NVDA and that can cause problems.

For your question about which version of Windows 10 you are using, press the windows key, and at the start menu, type "winver" (without the quotes" and press ENTER.  The dialog box will tell you which build of Windows you are on.

The Fall Creators Update is 1709.  Here's a wikipedia article with the different Windows 10 versions: https://en.wikipedia.org/wiki/Windows_10_version_history

Kind regards

Quentin.

On Tue, Dec 5, 2017 at 5:54 PM, Marisane Moruthanyana <marisanem@...> wrote:
Morning guys

I am Marisane from SA.

I use nvda as my screen reader on my win10 laptop.

I have just bought the laptop.

It came with win10.

I, before, used jaws without this problem.

I cannot open more than one application without nvda freezing.

It freezes and continuously goes unresponsive as well as even decides
to sometimes stop talking.

It is frustrating me as it is now my only screen reader to access
applications in win10.

Your assistance in this regard is appreciated in advance.


May I also ask this question?

How does one know that one's laptop has windows10 fall creators?

Please help.

Regards
Marisane
On 12/5/17, Rayn Darren <rayndarren@...> wrote:
> Evening everyone,
>
> I joined two groups today and cannot for the life of me find how to post to
> them. I don't know if this is an NVDA things or and I'm missing the obvious
> thing. Any help would be greatly appreciated.
>
> Thanks,
> Rayn
>
>
>






--
Quentin Christensen
Training and Support Manager

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

Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 

Re: Some misstakes in new rc NVDA version

Hareth
 

The developer created a mailing list for that, here is the link:
https://groups.io/g/espeak-ng

On 12/5/17, Brian's Mail list account via Groups.Io
<bglists=blueyonder.co.uk@groups.io> wrote:
It would also be good to see a very clear message somewhere permanent about

somewhere we can interact with the current Espeak team and shall we say, not

be sort of ignored as noise.
Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Quentin Christensen" <quentin@...>
To: <nvda@nvda.groups.io>
Sent: Monday, December 04, 2017 9:33 PM
Subject: Re: [nvda] Some misstakes in new rc NVDA version


We changed from using eSpeak NG 1.49.1 in 2017.3 to using 1.49.2, but for
those not using the Next or Master snaps, the RC builds (or the final
2017.4 when it comes out) are likely the first time they've tried it.
So,
as Brian guessed, it's likely that the issues here are not specific to
this
RC as such, but to the change in eSpeak version, since the RCs are a bit
more widely distributed. It would be good to get confirmation from Marco
though.

Regards

Quentin.

On Tue, Dec 5, 2017 at 1:57 AM, Brian's Mail list account via Groups.Io <
bglists=blueyonder.co.uk@groups.io> wrote:

I got the impressing it was RCs in this series actually.
I have certainly noticed some strangenesses in Espeak on recent
snapshots
since the last two updates of espeak NG, none for the better
particularly
in English hence my work around mentioned in my reply.

I guess the most noticable is the way it says the word for in some
circumstances, making it into fur. Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Antony Stone" <
antony.stone@...>
To: <nvda@nvda.groups.io>
Sent: Monday, December 04, 2017 2:49 PM
Subject: Re: [nvda] Some misstakes in new rc NVDA version


Your subject line refers to the new RC version.

Is this problem something new in the latest RC version and did not
exist
in
earlier (RC or otherwise) versions, or does the same problem also exist

in
older (especially standard release) versions of NVDA?


Antony.

On Monday 04 December 2017 at 11:43:33, Marco Oros wrote:

Hi!

At the first, where can I inform about this thing of NVDA misstakes
of,
for example Espeak NG?

Because I have noticed, that new Mandarin Chinese is badly pronounced
in
NVDA in that way, that syllable and some kind of number. Maybe, this
is
problem of Espeak NG, but I am not shure.

Nextly, arabic letter meem is pronounced in Espeak, like meetar, but I
think, that It is incorrect.

Where can I issued those things?

Thank You.

Marco Oros
--
"If I've told you once, I've told you a million times - stop
exaggerating!"

Please reply to the
list;
please *don't*
CC
me.






--
Quentin Christensen
Training and Support Manager

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

www.nvaccess.org
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess



Re: Some misstakes in new rc NVDA version

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

No me neither. I have a back of my memory feeling something like that did exist, but I'm not sure it was called that.

I don't think there is any need to throw away Espeak as a general workhorse it merely needs more people to actually listen to it and for the devs not to tinker with what worked and instead try to fix what does not, like US English, Some of the Chinese language rules etc, and possibly not try to get even more languages in till the ones it already has are good.
its awfully tempting for coders to tinker and put in new ideas, but its not much good doing this if you compromise what you already have.
Brian

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

----- Original Message -----
From: "John Isige" <gwynn@...>
To: <nvda@nvda.groups.io>
Sent: Tuesday, December 05, 2017 4:51 AM
Subject: Re: [nvda] Some misstakes in new rc NVDA version


Is that actually a thing? I mean is there literally a speech synthesizer called X Synth? Because googling gives me nothing.


On 12/4/2017 22:11, Shaun Everiss wrote:
No I don't have a link.

Not for that anyway.




On 5/12/2017 4:45 p.m., Quentin Christensen wrote:
Hi Sean,

Broadly speaking, we update the eSpeak for the same reason most things get
updated - because the new version may fix errors (such as the ones noted at
the start of this thread) or include new languages. Of course, as noted by
this thread, sometimes an update causes other things to break, and
obviously that is unintentional, and often not known until we get reports
like this.

Re X Synth, do you have a link please?

Regards

Quentin.

On Tue, Dec 5, 2017 at 2:00 PM, Shaun Everiss <@smeveriss> wrote:

Well to be honest why do we bother to always update stable to the latest
espeak ng.

In fact why do we use espeak ng at all, we should find a stable version of
x synth and use it.

The only reason I'd even update the synth is if it became a problem or
security risk





On 5/12/2017 10:33 a.m., Quentin Christensen wrote:

We changed from using eSpeak NG 1.49.1 in 2017.3 to using 1.49.2, but for
those not using the Next or Master snaps, the RC builds (or the final
2017.4 when it comes out) are likely the first time they've tried it. So,
as Brian guessed, it's likely that the issues here are not specific to
this
RC as such, but to the change in eSpeak version, since the RCs are a bit
more widely distributed. It would be good to get confirmation from Marco
though.

Regards

Quentin.

On Tue, Dec 5, 2017 at 1:57 AM, Brian's Mail list account via Groups.Io <
bglists=blueyonder.co.uk@groups.io> wrote:

I got the impressing it was RCs in this series actually.
I have certainly noticed some strangenesses in Espeak on recent snapshots
since the last two updates of espeak NG, none for the better particularly
in English hence my work around mentioned in my reply.

I guess the most noticable is the way it says the word for in some
circumstances, making it into fur. Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Antony Stone" <
antony.stone@...>
To: <nvda@nvda.groups.io>
Sent: Monday, December 04, 2017 2:49 PM
Subject: Re: [nvda] Some misstakes in new rc NVDA version


Your subject line refers to the new RC version.

Is this problem something new in the latest RC version and did not exist
in
earlier (RC or otherwise) versions, or does the same problem also exist
in
older (especially standard release) versions of NVDA?


Antony.

On Monday 04 December 2017 at 11:43:33, Marco Oros wrote:

Hi!

At the first, where can I inform about this thing of NVDA misstakes of,
for example Espeak NG?

Because I have noticed, that new Mandarin Chinese is badly pronounced
in
NVDA in that way, that syllable and some kind of number. Maybe, this is
problem of Espeak NG, but I am not shure.

Nextly, arabic letter meem is pronounced in Espeak, like meetar, but I
think, that It is incorrect.

Where can I issued those things?

Thank You.

Marco Oros

--
"If I've told you once, I've told you a million times - stop
exaggerating!"

Please reply to the
list;
please *don't*
CC
me.







Re: Some misstakes in new rc NVDA version

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

Having said that, Espeak for some languages used to be good and very stable. I'd not want to see it go, but on the other hand I too would wish to not keep on updating it unless there was a real pressing reason for it, say some nvda function it allows.
Also and not wanting to be too annoying, and certainly with a good deal of tongue in cheek here, I'd like to enquire quite who is actually listening to #English for GB on this. its sounding more like a lazy English speaker than it used to and it seems not to be able to say words it could manage before. The problem is there seems to be nobody posting here saying we have just done x in this language or y in that can some native speakers test it.

As I Say the option to backtrack to older versions of the synth should be a priority given the number of gotchas we have encountered with the latest build actually failing and just stopping working with no fall back or log indication of the problem in nvda. A lot of people use Espeak particularly people on the Indian Sub continent,and in the UK. It has a very big number of languages, but it is still an issue for US English people.
Brian

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

----- Original Message -----
From: "Shaun Everiss" <@smeveriss>
To: <nvda@nvda.groups.io>
Sent: Tuesday, December 05, 2017 3:00 AM
Subject: Re: [nvda] Some misstakes in new rc NVDA version


Well to be honest why do we bother to always update stable to the latest espeak ng.

In fact why do we use espeak ng at all, we should find a stable version of x synth and use it.

The only reason I'd even update the synth is if it became a problem or security risk




On 5/12/2017 10:33 a.m., Quentin Christensen wrote:
We changed from using eSpeak NG 1.49.1 in 2017.3 to using 1.49.2, but for
those not using the Next or Master snaps, the RC builds (or the final
2017.4 when it comes out) are likely the first time they've tried it. So,
as Brian guessed, it's likely that the issues here are not specific to this
RC as such, but to the change in eSpeak version, since the RCs are a bit
more widely distributed. It would be good to get confirmation from Marco
though.

Regards

Quentin.

On Tue, Dec 5, 2017 at 1:57 AM, Brian's Mail list account via Groups.Io <
bglists=blueyonder.co.uk@groups.io> wrote:

I got the impressing it was RCs in this series actually.
I have certainly noticed some strangenesses in Espeak on recent snapshots
since the last two updates of espeak NG, none for the better particularly
in English hence my work around mentioned in my reply.

I guess the most noticable is the way it says the word for in some
circumstances, making it into fur. Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Antony Stone" <
antony.stone@...>
To: <nvda@nvda.groups.io>
Sent: Monday, December 04, 2017 2:49 PM
Subject: Re: [nvda] Some misstakes in new rc NVDA version


Your subject line refers to the new RC version.
Is this problem something new in the latest RC version and did not exist
in
earlier (RC or otherwise) versions, or does the same problem also exist in
older (especially standard release) versions of NVDA?


Antony.

On Monday 04 December 2017 at 11:43:33, Marco Oros wrote:

Hi!
At the first, where can I inform about this thing of NVDA misstakes of,
for example Espeak NG?

Because I have noticed, that new Mandarin Chinese is badly pronounced in
NVDA in that way, that syllable and some kind of number. Maybe, this is
problem of Espeak NG, but I am not shure.

Nextly, arabic letter meem is pronounced in Espeak, like meetar, but I
think, that It is incorrect.

Where can I issued those things?

Thank You.

Marco Oros
--
"If I've told you once, I've told you a million times - stop
exaggerating!"

Please reply to the
list;
please *don't* CC
me.





Re: Some misstakes in new rc NVDA version

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

It would also be good to see a very clear message somewhere permanent about somewhere we can interact with the current Espeak team and shall we say, not be sort of ignored as noise.
Brian

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

----- Original Message -----
From: "Quentin Christensen" <quentin@...>
To: <nvda@nvda.groups.io>
Sent: Monday, December 04, 2017 9:33 PM
Subject: Re: [nvda] Some misstakes in new rc NVDA version


We changed from using eSpeak NG 1.49.1 in 2017.3 to using 1.49.2, but for
those not using the Next or Master snaps, the RC builds (or the final
2017.4 when it comes out) are likely the first time they've tried it. So,
as Brian guessed, it's likely that the issues here are not specific to this
RC as such, but to the change in eSpeak version, since the RCs are a bit
more widely distributed. It would be good to get confirmation from Marco
though.

Regards

Quentin.

On Tue, Dec 5, 2017 at 1:57 AM, Brian's Mail list account via Groups.Io <
bglists=blueyonder.co.uk@groups.io> wrote:

I got the impressing it was RCs in this series actually.
I have certainly noticed some strangenesses in Espeak on recent snapshots
since the last two updates of espeak NG, none for the better particularly
in English hence my work around mentioned in my reply.

I guess the most noticable is the way it says the word for in some
circumstances, making it into fur. Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Antony Stone" <
antony.stone@...>
To: <nvda@nvda.groups.io>
Sent: Monday, December 04, 2017 2:49 PM
Subject: Re: [nvda] Some misstakes in new rc NVDA version


Your subject line refers to the new RC version.

Is this problem something new in the latest RC version and did not exist
in
earlier (RC or otherwise) versions, or does the same problem also exist in
older (especially standard release) versions of NVDA?


Antony.

On Monday 04 December 2017 at 11:43:33, Marco Oros wrote:

Hi!

At the first, where can I inform about this thing of NVDA misstakes of,
for example Espeak NG?

Because I have noticed, that new Mandarin Chinese is badly pronounced in
NVDA in that way, that syllable and some kind of number. Maybe, this is
problem of Espeak NG, but I am not shure.

Nextly, arabic letter meem is pronounced in Espeak, like meetar, but I
think, that It is incorrect.

Where can I issued those things?

Thank You.

Marco Oros
--
"If I've told you once, I've told you a million times - stop
exaggerating!"

Please reply to the
list;
please *don't* CC
me.






--
Quentin Christensen
Training and Support Manager

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

www.nvaccess.org
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess

nvda 2017.3 and opening multiple applications

Marisane Moruthanyana
 

Morning guys

I am Marisane from SA.

I use nvda as my screen reader on my win10 laptop.

I have just bought the laptop.

It came with win10.

I, before, used jaws without this problem.

I cannot open more than one application without nvda freezing.

It freezes and continuously goes unresponsive as well as even decides
to sometimes stop talking.

It is frustrating me as it is now my only screen reader to access
applications in win10.

Your assistance in this regard is appreciated in advance.


May I also ask this question?

How does one know that one's laptop has windows10 fall creators?

Please help.

Regards
Marisane

On 12/5/17, Rayn Darren <rayndarren@...> wrote:
Evening everyone,

I joined two groups today and cannot for the life of me find how to post to
them. I don't know if this is an NVDA things or and I'm missing the obvious
thing. Any help would be greatly appreciated.

Thanks,
Rayn


Re: Some misstakes in new rc NVDA version

John Isige
 

Is that actually a thing? I mean is there literally a speech synthesizer called X Synth? Because googling gives me nothing.

On 12/4/2017 22:11, Shaun Everiss wrote:
No I don't have a link.

Not for that anyway.




On 5/12/2017 4:45 p.m., Quentin Christensen wrote:
Hi Sean,

Broadly speaking, we update the eSpeak for the same reason most things get
updated - because the new version may fix errors (such as the ones noted at
the start of this thread) or include new languages. Of course, as noted by
this thread, sometimes an update causes other things to break, and
obviously that is unintentional, and often not known until we get reports
like this.

Re X Synth, do you have a link please?

Regards

Quentin.

On Tue, Dec 5, 2017 at 2:00 PM, Shaun Everiss <@smeveriss> wrote:

Well to be honest why do we bother to always update stable to the latest
espeak ng.

In fact why do we use espeak ng at all, we should find a stable version of
x synth and use it.

The only reason I'd even update the synth is if it became a problem or
security risk





On 5/12/2017 10:33 a.m., Quentin Christensen wrote:

We changed from using eSpeak NG 1.49.1 in 2017.3 to using 1.49.2, but for
those not using the Next or Master snaps, the RC builds (or the final
2017.4 when it comes out) are likely the first time they've tried it. So,
as Brian guessed, it's likely that the issues here are not specific to
this
RC as such, but to the change in eSpeak version, since the RCs are a bit
more widely distributed. It would be good to get confirmation from Marco
though.

Regards

Quentin.

On Tue, Dec 5, 2017 at 1:57 AM, Brian's Mail list account via Groups.Io <
bglists=blueyonder.co.uk@groups.io> wrote:

I got the impressing it was RCs in this series actually.
I have certainly noticed some strangenesses in Espeak on recent snapshots
since the last two updates of espeak NG, none for the better particularly
in English hence my work around mentioned in my reply.

I guess the most noticable is the way it says the word for in some
circumstances, making it into fur. Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Antony Stone" <
antony.stone@...>
To: <nvda@nvda.groups.io>
Sent: Monday, December 04, 2017 2:49 PM
Subject: Re: [nvda] Some misstakes in new rc NVDA version


Your subject line refers to the new RC version.

Is this problem something new in the latest RC version and did not exist
in
earlier (RC or otherwise) versions, or does the same problem also exist
in
older (especially standard release) versions of NVDA?


Antony.

On Monday 04 December 2017 at 11:43:33, Marco Oros wrote:

Hi!

At the first, where can I inform about this thing of NVDA misstakes of,
for example Espeak NG?

Because I have noticed, that new Mandarin Chinese is badly pronounced
in
NVDA in that way, that syllable and some kind of number. Maybe, this is
problem of Espeak NG, but I am not shure.

Nextly, arabic letter meem is pronounced in Espeak, like meetar, but I
think, that It is incorrect.

Where can I issued those things?

Thank You.

Marco Oros

--
"If I've told you once, I've told you a million times - stop
exaggerating!"

Please reply to the
list;
please *don't*
CC
me.






Re: Some misstakes in new rc NVDA version

 

No I don't have a link.

Not for that anyway.

On 5/12/2017 4:45 p.m., Quentin Christensen wrote:
Hi Sean,

Broadly speaking, we update the eSpeak for the same reason most things get
updated - because the new version may fix errors (such as the ones noted at
the start of this thread) or include new languages. Of course, as noted by
this thread, sometimes an update causes other things to break, and
obviously that is unintentional, and often not known until we get reports
like this.

Re X Synth, do you have a link please?

Regards

Quentin.

On Tue, Dec 5, 2017 at 2:00 PM, Shaun Everiss <@smeveriss> wrote:

Well to be honest why do we bother to always update stable to the latest
espeak ng.

In fact why do we use espeak ng at all, we should find a stable version of
x synth and use it.

The only reason I'd even update the synth is if it became a problem or
security risk





On 5/12/2017 10:33 a.m., Quentin Christensen wrote:

We changed from using eSpeak NG 1.49.1 in 2017.3 to using 1.49.2, but for
those not using the Next or Master snaps, the RC builds (or the final
2017.4 when it comes out) are likely the first time they've tried it. So,
as Brian guessed, it's likely that the issues here are not specific to
this
RC as such, but to the change in eSpeak version, since the RCs are a bit
more widely distributed. It would be good to get confirmation from Marco
though.

Regards

Quentin.

On Tue, Dec 5, 2017 at 1:57 AM, Brian's Mail list account via Groups.Io <
bglists=blueyonder.co.uk@groups.io> wrote:

I got the impressing it was RCs in this series actually.
I have certainly noticed some strangenesses in Espeak on recent snapshots
since the last two updates of espeak NG, none for the better particularly
in English hence my work around mentioned in my reply.

I guess the most noticable is the way it says the word for in some
circumstances, making it into fur. Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Antony Stone" <
antony.stone@...>
To: <nvda@nvda.groups.io>
Sent: Monday, December 04, 2017 2:49 PM
Subject: Re: [nvda] Some misstakes in new rc NVDA version


Your subject line refers to the new RC version.

Is this problem something new in the latest RC version and did not exist
in
earlier (RC or otherwise) versions, or does the same problem also exist
in
older (especially standard release) versions of NVDA?


Antony.

On Monday 04 December 2017 at 11:43:33, Marco Oros wrote:

Hi!

At the first, where can I inform about this thing of NVDA misstakes of,
for example Espeak NG?

Because I have noticed, that new Mandarin Chinese is badly pronounced
in
NVDA in that way, that syllable and some kind of number. Maybe, this is
problem of Espeak NG, but I am not shure.

Nextly, arabic letter meem is pronounced in Espeak, like meetar, but I
think, that It is incorrect.

Where can I issued those things?

Thank You.

Marco Oros

--
"If I've told you once, I've told you a million times - stop
exaggerating!"

Please reply to the
list;
please *don't*
CC
me.





Posting to Google groups

Rayn Darren
 

Evening everyone,

 

I joined two groups today and cannot for the life of me find how to post to them. I don’t know if this is an NVDA things or and I’m missing the obvious thing. Any help would be greatly appreciated.

 

Thanks,

Rayn


Virus-free. www.avast.com

Re: Some misstakes in new rc NVDA version

Quentin Christensen
 

Hi Sean,

Broadly speaking, we update the eSpeak for the same reason most things get updated - because the new version may fix errors (such as the ones noted at the start of this thread) or include new languages.  Of course, as noted by this thread, sometimes an update causes other things to break, and obviously that is unintentional, and often not known until we get reports like this.

Re X Synth, do you have a link please?

Regards

Quentin.

On Tue, Dec 5, 2017 at 2:00 PM, Shaun Everiss <sm.everiss@...> wrote:
Well to be honest why do we bother to always update stable to the latest espeak ng.

In fact why do we use espeak ng at all, we should find a stable version of x synth and use it.

The only reason I'd even update the synth is if it became a problem or security risk





On 5/12/2017 10:33 a.m., Quentin Christensen wrote:
We changed from using eSpeak NG 1.49.1 in 2017.3 to using 1.49.2, but for
those not using the Next or Master snaps, the RC builds (or the final
2017.4 when it comes out) are likely the first time they've tried it.  So,
as Brian guessed, it's likely that the issues here are not specific to this
RC as such, but to the change in eSpeak version, since the RCs are a bit
more widely distributed.  It would be good to get confirmation from Marco
though.

Regards

Quentin.

On Tue, Dec 5, 2017 at 1:57 AM, Brian's Mail list account via Groups.Io <
bglists=blueyonder.co.uk@groups.io> wrote:

I got the impressing it was RCs in this series actually.
I have certainly noticed some strangenesses in Espeak on recent snapshots
since the last two updates of espeak NG, none for the better particularly
in English hence my work around mentioned in my reply.

I guess the most noticable is the way it says the word for in some
circumstances, making it into fur.  Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Antony Stone" <
antony.stone@....it>
To: <nvda@nvda.groups.io>
Sent: Monday, December 04, 2017 2:49 PM
Subject: Re: [nvda] Some misstakes in new rc NVDA version


Your subject line refers to the new RC version.
Is this problem something new in the latest RC version and did not exist
in
earlier (RC or otherwise) versions, or does the same problem also exist in
older (especially standard release) versions of NVDA?


Antony.

On Monday 04 December 2017 at 11:43:33, Marco Oros wrote:

Hi!
At the first, where can I inform about this thing of NVDA misstakes of,
for example Espeak NG?

Because I have noticed, that new Mandarin Chinese is badly pronounced in
NVDA in that way, that syllable and some kind of number. Maybe, this is
problem of Espeak NG, but I am not shure.

Nextly, arabic letter meem is pronounced in Espeak, like meetar, but I
think, that It is incorrect.

Where can I issued those things?

Thank You.

Marco Oros

--
"If I've told you once, I've told you a million times - stop
exaggerating!"

                                                   Please reply to the
list;
                                                         please *don't* CC
me.















--
Quentin Christensen
Training and Support Manager

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

Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 

Re: Some misstakes in new rc NVDA version

 

Well to be honest why do we bother to always update stable to the latest espeak ng.

In fact why do we use espeak ng at all, we should find a stable version of x synth and use it.

The only reason I'd even update the synth is if it became a problem or security risk

On 5/12/2017 10:33 a.m., Quentin Christensen wrote:
We changed from using eSpeak NG 1.49.1 in 2017.3 to using 1.49.2, but for
those not using the Next or Master snaps, the RC builds (or the final
2017.4 when it comes out) are likely the first time they've tried it. So,
as Brian guessed, it's likely that the issues here are not specific to this
RC as such, but to the change in eSpeak version, since the RCs are a bit
more widely distributed. It would be good to get confirmation from Marco
though.

Regards

Quentin.

On Tue, Dec 5, 2017 at 1:57 AM, Brian's Mail list account via Groups.Io <
bglists=blueyonder.co.uk@groups.io> wrote:

I got the impressing it was RCs in this series actually.
I have certainly noticed some strangenesses in Espeak on recent snapshots
since the last two updates of espeak NG, none for the better particularly
in English hence my work around mentioned in my reply.

I guess the most noticable is the way it says the word for in some
circumstances, making it into fur. Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Antony Stone" <
antony.stone@...>
To: <nvda@nvda.groups.io>
Sent: Monday, December 04, 2017 2:49 PM
Subject: Re: [nvda] Some misstakes in new rc NVDA version


Your subject line refers to the new RC version.
Is this problem something new in the latest RC version and did not exist
in
earlier (RC or otherwise) versions, or does the same problem also exist in
older (especially standard release) versions of NVDA?


Antony.

On Monday 04 December 2017 at 11:43:33, Marco Oros wrote:

Hi!
At the first, where can I inform about this thing of NVDA misstakes of,
for example Espeak NG?

Because I have noticed, that new Mandarin Chinese is badly pronounced in
NVDA in that way, that syllable and some kind of number. Maybe, this is
problem of Espeak NG, but I am not shure.

Nextly, arabic letter meem is pronounced in Espeak, like meetar, but I
think, that It is incorrect.

Where can I issued those things?

Thank You.

Marco Oros
--
"If I've told you once, I've told you a million times - stop
exaggerating!"

Please reply to the
list;
please *don't* CC
me.




Re: Will NVDA work if I Enable virtualization-based protection of code integrity

Quentin Christensen
 

Hi Pranav,

I must admit I haven't tried it.  It may operate at a deeper level than we do, in which case NVDA may be unaffected, but as I say, I haven't tried it, so if you have or do, I'd be interested in your findings.

Kind regards

Quentin.

On Tue, Dec 5, 2017 at 11:46 AM, Pranav Lal <pranav.lal@...> wrote:
Hi Brian,

I do not know. I have seen this only in Windows 10.

Pranav

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Brian's
Mail list account via Groups.Io
Sent: Friday, December 01, 2017 4:17 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Will NVDA work if I Enable virtualization-based
protection of code integrity

Is this what I might call paranoia node? :-)  I've never heard of it, is it
just in Windows 10?
 Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Pranav Lal" <pranav.lal@...>
To: <nvda@nvda.groups.io>
Sent: Friday, December 01, 2017 1:12 AM
Subject: [nvda] Will NVDA work if I Enable virtualization-based protection
of code integrity


> Hi all,
>
> Will NVDA work if I Enable virtualization-based protection of code
> integrity by following the steps at the following link?
> https://docs.microsoft.com/en-us/windows/device-security/enable-virtua
> lizati
> on-based-protection-of-code-integrity
> Pranav
>
>
>
>










--
Quentin Christensen
Training and Support Manager

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

Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 

Re: Will NVDA work if I Enable virtualization-based protection of code integrity

Pranav Lal
 

Hi Brian,

I do not know. I have seen this only in Windows 10.

Pranav

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Brian's
Mail list account via Groups.Io
Sent: Friday, December 01, 2017 4:17 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Will NVDA work if I Enable virtualization-based
protection of code integrity

Is this what I might call paranoia node? :-) I've never heard of it, is it
just in Windows 10?
Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Pranav Lal" <pranav.lal@...>
To: <nvda@nvda.groups.io>
Sent: Friday, December 01, 2017 1:12 AM
Subject: [nvda] Will NVDA work if I Enable virtualization-based protection
of code integrity


Hi all,

Will NVDA work if I Enable virtualization-based protection of code
integrity by following the steps at the following link?
https://docs.microsoft.com/en-us/windows/device-security/enable-virtua
lizati
on-based-protection-of-code-integrity
Pranav