start-up

[bob]

Why does Windows have at least two ways of specifying to run a program
at start-up? (i.e. the StartUp folder and registry)

 

[Guest]

The startup folder is for your use.

 

[Terry R.]

The date and time was Thursday, April 23, 2009 6:40:42 AM, and on a
whim, (e-mail address removed) pounded out on the keyboard:

Why does Windows have at least two ways of specifying to run a program
at start-up? (i.e. the StartUp folder and registry)

Hi Bob,

There are more areas that just those. It could be the age of the
program (old programs may have used win.ini or even autoexec.bat).
There are quite a few areas in the registry that could launch programs.
Do a Google search for Autoruns and install it. It will show you
almost all of them.

Other than that, it's up to the app writer where they launch the
program, not Windows.


Terry R.

 

[Tim Meddick]

You cannot use Win.ini (load= or run=) OR Autoexec.bat (only used to 'set'
environment variables now) anymore on any NT systems.

 

[Terry R.]

The date and time was Thursday, April 23, 2009 10:22:25 AM, and on a
whim, Tim Meddick pounded out on the keyboard:

You cannot use Win.ini (load= or run=) OR Autoexec.bat (only used to 'set'
environment variables now) anymore on any NT systems.

I did state, "...may have used...".

And are you so sure?
http://www.aumha.org/a/loads.php


Terry R.

 

[Randall Flagg]

The date and time was Thursday, April 23, 2009 10:22:25 AM, and on a
whim, Tim Meddick pounded out on the keyboard:


I did state, "...may have used...".

And are you so sure?

Tim isn't even sure he's replying to the correct person/post.

 

[Bruce Chambers]

Why does Windows have at least two ways of specifying to run a program
at start-up? (i.e. the StartUp folder and registry)

Flexibility. Why have unnecessary limitations?


--

Bruce Chambers

Help us help you:


http://support.microsoft.com/default.aspx/kb/555375

They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety. ~Benjamin Franklin

Many people would rather die than think; in fact, most do. ~Bertrand Russell

The philosopher has never killed any priests, whereas the priest has
killed a great many philosophers.
~ Denis Diderot

 

[Tim Meddick]

Terry,
Don't be so sensitive, was only 'adding' information for the
interest of any one who might want to know.

 

[Terry R.]

The date and time was Friday, April 24, 2009 7:11:06 AM, and on a whim,
Tim Meddick pounded out on the keyboard:

Terry,
Don't be so sensitive, was only 'adding' information for the
interest of any one who might want to know.

Hi Tim,

Well, your mail client incorrectly inserting a delimiter in your top
post caused everything relevant to be wiped out, and I don't feel like
going back and correcting it so this post doesn't properly show the flow
of the discussion. Oh well...

Rest assured, that was my NOT sensitive response. The info you "added"
wasn't correct, so why would anyone "want to know" incorrect info?

The link I gave you (and you can find a LOT of others) clearly states
that MS continues to include WIN.INI in their XP Help & Support
instructions for Selective Startup troubleshooting. I have manually
removed viruses loading from that file, so you can't say "you cannot use
WIN.INI anymore on NT systems".


Terry R.

 

[Tim Meddick]

WIN.INI:

[windows]
LOAD=bogus.exe
RUN=bogus.exe

DO NOT WORK ON NT SYSTEMS ANY MORE FACT - THEY DON'T
It is there for 16bit application support only

AUTOEXEC.BAT DOES NOT LOAD ANYTHING ON NT SYSTEMS ANYMORE FACT - IT DOSN'T
It parses it for the 'set' command only*

*(only when set to do so)

It may well be an irrelevant (to you) fact but true they are!