Date   

Re: safe mod and speech?

Carlos
 

You can enable audio in Safe Mode with this registry patch,.
https://iqu.ca/1/?B02B5B467B14
However, I don't know if it works with Windows 10 and I believe it may only work with Realtek audio devices. You can also try a USB audio device which might work even without this patch. I am somewhat vague about the details because while I did experiment with this and got it to work, that was several years ago. I don't usually bother with Safe Mode. If something annoys me enough that I have to resort to extreme measures, I usually just restore the registry from a backup or my entire system from an image.

----- Original Message -----
From: "Billy Inglis" <william.inglis72@gmail.com>
To: <main@TechTalk.groups.io>
Sent: Wednesday, July 06, 2016 5:32 AM
Subject: [TechTalk] safe mod and speech?


hi guys, Is it possible to have any speech in safe mode?,
--
Billy Inglis



Re: Android browser, add blocking

Carlos
 

There does seem to be a version of Adblock Plus for Android, but I have no idea with which browsers it works. I would assume the stock browser.

----- Original Message -----
From: "David Mehler" <dave.mehler@gmail.com>
To: <main@TechTalk.groups.io>
Sent: Wednesday, July 06, 2016 4:36 AM
Subject: [TechTalk] Android browser, add blocking


Hello,
On a windows machine I use either Firefox or Chrome with the Add Block
Plus and Add Block for Youtube addons to block popup adds. On Android
I'm using Lightning, and others I know are using whichever browser
came with their phone and they just hit browser on their dock. My
question is will the add block plus addon work with lightning or the
stock browser in android?

Thanks.
Dave.


Re: Help with drop box on iPad

George Basioli <gbmagoo@...>
 

You can also access the file off line through dropboxd so you can use the file when not connected to the wyfi

 

From: main@TechTalk.groups.io [mailto:main@TechTalk.groups.io] On Behalf Of Matt
Sent: Wednesday, July 06, 2016 03:43
To: main@TechTalk.groups.io
Subject: Re: [TechTalk] Help with drop box on iPad

 

You mean delete them from drop box? You cannot move them out of drop box on the phone or tablet . you can move the file around in the drop box app. Or you can share the file or open it up in another program but you cannot just move it out of the drop box app on a phone or tablet. You can delete it.

 

 

 

From: main@TechTalk.groups.io [mailto:main@TechTalk.groups.io] On Behalf Of Patrick Ford
Sent: Wednesday, July 06, 2016 5:13 AM
To: main@TechTalk.groups.io
Subject: [TechTalk] Help with drop box on iPad

 

Hi,

I’m trying to figure out how to move files out of drop box in an iPad mini. I have found a few menues  and even found one which states ‘move.’ But this does not actually move the files out of drop box.

Can anyone tell me how to move files out of drop box into another area of the iPad?

Thanks.

Patrick


Re: Help with drop box on iPad

Matt
 

You mean delete them from drop box? You cannot move them out of drop box on the phone or tablet . you can move the file around in the drop box app. Or you can share the file or open it up in another program but you cannot just move it out of the drop box app on a phone or tablet. You can delete it.

 

 

 

From: main@TechTalk.groups.io [mailto:main@TechTalk.groups.io] On Behalf Of Patrick Ford
Sent: Wednesday, July 06, 2016 5:13 AM
To: main@TechTalk.groups.io
Subject: [TechTalk] Help with drop box on iPad

 

Hi,

I’m trying to figure out how to move files out of drop box in an iPad mini. I have found a few menues  and even found one which states ‘move.’ But this does not actually move the files out of drop box.

Can anyone tell me how to move files out of drop box into another area of the iPad?

Thanks.

Patrick


Re: Avast Treasure chest is all resolved. thanks

Matt
 

Not only that usually you can set your anti-virus to delete these files after a certain time and you don’t even have to worry about them. I think I have my set to like 90 days or less.

 

 

 

From: main@TechTalk.groups.io [mailto:main@TechTalk.groups.io] On Behalf Of Gene
Sent: Wednesday, July 06, 2016 1:00 AM
To: main@TechTalk.groups.io
Subject: Re: [TechTalk] Avast Treasure chest is all resolved. thanks

 

Do you understand what quaranteening is?  The tech should have told you that it makes no practical difference if you delete the files or not.  When a file is quaranteened, it is kept in a part of the program where it is separate from everything else.  I don't know what your tech said.  But if he simply made the statement that it is better to delete a quaranteened file, then that calls his advice into question.  The answer should habve been that it makes no practical diffference and that, since antivirus programs sometimes quarantene files that should not be because of a false positive, that unless you know a file is not possibly needed, it's better to just leave it. 

 

Probably none of the files you deleted are needed by the computer.  But why delete files even if there is a small possibility they will be needed?  They can't do anything if they are quaraanteened and if necessary, you can move a file from quarantene back to where it was originally. 

 

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

From: Sugar

Sent: Tuesday, July 05, 2016 11:36 PM

Subject: [TechTalk] Avast Treasure chest is all resolved. thanks

 

Thank you all for your suggestions. With some chatting with a tech individual I was advised to delete them if I dit know what they were, so I did and all is well.

I saw no reason to keep them lurking in my pc..smile

Thanks again

Sugar

 

‘Faith is seeing light with your heart when all your eyes see is darkness.’

Sugar

 

Come and join me and my busy elves at the North Pole for yummy & Tasty Recipes:

https://groups.io/org/groupsio/Santas-Workshop

 

From: main@TechTalk.groups.io [mailto:main@TechTalk.groups.io] On Behalf Of Gene
Sent: Tuesday, July 05, 2016 9:19 PM
To: main@TechTalk.groups.io
Subject: Re: [TechTalk] Avast treasure chest question

 

Avast automatically quaranteens files by default.  If people want to delete them or just let them sit on their computer, it makes no practical difference. 

 

Gene

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

From: Brian Zolo

Sent: Tuesday, July 05, 2016 6:49 PM

Subject: Re: [TechTalk] Avast treasure chest question

 

Hey there, Sugar, Brian Zolo here, feel free to call me BZ, grin!  I'd
either delete them or quarantine them if Avast gives you that option.  Let
me know if I can be of further assistance, you have a great day!  BZ!

-----Original Message-----
From: main@TechTalk.groups.io [mailto:main@TechTalk.groups.io] On Behalf Of
Sugar
Sent: Tuesday, July 05, 2016 1:20 PM
To: main@TechTalk.groups.io
Subject: [TechTalk] Avast treasure chest question

Hi everyone
I use windows 7, Jaws 14, office 2010 on a 64 desk top I use Avast and in my
treasure chest I show 20 files. Should I delete these files?
Thanks
Sugar

"I Rather Walk In Darkness With God, Than To Walk Alone In The Light"
-Sugar

Come and joine me and my busy elves at the North Pole for fun and tasty
Recipes all around, especially for Christmas!:
https://groups.io/org/groupsio/Santas-Workshop








__________ Information from ESET NOD32 Antivirus, version of virus signature
database 13758P (20160705) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com



 

Virus-free. www.avast.com


Re: Windows 10 Anniversary Update/Microsoft Edge and UWP: one change affects everyone

Bharat
 

Certainly, i will do that!

On 7/6/16, Joseph Lee <joseph.lee22590@gmail.com> wrote:
Hi,
In this case, I'd say waiting until October would be the best bet, by then
major screen readers would have released responses.
Cheers,
Joseph

-----Original Message-----
From: main@TechTalk.groups.io [mailto:main@TechTalk.groups.io] On Behalf Of
Bharat
Sent: Wednesday, July 6, 2016 1:54 AM
To: main@TechTalk.groups.io
Subject: Re: [TechTalk] Windows 10 Anniversary Update/Microsoft Edge and
UWP: one change affects everyone

