[nvda] Re: When windows is ready...

This is a problem for sited people, too.  I am often annoyed by trying to
run things when windows first starts, because they start slowing, and the
system seems slow and slow to respond.   Many people experience this slow
behavor.  I am not sure how NVDA would ever know that.  Maybe have a program
that waits until your processor usage drops below a certain level, and then
makes a distinctive ding, or something.   However, how many people deal with
this problem is to have less things start at start up.    This will decrease
the time your computer is slow for, at start up.  Also, it maybe increase
you overall speed of the computer, by reducing the amount of stuff you
computer has running in the background.  To do this takes a little bit of
work, but it is really not that bad.  There is three basic ideas, find what
is ran at start up,  find out what those programs do and whether you need
them, then delete the ones you don't need.

You have to edit the registry to do this.  However, the part of the registry
you are working with does not really seem very dangerous to me.

If anyone is actually going to do this, or would like me to tell people how,
let me know.

The process is pretty easy, but writting it out, does not seem worth it, if
no one is interested.

For those of you you know the registry.  The registry directories to check
for run at start up items are:

HKEY_LOCAL_Machine > Software > Microsoft > Windows > Current Version > Run

and

HKEY_CURRENT_USER > Software > Microsoft > Windows > Current Version > Run

If you think a step by think is worth it. I will post it.

Grae

On Thu, May 28, 2009 at 4:02 PM, Zach <chickerland@xxxxxxxxx> wrote:

> another good point. When I know: when the windows-xp-balloon noise happens
> twice, but I don't know what your machine does at start up so there is no
> real way to tell.
> ----- Original Message ----- From: "Brian Gaff Lineone downstairs" <
> bgaff@xxxxxxxxxxx>
> To: <nvda@xxxxxxxxxxxxx>
> Sent: Monday, April 13, 2009 3:06 AM
> Subject: [nvda] When windows is ready...
>
>
> Is there any way to detect when booting up that Windows is truly ready to
>> go? I ask not just for me but from people I talk to. It seems that in XP at
>> least, well after the screenreader has loaded, things are going on that make
>> Windows unresponsive, jerky or do nothing at all. This is presumably due to
>> processes like anti virus or whatever, doing stuff. Is there any way that
>> some kind of tone could be  used to detect these events, say for 30 secs
>> after the last item in the startup list has fired?
>> OK its probably not possible, but I gather there often are flashing icons
>> in the tray or whatever that tend to indicate programs doing things.
>>
>> Just a thought.
>> Brian
>>
>> bgaff@xxxxxxxxxxx
>> Brian Gaff's other account.
>>
>>
>> To post messages to the list send email to
>> nvda@xxxxxxxxxxxxx
>> To modify your NVDA Email settings go to:
>> http://www.freelists.org/list/nvda
>> Thank you for your continued support of Nonvisual Desktop Access, an open
>> source free screen reader for Microsoft Windows:
>> http://www.nvda-project.org/
>> To get the latest NVDA snapshot:
>> http://www.nvda-project.org/snapshots/
>> Report bugs or make feature requests at:
>> http://trac.nvda-project.org/
>> Message Archive:
>> http://www.freelists.org/archives/nvda
>>
>
> To post messages to the list send email to
> nvda@xxxxxxxxxxxxx
> To modify your NVDA Email settings go to:
> http://www.freelists.org/list/nvda
> Thank you for your continued support of Nonvisual Desktop Access, an open
> source free screen reader for Microsoft Windows:
> http://www.nvda-project.org/
> To get the latest NVDA snapshot:
> http://www.nvda-project.org/snapshots/
> Report bugs or make feature requests at:
> http://trac.nvda-project.org/
> Message Archive:
> http://www.freelists.org/archives/nvda
>

Other related posts: