Methods for auto-starting embedded application

Hi,

There are two methods I am aware of for launching my embedded app
automatically at startup:

1. Add a shortcut (or the .exe itself) to \Documents and Settings\All
Users\Start Menu\Programs\Startup\

2. Add a registry key to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
\CurrentVersion\Run

What are the pros and cons of the 2 methods? This is a system with
only one application and one user.

Thanks
R.

In article <949585e1-3741-49d8-af18-
ed9ec954bb5c@h2g2000hsg.googlegroups.com>, news@rblack01.plus.com
says...
> Hi,
>
> There are two methods I am aware of for launching my embedded app
> automatically at startup:
>
> 1. Add a shortcut (or the .exe itself) to \Documents and Settings\All
> Users\Start Menu\Programs\Startup\
>
> 2. Add a registry key to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
> \CurrentVersion\Run
>
> What are the pros and cons of the 2 methods? This is a system with
> only one application and one user.

It's harder for the user to accidentally delete the automatic startup if
it's in the registry, rather than on the start menu.

Don't forget about the equivalent places for specific users as well.

--
/~\ The ASCII
\ / Ribbon Campaign
X Against HTML
/ \ Email!

Remove the ns_ from if replying by e-mail (but keep posts in the
newsgroups if possible).

On Oct 10, 12:06 pm, "Zaphod Beeblebrox"
<Zaphod.Arisztid.Beebleb...@gmail.com> wrote:

[snip]

>
> Any yet a third option would be to have your app run as the shell, if
> you don't need the Explorer shell.
>

Yes this is something we are looking into, presumably it also shortens
the boot time?
For debug and development we currently use the Explorer shell to
launch Windows Explorer, Device Manager, Task Manager, regedit, etc.
We also use some of the common dialogs to open configuration files etc
- presumably we would lose these along with the shell?

<news@rblack01.plus.com> wrote in message
news:d0ca0a39-fe43-4001-a2b3-a22011ba552b@v56g2000hsf.googlegroups.com...
> On Oct 10, 12:06 pm, "Zaphod Beeblebrox"
> <Zaphod.Arisztid.Beebleb...@gmail.com> wrote:
>
> [snip]
>
>>
>> Any yet a third option would be to have your app run as the shell, if
>> you don't need the Explorer shell.
>>
>
> Yes this is something we are looking into, presumably it also shortens
> the boot time?

It does shorten it some since Explorer doesn't have to load then load
your app. I've never tested to see what the difference is though.

> For debug and development we currently use the Explorer shell to
> launch Windows Explorer, Device Manager, Task Manager, regedit, etc.

You could always move to a setup where you have an administrative user
that has the Explorer shell and a separate user that has your app as the
shell, set to auto login. Then you can log out / back in as the
administrator if you need the Explorer shell for something.

> We also use some of the common dialogs to open configuration files etc
> - presumably we would lose these along with the shell?

I hadn't thought about that, but it doesn't seem to be the case. At
least, our app doesn't have any problems, and during some of our early
evaluation, etc. I launched Notepad as shell and everything worked fine
there.

--
Zaphod

No matter where you go, there you are!

On Oct 10, 2:58*pm, n...@rblack01.plus.com wrote:
> On Oct 10, 12:06 pm, "Zaphod Beeblebrox"
>
> <Zaphod.Arisztid.Beebleb...@gmail.com> wrote:
>
> [snip]
>
> > Any yet a third option would be to have your app run as the shell, if
> > you don't need the Explorer shell.
>
> Yes this is something we are looking into, presumably it also shortens
> the boot time?

It does for us.

> For debug and development we currently use the Explorer shell to
> launch Windows Explorer, Device Manager, Task Manager, regedit, etc.
> We also use some of the common dialogs to open configuration files etc
> - presumably we would lose these along with the shell?

You can use those dialogs as long as you include the corresponding
components. You can even start the explorer manually after logging in
to a user with a custom shell, e.g. for debugging purposes (assuming
you haven't taken measures to prevent this and the component is
included in your build). Just press ctrl+alt+delete, start the task
manager and from there run "explorer".

Best Regards,
Niko Demmel