And even though they're not from NVAccess, member Thee Quinn has produced a number of YouTube tutorials on using NVDA.  They're well worth checking out.

Thee Quinn's Channel on YouTube
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

The difference between a top-flight creative man and the hack is his ability to express powerful meanings indirectly.

         ~ Vance Packard

Just to let you all know I remember Debbie Scales very well.  I loved her nvda lists how ever I am very sad she passed away.

The reason I say its up to you. I learned from Debbie Scales that if you are going to test a beta screen reader you should have an old copy of the last version kicking around so you know there’s bugs.  I tested Jaws 5.0 that’s why you need to have a more stable version of your screen reader should you run a muck. Debbie Scales used to run a jaws list. She’d probably say its up to you.

 

Sent from Mail for Windows

 

From: Arlene via groups.io
Sent: November 27, 2021 12:13 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2021.2 - Error when checking for updates

 

That depends on you. You can install the beta and put it into a different folder. Some people say you shouldn’t install over a copy. If you are testing for bugs. If you are using it just for your own purposes and don’t want to test for bugs then go ahead. If you want to test for them its not  a good idea.  If you are a beta tester you shouldn’t do it.  That way you can better test for bugs.  Bryan might have his own ideas. I say its up to you.

 

Sent from Mail for Windows

 

From: Gtt North Bay
Sent: November 27, 2021 12:02 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2021.2 - Error when checking for updates

 

Brian,

Can I install the beta over the point 2 or do I need to uninstall 2021.2 first.

 

Thanks,

Brian B.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
Sent: Saturday, November 27, 2021 2:54 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2021.2 - Error when checking for updates

 

You're new, so will not have seen several previous conversations, but this is indeed a bug and it's been resolved with 2021.3.

I would, at this point, strongly suggest you just update to NVDA 2021.3beta2, as it's been working fine, fixes the problem, and will likely go to release candidate status shortly.  But even if you were to have issues with the beta and rolled back to 2021.2, what it fixes in regard to the update issue stays fixed, as it's external to NVDA itself and the fix made stays.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

The difference between a top-flight creative man and the hack is his ability to express powerful meanings indirectly.

         ~ Vance Packard

 

 

 

The reason I say its up to you. I learned from Debbie Scales that if you are going to test a beta screen reader you should have an old copy of the last version kicking around so you know there’s bugs.  I tested Jaws 5.0 that’s why you need to have a more stable version of your screen reader should you run a muck. Debbie Scales used to run a jaws list. She’d probably say its up to you.

 

Sent from Mail for Windows

 

From: Arlene via groups.io
Sent: November 27, 2021 12:13 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2021.2 - Error when checking for updates

 

That depends on you. You can install the beta and put it into a different folder. Some people say you shouldn’t install over a copy. If you are testing for bugs. If you are using it just for your own purposes and don’t want to test for bugs then go ahead. If you want to test for them its not  a good idea.  If you are a beta tester you shouldn’t do it.  That way you can better test for bugs.  Bryan might have his own ideas. I say its up to you.

 

Sent from Mail for Windows

 

From: Gtt North Bay
Sent: November 27, 2021 12:02 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2021.2 - Error when checking for updates

 

Brian,

Can I install the beta over the point 2 or do I need to uninstall 2021.2 first.

 

Thanks,

Brian B.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
Sent: Saturday, November 27, 2021 2:54 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2021.2 - Error when checking for updates

 

You're new, so will not have seen several previous conversations, but this is indeed a bug and it's been resolved with 2021.3.

I would, at this point, strongly suggest you just update to NVDA 2021.3beta2, as it's been working fine, fixes the problem, and will likely go to release candidate status shortly.  But even if you were to have issues with the beta and rolled back to 2021.2, what it fixes in regard to the update issue stays fixed, as it's external to NVDA itself and the fix made stays.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

The difference between a top-flight creative man and the hack is his ability to express powerful meanings indirectly.

         ~ Vance Packard

 

 

 

Hi folks,

I am new here and well last night I installed 2021.2 on my new to me laptop and this morning I went to help to check for updates and got an error note. Is this a problem with the point 2 or me as my desktop doesn’t have that error.

 

Thanks,

Brian B.

On Thu, May 17, 2018 at 02:06 PM, Kostadin Kolev wrote:

Hello all,

I've noticed this strange behavior after the update of Windows 10 to version 1803. The behavior is the following. When the machine starts and Windows 10 loads, it gets to the lock screen as it should. Initially it all looks normal, but only for a while. Moments after that, the lock screen displays not only the time and date as it normally does, but user-specific information as well (e.g. weather forecast, upcoming alarms, etc.). Not only that, but the NVDA startup sound is heard, as if the desktop copy of NVDA is loaded, even though it should load only when the specific user signs in. I can't tell for sure if the desktop copy of NVDA loads, because my NVDA settings for the desktop and secure screen copies of it are the same. On top of that, the "Ease of access" menu appears and NVDA starts reading its menu items one by one. This happens when I power up the machine with "Fast Boot" enabled. I haven't tried with "Fast Boot" disabled, but when I restart the machine, the behavior described above does not occur. So, it must be related to "Fast Boot" somehow. And this did not occur before the update to version 1803 of Windows 10.

