Date   
Re: NVDA saying unknown again in browsers

Scott Berry
 

That's not true.  You might just want to give Jaws 2020 a try.  It's pretty damn good.



On 7/9/2020 3:52 PM, g melconian wrote:

Thanks but no thanks. None of my business apps work correctly with JAWS to begin with.everything needs to    be scripted and cost an  arm and  a leg where  as it will work out of  the box  with NVDA and Window Eyes like quickbooks, tax applications like tax act, and so on.I am not going to waste  my time with a company who has no clue how to  optimize their producs  to work without haveot scripting to the moon to get them to work.they should   just work out of the box with the screen reader without all this heavy programming and scripting knowledge. 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Kenny Nead
Sent: Thursday, July 9, 2020 2:44 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA saying unknown again in browsers

 

If you are wondering about Jaws, on the Freedom Scientific web site, you can get Jaws free till the end of August, good way to try the Jaws 2020 out.

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of g melconian
Sent: Thursday, July 9, 2020 4:36 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA saying unknown again in browsers

 

Thast good to know. I think more and more of the windows 10 pro features are all coming to  home versions in some sort or fashion.same like you I have one pro machine for my financial / consulting business. All the others in the house are home windows 10 pcs with NVDA an older version of Window Eyes and JAWS , on them. What can I do and   there is no compeling reason to upgrade to  the latest JAWS as they don’t offer much lately just bells and whistles and gimmicks that I cant se myself using.as I am on business applications an make use of the web JAWS is a pig as far as resources when it comes to the web over  my old Window Eyes or NVDA. 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Kenny Nead
Sent: Thursday, July 9, 2020 2:06 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA saying unknown again in browsers

 

Thank you!

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Brian Vogel
Sent: Thursday, July 9, 2020 3:07 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA saying unknown again in browsers

 

Kenny,

            Unless there is something specific in Pro that you simply must have, I see no compelling reason to change edition from Home to Pro.  It's really a personal choice.  I'd still be on Home except for the fact that I have enough clients on Pro that when I need to troubleshoot something "Pro-specific" it's handy to have one machine that has Pro.  All the other Windows 10 machines in my household are Windows 10 Home.

Cearbhall,

             No great surprise there, and I'm glad that a demonstration has been made of the "intelligence" of the Windows 10 installer.  There was a time where you could actually force update a machine that was displaying the "not quite ready" message in the Windows Update Pane.  This never made the slightest sense to me, as if Microsoft deems the hardware "not ready" it's not ready, and any one of the ways of upgrading to the next Feature Update should detect that, and give a, "Whoa, Nelly!!," type message saying that the update cannot yet be done.

              Whatever method it was you used to try to force it clearly detected the "not ready" state and aborted, as it should.  That is, unless I'm misreading you and you're saying that you manually aborted a force update as soon as you had the opportunity after kicking it off.  In which case, ignore all that came before.
--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Science has become just another voice in the room; it has lost its platform.  Now, you simply declare your own truth.

      ~ Dr. Paul A. Offit, in New York Times article, How Anti-Vaccine Sentiment Took Hold in the United States, September 23, 2019

 

 

I have purchased vocalizer expressive, but where is my license key

Socheat Muth
 

Hi all, especially to the developer of the vocalizer expressive for NVDA


I have purchased the vocalizer expressive for NVDA, and I only receive PayPal e-mail confirmation about my order, but no actual e-mail from Tiflotecnia about my license. Is the license system suppose to be automatic, or it has to be processed manually? I also sent an e-mail to support contact found on the website, but I also email it in case the one I was sending not checked.


Thanks.

Re: wild cards in speech dictionary

Scott Berry
 

I disagree with you when you say that they are using dollars signs.  No some sites use a point system based the dollar whereas others sites use the actuall money ammount based on the dollar. So there is a difference when they say one has 11100 and when they say one has $.80.  I will try the regex but I am not a Python programmer so I know absolutely nothing about Python.

On 7/10/2020 7:10 AM, Luke Davis wrote:
On Fri, 10 Jul 2020, Scott Berry wrote:

I was wondering if there is a way to make a wild card speech dictionary entry.  The reason for this is that one of the many survey sites I use reads numbers like 11125 and it should be $111.25.  Thanks for the help.
Of course. That's what regular expression entries are for.
Python syntax is what NVDA uses, although you don't need all the function calls and such in this howto, just the regexp stuff: https://docs.python.org/3/howto/regex.html#regex-howto

I think in your case, if they use an 11 where they mean a dollar sign, you would want something like:

\b11([\d\.]{3,})

And the replacement:

$\1

That is quite untested though.

Also, it seems highly unlikely that they are using an 11 instead of a $. Something else is probably going on. You may need to use the log viewer to find out what is actually being sent to the synth (at input output debug level), in order to find out what you actually need to replace.

Luke

Re: wild cards in speech dictionary

Luke Davis
 

On Fri, 10 Jul 2020, Scott Berry wrote:

I was wondering if there is a way to make a wild card speech dictionary entry.  The reason for this is that one of the many survey sites I use reads numbers like  11125 and it should be $111.25.  Thanks for the help.
Of course. That's what regular expression entries are for.
Python syntax is what NVDA uses, although you don't need all the function calls and such in this howto, just the regexp stuff: https://docs.python.org/3/howto/regex.html#regex-howto

