The install needs to be done under a user with Admin privs. In your Install Shield project under the Dialogs topic, make sure the Customer Information dialogue is included. This allows them to install the app for ALL USERS which is what they must do. If this is not included, I am not sure what the default choice for this would be.

>Hi all,
>
>An installation routine recently failed miserably on a win2K machine running at the premises of one our customers. Shame on us...
>
>The situation:
>1) the "use"r account has limited control over the machine,
>2) the installation is run by a "third party" logged wk2 "administrator",
>3) the software is tested as "admin" and works fine,
>4) the "third party" reboots the machine and logs as "user", the application miserably because it cannot find the libraries (dlls).
>
>I'm currently in the process of rebuilding our installation routine in order to secure a better process, especially when the "end-user" has severely reduced access to ones machine.
>
>How should we organize the stuff:
>1) should the installation routine (installshield express) be run on "admin" account or as "user"?
>i expect the answer is "admin" since some the process may not run correctly under the "user" account (com component registration for example).
>
>2)where should the dll and ocx be located?
>I expect they should ALL be in application directory (PROGRAM FILES\my prog) including vfp dlls (vfp*.dll), included third-party ocx and even system-level ones (gdiplus and al) since winsys is getting more and more protection over time.
>
>Any help, clue, tip or trick welcome!
>
>Francis