Has anyone else experienced the behavior described above? Have you found any solutions besides turning off "Fast Boot"? Turning off "Fast Boot" is also a solution, but I'd prefer to keep it on if possible.

______
Best wishes,
Kostadin Kolev

That depends on you. You can install the beta and put it into a different folder. Some people say you shouldn’t install over a copy. If you are testing for bugs. If you are using it just for your own purposes and don’t want to test for bugs then go ahead. If you want to test for them its not  a good idea.  If you are a beta tester you shouldn’t do it.  That way you can better test for bugs.  Bryan might have his own ideas. I say its up to you.

Sent from Mail for Windows

Brian,

Can I install the beta over the point 2 or do I need to uninstall 2021.2 first.

Thanks,

Brian B.

You're new, so will not have seen several previous conversations, but this is indeed a bug and it's been resolved with 2021.3.

I would, at this point, strongly suggest you just update to NVDA 2021.3beta2, as it's been working fine, fixes the problem, and will likely go to release candidate status shortly.  But even if you were to have issues with the beta and rolled back to 2021.2, what it fixes in regard to the update issue stays fixed, as it's external to NVDA itself and the fix made stays.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

The difference between a top-flight creative man and the hack is his ability to express powerful meanings indirectly.

         ~ Vance Packard

Brian,

Can I install the beta over the point 2 or do I need to uninstall 2021.2 first.

Thanks,

Brian B.

You're new, so will not have seen several previous conversations, but this is indeed a bug and it's been resolved with 2021.3.

I would, at this point, strongly suggest you just update to NVDA 2021.3beta2, as it's been working fine, fixes the problem, and will likely go to release candidate status shortly.  But even if you were to have issues with the beta and rolled back to 2021.2, what it fixes in regard to the update issue stays fixed, as it's external to NVDA itself and the fix made stays.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

The difference between a top-flight creative man and the hack is his ability to express powerful meanings indirectly.

         ~ Vance Packard

You're new, so will not have seen several previous conversations, but this is indeed a bug and it's been resolved with 2021.3.

I would, at this point, strongly suggest you just update to NVDA 2021.3beta2, as it's been working fine, fixes the problem, and will likely go to release candidate status shortly.  But even if you were to have issues with the beta and rolled back to 2021.2, what it fixes in regard to the update issue stays fixed, as it's external to NVDA itself and the fix made stays.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

The difference between a top-flight creative man and the hack is his ability to express powerful meanings indirectly.

         ~ Vance Packard

On Thu, May 17, 2018 at 02:06 PM, Kostadin Kolev wrote:

Hello all,

I've noticed this strange behavior after the update of Windows 10 to version 1803. The behavior is the following. When the machine starts and Windows 10 loads, it gets to the lock screen as it should. Initially it all looks normal, but only for a while. Moments after that, the lock screen displays not only the time and date as it normally does, but user-specific information as well (e.g. weather forecast, upcoming alarms, etc.). Not only that, but the NVDA startup sound is heard, as if the desktop copy of NVDA is loaded, even though it should load only when the specific user signs in. I can't tell for sure if the desktop copy of NVDA loads, because my NVDA settings for the desktop and secure screen copies of it are the same. On top of that, the "Ease of access" menu appears and NVDA starts reading its menu items one by one. This happens when I power up the machine with "Fast Boot" enabled. I haven't tried with "Fast Boot" disabled, but when I restart the machine, the behavior described above does not occur. So, it must be related to "Fast Boot" somehow. And this did not occur before the update to version 1803 of Windows 10.

Has anyone else experienced the behavior described above? Have you found any solutions besides turning off "Fast Boot"? Turning off "Fast Boot" is also a solution, but I'd prefer to keep it on if possible.

______
Best wishes,
Kostadin Kolev

Hello all,

I've noticed this strange behavior after the update of Windows 10 to version 1803. The behavior is the following. When the machine starts and Windows 10 loads, it gets to the lock screen as it should. Initially it all looks normal, but only for a while. Moments after that, the lock screen displays not only the time and date as it normally does, but user-specific information as well (e.g. weather forecast, upcoming alarms, etc.). Not only that, but the NVDA startup sound is heard, as if the desktop copy of NVDA is loaded, even though it should load only when the specific user signs in. I can't tell for sure if the desktop copy of NVDA loads, because my NVDA settings for the desktop and secure screen copies of it are the same. On top of that, the "Ease of access" menu appears and NVDA starts reading its menu items one by one. This happens when I power up the machine with "Fast Boot" enabled. I haven't tried with "Fast Boot" disabled, but when I restart the machine, the behavior described above does not occur. So, it must be related to "Fast Boot" somehow. And this did not occur before the update to version 1803 of Windows 10.

Has anyone else experienced the behavior described above? Have you found any solutions besides turning off "Fast Boot"? Turning off "Fast Boot" is also a solution, but I'd prefer to keep it on if possible.

______
Best wishes,
Kostadin Kolev

My first questions is, is there any software that a blind highschooler can use in conjunction with NvDA to do their math work?