I think in your case, if they use an 11 where they mean a dollar sign, you would want something like:

\b11([\d\.]{3,})

And the replacement:

$\1

That is quite untested though.

Also, it seems highly unlikely that they are using an 11 instead of a $. Something else is probably going on. You may need to use the log viewer to find out what is actually being sent to the synth (at input output debug level), in order to find out what you actually need to replace.

Luke

Re: addon

Rui Fontes
 

Hello!


Enhanced Phonetic Reading


Rui Fontes


Às 12:43 de 10/07/2020, Robert Doc Wright godfearer escreveu:

What is the name of the addon that gave the phonetic of a letter when your cursor is sitting on it?

addon

Robert Doc Wright godfearer
 

What is the name of the addon that gave the phonetic of a letter when your cursor is sitting on it?

wild cards in speech dictionary

Scott Berry
 

Hello there,


I was wondering if there is a way to make a wild card speech dictionary entry.  The reason for this is that one of the many survey sites I use reads numbers like  11125 and it should be $111.25.  Thanks for the help.

Re: NVDA saying unknown again in browsers

 

Well I have updated my old hp amd ryzen 2500 system to windows 2004 and its ok.

The only things I needed to update were a connection utility and audio drivers.

There was an older intel 7th gen, an ay series, and that also just worked.

I just updated a elete desk 800g2 6th gen to windows 10 latest and also updated drivers and this from windows 1500.

One thing I did do before updating to the latest was to install all drivers and bios updates first.

Not sure if that had anything to do with it but it was all smooth and it  worked.

So check and see what needs updating by going to hp support assistant, and hitting space on the serial number, go to https://support.hp.com

click accept

click software and drivers

hit the identify button then hit ok.

Or hit laptop or desktop, enter the serial or product number from support assistant in the field previded, then go button, then download and run all drivers that say 2020 on themm.

Note have device manager open in control panel and add remove programs open to to see what you have installed so you get the right things.

Once all drivers and diagnostics are installed and the system is rebooted it should work.

The only exceptions are the firmware which may have different instructions.

Desktop bios on the elete and pro line you can update bios, back it up and ok it and let it run and update and it will eventually just do and it will work.

On the the laptops its a bit more of a visual doodle and will take a bit longer to update.

Basically when the system on a desktop stops boot looping and finally beeps hit enter and it will boot and go.

On a laptop wait till the fan stops spinning and windows loads and its done.

You may have to go for a break for a few minutes round 10 or so on laptops and just wing it and it will come back.

Just don't lose power is all.



On 10/07/2020 9:27 am, Kenny Nead wrote:

Hi, We have 2 computers, a Dell solid state, that I updated it to 2004, it went well, but slow, then my wife has a H P, and we updated it, it went all the way through the update, then messed up when it said to restart it, so we left it at 1909, and now it says it is up to date. So will leave it alone till it gets good and ready. This was several weeks ago.   

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Cearbhall O'Meadhra
Sent: Thursday, July 9, 2020 2:56 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA saying unknown again in browsers

 

Brian,

 

You may be glad to hear that Windows Update refused to complete saying that my PC settings were not ready for version 2004 and declaring that they are working on it and would get there eventually!

 

I have aborted the upgrade and will continue as I am for now.

 

 

All the best,

 

Cearbhall

 

m +353 (0)833323487 Ph: _353 (0)1-2864623 e: cearbhall.omeadhra@...

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
Sent: Thursday, July 9, 2020 4:48 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA saying unknown again in browsers

 

On Thu, Jul 9, 2020 at 08:22 AM, Kenny Nead wrote:

But why not update to 1909?

Unless you happen to have the ISO file for 1909 on hand (or can get it) that's not happening these days.  The Media Creation Tool will always create the ISO (or bootable USB media from the ISO) for the currently released version of Windows 10, which is now 2004.

Also, figuring out what's up here and getting it fixed under 2004 (whether that fix is in NVDA or not), while a pain, is a useful exercise in itself, as it's going to keep occurring if the root cause is not determined.

And Gene's comment earlier this morning echoes what Joseph Lee and myself have been saying for years now on the Windows 10 for Screen Reader users group:  Unless there is something in a feature update that you absolutely need, which seldom if ever occurs, don't elect to apply it in the early days of the roll out.  Even Windows 10 Home Users have the ability now to just not activate that Download and install now link in the Windows Update pane.  Waiting a couple of months is virtually never a bad idea.

It will be interesting to learn what the root cause of this change is, as I wouldn't have thought that an unchanged browser coupled with an unchanged NVDA, even with a new version of Windows 10, would do this.  Signs point to something about Windows 10, though.
 
--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Science has become just another voice in the room; it has lost its platform.  Now, you simply declare your own truth.

      ~ Dr. Paul A. Offit, in New York Times article, How Anti-Vaccine Sentiment Took Hold in the United States, September 23, 2019

 

 

Re: NVDA saying unknown again in browsers

 

On Thu, Jul 9, 2020 at 07:03 PM, Cearbhall O'Meadhra wrote:
I discovered that they only mean that you now have all the updates relevant to your version!
This has always been the case since automatic feature updates became a thing of the past.  You will be notified that Microsoft considers your machine ready (or not quite ready) for a Feature Update in Settings, Update & Security, Windows Update pane.

