Community Forums
Page 1 of 2 12 LastLast
Results 1 to 5 of 6

Thread: Installer runs whenever I run my program

  1. #1
    Join Date
    Sep 2005
    Posts
    4

    Question Installer runs whenever I run my program

    I have created an install using Express 11. After the installation when my executable program is run the installer keeps starting. What is the cause and how do I fix it?

    Please help my users are getting PO'ed and I am at a loss.

    Thanks

    Jim

  2. #2
    Join Date
    Nov 2005
    Posts
    5

    ????

    I have installed in mine schemes BDE 5,01, more I do not have the Delphi, in my project in the part redistributables does not appear BDE to select. My project demands that the BDE is installed therefore the EXE was compiled in dephi.

  3. #3
    Join Date
    Jan 2002
    Location
    Oakland, CA, USA
    Posts
    5,427
    This thread should point you in a direction where you can start troubleshooting.
    Tsung-Huang Hsieh
    "A problem well stated is a problem half solved." --Charles F. Kettering

  4. #4
    Join Date
    Nov 2002
    Posts
    50
    By the way - I have changed the setting (copy media to target machine=yes) in all my installers and I still see the same problem.

    After installation, when running my program the installer start again, etc...

    Right now, I tell my users to re-install and that usually works, although it's a bad solution to a bigger problem.

    Perhaps there are other settings we should be looking at as well?
    For example, I set 'Delay MSI engine reboot=yes'.....

  5. #5
    Join Date
    Jan 2002
    Location
    Oakland, CA, USA
    Posts
    5,427
    When letting Windows Installer complete self-healing, does the application launch ok? Or Windows Installer throws some sort of error?

    If Windows Installer starts when a new user launches the program for the first time, it is very likely that there is per-user information, such as registry entries under HKCU, files going to user-specific folder, in the setup, and Windows Installer is simply putting down these pieces. In this case, there is not much we can do about it.

    If Windows Installer starts every time a user, or any user including administrators of the machine, launches the program, we are back to looking at Event Viewer for clues, and try to identify the component(s) that are triggering self-healing. If it only happens for non-admin users, user's permissions on some files and/or registry could be the culprit.

    Also, a compressed media may make a difference. I thought having "copy media to target machine=yes" would nullify the difference, but I might be wrong on this.

    If uninstall followed by a reinstall eliminates self-healing for all users, it may have to come to inspecting each and every machine that has the problem. Even so, understanding of why and what is not guaranteed.
    Tsung-Huang Hsieh
    "A problem well stated is a problem half solved." --Charles F. Kettering

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •