|
Re: confused
Gene
I saw that but I thought you were sayng that you
would repair Windows as a first option. Evidently, you weren't saying
that.
I don't recall what corrected the problem, though I
recall seeing a message about it perhaps two days ago.
Gene
----- Original Message -----
----- Original Message -----
But running the registration fixing tool is fast and easy and would take much less time than the Windows correcting procedures.Which, Gene, as I and the original poster have already stated, has been done, at least once and now possibly twice, to no effect. See: https://nvda.groups.io/g/nvda/message/68112 including the quote of Tyler's suggestion at the bottom. Doing it again is not likely to have any effect. We're now on to plans B, C, D, etc. -- Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363 Most of the change we think we see in life is due to truths being in and out of favor. ~ Robert Frost, The Black Cottage (1914)
|
|
|
|
Re: confused
On Fri, Dec 27, 2019 at 12:14 PM, Gene wrote:
But running the registration fixing tool is fast and easy and would take much less time than the Windows correcting procedures.Which, Gene, as I and the original poster have already stated, has been done, at least once and now possibly twice, to no effect. See: https://nvda.groups.io/g/nvda/message/68112 including the quote of Tyler's suggestion at the bottom. Doing it again is not likely to have any effect. We're now on to plans B, C, D, etc. -- Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363 Most of the change we think we see in life is due to truths being in and out of favor. ~ Robert Frost, The Black Cottage (1914)
|
|
|
|
Re: confused
Jackie
Hey Robert, just for the halibut, does Narrator perform likewise?
toggle quoted messageShow quoted text
On 12/27/19, Gene <gsasner@gmail.com> wrote:
But running the registration fixing tool is fast and easy and would take --
Subscribe to a WordPress for Newbies Mailing List by sending a message to: wp4newbs-request@freelists.org with 'subscribe' in the Subject field OR by visiting the list page at http://www.freelists.org/list/wp4newbs & check out my sites at www.brighter-vision.com & www.mysitesbeenhacked.com
|
|
|
|
Re: confused
Gene
But running the registration fixing tool is fast
and easy and would take much less time than the Windows correcting
procedures.
If the problem were only the treeview, it would be
unlikely to correct it, but when browser problems that are typical of
unregistered dll files started to be discussed, then I think that should have
been tried first.
Gene
Gene
----- Original Message -----
I cannot discount Tyler’s comment though, as whatever he did cured it.And I'm not, either, but I am always one who takes the "path of least resistance" first. I've just seen too many problems, of too many varieties, never be fixable except by trying to clean up Windows first, so I always do that since it's simple. If that doesn't work then I'll go into under the hood digging. -- Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363 Most of the change we think we see in life is due to truths being in and out of favor. ~ Robert Frost, The Black Cottage (1914)
|
|
|
|
Re: confused
On Fri, Dec 27, 2019 at 12:03 PM, Joseph Lee wrote:
I cannot discount Tyler’s comment though, as whatever he did cured it.And I'm not, either, but I am always one who takes the "path of least resistance" first. I've just seen too many problems, of too many varieties, never be fixable except by trying to clean up Windows first, so I always do that since it's simple. If that doesn't work then I'll go into under the hood digging. -- Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363 Most of the change we think we see in life is due to truths being in and out of favor. ~ Robert Frost, The Black Cottage (1914)
|
|
|
|
Re: confused
Hi, I cannot discount Tyler’s comment though, as whatever he did cured it. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
I have merged the "more confused" topic into this one as they are about one and the same machine and issue. Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363 Most of the change we think we see in life is due to truths being in and out of favor. ~ Robert Frost, The Black Cottage (1914)
|
|
|
|
Re: confused
I have merged the "more confused" topic into this one as they are about one and the same machine and issue.
Joseph, the OP indicates they've tried the COM registration fixing tool with no change, but that was in the former "more confused" topic that's now merged with this one. I stand by my suggestions at this juncture as appropriate first steps in light of the tool already having been run and failed. Using SFC/DISM or doing a Repair Install risks nothing. At worst it doesn't work. -- Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363 Most of the change we think we see in life is due to truths being in and out of favor. ~ Robert Frost, The Black Cottage (1914)
|
|
|
|
Re: confused
Hi, Or perhaps a corrupt DLL registration, something Tyler talked about earlier as he noted a few moments ago, Let’s try that first, and if that doesn’t work, a restore is in order. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
On Fri, Dec 27, 2019 at 05:14 AM, David Griffith wrote:
I would be inclined to agree, but only if the two things I suggested earlier, which are less aggressive, don't fix the issue:
Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363 Most of the change we think we see in life is due to truths being in and out of favor. ~ Robert Frost, The Black Cottage (1914)
|
|
|
|
Re: confused
On Fri, Dec 27, 2019 at 05:14 AM, David Griffith wrote:
I would be tempted to do a Windows Re-install with all these difficulties with the core functioning of my main screenreader.I would be inclined to agree, but only if the two things I suggested earlier, which are less aggressive, don't fix the issue:
-- Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363 Most of the change we think we see in life is due to truths being in and out of favor. ~ Robert Frost, The Black Cottage (1914)
|
|
|
|
winamp is invisible with extention
ken lawrence
Hi list I have continued to fiddle with the NVDA reenabling the winamp extention then removing it and reinstalling it but still it is as if NVDA can’t see. The functionality is still there but arrowing up or down just see “list item. Insirt t does’t talk it can’t read anything on my computer with1.2 installed. And I can’t mute or change volume or view how must time is left in a song without the winamp extention. I can’t believe it’s just my computer. Should I wait and update windows 10 to the 1909 version and then try it? As mentioned it ca’t even tell me I’m sitting on winamp with the extention. If I prep a show in advance I like to use winamp because I have better control of hearing what sounds right with what. I can’t believe it’s just me what is wrong with 1.2 winamp extention?
Sent from Mail for Windows 10
|
|
|
|
Re: confused
Robert Doc Wright godfearer
I don’t know if its getting worse. I pressed windows x and nothing was announced. But it was there because I then pressed u then r and it restarted even though NVDA said not a word.
****** character is found in how you treat people who cannot do anything for you!
From: Gene
Sent: Friday, December 27, 2019 3:19 AM To: nvda@nvda.groups.io Subject: Re: [nvda] more confusion
Run the COM Registration Fixing tool in the tools submenu of the NVDA menu. That may solve all your problems. It registers some dll files that may become unregistered for one reason or another and which must be registered for NVDA to perform properly.
Gene ---[—Original Message ----- Sent: Thursday, December 26, 2019 9:13 PM Subject: [nvda] more confusion
Now when I go to chrome it only says unknown. In IE it only reads the title bar. In Edge I get a little more but it drags a lot before saying anything.
****** character is found in how you treat people who cannot do anything for you!
|
|
|
|
Re: confused
Robert Doc Wright godfearer
I’ll try it again. I ran it before with no noticeable results.
****** character is found in how you treat people who cannot do anything for you!
From: Gene
Sent: Friday, December 27, 2019 3:19 AM To: nvda@nvda.groups.io Subject: Re: [nvda] more confusion
Run the COM Registration Fixing tool in the tools submenu of the NVDA menu. That may solve all your problems. It registers some dll files that may become unregistered for one reason or another and which must be registered for NVDA to perform properly.
Gene ---[—Original Message ----- Sent: Thursday, December 26, 2019 9:13 PM Subject: [nvda] more confusion
Now when I go to chrome it only says unknown. In IE it only reads the title bar. In Edge I get a little more but it drags a lot before saying anything.
****** character is found in how you treat people who cannot do anything for you!
|
|
|
|
Re: confused
Tyler Spivey
If the COM Registration Fixing tool doesn't work, then you've hit an issue
toggle quoted messageShow quoted text
that I reported a while ago but nobody fixed yet. Anyone who wants to walk him through fixing it search for mathplayer in the issues and have at it. I can't come up with a list of steps right now, but I'm 99% sure that given the symptoms, that'll fix it. The Python Console command in the issue description will work (as long as NVDA is elevated).
On Fri, Dec 27, 2019 at 04:19:35AM -0600, Gene wrote:
Run the COM Registration Fixing tool in the tools submenu of the NVDA menu. That may solve all your problems. It registers some dll files that may become unregistered for one reason or another and which must be registered for NVDA to perform properly.
|
|
|
|
Re: confused
Gene
Run the COM Registration Fixing tool in the tools submenu of the NVDA
menu. That may solve all your problems. It registers some dll files
that may become unregistered for one reason or another and which must be
registered for NVDA to perform properly.
Gene
---[—Original Message -----
Sent: Thursday, December 26, 2019 9:13 PM
Subject: [nvda] more confusion Now when I go to chrome it only says unknown. In IE it only reads the title bar. In Edge I get a little more but it drags a lot before saying anything.
****** character is found in how you treat people who cannot do anything for you!
|
|
|
|
Re: confused
David Griffith
I would be tempted to do a Windows Re-install with all these difficulties with the core functioning of my main screenreader. However assuming that you want to stick with your setup and do not want to switch to using Explorer ++ the way I have coped with NVDA difficulties with File Explorer in the past was to switch to Narrator with control windows enter until NVDA started responding again. The situation is better now but for a long time NVDA was pretty dreadful with File Explorer for me, taking ages and ages to recognise and respond to any files in a file explorer list. Not just sluggish but completely unresponsive. In those situations I simply switched to Narrator and used that with File Explorer. Unlike NVDA Narrator would instantly start reading the necessary filenames as you cursor down. I continued like this until NVDA decided to wake up again. As soon as NVDA was responding again I would turn Narrator off again with control windows enter and revert to using NVDA solely. You could try the same approach with your File Explorer Drive tree. David Griffith
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Robert Doc Wright godfearer
Sent: 27 December 2019 07:28 To: nvda@nvda.groups.io Subject: Re: [nvda] confused
I use the tree view to get to places quickly. Aside from drive C I have E, F, H, K, and N as well as needing to get to Dropbox quickly. Can you imagine all the backspacing I would have to do?
****** character is found in how you treat people who cannot do anything for you!
From: Gene
Its interesting. You have established that the tree view is workihng properlhy but that NVDA isn’t recognizing it. Are you pursuing this because you particularly want to use the tree view instead of the list view or just as a matter of curiosity and interest?
Gene ----- Original Message ----- Sent: Thursday, December 26, 2019 5:32 PM Subject: Re: [nvda] confused
Here is an update. I discovered that when I shift tab to where the tree view is suppose to be and I know the first two letters of where I am trying to get to I find I am in the correct place. Even though nothing is announced until I tab to the item view and voila! I’m in the right place. So the tree view is there but NVDA is not announcing where I am.
****** character is found in how you treat people who cannot do anything for you!
From: Gene
I just looked at the setting in the advanced category. I don't think it applies, but if the check box is checked, uncheck it. I doubt you ever changed the setting but I was trying to think of something that might apply.
Also, though I don't think it would make any difference, have you tried changing the window, maximizing it if it isn't, or restoring it if it isn't?
Gene ----- Original Message -----
Is the item view the same as a list view? If so, you can use it very efficiently and, I prefer the list view because nothing automatically opens. Simply back space to move up one level and press enter to open something like a drive or a folder.
]Gene ----- Original Message ----- Sent: Thursday, December 26, 2019 6:46 AM Subject: [nvda] confused
I have downgraded to 2019.2 and I still get the same result. When I open file explorer and shift tab from the item view to what should be the tree view NVDA does not speak. If I shift tab again it says Cortana. When I turn NVDA off and open JAWS the tree view is there. Two weeks ago everything was fine. I have even uninstalled NVDA and reinstalled and get the same results. On my laptop which is also running NVDA2019.2.1 it is working just fine in this area. The only major thing that I have done in this time period is to upgrade Windows to Version 1909 OS build 18365.535. I am running the same version and build on the laptop but not having this problem in file explorer there. ****** character is found in how you treat people who cannot do anything for you!
|
|
|
|
Re: confused
Robert Doc Wright godfearer
I use the tree view to get to places quickly. Aside from drive C I have E, F, H, K, and N as well as needing to get to Dropbox quickly. Can you imagine all the backspacing I would have to do?
****** character is found in how you treat people who cannot do anything for you!
From: Gene
Sent: Thursday, December 26, 2019 5:39 PM To: nvda@nvda.groups.io Subject: Re: [nvda] confused
Its interesting. You have established that the tree view is workihng properlhy but that NVDA isn’t recognizing it. Are you pursuing this because you particularly want to use the tree view instead of the list view or just as a matter of curiosity and interest?
Gene ----- Original Message ----- Sent: Thursday, December 26, 2019 5:32 PM Subject: Re: [nvda] confused
Here is an update. I discovered that when I shift tab to where the tree view is suppose to be and I know the first two letters of where I am trying to get to I find I am in the correct place. Even though nothing is announced until I tab to the item view and voila! I’m in the right place. So the tree view is there but NVDA is not announcing where I am.
****** character is found in how you treat people who cannot do anything for you!
From: Gene
I just looked at the setting in the advanced category. I don't think it applies, but if the check box is checked, uncheck it. I doubt you ever changed the setting but I was trying to think of something that might apply.
Also, though I don't think it would make any difference, have you tried changing the window, maximizing it if it isn't, or restoring it if it isn't?
Gene ----- Original Message -----
Is the item view the same as a list view? If so, you can use it very efficiently and, I prefer the list view because nothing automatically opens. Simply back space to move up one level and press enter to open something like a drive or a folder.
]Gene ----- Original Message ----- Sent: Thursday, December 26, 2019 6:46 AM Subject: [nvda] confused
I have downgraded to 2019.2 and I still get the same result. When I open file explorer and shift tab from the item view to what should be the tree view NVDA does not speak. If I shift tab again it says Cortana. When I turn NVDA off and open JAWS the tree view is there. Two weeks ago everything was fine. I have even uninstalled NVDA and reinstalled and get the same results. On my laptop which is also running NVDA2019.2.1 it is working just fine in this area. The only major thing that I have done in this time period is to upgrade Windows to Version 1909 OS build 18365.535. I am running the same version and build on the laptop but not having this problem in file explorer there. ****** character is found in how you treat people who cannot do anything for you!
|
|
|
|
Re: confused
Robert Doc Wright godfearer
The problem still exists. I noticed that when I press windows +t to bring up the task bar it says unknown there too. I have done the following: Run restore Uninstalled NVDA Deleted the NVDA folder in app-data\roaming Downgraded to 2019.2 There is no change.
Is there something else I should have deleted after uninstalling to make sure NVDA was completely removed?
****** character is found in how you treat people who cannot do anything for you!
From: Joseph Lee
Sent: Thursday, December 26, 2019 8:48 PM To: nvda@nvda.groups.io Subject: Re: [nvda] more confusion
Hi, Try the following in the order shown:
Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Robert Doc Wright godfearer
Now when I go to chrome it only says unknown. In IE it only reads the title bar. In Edge I get a little more but it drags a lot before saying anything.
****** character is found in how you treat people who cannot do anything for you!
|
|
|
|
Re: confused
Hi, Try the following in the order shown:
Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Robert Doc Wright godfearer
Sent: Thursday, December 26, 2019 7:14 PM To: nvda@nvda.groups.io Subject: [nvda] more confusion
Now when I go to chrome it only says unknown. In IE it only reads the title bar. In Edge I get a little more but it drags a lot before saying anything.
****** character is found in how you treat people who cannot do anything for you!
|
|
|
|
confused
Robert Doc Wright godfearer
Now when I go to chrome it only says unknown. In IE it only reads the title bar. In Edge I get a little more but it drags a lot before saying anything.
****** character is found in how you treat people who cannot do anything for you!
|
|
|
|
Re: Announcing Capital Letters
Gene
It isn’t a question of right or wrong. Your synthesizer may respond,
or respond as you wish at fifthy percent. But Eloquence users would find
fifthy percent to be very piercing and extremely exaggerated. It depends
on the synthesizer, so I don’t suggest or prescribe a general setting.
Gene
----- Original Message -----
From: Chris Mullins
Sent: Thursday, December 26, 2019 5:47 PM
Subject: Re: [nvda] Announcing Capital Letters Hi Maybe I've been doing it wrong all these years then. I use 50% to make it obvious because I find 30% can be indistinct in some cases. At least when Colin experiences the output for whatever synthesizer he uses, I'm sure he is capable of adjusting the setting to his personal preference. Cheers Chris On 26/12/2019, Gene <gsasner@...> wrote: > That is not correct. Fifty percent is extrremely too high pitched for some > synthesizers. It may be alright for others. the default is 30 percent and > I wouldn't assume that that is remotely correct for a lot of synthesizers. > also, these settings are all on by default and they don't change from one > synthesizer to another. It is very unlikely that a new user would turn them > off. Therefore, the problem is very likely related to the synthesizer or > some problem with the NVDA installation. > > Gene > ----- Original Message ----- > > From: Chris Mullins > Sent: Thursday, December 26, 2019 3:04 PM > To: nvda@nvda.groups.io > Subject: Re: [nvda] Announcing Capital Letters > > > Hi > Use NVDA+Control+k to open the Keyboard settings dialog and ensure the > check box entitled "Beep if typing lowercase when caps lock is on" is > checked. This will cause a beep to sound if you type a shifted > letter, giving you a big clue that caps lock is on." > Secondly, for each synthesizer you use, press NVDA+Control+v to open > the Voice Settings dialog and ensure the edit box entitled "Capital > pitch change perCentage" is set to at least 50% This will make it > obvious that you are typing a capital letter or reviewing one when > reading letter by letter. Note: Ensure you have "Speak typed > characters" active (NVDA+NumRow 2) to get this feedback when typing. > > Cheers > Chris > > On 26/12/2019, Gene <gsasner@...> wrote: >> I suspect you are using the illegal add-on which isn’t supported on the >> list. the list can’t, for legal reasons, support oor assist in using >> such >> software. If you want Eloquence that functions properlhy, you can >> ppurchase >> either an add-on for it or an MSAPI version of Eloquence. I and other >> list >> members would be happy to provide more information. You can try demos of >> both, if you wish. >> >> Meantime, trhy switching to another synthesizer to see if capital >> notification works properly. >> >> Gene >> ----- Original Message ----- >> From: Colin Phelan >> Sent: Thursday, December 26, 2019 12:58 PM >> To: nvda@nvda.groups.io >> Subject: Re: [nvda] Announcing Capital Letters >> >> You might be onto something there I am using eloquence which did not come >> as >> part of the initial NVDA download thoughts welcome and thanks Colin >> >> >> >> On 26 Dec 2019, at 6:44 pm, Gene <gsasner@...> wrote: >> >> >> You should hear a beep if the caps lock is on and you use the shift key >> and type a letter. NVDA by default raises the pitch of capital letters. >> If >> you don’t hear that, what synthesizer are you using. The first thing we >> need to determine is whether the problem is a limitation of the >> synthesizer >> or some problem perhaps with the NVDA installation. >> >> Gene >> ----- Original Message ----- >> From: Colin Phelan >> Sent: Thursday, December 26, 2019 12:33 PM >> To: nvda@nvda.groups.io >> Subject: [nvda] Announcing Capital Letters >> >> I am new to NVDA and recognise this is a basic question, however, I >> cannot >> seem to get NVDA to give me feedback with regard to if I am typing >> capital >> letters which is a concern as caps lock may be on by accident. >> >> Please confirm settings to be ticked and how to ensure settings are >> saved >> in case this is the issue. >> >> Thanks >> >> Colin >> >> >> >> >> >> >> > > > > > >
|
|
|