Until you activate the Download and install link for the feature update, you will stay on your current version, at least for as long as the version you're on remains in support.  Very few will keep any one version on their machines until it is completely out of support. 

While there is no need to rush out to get the most recent Feature Update when it first comes out, it is a very good idea to manually trigger an update on your machine if Microsoft has put out the word that a given feature update is now considered "available for all computers."   As an example, Version 1909 was declared "available for all" months ago, and Joseph Lee posted an announcement to that effect in this very group.  When such comes out, if you are not on that version that's the time to manually update.

That day will come for 2004, too, and if you're on anything earlier than 2004 when it does (and most will be on 2004 already by then) you should manually update.  I don't know (and probably never will) why certain machines seem to not follow the standard presentation sequence for a feature update roll out.  If it doesn't, then you have good reason to manually trigger once the all clear has been given by Microsoft.  It prevents you from ending up 2 or more feature updates behind. 
 
--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Science has become just another voice in the room; it has lost its platform.  Now, you simply declare your own truth.

      ~ Dr. Paul A. Offit, in New York Times article, How Anti-Vaccine Sentiment Took Hold in the United States, September 23, 2019

 

 

Re: NVDA saying unknown again in browsers

Cearbhall O'Meadhra
 

Yes, It is a bit confusing when Windows update tells you that your Windows is up to date! I discovered that they only mean that you now have all the updates relevant to your version!

 

All the best,

 

Cearbhall

 

m +353 (0)833323487 Ph: _353 (0)1-2864623 e: cearbhall.omeadhra@...

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Kenny Nead
Sent: Thursday, July 9, 2020 10:27 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA saying unknown again in browsers

 

Hi, We have 2 computers, a Dell solid state, that I updated it to 2004, it went well, but slow, then my wife has a H P, and we updated it, it went all the way through the update, then messed up when it said to restart it, so we left it at 1909, and now it says it is up to date. So will leave it alone till it gets good and ready. This was several weeks ago.   

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Cearbhall O'Meadhra
Sent: Thursday, July 9, 2020 2:56 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA saying unknown again in browsers

 

Brian,

 

You may be glad to hear that Windows Update refused to complete saying that my PC settings were not ready for version 2004 and declaring that they are working on it and would get there eventually!

 

I have aborted the upgrade and will continue as I am for now.

 

 

All the best,

 

Cearbhall

 

m +353 (0)833323487 Ph: _353 (0)1-2864623 e: cearbhall.omeadhra@...

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
Sent: Thursday, July 9, 2020 4:48 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA saying unknown again in browsers

 

On Thu, Jul 9, 2020 at 08:22 AM, Kenny Nead wrote:

But why not update to 1909?

Unless you happen to have the ISO file for 1909 on hand (or can get it) that's not happening these days.  The Media Creation Tool will always create the ISO (or bootable USB media from the ISO) for the currently released version of Windows 10, which is now 2004.

Also, figuring out what's up here and getting it fixed under 2004 (whether that fix is in NVDA or not), while a pain, is a useful exercise in itself, as it's going to keep occurring if the root cause is not determined.

And Gene's comment earlier this morning echoes what Joseph Lee and myself have been saying for years now on the Windows 10 for Screen Reader users group:  Unless there is something in a feature update that you absolutely need, which seldom if ever occurs, don't elect to apply it in the early days of the roll out.  Even Windows 10 Home Users have the ability now to just not activate that Download and install now link in the Windows Update pane.  Waiting a couple of months is virtually never a bad idea.

It will be interesting to learn what the root cause of this change is, as I wouldn't have thought that an unchanged browser coupled with an unchanged NVDA, even with a new version of Windows 10, would do this.  Signs point to something about Windows 10, though.
 
--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Science has become just another voice in the room; it has lost its platform.  Now, you simply declare your own truth.

      ~ Dr. Paul A. Offit, in New York Times article, How Anti-Vaccine Sentiment Took Hold in the United States, September 23, 2019

 

 

Re: NVDA saying unknown again in browsers

Cearbhall O'Meadhra
 

Brian,

 

Yes, I agree that Tylers recommendation is excellent and I have it kept for future use.

 

I tried to upgrade today and the Windows Update stopped and said that Microsoft could not accommodate my settings or something similar but soon would be able to accommodate everything.  So, I have decided to sit tight and wait.

 

I should mention that the unknown issue is not mine but something I am helping another person with.

 

 

All the best,

 

Cearbhall

 

m +353 (0)833323487 Ph: _353 (0)1-2864623 e: cearbhall.omeadhra@...

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of hurrikennyandopo ...
Sent: Thursday, July 9, 2020 10:17 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA saying unknown again in browsers

 

Hi Cearbhall

 

I am running the latest version of Windows 2004 stable and I have no problems with any of the browsers or nvda saying unknown etc even down on the task bar etc.

 

They say its a big job to upgrade and unless there is a killer feature you need to use the end of the day it is up to the user.

 

Did you also see the reply from Tyler just in case you missed it?

 

 


My guess is this is an instance of #9039. To avoid a lot of back and forth, let's assume it is; if it's not, no harm done.

1. Run the COM Registration Fixing Tool, follow its prompts, and reboot just for good measure. If it fixed it, then great, nothing to worry about and you can stop here.