I am a windows 10 pro user with the latest release. I would opt for the
delay update option in that case & opt for the update once this issue is
fixed!

On 7/6/16, Joseph Lee <joseph.lee22590@gmail.com> wrote:
Hi,
If you are using Windows 7 or 8.1, the free upgrade offer will expire
in about three weeks. I do recommend upgrading now unless if you are
happy with the current version you are using. If you are using Windows
10 Version 1511 (build 10586), the message I sent earlier applies.
Cheers,
Joseph

-----Original Message-----
From: main@TechTalk.groups.io [mailto:main@TechTalk.groups.io] On
Behalf Of Bharat
Sent: Wednesday, July 6, 2016 1:49 AM
To: main@TechTalk.groups.io
Subject: Re: [TechTalk] Windows 10 Anniversary Update/Microsoft Edge
and
UWP: one change affects everyone

Joseph,

I want to know, Should one delay upgrading?

On 7/6/16, Joseph Lee <joseph.lee22590@gmail.com> wrote:
Hi,
For Windows 10 Home users, you cannot delay it indefinitely. For
Windows 10 Pro, Enterprise (regular update) and Education, you can
delay it for several months (defer upgrades). For Windows 10
Enterprise LTSB, you'll only get security updates until October 2025.
Cheers,
Joseph

-----Original Message-----
From: main@TechTalk.groups.io [mailto:main@TechTalk.groups.io] On
Behalf Of Bharat
Sent: Wednesday, July 6, 2016 1:00 AM
To: main@TechTalk.groups.io
Subject: Re: [TechTalk] Windows 10 Anniversary Update/Microsoft Edge
and
UWP: one change affects everyone

does it mean, we should delay updating to the anniversary edition as
it is released? should i put it on no update or whatever it is
called in Windows 10? with around 25 days to go for the anniversary
update rollout, i don't quite think these things would be fixed so
soon as that & that, we may then have to struggle with things...? isn't
it?

On 7/6/16, Carolyn Arnold <4carolyna@windstream.net> wrote:
Thank you, Joseph. Good to know that there is someone like you with
your know-how working with Microsoft. I hope they will be accepting
of your recommendations.

Bye for now,

Carolyn


