AutoStart - what is better: EXE or LNK

[NewsArchive]

Hello all,

I would like to have one program to be autostarted at Windows startup, but
what belongs into the startup-group?

Do I copy the EXE over there or do I store the EXE in the usual folder and
use a shortcut .LNK instead?

Both seem to work, I tried it manually.

Does it matter at all? (as long as it works...)

Any advice appreciatetd! Thanks in advance
Wolfgang



--
Grüße / Regards
Wolfgang Orth

http://www.odata.de

KiK - Kompatibilität im Katheter
http://www.kik-service.de

KiK - Compatibility in Catheters
http://www.kik-service.de/?English_Description




NewsClient: http://www.opera.com/mail/

[NewsArchive]

Wolfgang,

> I would like to have one program to be autostarted at Windows startup, but
> what belongs into the startup-group?

I would use the "Add RegistryRun Entry function". It creates a Run key
that contains the name of a program to run when the computer starts.

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

SetupBuilder is installation -- "point. click. ship"

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

I would do the shortcut in the Startup folder.

As long as you're contending with the hassles of UAC, might as well take
advantage of the security of the \Program Files\xx folder protections for
your software.

Many users are familiar with the Startup folder and can remove your shortcut
if they don't want your app to start at logon.
Many don't know about msconfig or editing the Registry.
If you put the startup into the Registry, as a courtesy I think you ought to
give your users a program function to remove that if they want to... which
complicates both your life and theirs.
Of course, if you don't want them to be able to turn off the start-at-logon,
the Registry would be a good choice.

Jane

[NewsArchive]

> I would use the "Add RegistryRun Entry function". It creates a Run key
> that contains the name of a program to run when the computer starts.

cool - didn't knew that this exists, beside Startup


But I had to learn that my program does not perform completely as desired
when running under a user account.

START(OtherProc) where OtherProc contains a ShellExecute (PowerRum from G.
Berthume)

Tried your advice you gave Arnor, but with no success yet :-(

Neue Baustelle..... grummel




--
Grüße / Regards
Wolfgang Orth

http://www.odata.de

KiK - Kompatibilität im Katheter
http://www.kik-service.de

KiK - Compatibility in Catheters
http://www.kik-service.de/?English_Description




NewsClient: http://www.opera.com/mail/

[NewsArchive]

Hello Jane,

yes, very good arguments...

> Of course, if you don't want them to be able to turn off the
> start-at-logon, the Registry would be a good choice.

.... but this one is the best! <g>


Its a program for a school, and teachers are computer illaterate, but they
"know" ecerything and they know it even better!

Thanks for your input.

bye
Wolfgang





--
Grüße / Regards
Wolfgang Orth

http://www.odata.de

KiK - Kompatibilität im Katheter
http://www.kik-service.de

KiK - Compatibility in Catheters
http://www.kik-service.de/?English_Description




NewsClient: http://www.opera.com/mail/

[NewsArchive]

> If you put the startup into the Registry, as a courtesy I think you ought
> to give your users a program function to remove that if they want to...
> which complicates both your life and theirs.

Good point!

Friedrich

[NewsArchive]

> I would do the shortcut in the Startup folder.

Jane, I followed your advice.

Handling the Startup via Registry would make it transparent for the user
and would prevent them from fiddling around easily, but I had to learn
that my program needs admin permissions to run. This was to achieve with a
shortcut in the startup, as you suggsted.

Thanks again!


--
Grüße / Regards
Wolfgang Orth

http://www.odata.de

KiK - Kompatibilität im Katheter
http://www.kik-service.de

KiK - Compatibility in Catheters
http://www.kik-service.de/?English_Description




NewsClient: http://www.opera.com/mail/

[NewsArchive]

> Handling the Startup via Registry would make it transparent for the
> user and would prevent them from fiddling around easily, but I had
> to learn that my program needs admin permissions to run. This was
> to achieve with a shortcut in the startup, as you suggsted.

Just curious, why does your program need administrator execution level
privileges to run?

BTW, and see this:

http://www.lindersoft.com/forums/showthread.php?t=18820

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

SetupBuilder is installation -- "point. click. ship"

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

> Just curious, why does your program need administrator execution level
> privileges to run?

Honestly, I do not know!

My tiny program simply calls a DOS batch file, handing some parameters to
it and in this batch another DOS program is called with just these
parameters. (secure FTP)

During my tests I had to learn that it run well when I was logged-in as
admin, but it failed when I was a user. Altering the priviledges solved
the problem.


> BTW, and see this:
>
> http://www.lindersoft.com/forums/showthread.php?t=18820

Yes, exactly that helped me in my case too - what a coincidence!

Thanks again for your support, Friedrich!

Wolfgang Orth

--
Erstellt mit Operas revolutionärem E-Mail-Modul: http://www.opera.com/mail/