However if that didn't fix it (which I doubt it would), please do the following, assuming you have an installed copy of NVDA 2019.3 or higher:
1. Press windows+r to open the run dialog.
2. Type nvda
3. Press control shift enter and answer yes to the prompt that appears to run as administrator.
4. When NVDA restarts, open the python console either with NVDA+CTRL+z or in the tools menu.
5. Paste this long line in and hit enter. If you're using teamviewer, I'm not sure how you get the clipboard across; maybe it does it automatically.

import comtypes,ctypes;p=comtypes.typeinfo.LoadTypeLibEx(r"c:\windows\syswow64\oleacc.dll");ctypes.windll.oleaut32.RegisterTypeLib(p,r"c:\windows\syswow64\oleacc.dll", None)

If it says traceback, then the line didn't work, and it may have been pasted incorrectly. In that case, come back here and we'll figure out why.

6. Restart NVDA. Things should work again. If they don't, try rebooting.

 

 

They might even be able to roll back windows to a date before it happened and it may do the job.

 

I did also a while ago see another which was similar but it was when you installed a program called maths some thing where it would let nvda reads maths stuff but can not find a reference to it in the user guide now. When it was used it was good but when it was uninstalled it caused those type of problems as well.

 

You had to re install it again to fix the problem it caused.

 

Gene nz

 

On 9/07/2020 11:33 pm, Cearbhall O'Meadhra wrote:

Gene nz,

 

The problem exists on another computer where I am assisting someone to resolve their difficulty. My own PC is running fine. I have been in touch with the Microsoft Accessibility Help desk and it seems that there are some access issues with version 2004 of Windows 10. Would you advise me to install version 2004 or should I keep my current version which is:

Version 1903 (OS Build 18362.900)

 

 

All the best,

 

Cearbhall

 

m +353 (0)833323487 Ph: _353 (0)1-2864623 e: cearbhall.omeadhra@...

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of hurrikennyandopo ...
Sent: Wednesday, July 8, 2020 1:12 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA saying unknown again in browsers

 

Hi

 

You might need some sighted help to do the following.

 

This is off my website and it may depend on the version you are using of nvda.

 

One part is for the older nvda and one for the newer nvda do not enter those details only the lines below each one.

 

Do you know the nvda version?

 

The very last part was for the run com tool but if you have done that and rebooted and it is still playing up look for your version number of nvda.

 

The later one has fixed it also on later versions of windows .

 

hope it helps

 

Troubleshooting - NVDA says “unknown” or “pane” in all of your browsers, Mozilla Thunderbird email client and other places
If for some reason you have problems with NVDA saying “unknown” or “pane” check for the following symptoms:

In all of your browsers, or the Mozilla Thunderbird email client, no matter what you do, you still hear “unknown” or “pane”.

In the browser, email client and other menus you notice you cannot get into your menus, or you are unable to use the quick navigation keys

When you have been told the page is loaded and notice strange behaviour

Mozilla Thunderbird saying unknown while you try to navigate it

Your applications key does not work with it being spoken out and other strange behaviour in Windows

The running applications icons are not being spoken out
It might be a good idea to do the following:
Please note: If you are hearing “unknown” or “pane” (as discussed above) NVDA might seem like it is still working properly but it may not be completely in Windows and other programmes.
You could try the following solution which will allow you to re-register your dll files in case they are causing the problem.
Press the Windows key then type the following into the search box. Type in “command prompt”. Once you have located command prompt, in the search results, press the Applications key to bring up the context menu. Arrow down to select “run as administrator” and press the Enter key. This will take you to a command prompt window. This will not be spoken out. You may need sighted assistance for this.
Type in the following command/s:
Old NVDA, Pre 2019.3
import comtypes,ctypes;p=comtypes.typeinfo.LoadTypeLibEx(r"c:\windows\syswow64\oleacc.dll");ctypes.windll.oleaut32.RegisterTypeLib(p,ur"c:\windows\syswow64\oleacc.dll", None)
Current NVDA 2019.3 onward
import comtypes,ctypes;p=comtypes.typeinfo.LoadTypeLibEx(r"c:\windows\syswow64\oleacc.dll");ctypes.windll.oleaut32.RegisterTypeLib(p,r"c:\windows\syswow64\oleacc.dll", None)

This should re-register all components in the system32 folder.
When it is finished, you can close the command prompt window with the Alt + F4 key. You should notice now where NVDA was saying “unknown” as in some examples given, NVDA should now read the icons in the running applications area of Windows, speak the content of the webpage and menus, and also in Mozilla Thunderbird and other places in Windows including the Windows applications context menu.
Run COM Registration Fixing tool
If you are getting any of the following problems below - with Windows unregistering some of the files needed by NVDA - the following tool section in NVDA will get you out of trouble. To access this tool press the NVDA key + letter N while NVDA is running. Arrow down to the tools menu. A submenu will come up. Arrow down to the menu called Run COM Registration Fixing tool... then press the Enter key.  It should register the files needed by NVDA.

 

 

Gene nz

 

On 8/07/2020 9:40 am, Cearbhall O'Meadhra wrote:

Hi,

 

Just as in 2018 under issue #33784  NVDA says unknown instead of reading any content in Firefox and Chrome. It does work in Edge. All latest version of windows 10, Firefox, Google Chrome, Easy keys, and NVDA 2020.1.

 

The earlier issue seemed to relate to a windows update but I dont think there was an update in this case today.

 

Can anyone point to a solution? This problem began only about one week ago.

 

