Maintenance mode folder search dialog

[FJGG]

Hello,

Is it normal for the installer to prompt for the installer source file when Add/Remove or Reinstall/Repair options where chosen from the maintenance dialog. This happens when i click on the Uninstall shortcut or Remove button from the Control Panel->Add/Remove programs.

Is there away to keep that from poping up and automatically provide the original installer file?

[Ton_B]

Sometimes I've got the same problem.
I'n not sure, but I believe the problem will occur when the UninstallString in the registry points to a non existing file.

see register key:

HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Uninstall\\$TITLE$\\UninstallString

Where $TITLE$ is the the Title of your project, set in the Project Options dialog (summary information)

[MichaelNesmith]

Actually, this occurs only when access to the original setup sources are required, so it happens only during a reinstall or change of installed feature set. It does not happen with uninstalls.

And, if web builds are used to deploy an application, this prompt will never be seen. This is because web builds cache their setup data locally. Therefore the installer will always find the data it is looking for, and never display this prompt.

[slang]

I'm invoking the Add/Remove control panel applet and clicking on my installed program Change button. When I select Repair/Reinstall in the maintenance dialog, a dialog window pops up asking "Please specify your original setup sources to continue operation"

Forgive my ignorance, but what are "setup sources"?

I created a Compressed Single Self-Installing EXE. The installer is not prompting for a file but rather a folder, as in the dialog box title "Browse for Folder".

I tried using the folder containing the Compressed Single Self-Installing EXE but it didn't accept that. I next tried the temporary "mia" folder containing the extracted installer files, but it didn't accept that either. What folder does it want?

If the developer of the IA installer can't figure this out, chances are a user won't fare any better.

Issues:

1) A much clearer message needs to be generated, telling the user exactly what folder they need to browse to.

2) Is there some sort of way to automate this? Could I store the path to the necessary folder in a registry entry and then pass it to Apply Install?

Steve Lang
JeVal Software Engineering

[jimo]

Steve,

Here's how its done in IA;

Like Michael said only web builds will cache the original install source files, so, the way I overcome all of this is to use Web Builds. By using web builds you break your package into small pieces, this then allows the users that are downloading to install to only get the files they need for their system. So, if your package requires .net20 and the user already has it installed the users total download will be less than the Single Executable.

Now let's say you have to distribute a CD as well, then you place the web build files in the same directory with the MyAppSetup.exe and IA will use the local files instead of downloading from the web AND it will cache the files locally.

If you use these methods your users will never get a message asking for source files.

Sorry for being long winded,
Hope this helps.

Jim Oswell
V.P. Engineering
MMD Systems, Inc.

[slang]

Hi Jim:

Thanks for the work-around. I'll have to check it out.

I'm still confused, though, as to what folder the prompt is looking for? Can the prompt be answered by a user? If not, then it's pointless to ask him/her for something that can't be provided. If that's the case then Add/Remove Features and Repair/Reinstall need to be blocked where they aren't supported.

Steve Lang
JeVal Software Engineering

[jimo]

Thanks for the work-around. I'll have to check it out.

No Problem, glad to help.

I'm still confused, though, as to what folder the prompt is looking for?

The exact location of the the uncompressed install files.

Can the prompt be answered by a user?

Yes, but it ain't always pretty.

If that's the case then Add/Remove Features and Repair/Reinstall need to be blocked where they aren't supported.

This one is up to us, if you use a compressed single file build for distribution then (IMHO) you should remove the Add/Remove Features and Repair/Reinstall from the maintenance dialog and the change button in Add Remove Programs.

The methodology I outlined im my previous post has the added benefit of facilitating patch distribution.

[mwilner]

HI Jim,
Your workaround suggestion is all well and good but I had previously an installation that worked without this annoying and confusing dialog popping up and it was a compressed install file installer.
Something must have changed between the previous version of Install Aware and the 2012 version that I am using now.
I don't want many files I only need 1 file.
Is there a solution for?
Thank you,
\Manfred

[FrancescoT]

Dear Manfred,

If I have not missed anything, have you tried to set as checked the "Always Cache Setup Sources" control in "Build Settings"?

This three-state check-box lets you control setup source caching. When the box is filled, the default source caching option (as described above for each build type) is in effect. When cleared, setup sources are never cached. When checked, setup sources are always cached.

Regards

[mwilner]

Thank you Francesco this was the solution! It was filled not checked and that caused the program to not cache by default.
Now it is working as expected, a single executable file with no errors on un-installing.

[FrancescoT]

Happy that you solved!