Announcement

Collapse
No announcement yet.

Setup does not work on all computers

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Setup does not work on all computers

    We have recently started using Setup Factory. An install I created does not seem to be working on all computers it is distributed to. The install is very small (4 files). All it does is read the registry, copy the files and offer the user an option to run an external program. The install was created on a computer with Windows 2000 Pro SP1.

    Typically the following errors will appear when the install is started: "Unable to open output file" (the title of this error dialog is "C:\DOCUME~1\DWDOOL~1.ID_\LOCALS~1\TEMP\irsetup.exe"). The second error is "Could not extract support files - setup will abort".

    I have also had this install completely hang up when launched - with no error messages at all. I must then use the task manager to close irsetup.exe.

    I have installed the latest update to Setup Factory, but that didn't help.

  • #2
    Re: Setup does not work on all computers

    Hi,
    Is this error occurring on WIN 2000 or WIN NT? Have you tried cleaning out the C:\DOCUME~1\DWDOOL~1.ID_\LOCALS~1\TEMP\ directory and then restarting the system? Does the installation work on that system now?
    Do you have the latest version of Setup Factory version 5.0.1.3? If not download the update from: http://www.indigorose.com/setup/update.html and see if that solves the problem.

    mark.
    MSI Factory The Next Generation Intelligent Setup Builder

    Comment


    • #3
      Re: Setup does not work on all computers

      The computer is running Windows 2000 Professional. We cleaned out the temp folder and restarted, but it is still giving the same errors. I am using Setup Factory 5.0.1.3.

      The computer that in completely hangs on (without an error message) is running Windows 2000 Server.

      Comment


      • #4
        Re: Setup does not work on all computers

        Hi,
        I'm not really sure why this is happening, try RUNNING your setup from START RUN and pass it "C:\TEMP" as a command line parameter. So basically type in: START -> RUN -> C:\SETUP\SETUP.EXE C:\TEMP, assuming that your install is located in C:\SETUP\. Before doing this make sure that the C:\TEMP directory exists.
        Does this work? If it does not work, what happens? Is it the same error?

        mark.
        MSI Factory The Next Generation Intelligent Setup Builder

        Comment


        • #5
          Re: Setup does not work on all computers

          OK, forget the original problem as described - we have determined what causes that. Here is the problem as it occures on two of our computers (One running W2K Pro, the other W2K Server), as well as a few of our customer's computers:

          When our setup is launched (setup.exe), the "Initializing Setup" dialog is displayed for a second, then it appears that nothing is happening - no dialog box, no error. When we check the Task Manager, we see that irsetup.exe is listed as a running process, and is taking up 98-99 percent of the processor. No matter how long we let it run, nothing happens.

          The original error I mentioned happens when you try to launch a second instance of setup.exe - while the first one is locked up.

          We really need to get this problem solved quickly, it is holding up distribution of our software. Thanks.

          Comment


          • #6
            Re: Setup does not work on all computers

            I have determined what causes this to happen - the setup is attempting to read 5 string values from the registry, which may or may not exist (this is how we determine which version and where to install our update). If one of these keys is missing, the setup hangs.

            Any suggestions? I assumed if the registry key did not exist, the variable would contain the default value.

            Comment


            • #7
              Re: Setup does not work on all computers

              Here's the problem and solution (for future reference):

              The Default Value I had entered in the Registry Variable screen was the same as the variable Name (both were %DynDir55%). I don't know why I did that, but it must have made sense at the time.

              My solution was to leave the Default Value blank, since I really didn't want a default value anyway.

              Comment


              • #8
                Re: Setup does not work on all computers

                Hi,
                Thanks for the information Integrity Data. Glad to hear that everything worked out for you in the end.

                mark.
                MSI Factory The Next Generation Intelligent Setup Builder

                Comment

                Working...
                X
                😀
                🥰
                🤢
                😎
                😡
                👍
                👎