I might have missed something here, but shouldn't the screen saver only
come on after there is no activity on the PC for awhile? I know we had an
issue at one time where if you were reading a particularly long piece of
text (which took longer to read than the timeout for the screensaver) it
would stop reading when the screensaver starter. I think we actually
resolved that one, but that's about the only instance I can think of where
the screensaver should cause a problem?

The only other "screensaver" type thing which can be problematic, is there
are a few "distributed computing" programs around now like BOINC and
Folding @ Home and others. They use your computer's idle time (when the
processor isn't busy doing anything else) to compute various things from
finding cures for cancer (or Covid_19), to searching for alien life and
anything else you can think of which would take a lot of computing power.
Sometimes those programs will keep trying to use processing power even when
you are using the PC, and this can cause significant degradation of
performance with screenreaders (and even in general without using a
screenreader).

Otherwise, I'd be interested to learn more about the screenreader causing
problems.

Quentin.

On Tue, Oct 20, 2020 at 1:11 AM Chris Smart <ve3rwj@winsystem.org> wrote:

I just got an error trying that at the Windows 10 CLI:

"set invalid alias verb"


Please advise.


Chris



On 2020-10-19 4:55 a.m., Martin O'Sullivan wrote:

Well I have managed to resolve the problem.

I used the following command to give NVDA a Realtime priority on the

system.

wmic process where name="nvda.exe" CALL set priority 256

NVDA is working faster than it ever did.

The reason I was using task manager is that NVDA was slow.

I also found out why NVDA was slow. Looks like my company is running

some sort of data processing screen saver in the background (World
Community Grid) which is working on testing for bloody covid. So, I am
giving NVDA higher priority than a deadly virus.

--
Quentin Christensen
Training and Support Manager

Web: www.nvaccess.org
Training: https://www.nvaccess.org/shop/
Certification: https://certification.nvaccess.org/
User group: https://nvda.groups.io/g/nvda
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess <https://twitter.com/NVAccess>;

Well I have managed to resolve the problem.

I used the following command to give NVDA a Realtime priority on the system.

wmic process where name="nvda.exe" CALL set priority 256

NVDA is working faster than it ever did.

The reason I was using task manager is that NVDA was slow.

I also found out why NVDA was slow.  Looks like my company is running some sort of data processing screen saver in the background (World Community Grid) which is working on testing for bloody covid.  So, I am giving NVDA higher priority than a deadly virus.

Well I have managed to resolve the problem.

I used the following command to give NVDA a Realtime priority on the system.

wmic process where name="nvda.exe" CALL set priority 256

NVDA is working faster than it ever did.

The reason I was using task manager is that NVDA was slow.

I also found out why NVDA was slow.  Looks like my company is running some sort of data processing screen saver in the background (World Community Grid) which is working on testing for bloody covid.  So, I am giving NVDA higher priority than a deadly virus.

Well I have managed to resolve the problem.

I used the following command to give NVDA a Realtime priority on the system.

wmic process where name="nvda.exe" CALL set priority 256

NVDA is working faster than it ever did.

The reason I was using task manager is that NVDA was slow.

I also found out why NVDA was slow.  Looks like my company is running some sort of data processing screen saver in the background (World Community Grid) which is working on testing for bloody covid.  So, I am giving NVDA higher priority than a deadly virus.

Imo the new task manager is much better. I used to use Process Explorer instead of the old (so called classic) task manager, but I don't bother with it much anymore (well, it also doesn't work great with nVDA, to be fair...)
I did notice that there were huge and annoying lag for my screen-readers (never tried narrator though) with both task manager and settings apps...I mean, having to wait five or six seconds between a key press and speech output. Thankfully this "went away' several windows updates back, though I'm not really sure when.


-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Chris Smart
Sent: October 16, 2020 12:29 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA With Task Manager

That's true about slower machines. There is an alternative though, a utility that can get classic old Task Manager in Windows 10 back.

https://winaero.com/get-classic-old-task-manager-in-windows-10/

Sorry should have mentioned that I have tried 3 synths, and they were all the same. 

I have also tried no speech, and got someone with site to watch as I used the computer and it was still lagging.

I turned the speech viewer tool on , and the sited person was able to see that most of the time that the computer would move the cursor, and then NVDA would output speech after a delay.

I went into windows settings and gave the following files  high performance on the Graphics performance settings.

nvda.exe

nvda_eoaProxy.exe

nvda_noUIAccess.exe

nvda_slave.exe

nvda_uiAccess.exe

If NVDA is not running the performance of the computer is not much different.  That is the computer seems to perform ok, however there is a delay from NVDA.

And here is another problem, which seems to me to be related.

Every so often NVDA will read the previous line and it will only read the line which I am on correctly once  I actually highlight that line.

There is no other way of getting it to read the line, it just will not read that text. Like never and I mean  never just will not read it.  It sees  the text in one line as another.  This is very hard to explain,

However, if you had one line which had the word cat, and another line which had the word dog,

Nvda would read the line which said cat, then you would arrow down to the line with the word dog, and nvda would say cat.

This problem  is intermittent. .

I just need it to go faster.

On Oct 16, 2020, at 5:59 AM, Martin O'Sullivan <osumartin@...> wrote:



Sorry should have mentioned that I have tried 3 synths, and they were all the same. 

I have also tried no speech, and got someone with site to watch as I used the computer and it was still lagging.

 

I turned the speech viewer tool on , and the sited person was able to see that most of the time that the computer would move the cursor, and then NVDA would output speech after a delay.

 

I went into windows settings and gave the following files  high performance on the Graphics performance settings.

 

nvda.exe

nvda_eoaProxy.exe

nvda_noUIAccess.exe

nvda_slave.exe

nvda_uiAccess.exe

 

If NVDA is not running the performance of the computer is not much different.  That is the computer seems to perform ok, however there is a delay from NVDA.

 

And here is another problem, which seems to me to be related.

 

Every so often NVDA will read the previous line and it will only read the line which I am on correctly once  I actually highlight that line.

 

There is no other way of getting it to read the line, it just will not read that text. Like never and I mean  never just will not read it.  It sees  the text in one line as another.  This is very hard to explain,

However, if you had one line which had the word cat, and another line which had the word dog,

Nvda would read the line which said cat, then you would arrow down to the line with the word dog, and nvda would say cat.

This problem  is intermittent. .

 

 

I just need it to go faster.