All the best,

 

Cearbhall

 

m +353 (0)833323487 Ph: _353 (0)1-2864623 e: cearbhall.omeadhra@...

 

 

Re: NVDA saying unknown again in browsers

g melconian
 

Thanks but no thanks. None of my business apps work correctly with JAWS to begin with.everything needs to    be scripted and cost an  arm and  a leg where  as it will work out of  the box  with NVDA and Window Eyes like quickbooks, tax applications like tax act, and so on.I am not going to waste  my time with a company who has no clue how to  optimize their producs  to work without haveot scripting to the moon to get them to work.they should   just work out of the box with the screen reader without all this heavy programming and scripting knowledge. 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Kenny Nead
Sent: Thursday, July 9, 2020 2:44 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA saying unknown again in browsers

 

If you are wondering about Jaws, on the Freedom Scientific web site, you can get Jaws free till the end of August, good way to try the Jaws 2020 out.

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of g melconian
Sent: Thursday, July 9, 2020 4:36 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA saying unknown again in browsers

 

Thast good to know. I think more and more of the windows 10 pro features are all coming to  home versions in some sort or fashion.same like you I have one pro machine for my financial / consulting business. All the others in the house are home windows 10 pcs with NVDA an older version of Window Eyes and JAWS , on them. What can I do and   there is no compeling reason to upgrade to  the latest JAWS as they don’t offer much lately just bells and whistles and gimmicks that I cant se myself using.as I am on business applications an make use of the web JAWS is a pig as far as resources when it comes to the web over  my old Window Eyes or NVDA. 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Kenny Nead
Sent: Thursday, July 9, 2020 2:06 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA saying unknown again in browsers

 

Thank you!

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Brian Vogel
Sent: Thursday, July 9, 2020 3:07 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA saying unknown again in browsers

 

Kenny,

            Unless there is something specific in Pro that you simply must have, I see no compelling reason to change edition from Home to Pro.  It's really a personal choice.  I'd still be on Home except for the fact that I have enough clients on Pro that when I need to troubleshoot something "Pro-specific" it's handy to have one machine that has Pro.  All the other Windows 10 machines in my household are Windows 10 Home.

Cearbhall,

             No great surprise there, and I'm glad that a demonstration has been made of the "intelligence" of the Windows 10 installer.  There was a time where you could actually force update a machine that was displaying the "not quite ready" message in the Windows Update Pane.  This never made the slightest sense to me, as if Microsoft deems the hardware "not ready" it's not ready, and any one of the ways of upgrading to the next Feature Update should detect that, and give a, "Whoa, Nelly!!," type message saying that the update cannot yet be done.

              Whatever method it was you used to try to force it clearly detected the "not ready" state and aborted, as it should.  That is, unless I'm misreading you and you're saying that you manually aborted a force update as soon as you had the opportunity after kicking it off.  In which case, ignore all that came before.
--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Science has become just another voice in the room; it has lost its platform.  Now, you simply declare your own truth.

      ~ Dr. Paul A. Offit, in New York Times article, How Anti-Vaccine Sentiment Took Hold in the United States, September 23, 2019

 

 

Re: NVDA saying unknown again in browsers

Kenny Nead
 

If you are wondering about Jaws, on the Freedom Scientific web site, you can get Jaws free till the end of August, good way to try the Jaws 2020 out.

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of g melconian
Sent: Thursday, July 9, 2020 4:36 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA saying unknown again in browsers

 

Thast good to know. I think more and more of the windows 10 pro features are all coming to  home versions in some sort or fashion.same like you I have one pro machine for my financial / consulting business. All the others in the house are home windows 10 pcs with NVDA an older version of Window Eyes and JAWS , on them. What can I do and   there is no compeling reason to upgrade to  the latest JAWS as they don’t offer much lately just bells and whistles and gimmicks that I cant se myself using.as I am on business applications an make use of the web JAWS is a pig as far as resources when it comes to the web over  my old Window Eyes or NVDA. 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Kenny Nead
Sent: Thursday, July 9, 2020 2:06 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA saying unknown again in browsers

 

Thank you!

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Brian Vogel
Sent: Thursday, July 9, 2020 3:07 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA saying unknown again in browsers

 

Kenny,

            Unless there is something specific in Pro that you simply must have, I see no compelling reason to change edition from Home to Pro.  It's really a personal choice.  I'd still be on Home except for the fact that I have enough clients on Pro that when I need to troubleshoot something "Pro-specific" it's handy to have one machine that has Pro.  All the other Windows 10 machines in my household are Windows 10 Home.

Cearbhall,

             No great surprise there, and I'm glad that a demonstration has been made of the "intelligence" of the Windows 10 installer.  There was a time where you could actually force update a machine that was displaying the "not quite ready" message in the Windows Update Pane.  This never made the slightest sense to me, as if Microsoft deems the hardware "not ready" it's not ready, and any one of the ways of upgrading to the next Feature Update should detect that, and give a, "Whoa, Nelly!!," type message saying that the update cannot yet be done.

              Whatever method it was you used to try to force it clearly detected the "not ready" state and aborted, as it should.  That is, unless I'm misreading you and you're saying that you manually aborted a force update as soon as you had the opportunity after kicking it off.  In which case, ignore all that came before.