-----Original Message-----
From: main@TechTalk.groups.io
[mailto:main@TechTalk.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, July 5, 2016 6:46 PM
To: main@TechTalk.groups.io
Subject: [TechTalk] Windows 10 Anniversary Update/Microsoft Edge and
UWP: one change affects everyone

Hi all,

As a follow-up to a thread on Edge and what not, here's the story
behind it:



Back in 2015, when Microsoft was working on Edge, it used a specific
info in a UI Automation attribute. In a recent Windows 10
Anniversary Update Preview builds, this information has changed. Not
only it broke Edge for some screen readers, it also broke search
results announcement in Start menu among other controls. I and other
developers have been working with Microsoft on understanding what's
going on and provide needed fixes in our screen readers.



In regards to Edge support: Edge is a UIA universe.
Therefore a reasonable support for Edge will require good UIA
support from screen readers (termed UIA clients). Recent screen
readers do include UIA support facility (UIA handler in NVDA, FSUIA in
JAWS).
However, it is known that Microsoft includes broken UIA
implementations in some apps (including Office 2013, and in older
releases, Edge), and MS is known for changing UIA attributes without
notice, giving screen reader vendors (NV Access, VFO and others) a
headache when it comes to writing workarounds (hence Eric Damery's
statement on difficulty in supporting Edge in JAWS is justified). I
can go on about UIA stuff and workarounds that screen reader
developers came up with (I think it should be a separate thread), as
part of my recent work has been hunting for weirdness in UIA and
writing workarounds for it in NVDA (my patch on UAC redesign
workaround is a good example, something that taught me not to trust
MS completely when it comes to certain UIA information).



In regards to UWP: due to security mechanism in place, some screen
readers will not announce typed characters (it was observed in NVDA).
Screen reader vendors and Microsoft were told about this problem.



Third, about toasts: when toasts appear, they usually fire a tool
tip event, letting screen readers know that they should announce new
notifications. In a more recent Insider Preview build, toasts do not
fire this event, which means toasts will not be announced by
third-party screen readers automatically (exception is Narrator). I
raised this issue with Microsoft and with NV Access, and at least NV
Access has put this as a high priority issue.



New UAC: Due to redesigned look of User Account Control in
Anniversary Update, some screen readers would not announce UAC
prompts. This affects not only third-party screen readers, but also
affects Narrator (turns out there is some misunderstanding between
MS and screen reader developers when defining what exactly a dialog
is).
At least for NVDA, this was resolved and is going through active
testing in the next/alpha snapshots.



Lastly, about so-called OneCore: According to Peter Bright (Ars
Technica) and various talks given by Microsoft staff, OneCore is a
group of shared components that power Windows 10. This include
essential components all variants of Windows 10 come with, with each
variant including variant-specific layer on top of that. For
example, Windows
10 for PC's include oneCore, and on top are desktop and UWP
(Universal Windows Platform) components and other support routines,
whereas Windows 10 Mobile include OneCore and phone functionality.
An interesting variant is Windows Holographic, which includes
OneCore plus holographic user interface and UWP.



The high-level overview of components included in each variant of
Windows 10 (to be seen in Anniversary Update)
are:



* OneCore: Windows NT kernel (ntoskrnl.exe),
subsystems support.

* PC's: OneCore, desktop experience, UWP, features
for different versions of Windows 10 (Home, Pro,
Enterprise/Enterprise LTSB, Education), Windows Subsystem for Linux
if enabled (for 64-bit versions).

* Windows 10 Mobile: OneCore, telephony stack,
cellular connectivity components, UWP.

* Windows 10 IoT (Internet of Things): OneCore, UWP,
IoT-specific components.

* Windows Holographic (Microsoft HoloLens and
friends): OneCore, Windows Holographic interface, UWP.

* Xbox One: OneCore, game/OS hypervisor control
routine (called Nanovisor according to Peter Bright), UWP, gaming
components.

* Windows Server 2016: OneCore, choice of components
for server roles.



References:

* OneCore to rule them all (Ars Technica):
http://arstechnica.com/information-technology/2016/05/onecor
e-to-rule-them-all-how-windows-everywhere-finally-happened/

* UAC prompt not announced by NVDA:
https://github.com/nvaccess/nvda/issues/5942

* UIA frameowkr ID for Edge has changed:
https://github.com/nvaccess/nvda/issues/5955

* Toasts not announced by NVDA in build 14366:
https://github.com/nvaccess/nvda/issues/6096



The NVDA issue references are included as they contain useful
background info.



Cheers,

Joseph
























safe mod and speech?

Billy Inglis
 

hi guys, Is it possible to have any speech in safe mode?,
--
Billy Inglis


Help with drop box on iPad

Patrick Ford
 

Hi,

I’m trying to figure out how to move files out of drop box in an iPad mini. I have found a few menues  and even found one which states ‘move.’ But this does not actually move the files out of drop box.

Can anyone tell me how to move files out of drop box into another area of the iPad?

Thanks.

Patrick


Re: Windows 10 Anniversary Update/Microsoft Edge and UWP: one change affects everyone

Joseph Lee <joseph.lee22590@...>
 

Hi,
In this case, I'd say waiting until October would be the best bet, by then major screen readers would have released responses.
Cheers,
Joseph

-----Original Message-----
From: main@TechTalk.groups.io [mailto:main@TechTalk.groups.io] On Behalf Of Bharat
Sent: Wednesday, July 6, 2016 1:54 AM
To: main@TechTalk.groups.io
Subject: Re: [TechTalk] Windows 10 Anniversary Update/Microsoft Edge and UWP: one change affects everyone

I am a windows 10 pro user with the latest release. I would opt for the delay update option in that case & opt for the update once this issue is fixed!

On 7/6/16, Joseph Lee <joseph.lee22590@gmail.com> wrote:
Hi,
If you are using Windows 7 or 8.1, the free upgrade offer will expire
in about three weeks. I do recommend upgrading now unless if you are
happy with the current version you are using. If you are using Windows
10 Version 1511 (build 10586), the message I sent earlier applies.
Cheers,
Joseph

-----Original Message-----
From: main@TechTalk.groups.io [mailto:main@TechTalk.groups.io] On
Behalf Of Bharat
Sent: Wednesday, July 6, 2016 1:49 AM
To: main@TechTalk.groups.io
Subject: Re: [TechTalk] Windows 10 Anniversary Update/Microsoft Edge
and
UWP: one change affects everyone

Joseph,

I want to know, Should one delay upgrading?

On 7/6/16, Joseph Lee <joseph.lee22590@gmail.com> wrote:
Hi,
For Windows 10 Home users, you cannot delay it indefinitely. For
Windows 10 Pro, Enterprise (regular update) and Education, you can
delay it for several months (defer upgrades). For Windows 10
Enterprise LTSB, you'll only get security updates until October 2025.
Cheers,
Joseph

-----Original Message-----
From: main@TechTalk.groups.io [mailto:main@TechTalk.groups.io] On
Behalf Of Bharat
Sent: Wednesday, July 6, 2016 1:00 AM
To: main@TechTalk.groups.io
Subject: Re: [TechTalk] Windows 10 Anniversary Update/Microsoft Edge
and
UWP: one change affects everyone

does it mean, we should delay updating to the anniversary edition as
it is released? should i put it on no update or whatever it is
called in Windows 10? with around 25 days to go for the anniversary
update rollout, i don't quite think these things would be fixed so
soon as that & that, we may then have to struggle with things...? isn't it?

On 7/6/16, Carolyn Arnold <4carolyna@windstream.net> wrote:
Thank you, Joseph. Good to know that there is someone like you with
your know-how working with Microsoft. I hope they will be accepting
of your recommendations.

Bye for now,

Carolyn


-----Original Message-----
From: main@TechTalk.groups.io
[mailto:main@TechTalk.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, July 5, 2016 6:46 PM
To: main@TechTalk.groups.io
Subject: [TechTalk] Windows 10 Anniversary Update/Microsoft Edge and
UWP: one change affects everyone

Hi all,

As a follow-up to a thread on Edge and what not, here's the story
behind it:



Back in 2015, when Microsoft was working on Edge, it used a specific
info in a UI Automation attribute. In a recent Windows 10
Anniversary Update Preview builds, this information has changed. Not
only it broke Edge for some screen readers, it also broke search
results announcement in Start menu among other controls. I and other
developers have been working with Microsoft on understanding what's
going on and provide needed fixes in our screen readers.



In regards to Edge support: Edge is a UIA universe.
Therefore a reasonable support for Edge will require good UIA
support from screen readers (termed UIA clients). Recent screen
readers do include UIA support facility (UIA handler in NVDA, FSUIA in JAWS).
However, it is known that Microsoft includes broken UIA
implementations in some apps (including Office 2013, and in older
releases, Edge), and MS is known for changing UIA attributes without
notice, giving screen reader vendors (NV Access, VFO and others) a
headache when it comes to writing workarounds (hence Eric Damery's
statement on difficulty in supporting Edge in JAWS is justified). I
can go on about UIA stuff and workarounds that screen reader
developers came up with (I think it should be a separate thread), as
part of my recent work has been hunting for weirdness in UIA and
writing workarounds for it in NVDA (my patch on UAC redesign
workaround is a good example, something that taught me not to trust
MS completely when it comes to certain UIA information).



In regards to UWP: due to security mechanism in place, some screen
readers will not announce typed characters (it was observed in NVDA).
Screen reader vendors and Microsoft were told about this problem.



Third, about toasts: when toasts appear, they usually fire a tool
tip event, letting screen readers know that they should announce new
notifications. In a more recent Insider Preview build, toasts do not
fire this event, which means toasts will not be announced by
third-party screen readers automatically (exception is Narrator). I
raised this issue with Microsoft and with NV Access, and at least NV
Access has put this as a high priority issue.



New UAC: Due to redesigned look of User Account Control in
Anniversary Update, some screen readers would not announce UAC
prompts. This affects not only third-party screen readers, but also
affects Narrator (turns out there is some misunderstanding between
MS and screen reader developers when defining what exactly a dialog is).
At least for NVDA, this was resolved and is going through active
testing in the next/alpha snapshots.



Lastly, about so-called OneCore: According to Peter Bright (Ars
Technica) and various talks given by Microsoft staff, OneCore is a
group of shared components that power Windows 10. This include
essential components all variants of Windows 10 come with, with each
variant including variant-specific layer on top of that. For
example, Windows
10 for PC's include oneCore, and on top are desktop and UWP
(Universal Windows Platform) components and other support routines,
whereas Windows 10 Mobile include OneCore and phone functionality.
An interesting variant is Windows Holographic, which includes
OneCore plus holographic user interface and UWP.



The high-level overview of components included in each variant of
Windows 10 (to be seen in Anniversary Update)
are:



* OneCore: Windows NT kernel (ntoskrnl.exe),
subsystems support.

* PC's: OneCore, desktop experience, UWP, features
for different versions of Windows 10 (Home, Pro,
Enterprise/Enterprise LTSB, Education), Windows Subsystem for Linux
if enabled (for 64-bit versions).

* Windows 10 Mobile: OneCore, telephony stack,
cellular connectivity components, UWP.

* Windows 10 IoT (Internet of Things): OneCore, UWP,
IoT-specific components.

* Windows Holographic (Microsoft HoloLens and
friends): OneCore, Windows Holographic interface, UWP.

* Xbox One: OneCore, game/OS hypervisor control
routine (called Nanovisor according to Peter Bright), UWP, gaming
components.

* Windows Server 2016: OneCore, choice of components
for server roles.



References:

* OneCore to rule them all (Ars Technica):
http://arstechnica.com/information-technology/2016/05/onecor
e-to-rule-them-all-how-windows-everywhere-finally-happened/

* UAC prompt not announced by NVDA:
https://github.com/nvaccess/nvda/issues/5942

* UIA frameowkr ID for Edge has changed:
https://github.com/nvaccess/nvda/issues/5955

* Toasts not announced by NVDA in build 14366:
https://github.com/nvaccess/nvda/issues/6096



The NVDA issue references are included as they contain useful
background info.



Cheers,

Joseph



















Re: Windows 10 Anniversary Update/Microsoft Edge and UWP: one change affects everyone

Bharat
 

I am a windows 10 pro user with the latest release. I would opt for
the delay update option in that case & opt for the update once this
issue is fixed!

On 7/6/16, Joseph Lee <joseph.lee22590@gmail.com> wrote:
Hi,
If you are using Windows 7 or 8.1, the free upgrade offer will expire in
about three weeks. I do recommend upgrading now unless if you are happy with
the current version you are using. If you are using Windows 10 Version 1511
(build 10586), the message I sent earlier applies.
Cheers,
Joseph

-----Original Message-----
From: main@TechTalk.groups.io [mailto:main@TechTalk.groups.io] On Behalf Of
Bharat
Sent: Wednesday, July 6, 2016 1:49 AM
To: main@TechTalk.groups.io
Subject: Re: [TechTalk] Windows 10 Anniversary Update/Microsoft Edge and
UWP: one change affects everyone

Joseph,

I want to know, Should one delay upgrading?

On 7/6/16, Joseph Lee <joseph.lee22590@gmail.com> wrote:
Hi,
For Windows 10 Home users, you cannot delay it indefinitely. For
Windows 10 Pro, Enterprise (regular update) and Education, you can
delay it for several months (defer upgrades). For Windows 10
Enterprise LTSB, you'll only get security updates until October 2025.
Cheers,
Joseph

-----Original Message-----
From: main@TechTalk.groups.io [mailto:main@TechTalk.groups.io] On
Behalf Of Bharat
Sent: Wednesday, July 6, 2016 1:00 AM
To: main@TechTalk.groups.io
Subject: Re: [TechTalk] Windows 10 Anniversary Update/Microsoft Edge
and
UWP: one change affects everyone

does it mean, we should delay updating to the anniversary edition as
it is released? should i put it on no update or whatever it is called
in Windows 10? with around 25 days to go for the anniversary update
rollout, i don't quite think these things would be fixed so soon as
that & that, we may then have to struggle with things...? isn't it?

On 7/6/16, Carolyn Arnold <4carolyna@windstream.net> wrote:
Thank you, Joseph. Good to know that there is someone like you with
your know-how working with Microsoft. I hope they will be accepting
of your recommendations.

Bye for now,

Carolyn


-----Original Message-----
From: main@TechTalk.groups.io
[mailto:main@TechTalk.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, July 5, 2016 6:46 PM
To: main@TechTalk.groups.io
Subject: [TechTalk] Windows 10 Anniversary Update/Microsoft Edge and
UWP: one change affects everyone

Hi all,

As a follow-up to a thread on Edge and what not, here's the story
behind it:



Back in 2015, when Microsoft was working on Edge, it used a specific
info in a UI Automation attribute. In a recent Windows 10 Anniversary
Update Preview builds, this information has changed. Not only it
broke Edge for some screen readers, it also broke search results
announcement in Start menu among other controls. I and other
developers have been working with Microsoft on understanding what's
going on and provide needed fixes in our screen readers.



In regards to Edge support: Edge is a UIA universe.
Therefore a reasonable support for Edge will require good UIA support
from screen readers (termed UIA clients). Recent screen readers do
include UIA support facility (UIA handler in NVDA, FSUIA in JAWS).
However, it is known that Microsoft includes broken UIA
implementations in some apps (including Office 2013, and in older
releases, Edge), and MS is known for changing UIA attributes without
notice, giving screen reader vendors (NV Access, VFO and others) a
headache when it comes to writing workarounds (hence Eric Damery's
statement on difficulty in supporting Edge in JAWS is justified). I
can go on about UIA stuff and workarounds that screen reader
developers came up with (I think it should be a separate thread), as
part of my recent work has been hunting for weirdness in UIA and
writing workarounds for it in NVDA (my patch on UAC redesign
workaround is a good example, something that taught me not to trust
MS completely when it comes to certain UIA information).



In regards to UWP: due to security mechanism in place, some screen
readers will not announce typed characters (it was observed in NVDA).
Screen reader vendors and Microsoft were told about this problem.



Third, about toasts: when toasts appear, they usually fire a tool tip
event, letting screen readers know that they should announce new
notifications. In a more recent Insider Preview build, toasts do not
fire this event, which means toasts will not be announced by
third-party screen readers automatically (exception is Narrator). I
raised this issue with Microsoft and with NV Access, and at least NV
Access has put this as a high priority issue.



New UAC: Due to redesigned look of User Account Control in
Anniversary Update, some screen readers would not announce UAC
prompts. This affects not only third-party screen readers, but also
affects Narrator (turns out there is some misunderstanding between MS
and screen reader developers when defining what exactly a dialog is).
At least for NVDA, this was resolved and is going through active
testing in the next/alpha snapshots.



Lastly, about so-called OneCore: According to Peter Bright (Ars
Technica) and various talks given by Microsoft staff, OneCore is a
group of shared components that power Windows 10. This include
essential components all variants of Windows 10 come with, with each
variant including variant-specific layer on top of that. For example,
Windows
10 for PC's include oneCore, and on top are desktop and UWP
(Universal Windows Platform) components and other support routines,
whereas Windows 10 Mobile include OneCore and phone functionality. An
interesting variant is Windows Holographic, which includes OneCore
plus holographic user interface and UWP.



The high-level overview of components included in each variant of
Windows 10 (to be seen in Anniversary Update)
are:



* OneCore: Windows NT kernel (ntoskrnl.exe),
subsystems support.

* PC's: OneCore, desktop experience, UWP, features
for different versions of Windows 10 (Home, Pro,
Enterprise/Enterprise LTSB, Education), Windows Subsystem for Linux
if enabled (for 64-bit versions).

* Windows 10 Mobile: OneCore, telephony stack,
cellular connectivity components, UWP.

* Windows 10 IoT (Internet of Things): OneCore, UWP,
IoT-specific components.

* Windows Holographic (Microsoft HoloLens and
friends): OneCore, Windows Holographic interface, UWP.

* Xbox One: OneCore, game/OS hypervisor control
routine (called Nanovisor according to Peter Bright), UWP, gaming
components.

* Windows Server 2016: OneCore, choice of components
for server roles.



References:

* OneCore to rule them all (Ars Technica):
http://arstechnica.com/information-technology/2016/05/onecor
e-to-rule-them-all-how-windows-everywhere-finally-happened/

* UAC prompt not announced by NVDA:
https://github.com/nvaccess/nvda/issues/5942

* UIA frameowkr ID for Edge has changed:
https://github.com/nvaccess/nvda/issues/5955

* Toasts not announced by NVDA in build 14366:
https://github.com/nvaccess/nvda/issues/6096



The NVDA issue references are included as they contain useful
background info.



Cheers,

Joseph



















Re: Windows 10 Anniversary Update/Microsoft Edge and UWP: one change affects everyone

Joseph Lee <joseph.lee22590@...>
 

Hi,
If you are using Windows 7 or 8.1, the free upgrade offer will expire in about three weeks. I do recommend upgrading now unless if you are happy with the current version you are using. If you are using Windows 10 Version 1511 (build 10586), the message I sent earlier applies.
Cheers,
Joseph

-----Original Message-----
From: main@TechTalk.groups.io [mailto:main@TechTalk.groups.io] On Behalf Of Bharat
Sent: Wednesday, July 6, 2016 1:49 AM
To: main@TechTalk.groups.io
Subject: Re: [TechTalk] Windows 10 Anniversary Update/Microsoft Edge and UWP: one change affects everyone

Joseph,

I want to know, Should one delay upgrading?

On 7/6/16, Joseph Lee <joseph.lee22590@gmail.com> wrote:
Hi,
For Windows 10 Home users, you cannot delay it indefinitely. For
Windows 10 Pro, Enterprise (regular update) and Education, you can
delay it for several months (defer upgrades). For Windows 10
Enterprise LTSB, you'll only get security updates until October 2025.
Cheers,
Joseph

-----Original Message-----
From: main@TechTalk.groups.io [mailto:main@TechTalk.groups.io] On
Behalf Of Bharat
Sent: Wednesday, July 6, 2016 1:00 AM
To: main@TechTalk.groups.io
Subject: Re: [TechTalk] Windows 10 Anniversary Update/Microsoft Edge
and
UWP: one change affects everyone

does it mean, we should delay updating to the anniversary edition as
it is released? should i put it on no update or whatever it is called
in Windows 10? with around 25 days to go for the anniversary update
rollout, i don't quite think these things would be fixed so soon as
that & that, we may then have to struggle with things...? isn't it?

On 7/6/16, Carolyn Arnold <4carolyna@windstream.net> wrote:
Thank you, Joseph. Good to know that there is someone like you with
your know-how working with Microsoft. I hope they will be accepting
of your recommendations.

Bye for now,

Carolyn


-----Original Message-----
From: main@TechTalk.groups.io
[mailto:main@TechTalk.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, July 5, 2016 6:46 PM
To: main@TechTalk.groups.io
Subject: [TechTalk] Windows 10 Anniversary Update/Microsoft Edge and
UWP: one change affects everyone

Hi all,

As a follow-up to a thread on Edge and what not, here's the story
behind it:



Back in 2015, when Microsoft was working on Edge, it used a specific
info in a UI Automation attribute. In a recent Windows 10 Anniversary
Update Preview builds, this information has changed. Not only it
broke Edge for some screen readers, it also broke search results
announcement in Start menu among other controls. I and other
developers have been working with Microsoft on understanding what's
going on and provide needed fixes in our screen readers.



In regards to Edge support: Edge is a UIA universe.
Therefore a reasonable support for Edge will require good UIA support
from screen readers (termed UIA clients). Recent screen readers do
include UIA support facility (UIA handler in NVDA, FSUIA in JAWS).
However, it is known that Microsoft includes broken UIA
implementations in some apps (including Office 2013, and in older
releases, Edge), and MS is known for changing UIA attributes without
notice, giving screen reader vendors (NV Access, VFO and others) a
headache when it comes to writing workarounds (hence Eric Damery's
statement on difficulty in supporting Edge in JAWS is justified). I
can go on about UIA stuff and workarounds that screen reader
developers came up with (I think it should be a separate thread), as
part of my recent work has been hunting for weirdness in UIA and
writing workarounds for it in NVDA (my patch on UAC redesign
workaround is a good example, something that taught me not to trust
MS completely when it comes to certain UIA information).



In regards to UWP: due to security mechanism in place, some screen
readers will not announce typed characters (it was observed in NVDA).
Screen reader vendors and Microsoft were told about this problem.



Third, about toasts: when toasts appear, they usually fire a tool tip
event, letting screen readers know that they should announce new
notifications. In a more recent Insider Preview build, toasts do not
fire this event, which means toasts will not be announced by
third-party screen readers automatically (exception is Narrator). I
raised this issue with Microsoft and with NV Access, and at least NV
Access has put this as a high priority issue.



New UAC: Due to redesigned look of User Account Control in
Anniversary Update, some screen readers would not announce UAC
prompts. This affects not only third-party screen readers, but also
affects Narrator (turns out there is some misunderstanding between MS
and screen reader developers when defining what exactly a dialog is).
At least for NVDA, this was resolved and is going through active
testing in the next/alpha snapshots.



Lastly, about so-called OneCore: According to Peter Bright (Ars
Technica) and various talks given by Microsoft staff, OneCore is a
group of shared components that power Windows 10. This include
essential components all variants of Windows 10 come with, with each
variant including variant-specific layer on top of that. For example,
Windows
10 for PC's include oneCore, and on top are desktop and UWP
(Universal Windows Platform) components and other support routines,
whereas Windows 10 Mobile include OneCore and phone functionality. An
interesting variant is Windows Holographic, which includes OneCore
plus holographic user interface and UWP.



The high-level overview of components included in each variant of
Windows 10 (to be seen in Anniversary Update)
are:



* OneCore: Windows NT kernel (ntoskrnl.exe),
subsystems support.

* PC's: OneCore, desktop experience, UWP, features
for different versions of Windows 10 (Home, Pro,
Enterprise/Enterprise LTSB, Education), Windows Subsystem for Linux
if enabled (for 64-bit versions).

* Windows 10 Mobile: OneCore, telephony stack,
cellular connectivity components, UWP.

* Windows 10 IoT (Internet of Things): OneCore, UWP,
IoT-specific components.

* Windows Holographic (Microsoft HoloLens and
friends): OneCore, Windows Holographic interface, UWP.

* Xbox One: OneCore, game/OS hypervisor control
routine (called Nanovisor according to Peter Bright), UWP, gaming
components.

* Windows Server 2016: OneCore, choice of components
for server roles.



References:

* OneCore to rule them all (Ars Technica):
http://arstechnica.com/information-technology/2016/05/onecor
e-to-rule-them-all-how-windows-everywhere-finally-happened/

* UAC prompt not announced by NVDA:
https://github.com/nvaccess/nvda/issues/5942

* UIA frameowkr ID for Edge has changed:
https://github.com/nvaccess/nvda/issues/5955

* Toasts not announced by NVDA in build 14366:
https://github.com/nvaccess/nvda/issues/6096



The NVDA issue references are included as they contain useful
background info.



Cheers,

Joseph














Re: Windows 10 Anniversary Update/Microsoft Edge and UWP: one change affects everyone

Bharat
 

Joseph,

I want to know, Should one delay upgrading?

On 7/6/16, Joseph Lee <joseph.lee22590@gmail.com> wrote:
Hi,
For Windows 10 Home users, you cannot delay it indefinitely. For Windows 10
Pro, Enterprise (regular update) and Education, you can delay it for several
months (defer upgrades). For Windows 10 Enterprise LTSB, you'll only get
security updates until October 2025.
Cheers,
Joseph

-----Original Message-----
From: main@TechTalk.groups.io [mailto:main@TechTalk.groups.io] On Behalf Of
Bharat
Sent: Wednesday, July 6, 2016 1:00 AM
To: main@TechTalk.groups.io
Subject: Re: [TechTalk] Windows 10 Anniversary Update/Microsoft Edge and
UWP: one change affects everyone

does it mean, we should delay updating to the anniversary edition as it is
released? should i put it on no update or whatever it is called in Windows
10? with around 25 days to go for the anniversary update rollout, i don't
quite think these things would be fixed so soon as that & that, we may then
have to struggle with things...? isn't it?

On 7/6/16, Carolyn Arnold <4carolyna@windstream.net> wrote:
Thank you, Joseph. Good to know that there is someone like you with
your know-how working with Microsoft. I hope they will be accepting of
your recommendations.

Bye for now,

Carolyn


-----Original Message-----
From: main@TechTalk.groups.io
[mailto:main@TechTalk.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, July 5, 2016 6:46 PM
To: main@TechTalk.groups.io
Subject: [TechTalk] Windows 10 Anniversary Update/Microsoft Edge and
UWP: one change affects everyone

Hi all,

As a follow-up to a thread on Edge and what not, here's the story
behind it:



Back in 2015, when Microsoft was working on Edge, it used a specific
info in a UI Automation attribute. In a recent Windows 10 Anniversary
Update Preview builds, this information has changed. Not only it broke
Edge for some screen readers, it also broke search results
announcement in Start menu among other controls. I and other
developers have been working with Microsoft on understanding what's
going on and provide needed fixes in our screen readers.



In regards to Edge support: Edge is a UIA universe.
Therefore a reasonable support for Edge will require good UIA support
from screen readers (termed UIA clients). Recent screen readers do
include UIA support facility (UIA handler in NVDA, FSUIA in JAWS).
However, it is known that Microsoft includes broken UIA
implementations in some apps (including Office 2013, and in older
releases, Edge), and MS is known for changing UIA attributes without
notice, giving screen reader vendors (NV Access, VFO and others) a
headache when it comes to writing workarounds (hence Eric Damery's
statement on difficulty in supporting Edge in JAWS is justified). I
can go on about UIA stuff and workarounds that screen reader
developers came up with (I think it should be a separate thread), as
part of my recent work has been hunting for weirdness in UIA and
writing workarounds for it in NVDA (my patch on UAC redesign
workaround is a good example, something that taught me not to trust MS
completely when it comes to certain UIA information).



In regards to UWP: due to security mechanism in place, some screen
readers will not announce typed characters (it was observed in NVDA).
Screen reader vendors and Microsoft were told about this problem.



Third, about toasts: when toasts appear, they usually fire a tool tip
event, letting screen readers know that they should announce new
notifications. In a more recent Insider Preview build, toasts do not
fire this event, which means toasts will not be announced by
third-party screen readers automatically (exception is Narrator). I
raised this issue with Microsoft and with NV Access, and at least NV
Access has put this as a high priority issue.



New UAC: Due to redesigned look of User Account Control in Anniversary
Update, some screen readers would not announce UAC prompts. This
affects not only third-party screen readers, but also affects Narrator
(turns out there is some misunderstanding between MS and screen reader
developers when defining what exactly a dialog is). At least for NVDA,
this was resolved and is going through active testing in the
next/alpha snapshots.



Lastly, about so-called OneCore: According to Peter Bright (Ars
Technica) and various talks given by Microsoft staff, OneCore is a
group of shared components that power Windows 10. This include
essential components all variants of Windows 10 come with, with each
variant including variant-specific layer on top of that. For example,
Windows
10 for PC's include oneCore, and on top are desktop and UWP (Universal
Windows Platform) components and other support routines, whereas
Windows 10 Mobile include OneCore and phone functionality. An
interesting variant is Windows Holographic, which includes OneCore
plus holographic user interface and UWP.



The high-level overview of components included in each variant of
Windows 10 (to be seen in Anniversary Update)
are:



* OneCore: Windows NT kernel (ntoskrnl.exe),
subsystems support.

* PC's: OneCore, desktop experience, UWP, features
for different versions of Windows 10 (Home, Pro, Enterprise/Enterprise
LTSB, Education), Windows Subsystem for Linux if enabled (for 64-bit
versions).

* Windows 10 Mobile: OneCore, telephony stack,
cellular connectivity components, UWP.

* Windows 10 IoT (Internet of Things): OneCore, UWP,
IoT-specific components.

* Windows Holographic (Microsoft HoloLens and
friends): OneCore, Windows Holographic interface, UWP.

* Xbox One: OneCore, game/OS hypervisor control
routine (called Nanovisor according to Peter Bright), UWP, gaming
components.

* Windows Server 2016: OneCore, choice of components
for server roles.



References:

* OneCore to rule them all (Ars Technica):
http://arstechnica.com/information-technology/2016/05/onecor
e-to-rule-them-all-how-windows-everywhere-finally-happened/

* UAC prompt not announced by NVDA:
https://github.com/nvaccess/nvda/issues/5942

* UIA frameowkr ID for Edge has changed:
https://github.com/nvaccess/nvda/issues/5955

* Toasts not announced by NVDA in build 14366:
https://github.com/nvaccess/nvda/issues/6096



The NVDA issue references are included as they contain useful
background info.



Cheers,

Joseph














Android browser, add blocking

David Mehler
 

Hello,
On a windows machine I use either Firefox or Chrome with the Add Block
Plus and Add Block for Youtube addons to block popup adds. On Android
I'm using Lightning, and others I know are using whichever browser
came with their phone and they just hit browser on their dock. My
question is will the add block plus addon work with lightning or the
stock browser in android?

Thanks.
Dave.


Re: Windows 10 Anniversary Update/Microsoft Edge and UWP: one change affects everyone

Joseph Lee <joseph.lee22590@...>
 

Hi,
For Windows 10 Home users, you cannot delay it indefinitely. For Windows 10 Pro, Enterprise (regular update) and Education, you can delay it for several months (defer upgrades). For Windows 10 Enterprise LTSB, you'll only get security updates until October 2025.
Cheers,
Joseph

-----Original Message-----
From: main@TechTalk.groups.io [mailto:main@TechTalk.groups.io] On Behalf Of Bharat
Sent: Wednesday, July 6, 2016 1:00 AM
To: main@TechTalk.groups.io
Subject: Re: [TechTalk] Windows 10 Anniversary Update/Microsoft Edge and UWP: one change affects everyone

does it mean, we should delay updating to the anniversary edition as it is released? should i put it on no update or whatever it is called in Windows 10? with around 25 days to go for the anniversary update rollout, i don't quite think these things would be fixed so soon as that & that, we may then have to struggle with things...? isn't it?

On 7/6/16, Carolyn Arnold <4carolyna@windstream.net> wrote:
Thank you, Joseph. Good to know that there is someone like you with
your know-how working with Microsoft. I hope they will be accepting of
your recommendations.

Bye for now,

Carolyn


-----Original Message-----
From: main@TechTalk.groups.io
[mailto:main@TechTalk.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, July 5, 2016 6:46 PM
To: main@TechTalk.groups.io
Subject: [TechTalk] Windows 10 Anniversary Update/Microsoft Edge and
UWP: one change affects everyone

Hi all,

As a follow-up to a thread on Edge and what not, here's the story
behind it:



Back in 2015, when Microsoft was working on Edge, it used a specific
info in a UI Automation attribute. In a recent Windows 10 Anniversary
Update Preview builds, this information has changed. Not only it broke
Edge for some screen readers, it also broke search results
announcement in Start menu among other controls. I and other
developers have been working with Microsoft on understanding what's
going on and provide needed fixes in our screen readers.



In regards to Edge support: Edge is a UIA universe.
Therefore a reasonable support for Edge will require good UIA support
from screen readers (termed UIA clients). Recent screen readers do
include UIA support facility (UIA handler in NVDA, FSUIA in JAWS).
However, it is known that Microsoft includes broken UIA
implementations in some apps (including Office 2013, and in older
releases, Edge), and MS is known for changing UIA attributes without
notice, giving screen reader vendors (NV Access, VFO and others) a
headache when it comes to writing workarounds (hence Eric Damery's
statement on difficulty in supporting Edge in JAWS is justified). I
can go on about UIA stuff and workarounds that screen reader
developers came up with (I think it should be a separate thread), as
part of my recent work has been hunting for weirdness in UIA and
writing workarounds for it in NVDA (my patch on UAC redesign
workaround is a good example, something that taught me not to trust MS
completely when it comes to certain UIA information).



In regards to UWP: due to security mechanism in place, some screen
readers will not announce typed characters (it was observed in NVDA).
Screen reader vendors and Microsoft were told about this problem.



Third, about toasts: when toasts appear, they usually fire a tool tip
event, letting screen readers know that they should announce new
notifications. In a more recent Insider Preview build, toasts do not
fire this event, which means toasts will not be announced by
third-party screen readers automatically (exception is Narrator). I
raised this issue with Microsoft and with NV Access, and at least NV
Access has put this as a high priority issue.



New UAC: Due to redesigned look of User Account Control in Anniversary
Update, some screen readers would not announce UAC prompts. This
affects not only third-party screen readers, but also affects Narrator
(turns out there is some misunderstanding between MS and screen reader
developers when defining what exactly a dialog is). At least for NVDA,
this was resolved and is going through active testing in the
next/alpha snapshots.



Lastly, about so-called OneCore: According to Peter Bright (Ars
Technica) and various talks given by Microsoft staff, OneCore is a
group of shared components that power Windows 10. This include
essential components all variants of Windows 10 come with, with each
variant including variant-specific layer on top of that. For example,
Windows
10 for PC's include oneCore, and on top are desktop and UWP (Universal
Windows Platform) components and other support routines, whereas
Windows 10 Mobile include OneCore and phone functionality. An
interesting variant is Windows Holographic, which includes OneCore
plus holographic user interface and UWP.



The high-level overview of components included in each variant of
Windows 10 (to be seen in Anniversary Update)
are:



* OneCore: Windows NT kernel (ntoskrnl.exe),
subsystems support.

* PC's: OneCore, desktop experience, UWP, features
for different versions of Windows 10 (Home, Pro, Enterprise/Enterprise
LTSB, Education), Windows Subsystem for Linux if enabled (for 64-bit
versions).

* Windows 10 Mobile: OneCore, telephony stack,
cellular connectivity components, UWP.

* Windows 10 IoT (Internet of Things): OneCore, UWP,
IoT-specific components.

* Windows Holographic (Microsoft HoloLens and
friends): OneCore, Windows Holographic interface, UWP.

* Xbox One: OneCore, game/OS hypervisor control
routine (called Nanovisor according to Peter Bright), UWP, gaming
components.

* Windows Server 2016: OneCore, choice of components
for server roles.



References:

* OneCore to rule them all (Ars Technica):
http://arstechnica.com/information-technology/2016/05/onecor
e-to-rule-them-all-how-windows-everywhere-finally-happened/

* UAC prompt not announced by NVDA:
https://github.com/nvaccess/nvda/issues/5942

* UIA frameowkr ID for Edge has changed:
https://github.com/nvaccess/nvda/issues/5955

* Toasts not announced by NVDA in build 14366:
https://github.com/nvaccess/nvda/issues/6096



The NVDA issue references are included as they contain useful
background info.



Cheers,

Joseph









Re: Windows 10 Anniversary Update/Microsoft Edge and UWP: one change affects everyone

Bharat
 

does it mean, we should delay updating to the anniversary edition as
it is released? should i put it on no update or whatever it is called
in Windows 10? with around 25 days to go for the anniversary update
rollout, i don't quite think these things would be fixed so soon as
that & that, we may then have to struggle with things...? isn't it?

On 7/6/16, Carolyn Arnold <4carolyna@windstream.net> wrote:
Thank you, Joseph. Good to know that there is someone like
you with your know-how working with Microsoft. I hope they
will be accepting of your recommendations.

Bye for now,

Carolyn


-----Original Message-----
From: main@TechTalk.groups.io
[mailto:main@TechTalk.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, July 5, 2016 6:46 PM
To: main@TechTalk.groups.io
Subject: [TechTalk] Windows 10 Anniversary Update/Microsoft
Edge and UWP: one change affects everyone

Hi all,

As a follow-up to a thread on Edge and what not, here's the
story behind it:



Back in 2015, when Microsoft was working on Edge, it used a
specific info in a UI Automation attribute. In a recent
Windows 10 Anniversary Update Preview builds, this
information has changed. Not only it broke Edge for some
screen readers, it also broke search results announcement in
Start menu among other controls. I and other developers have
been working with Microsoft on understanding what's going on
and provide needed fixes in our screen readers.



In regards to Edge support: Edge is a UIA universe.
Therefore a reasonable support for Edge will require good
UIA support from screen readers (termed UIA clients). Recent
screen readers do include UIA support facility (UIA handler
in NVDA, FSUIA in JAWS). However, it is known that Microsoft
includes broken UIA implementations in some apps (including
Office 2013, and in older releases, Edge), and MS is known
for changing UIA attributes without notice, giving screen
reader vendors (NV Access, VFO and others) a headache when
it comes to writing workarounds (hence Eric Damery's
statement on difficulty in supporting Edge in JAWS is
justified). I can go on about UIA stuff and workarounds that
screen reader developers came up with (I think it should be
a separate thread), as part of my recent work has been
hunting for weirdness in UIA and writing workarounds for it
in NVDA (my patch on UAC redesign workaround is a good
example, something that taught me not to trust MS completely
when it comes to certain UIA information).



In regards to UWP: due to security mechanism in place, some
screen readers will not announce typed characters (it was
observed in NVDA). Screen reader vendors and Microsoft were
told about this problem.



Third, about toasts: when toasts appear, they usually fire a
tool tip event, letting screen readers know that they should
announce new notifications. In a more recent Insider Preview
build, toasts do not fire this event, which means toasts
will not be announced by third-party screen readers
automatically (exception is Narrator). I raised this issue
with Microsoft and with NV Access, and at least NV Access
has put this as a high priority issue.



New UAC: Due to redesigned look of User Account Control in
Anniversary Update, some screen readers would not announce
UAC prompts. This affects not only third-party screen
readers, but also affects Narrator (turns out there is some
misunderstanding between MS and screen reader developers
when defining what exactly a dialog is). At least for NVDA,
this was resolved and is going through active testing in the
next/alpha snapshots.



Lastly, about so-called OneCore: According to Peter Bright
(Ars Technica) and various talks given by Microsoft staff,
OneCore is a group of shared components that power Windows
10. This include essential components all variants of
Windows 10 come with, with each variant including
variant-specific layer on top of that. For example, Windows
10 for PC's include oneCore, and on top are desktop and UWP
(Universal Windows Platform) components and other support
routines, whereas Windows 10 Mobile include OneCore and
phone functionality. An interesting variant is Windows
Holographic, which includes OneCore plus holographic user
interface and UWP.



The high-level overview of components included in each
variant of Windows 10 (to be seen in Anniversary Update)
are:



* OneCore: Windows NT kernel (ntoskrnl.exe),
subsystems support.

* PC's: OneCore, desktop experience, UWP, features
for different versions of Windows 10 (Home, Pro,
Enterprise/Enterprise LTSB, Education), Windows Subsystem
for Linux if enabled (for 64-bit versions).

* Windows 10 Mobile: OneCore, telephony stack,
cellular connectivity components, UWP.

* Windows 10 IoT (Internet of Things): OneCore, UWP,
IoT-specific components.

* Windows Holographic (Microsoft HoloLens and
friends): OneCore, Windows Holographic interface, UWP.

* Xbox One: OneCore, game/OS hypervisor control
routine (called Nanovisor according to Peter Bright), UWP,
gaming components.

* Windows Server 2016: OneCore, choice of components
for server roles.



References:

* OneCore to rule them all (Ars Technica):
http://arstechnica.com/information-technology/2016/05/onecor
e-to-rule-them-all-how-windows-everywhere-finally-happened/

* UAC prompt not announced by NVDA:
https://github.com/nvaccess/nvda/issues/5942

* UIA frameowkr ID for Edge has changed:
https://github.com/nvaccess/nvda/issues/5955

* Toasts not announced by NVDA in build 14366:
https://github.com/nvaccess/nvda/issues/6096



The NVDA issue references are included as they contain
useful background info.



Cheers,

Joseph









Re: Attention Carlos re XP burning utility problem solved

Carlos
 

Hi Alan,
You're quite welcome.  Glad you got it sorted out.

----- Original Message -----
Sent: Wednesday, July 06, 2016 1:45 AM
Subject: [TechTalk] Attention Carlos re XP burning utility problem solved

Hi carlos, just a short note to thank you for your advice re my XP burner would not recognise a blank Disk. ,your advice to try another brand worked   perfectly !. thanks again Alan


Attention Carlos re XP burning utility problem solved

Alan Pollard
 

Hi carlos, just a short note to thank you for your advice re my XP burner would not recognise a blank Disk. ,your advice to try another brand worked   perfectly !. thanks again Alan


Re: fn key and jaws key issue

Michael Amaro
 

thank you very much sir, that did the trick

From: Carlos
Sent: Tuesday, July 5, 2016 8:21 PM
Subject: Re: [TechTalk] fn key and jaws key issue

Try pressing Fn+Escape to reverse the functionality of the F keys.
Source:
----- Original Message -----
Sent: Tuesday, July 05, 2016 9:45 PM
Subject: Re: [TechTalk] fn key and jaws key issue

it is a dell Inspiron 5558  

From: Carlos
Sent: Tuesday, July 5, 2016 4:57 PM
Subject: Re: [TechTalk] fn key and jaws key issue

Yes, you will need sighted assistance.  And the key to access the BIOS again depends on the manufacturer/model.  What is the brand an model?  Using the brand and model number, you can usually find this information in a quick Google search.
----- Original Message -----
Sent: Tuesday, July 05, 2016 7:50 PM
Subject: Re: [TechTalk] fn key and jaws key issue

just to be clear, I need some one sited?  How do I access the bios?

From: Carlos
Sent: Tuesday, July 5, 2016 4:47 PM
Subject: Re: [TechTalk] fn key and jaws key issue

Look for an item labeled something like
"Action Keys"
or
"Hotkeys"
Unfortunately, it is dependent on the manufacturer/model.
----- Original Message -----
Sent: Tuesday, July 05, 2016 7:41 PM
Subject: Re: [TechTalk] fn key and jaws key issue

how do I access the bios? Once there, what do I need to change

From: George B
Sent: Tuesday, July 5, 2016 1:03 PM
Subject: Re: [TechTalk] fn key and jaws key issue

I had to have someone change mine in the bios on my lenova yoga 900

 

From: main@TechTalk.groups.io [mailto:main@TechTalk.groups.io] On Behalf Of Carlos
Sent: Tuesday, July 05, 2016 12:07
To: main@TechTalk.groups.io
Subject: Re: [TechTalk] fn key and jaws key issue

 

As I said, with some laptops this has to be changed in the BIOS.

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

Sent: Tuesday, July 05, 2016 2:56 PM

Subject: Re: [TechTalk] fn key and jaws key issue

 

    I tried using the fn key with the f12 and f11 keys all it says is f11 and f12.  It doesn't do what its supposed to. I also tried going to the mobility center.  I didn't see anything about changing keyboard functions.

 

From: Carlos

Sent: Tuesday, July 5, 2016 11:20 AM

Subject: Re: [TechTalk] fn key and jaws key issue

 

The standard F key operations are probably reversed which is common on many laptops.   In such cases, the F keys will perform their normal function in combination with the Fn key.  You can usually change this behavior either in the BIOS, with a manufacturer supplied utility, or Mobility Center depending on the brand/model.  With some Dell laptops you can change this behavior in Mobility Center.

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

Sent: Tuesday, July 05, 2016 2:10 PM

Subject: [TechTalk] fn key and jaws key issue

 

Hello Listers,

 

I am running windows 10 pro jaws 17.  I found out that when I disconnect my USB keyboard and I try to use the jaws key plus f11 or jaws plus f12 functions via the laptop keyboard.  I have to use the fn key in order to make them work.  How do I make it so I don't have to use the fn key?

 

thanks

 

Michael

 

email/skype:

 

 

JFK"

 

What kind of peace do I mean? What kind of peace do we seek? Not a Pax Americana enforced on the world by American weapons of war. Not the peace of the grave or the security of the slave. I am talking about genuine peace - - the kind of peace that makes life on earth worth living -- the kind that enables man and nations to grow and to hope and to build a better life for their children - - not merely peace for Americans by peace for all men and women - - not merely peace in our time but peace for all time."


Re: Avast Treasure chest is all resolved. thanks

Gene
 

Do you understand what quaranteening is?  The tech should have told you that it makes no practical difference if you delete the files or not.  When a file is quaranteened, it is kept in a part of the program where it is separate from everything else.  I don't know what your tech said.  But if he simply made the statement that it is better to delete a quaranteened file, then that calls his advice into question.  The answer should habve been that it makes no practical diffference and that, since antivirus programs sometimes quarantene files that should not be because of a false positive, that unless you know a file is not possibly needed, it's better to just leave it. 
 
Probably none of the files you deleted are needed by the computer.  But why delete files even if there is a small possibility they will be needed?  They can't do anything if they are quaraanteened and if necessary, you can move a file from quarantene back to where it was originally. 
 
Gene 
----- Original Message -----

From: Sugar
Sent: Tuesday, July 05, 2016 11:36 PM
Subject: [TechTalk] Avast Treasure chest is all resolved. thanks

Thank you all for your suggestions. With some chatting with a tech individual I was advised to delete them if I dit know what they were, so I did and all is well.

I saw no reason to keep them lurking in my pc..smile

Thanks again

Sugar

 

‘Faith is seeing light with your heart when all your eyes see is darkness.’

Sugar

 

Come and join me and my busy elves at the North Pole for yummy & Tasty Recipes:

https://groups.io/org/groupsio/Santas-Workshop

 

From: main@TechTalk.groups.io [mailto:main@TechTalk.groups.io] On Behalf Of Gene
Sent: Tuesday, July 05, 2016 9:19 PM
To: main@TechTalk.groups.io
Subject: Re: [TechTalk] Avast treasure chest question

 

Avast automatically quaranteens files by default.  If people want to delete them or just let them sit on their computer, it makes no practical difference. 

 

Gene

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

From: Brian Zolo

Sent: Tuesday, July 05, 2016 6:49 PM

Subject: Re: [TechTalk] Avast treasure chest question

 

Hey there, Sugar, Brian Zolo here, feel free to call me BZ, grin!  I'd
either delete them or quarantine them if Avast gives you that option.  Let
me know if I can be of further assistance, you have a great day!  BZ!

-----Original Message-----
From: main@TechTalk.groups.io [mailto:main@TechTalk.groups.io] On Behalf Of
Sugar
Sent: Tuesday, July 05, 2016 1:20 PM
To: main@TechTalk.groups.io
Subject: [TechTalk] Avast treasure chest question

Hi everyone
I use windows 7, Jaws 14, office 2010 on a 64 desk top I use Avast and in my
treasure chest I show 20 files. Should I delete these files?
Thanks
Sugar

"I Rather Walk In Darkness With God, Than To Walk Alone In The Light"
-Sugar

Come and joine me and my busy elves at the North Pole for fun and tasty
Recipes all around, especially for Christmas!:
https://groups.io/org/groupsio/Santas-Workshop








__________ Information from ESET NOD32 Antivirus, version of virus signature
database 13758P (20160705) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com





Virus-free. www.avast.com


Re: ipad air 2 question

Kimsan <kimsansong@...>
 

Yeah, that is what I found out. Apparently you were sending your email while I was researching it haha.

 

From: main@TechTalk.groups.io [mailto:main@TechTalk.groups.io] On Behalf Of Joseph Hudson
Sent: Tuesday, July 5, 2016 9:51 PM
To: main@TechTalk.groups.io
Subject: Re: [TechTalk] ipad air 2 question

 

Yes, that is correct.

Joseph Hudson

Email

I device support

Telephone

2543007667

Skype

joseph.hudson89 facebook

Twitter

 

FaceTime/iMessage

 

On Jul 4, 2016, at 11:14 PM, Kimsan <kimsansong@...> wrote:

 

So according to what I found out Mr Joseph, I can indeed send text messages if I set up the continuity option between the ipad and iphone. Not speaking macs seeing as no macs are here in the house.

However, every sent and received message can be viewed from both devices.

 

From: main@TechTalk.groups.io[mailto:main@TechTalk.groups.io] On Behalf Of Joseph Hudson
Sent: Monday, July 4, 2016 8:52 PM
To: main@TechTalk.groups.io
Subject: Re: [TechTalk] ipad air 2 question

 

Hello, yes you can. If you have text messaging enabled on an iPhone 5S or later. Having said that, you ask what the purpose of a message app on the iPad is for. Well the iPhone and Mac and iPad also are able to send Messages to each other and they're called iMessages. These are messages, that travel through the Internet.

Joseph Hudson

Email

I device support

Telephone

2543007667

Skype

joseph.hudson89 facebook

Twitter

 

FaceTime/iMessage

 

On Jul 4, 2016, at 10:49 PM, Kimsan <kimsansong@...> wrote:

 

I have never owned an ipad, so excuse the stupid question.  Can one send a text message using an ipad?

If not, what’s the purpose of the message app on the ipad.

Thanks.

 

 

76741 - 76760 of 103963