Advanced Installer Community

Swan

Thanks for the reply cosmin.

It doesn't look like the Qualified Components Groups edit will help us in our particular case. I ended up building a batch script to build the installer from the command line then run another executable that adds the PublishComponent table to the .msi. This worked well.

Swan

I'm using AI Enterprise v6.0.1.

Is there any way to have an external application or batch script run *after* the .msi file is built? I need to add a PublishComponent table to my .msi. I currently manually run the batch script that adds that table to the .msi but I'd rather have AI run the script ...

Swan

Thank you, cosmin.

Swan

I'm using AI Enterprise v6.0.1.

I'm trying to create a file:// URL as an Internet shortcut. I'd like to reference a URL that refers to a file in a sub-folder of the application folder. When I use the "Edit Internet Shortcut Properties" dialog, I use the following string in the "URL:" field:
file ...

Swan

Hello,

After talking with the customer, it appears the root path in question, "C:\ProgramData\Documents\" was damaged somehow on his Vista OEM installation. Even when logged in as Administrator, he was not able to change to that folder. So, it looks like the Error 1320 diagnosis of "path too long ...

Swan

Hi Gigi,

Thanks for your reply.

Is there anything within the installer that would cause the DOS SUBST command to be executed or would SUBST have to be explicitly executed by the user separate from the installation that would affect the installation?

I don't believe the 1320 error has to do with ...

Swan

We have some customers using a .msi produced by Advanced Installer 4.8.1 that are running into an "Installer Information" alert which states:
"The specified path is too long: C:\ProgramData\Documents\Neon Software".

The problem seems to occur when running the installer on a Vista machine that has ...

Swan

Thanks for your reply Gigi. We look forward to the future version of AI. For now, we'll create new projects for each language, as you suggest.

Swan

From the previous replys, I understand that the following entry into the Dictionary file will not work:

<ENTRY id="File.Product.chm">
<STRING lang="en" value="Product"/>
<STRING lang="de" value="C:\Development\Product\Installers\MSI Installer\de\Product.chm"/>
<STRING lang="fr" value="C ...

Swan

To summarize the solution which Gigi provided me in an email:

1. Create a property in the "Install Parameters" page name it COMMON_DOCUMENTS (upper cases).
2. Switch to "Custom Actions" page and create a new "Property Set With Formatted" custom action under "InstallUISequence->Begin". Use following ...

Swan

Hi Gigi,

I moved the custom action to "InstallUISequence>Begin". The same thing happens: the items in the CommonDocuments folder get put into C:\ rather than C:\Documents and Settings\All Users.Windows\Shared Documents. (By the way, in previous posts I wrote "Documents" when I really meant "Shared ...

Swan

Thanks, again, Gigi.

We're closer but still not there.

I moved the InstallExecuteSequence->CostFinalize property to "InstallExecuteSequence->Begin". I also editted the CommonDocuments property Value to be "C:\".

The installer ran, but installed the items in the Files & Folders CommonDocuments ...

Swan

Thanks, again, for your reply Gigi.

Sorry to be dense, but could you be more specific about your answer as both of the solutions you presented are not untuitive to me.

If I schdule the custom action "Property Set with Formated" under "InstallUISequence->Begin" with the same parameters, what ...

Swan

Thanks again, Gigi, for your reply.

We've tried several combinations of what you suggested below. We're probably making a silly mistake so perhaps you can set us straight. Here's exactly what we did:

1. Under Install Parameters>Properties we created a new property: Name is CommonDocuments, Value ...

Swan

Thanks for your reply, Gigi.

I have another related question. We need to install some files in the CSIDL_COMMON_DOCUMENTS folder, which normally maps to "C:\Documents and Settings\All Users\Documents" (or "C:\Documents and Settings\All Users.WINDOWS\Documents" on some machines). I don't see this ...

Suggested Articles

User Guide

Videos

Refer & Save Up to 30% On Your Renewal

Search found 18 matches

Automatically run an external application after build?

Shortcut URLs and a file:// URL

Specified path is too long