--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Science has become just another voice in the room; it has lost its platform.  Now, you simply declare your own truth.

      ~ Dr. Paul A. Offit, in New York Times article, How Anti-Vaccine Sentiment Took Hold in the United States, September 23, 2019

 

 

Re: NVDA saying unknown again in browsers

g melconian
 

Thast good to know. I think more and more of the windows 10 pro features are all coming to  home versions in some sort or fashion.same like you I have one pro machine for my financial / consulting business. All the others in the house are home windows 10 pcs with NVDA an older version of Window Eyes and JAWS , on them. What can I do and   there is no compeling reason to upgrade to  the latest JAWS as they don’t offer much lately just bells and whistles and gimmicks that I cant se myself using.as I am on business applications an make use of the web JAWS is a pig as far as resources when it comes to the web over  my old Window Eyes or NVDA. 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Kenny Nead
Sent: Thursday, July 9, 2020 2:06 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA saying unknown again in browsers

 

Thank you!

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Brian Vogel
Sent: Thursday, July 9, 2020 3:07 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA saying unknown again in browsers

 

Kenny,

            Unless there is something specific in Pro that you simply must have, I see no compelling reason to change edition from Home to Pro.  It's really a personal choice.  I'd still be on Home except for the fact that I have enough clients on Pro that when I need to troubleshoot something "Pro-specific" it's handy to have one machine that has Pro.  All the other Windows 10 machines in my household are Windows 10 Home.

Cearbhall,

             No great surprise there, and I'm glad that a demonstration has been made of the "intelligence" of the Windows 10 installer.  There was a time where you could actually force update a machine that was displaying the "not quite ready" message in the Windows Update Pane.  This never made the slightest sense to me, as if Microsoft deems the hardware "not ready" it's not ready, and any one of the ways of upgrading to the next Feature Update should detect that, and give a, "Whoa, Nelly!!," type message saying that the update cannot yet be done.

              Whatever method it was you used to try to force it clearly detected the "not ready" state and aborted, as it should.  That is, unless I'm misreading you and you're saying that you manually aborted a force update as soon as you had the opportunity after kicking it off.  In which case, ignore all that came before.
--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Science has become just another voice in the room; it has lost its platform.  Now, you simply declare your own truth.

      ~ Dr. Paul A. Offit, in New York Times article, How Anti-Vaccine Sentiment Took Hold in the United States, September 23, 2019

 

 

Re: NVDA saying unknown again in browsers

Kenny Nead
 

Hi, We have 2 computers, a Dell solid state, that I updated it to 2004, it went well, but slow, then my wife has a H P, and we updated it, it went all the way through the update, then messed up when it said to restart it, so we left it at 1909, and now it says it is up to date. So will leave it alone till it gets good and ready. This was several weeks ago.   

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Cearbhall O'Meadhra
Sent: Thursday, July 9, 2020 2:56 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA saying unknown again in browsers

 

Brian,

 

You may be glad to hear that Windows Update refused to complete saying that my PC settings were not ready for version 2004 and declaring that they are working on it and would get there eventually!

 

I have aborted the upgrade and will continue as I am for now.

 

 

All the best,

 

Cearbhall

 

m +353 (0)833323487 Ph: _353 (0)1-2864623 e: cearbhall.omeadhra@...

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
Sent: Thursday, July 9, 2020 4:48 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA saying unknown again in browsers

 

On Thu, Jul 9, 2020 at 08:22 AM, Kenny Nead wrote:

But why not update to 1909?

Unless you happen to have the ISO file for 1909 on hand (or can get it) that's not happening these days.  The Media Creation Tool will always create the ISO (or bootable USB media from the ISO) for the currently released version of Windows 10, which is now 2004.

Also, figuring out what's up here and getting it fixed under 2004 (whether that fix is in NVDA or not), while a pain, is a useful exercise in itself, as it's going to keep occurring if the root cause is not determined.

And Gene's comment earlier this morning echoes what Joseph Lee and myself have been saying for years now on the Windows 10 for Screen Reader users group:  Unless there is something in a feature update that you absolutely need, which seldom if ever occurs, don't elect to apply it in the early days of the roll out.  Even Windows 10 Home Users have the ability now to just not activate that Download and install now link in the Windows Update pane.  Waiting a couple of months is virtually never a bad idea.

It will be interesting to learn what the root cause of this change is, as I wouldn't have thought that an unchanged browser coupled with an unchanged NVDA, even with a new version of Windows 10, would do this.  Signs point to something about Windows 10, though.
 
--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Science has become just another voice in the room; it has lost its platform.  Now, you simply declare your own truth.

      ~ Dr. Paul A. Offit, in New York Times article, How Anti-Vaccine Sentiment Took Hold in the United States, September 23, 2019

 

 

Re: NVDA saying unknown again in browsers

hurrikennyandopo ...
 

Hi Cearbhall


I am running the latest version of Windows 2004 stable and I have no problems with any of the browsers or nvda saying unknown etc even down on the task bar etc.


They say its a big job to upgrade and unless there is a killer feature you need to use the end of the day it is up to the user.


Did you also see the reply from Tyler just in case you missed it?




My guess is this is an instance of #9039. To avoid a lot of back and forth, let's assume it is; if it's not, no harm done.

1. Run the COM Registration Fixing Tool, follow its prompts, and reboot just for good measure. If it fixed it, then great, nothing to worry about and you can stop here.

