ACCESS CONTROL & RUN PROGRAMS from Visual view

[Superfreak3]

I have some questions regarding two of the function areas which can be called from the Visual view/tab.

First, I'll deal with RUN PROGRAMS. It appears to me that this is where you set up calling executables, which I'm accustomed to calling Custom Actions. Is this the case? Also, we used [INSTALLDIR] to reference the main installation directory on the command line/parameters for our Custom Action of this nature. What $<property>$ should can I use? Can I still use the normal Windows Installer properties? One more question... can I use $SUPPORTDIR$ to call an .exe that I have added to Source Files in RUN PROGRAMS or do these need to be coded into the Script in the proper location (just prior to the close of the installation)?

Now, ACCESS CONTROL... First, let me tell you my scenario. We have an install where we basically require admin rights to install, but a user can execute the program. Our issue is that Windows Installer causes a self-repair because we right Per User information and files to a user's Profile, which will be lacking since the initiating user of the app. is not the installer - typical Windows Installer behavior. Can I leverage ACCESS CONTROL in any way to allow a non-admin to write to HKLM in the registry for example. My thinking is I may be able to use this to allow non-admins to install our application. If this is the case, how would uninstall react? Would it still require an admin to uninstall?

Any help is Greatly Appreciated!

As you may have guessed, I'm basically moving down the Visual tree and walking through my current Wise template in initial attempts to recreate in InstallAware.

I'm hoping to get as much info from the forum, but will email support with any outstanding questions/issues when it comes time to compile the installation.