Re: NVDA sluggishness w/win 10, my experience
Gene
I'm not convinced it is necessary or a good idea to update the BIOS unless
it provides features that are wanted or needed. I'm very doubtful that the
BIOS is causing sluggishness.
Gene
----- Original Message -----
From: Jackie
Sent: Monday, April 06, 2020 7:15 PM
Subject: [nvda] NVDA sluggishness w/win 10, my
experience Ok,
so this is just my experience, & I don't pretend or contend that it's applicable to anyone else who's experienced NVDA sluggishness so severe as to render it unusable. Having thus said, though, it might be something folks might wish to consider when troubleshooting this for themselves. I have a computer I was going to give to my daughter. Unfortunately, it intermittently kept going into bios instead of booting into windows. Resetting the computer didn't help. I therefore suspected either the hard drive or the CMOS battery. Husband Karl took it apart to replace the battery. He never did find 1 (they're starting not to use those anymore), but he did find a cable that seemed to have become detached, which he reconnected. It was still very slow, but at least it didn't go into bios anymore. I then did a 2nd pc reset, removing all user files. Once that was done, it was still really slow, I could just barely use Narrator, &, imo, that's barely usable anyway, though it is much improved from earlier incarnations. Forget about NVDA--it simply was not happening. So the first thing I did was disable 1 drive & Skype from starting up automatically, which tends to occur when signing into windows via a Microsoft account. That sped things up *considerably* & NVDA became quite usable at that point. The bios is 3 versions behind for this machine. Whenever the Windows 10 update finishes (it's a big 1), I'm going to update the bios & pray I don't brick the machine in doing so. At that point I'll see what other driver updates are available. I also think I'm gonna run some hard drive diagnostics to make sure that the hard drive isn't in trouble, though that's beginning to look less likely now than it did a day ago. Despite the first reset, I do think the files were corrupted because of the hardware problems this machine was experiencing, thus necessitating a 2nd one. The machine is still not as fast as I'd like to see it, but it's improving. This was clearly a complex set of issues, but that's actually pretty typical when fixing these beasties--it's fairly seldom that only 1 thing is wrong w/them, at least from my experience, which is about 30 years worth. I think my point is that if NVDA isn't usable on a given machine, it's most likely there's something (or things) wrong w/that machine. Usually, if one thinks about it, the machine is having other difficulties as well, & these, although annoying, may actually help to troubleshoot the problem. If you're getting out of memory errors, for example, then perhaps a ram stick is faulty. If you're getting errors regarding being unable to access files, then perhaps the hard drive is the culprit. Anyway, I hth those who might be having problems w/NVDA on win 10 & who are looking for resolution of the problem. My particular set of circumstances will not be applicable, but perhaps my thought processes might be helpful in spurring yours on toward a successful resolution. Best wishes & much success. Stay well & safe. -- Subscribe to a WordPress for Newbies Mailing List by sending a message to: wp4newbs-request@... 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
|
|