However if that didn't fix it (which I doubt it would), please do the following, assuming you have an installed copy of NVDA 2019.3 or higher:
1. Press windows+r to open the run dialog.
2. Type nvda
3. Press control shift enter and answer yes to the prompt that appears to run as administrator.
4. When NVDA restarts, open the python console either with NVDA+CTRL+z or in the tools menu.
5. Paste this long line in and hit enter. If you're using teamviewer, I'm not sure how you get the clipboard across; maybe it does it automatically.

import comtypes,ctypes;p=comtypes.typeinfo.LoadTypeLibEx(r"c:\windows\syswow64\oleacc.dll");ctypes.windll.oleaut32.RegisterTypeLib(p,r"c:\windows\syswow64\oleacc.dll", None)

If it says traceback, then the line didn't work, and it may have been pasted incorrectly. In that case, come back here and we'll figure out why.

6. Restart NVDA. Things should work again. If they don't, try rebooting.



They might even be able to roll back windows to a date before it happened and it may do the job.


I did also a while ago see another which was similar but it was when you installed a program called maths some thing where it would let nvda reads maths stuff but can not find a reference to it in the user guide now. When it was used it was good but when it was uninstalled it caused those type of problems as well.


You had to re install it again to fix the problem it caused.


Gene nz

 

On 9/07/2020 11:33 pm, Cearbhall O'Meadhra wrote:

Gene nz,

 

The problem exists on another computer where I am assisting someone to resolve their difficulty. My own PC is running fine. I have been in touch with the Microsoft Accessibility Help desk and it seems that there are some access issues with version 2004 of Windows 10. Would you advise me to install version 2004 or should I keep my current version which is:

Version 1903 (OS Build 18362.900)

 

 

All the best,

 

Cearbhall

 

m +353 (0)833323487 Ph: _353 (0)1-2864623 e: cearbhall.omeadhra@...

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of hurrikennyandopo ...
Sent: Wednesday, July 8, 2020 1:12 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA saying unknown again in browsers

 

Hi

 

You might need some sighted help to do the following.

 

This is off my website and it may depend on the version you are using of nvda.

 

One part is for the older nvda and one for the newer nvda do not enter those details only the lines below each one.

 

Do you know the nvda version?

 

The very last part was for the run com tool but if you have done that and rebooted and it is still playing up look for your version number of nvda.

 

The later one has fixed it also on later versions of windows .

 

hope it helps

 

Troubleshooting - NVDA says “unknown” or “pane” in all of your browsers, Mozilla Thunderbird email client and other places
If for some reason you have problems with NVDA saying “unknown” or “pane” check for the following symptoms:

In all of your browsers, or the Mozilla Thunderbird email client, no matter what you do, you still hear “unknown” or “pane”.

In the browser, email client and other menus you notice you cannot get into your menus, or you are unable to use the quick navigation keys

When you have been told the page is loaded and notice strange behaviour

Mozilla Thunderbird saying unknown while you try to navigate it

Your applications key does not work with it being spoken out and other strange behaviour in Windows

The running applications icons are not being spoken out
It might be a good idea to do the following:
Please note: If you are hearing “unknown” or “pane” (as discussed above) NVDA might seem like it is still working properly but it may not be completely in Windows and other programmes.
You could try the following solution which will allow you to re-register your dll files in case they are causing the problem.
Press the Windows key then type the following into the search box. Type in “command prompt”. Once you have located command prompt, in the search results, press the Applications key to bring up the context menu. Arrow down to select “run as administrator” and press the Enter key. This will take you to a command prompt window. This will not be spoken out. You may need sighted assistance for this.
Type in the following command/s:
Old NVDA, Pre 2019.3
import comtypes,ctypes;p=comtypes.typeinfo.LoadTypeLibEx(r"c:\windows\syswow64\oleacc.dll");ctypes.windll.oleaut32.RegisterTypeLib(p,ur"c:\windows\syswow64\oleacc.dll", None)
Current NVDA 2019.3 onward
import comtypes,ctypes;p=comtypes.typeinfo.LoadTypeLibEx(r"c:\windows\syswow64\oleacc.dll");ctypes.windll.oleaut32.RegisterTypeLib(p,r"c:\windows\syswow64\oleacc.dll", None)

This should re-register all components in the system32 folder.
When it is finished, you can close the command prompt window with the Alt + F4 key. You should notice now where NVDA was saying “unknown” as in some examples given, NVDA should now read the icons in the running applications area of Windows, speak the content of the webpage and menus, and also in Mozilla Thunderbird and other places in Windows including the Windows applications context menu.
Run COM Registration Fixing tool
If you are getting any of the following problems below - with Windows unregistering some of the files needed by NVDA - the following tool section in NVDA will get you out of trouble. To access this tool press the NVDA key + letter N while NVDA is running. Arrow down to the tools menu. A submenu will come up. Arrow down to the menu called Run COM Registration Fixing tool... then press the Enter key.  It should register the files needed by NVDA.

 

 

Gene nz

 

On 8/07/2020 9:40 am, Cearbhall O'Meadhra wrote:

Hi,

 

Just as in 2018 under issue #33784  NVDA says unknown instead of reading any content in Firefox and Chrome. It does work in Edge. All latest version of windows 10, Firefox, Google Chrome, Easy keys, and NVDA 2020.1.

 

