Program Access Alert

That pretty much echoes my findings. I've played around with changing where
things start and also found some inconsistent results.

Thanks.

--
Kerry Brown
Microsoft MVP - Shell/User
http://www.vistahelp.ca


"Ronnie Vernon MVP" <rv@invalid.org> wrote in message
news:u9zRy5maHHA.2296@TK2MSFTNGP03.phx.gbl...

> Hi Kerry
>
> In my testing, I have found that some start up programs that prompt for
> elevation (like IPoint) and that have their source as HKLM/Run can be
> 'fixed' by changing the source to HKCU/Run. I have also seen programs work
> by deleting the source from the registry and placing a shortcut for the
> program in the users common start up folder.
>
> The problem is that there is no consistency? IPoint is a good example. Why
> does it place the start up source in HKCU/Run and work without elevation
> on some systems and HKLM/Run and prompt for elevation on others, and place
> the source at different locations, during installation? Regardless of
> where it is placed, why does it prompt for elevation on some systems, and
> not prompt on others when the start up source is the same?
>
> I use a clipboard program that archives everything that is copied to the
> clipboard. It runs from a shortcut in the Start Up folder. This program
> has not been updated in at least 6 years, and it works perfectly with
> Vista. It is installed in Program Files, all of the data and configuration
> files are placed in the virtual store folder and it does not ask for
> elevation, at any time.
>
> As Jimmy said, there is no way to give the program admin privileges prior
> to starting.
>
> If none of these fixes work, I usually recommend that the user place a
> shortcut to the program in a handy location and start as soon as the boot
> is finished. As of now, there is no solution that I have found, it's
> strictly a hit or miss proposition.
>
> Let me know what you find on your system.
>
> --
>
> Ronnie Vernon
> Microsoft MVP
> Windows Shell/User
>
>
> "Kerry Brown" <kerry@kdbNOSPAMsys-tems.c*a*m> wrote in message
> news:OofntLeaHHA.4616@TK2MSFTNGP03.phx.gbl...

>