The earlier issue seemed to relate to a windows update but I dont think there was an update in this case today.

 

Can anyone point to a solution? This problem began only about one week ago.

 

All the best,

 

Cearbhall

 

m +353 (0)833323487 Ph: _353 (0)1-2864623 e: cearbhall.omeadhra@...

 

 

Re: NVDA saying unknown again in browsers

Kenny Nead
 

Thank you!

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Brian Vogel
Sent: Thursday, July 9, 2020 3:07 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA saying unknown again in browsers

 

Kenny,

            Unless there is something specific in Pro that you simply must have, I see no compelling reason to change edition from Home to Pro.  It's really a personal choice.  I'd still be on Home except for the fact that I have enough clients on Pro that when I need to troubleshoot something "Pro-specific" it's handy to have one machine that has Pro.  All the other Windows 10 machines in my household are Windows 10 Home.

Cearbhall,

             No great surprise there, and I'm glad that a demonstration has been made of the "intelligence" of the Windows 10 installer.  There was a time where you could actually force update a machine that was displaying the "not quite ready" message in the Windows Update Pane.  This never made the slightest sense to me, as if Microsoft deems the hardware "not ready" it's not ready, and any one of the ways of upgrading to the next Feature Update should detect that, and give a, "Whoa, Nelly!!," type message saying that the update cannot yet be done.

              Whatever method it was you used to try to force it clearly detected the "not ready" state and aborted, as it should.  That is, unless I'm misreading you and you're saying that you manually aborted a force update as soon as you had the opportunity after kicking it off.  In which case, ignore all that came before.
--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Science has become just another voice in the room; it has lost its platform.  Now, you simply declare your own truth.

      ~ Dr. Paul A. Offit, in New York Times article, How Anti-Vaccine Sentiment Took Hold in the United States, September 23, 2019

 

 

NVDA and AVG antivirus paid version

Hettie
 

Hi all

Is there an add-on for the paid version of AVG antivirus?

Thanks


Hettie



--
This email has been checked for viruses by AVG.
https://www.avg.com

Re: NVDA saying unknown again in browsers

 

Kenny,

            Unless there is something specific in Pro that you simply must have, I see no compelling reason to change edition from Home to Pro.  It's really a personal choice.  I'd still be on Home except for the fact that I have enough clients on Pro that when I need to troubleshoot something "Pro-specific" it's handy to have one machine that has Pro.  All the other Windows 10 machines in my household are Windows 10 Home.

Cearbhall,

             No great surprise there, and I'm glad that a demonstration has been made of the "intelligence" of the Windows 10 installer.  There was a time where you could actually force update a machine that was displaying the "not quite ready" message in the Windows Update Pane.  This never made the slightest sense to me, as if Microsoft deems the hardware "not ready" it's not ready, and any one of the ways of upgrading to the next Feature Update should detect that, and give a, "Whoa, Nelly!!," type message saying that the update cannot yet be done.

              Whatever method it was you used to try to force it clearly detected the "not ready" state and aborted, as it should.  That is, unless I'm misreading you and you're saying that you manually aborted a force update as soon as you had the opportunity after kicking it off.  In which case, ignore all that came before.
--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Science has become just another voice in the room; it has lost its platform.  Now, you simply declare your own truth.

      ~ Dr. Paul A. Offit, in New York Times article, How Anti-Vaccine Sentiment Took Hold in the United States, September 23, 2019

 

 

Re: NVDA saying unknown again in browsers

Cearbhall O'Meadhra
 

Brian,

 

You may be glad to hear that Windows Update refused to complete saying that my PC settings were not ready for version 2004 and declaring that they are working on it and would get there eventually!

 

I have aborted the upgrade and will continue as I am for now.

 

 

All the best,

 

Cearbhall

 

m +353 (0)833323487 Ph: _353 (0)1-2864623 e: cearbhall.omeadhra@...

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
Sent: Thursday, July 9, 2020 4:48 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA saying unknown again in browsers

 

On Thu, Jul 9, 2020 at 08:22 AM, Kenny Nead wrote:

But why not update to 1909?

Unless you happen to have the ISO file for 1909 on hand (or can get it) that's not happening these days.  The Media Creation Tool will always create the ISO (or bootable USB media from the ISO) for the currently released version of Windows 10, which is now 2004.

Also, figuring out what's up here and getting it fixed under 2004 (whether that fix is in NVDA or not), while a pain, is a useful exercise in itself, as it's going to keep occurring if the root cause is not determined.

And Gene's comment earlier this morning echoes what Joseph Lee and myself have been saying for years now on the Windows 10 for Screen Reader users group:  Unless there is something in a feature update that you absolutely need, which seldom if ever occurs, don't elect to apply it in the early days of the roll out.  Even Windows 10 Home Users have the ability now to just not activate that Download and install now link in the Windows Update pane.  Waiting a couple of months is virtually never a bad idea.

It will be interesting to learn what the root cause of this change is, as I wouldn't have thought that an unchanged browser coupled with an unchanged NVDA, even with a new version of Windows 10, would do this.  Signs point to something about Windows 10, though.
 
--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Science has become just another voice in the room; it has lost its platform.  Now, you simply declare your own truth.

      ~ Dr. Paul A. Offit, in New York Times article, How Anti-Vaccine Sentiment Took Hold in the United States, September 23, 2019