Flexera Software Community

DCOM permissions

soerenpc — Thu, 02 Sep 2010 14:12:18 GMT

Hi
Can I install and set DCOM permissions with InstallAnywhere or InstallShield (Express)?

If so, then which version and how?

S�ren PC

DCOM permissions

soerenpc — Thu, 02 Sep 2010 14:11:12 GMT

Hi
Can I install and set DCOM permissions with InstallAnywhere or InstallShield?

S�ren PC

is START attribute license start date?

jiOeyji — Thu, 02 Sep 2010 13:25:15 GMT

Hi,
Advance excuse if it is not appropriate forum for this question.
I have to filled one dialog to contains flexlm license information with column heading "License start date".
I just want to know "START" or "ISSUED" attribute represent the start date of license or is there any other attribute which represent the start date of license.
thank you
JiOeyJi

Editing a dialog

boaz@imedix.com — Thu, 02 Sep 2010 13:21:37 GMT

Hi,

I chose to edit an existing dialog in my installation project.
I can modify/delete current entities on the dialog, but for some reason
I can't add new ones....

I read that I suppose to drag them to the dialog area, but nothing happens, and nothing is added to the dialog....

help :)
Boaz

is START attribute license start date?

jiOeyji — Thu, 02 Sep 2010 13:02:29 GMT

is START attribute license start date?

jiOeyji — Thu, 02 Sep 2010 13:01:49 GMT

OnInstalledFile - need example help

ZygoCorp — Thu, 02 Sep 2010 12:16:56 GMT

INSTALLSCRIPT PROJECT
So I want to manipulate a file once it is installed; updates, etc don't need the manipulation so it seems OnInstalledFile event handler is the way to go. I must be having a bad day because I can't figure out how to code this. I added the event handle to my rul file.

the szFile parameter - the file I want to manipulate is: \company\product\abc.config

So do I put FOLDER_COMMON_APP\\company\\product\\abc.config in place of szFile? since we install to both 32 and 64 bit systems we rely a lot on the predefined variables for install locations.

is START attribute license start date?

jiOeyji — Thu, 02 Sep 2010 11:35:36 GMT

is START attribute license start date?

jiOeyji — Thu, 02 Sep 2010 11:08:21 GMT

Hi,
Advance excuse if it is not appropriate forum for this question. :)
I have to filled one dialog to contains flexlm license information with column heading "License start date".
I just want to know "START" or "ISSUED" attribute represent the start date of license or is there any other attribute which represent the start date of license.
thank you
JiOeyJi

Best Practice for upgrading a 32-bit installation to 64-bit

Tom Teboda — Thu, 02 Sep 2010 08:32:10 GMT

I am having issues performing a major upgrade on a 64-bit OS (Windows 2008) from my old version (created using InstallShield 8.2 Developer) which is mainly 32-bit to a 64-bit install (using InstallShield 2010 Premier). On 32bit systems I have no issue upgrading the IS8.2 build to the IS2010 build, but on 64-bit Windows the existing installation is not detected (Upgrade codes are the same, product code is different).

I have read (here) that there are some issues with performing upgrades on 64-bit OS from previous IS versions so that is an issue in and of itself. However, since installations paths are different ("Program Files" vs. "Program Files (x86)") I believe the best thing to do is to install to a new folder as well. What's the best practice for migrating an application from 32-bit to 64-bit from an installer point-of-view?

creating a unupdateable release

mary_v — Thu, 02 Sep 2010 07:57:23 GMT

Hi there,

i am faced with following situation:
- i have to different versions (releases) already - compiled via release flags (e.g. rel1 and rel2)
- both are able to update

now i want to create a kind of example release (e.g. release flag relex)
- which installs itself (Firsttime install)
- which is NOT able to update as release "relex" but as install rel1 or rel2

hope to have explained clear enough what i want to achieve...
would be the way of compiling another release (relex) the best way for this?

any other ideas are highly appreciated ,-)
mary

Merge Module, Visual C++ 9.0 CRT (x86)

IncontrolTech — Thu, 02 Sep 2010 05:48:29 GMT

Hi all,

I have an installer which requires the following 2 merge modules:

Visual C++ 9.0 ATL (x86) WinSXS
Visual C++ 9.0 CRT (x86) WinSXS

These are sellected and being added to the finall .exe installer as the following two lines are in the build output log.
"Merging Visual C++ 9.0 ATL (x86) WinSXS MSM: C:\Program Files\Common Files\Merge Modules\Microsoft_VC90_ATL_x86.msm"
"Merging Visual C++ 9.0 CRT (x86) WinSXS MSM: C:\Program Files\Common Files\Merge Modules\Microsoft_VC90_CRT_x86.msm"

The problem is when the installer is run these merge modules are NOT installed. :mad: What are the possible reasons for this? :confused:

I validated the files are not installed by running an .exe (which i know requires them) through "depends" and the corrosponding .dll files came up missing even after the install.

Any help is much appreciated. :)

Install Multiple versions of the same product

Jpmon1 — Wed, 01 Sep 2010 20:50:53 GMT

Hello,

Please forgive my ignorance, but I could not seem to find if there is a way to install different versions of the same product. I would like to do this similar in manner to how InstallShield 2010 and InstallShield 2010 LE are installed but with the product version number instead (they are both in 'Program Files->InstallShield' and then they have separate folders), . Is this possible with InstallShield?

Thank You,

- Jon

Wanted: Freelance Installshield Developer

partlysunny — Wed, 01 Sep 2010 18:07:57 GMT

Does anyone in this community know of any freelance Installshield developers that might be interested in helping a small software company improve/tighten/debug the installer for their product?

Thank you in advance

LaunchAppAndWait--app runs on Win2008, but not Win 2003?

DMorisseau — Wed, 01 Sep 2010 17:30:17 GMT

I've got a Basic MSI project with an InstallScript deferred CA that launches an executable (really old velocis database server utility) with the name of a script file included in the install. If I run the setup on WindowsServer 2008, the CA runs properly. But if I run the setup on WinServer2003 (which the majority of our install base runs), the exe does not run the same way.

I tried 2 different ways of invoking the exe with LaunchAppAndWait

a) rsql.exe as program, file name to process as the command line argument.

In this case, I get the rsql execution window coming up with an error message that it could not open the command file I passed to it. I verified that the file is present. At the rsql prompt, I entered the exit command.

b) I wrote a RunScript.bat that is just rsql

In this case, I get an error from LaunchAppAndWait saying the runscript.bat could not be executed. Interrogating LAAW_PARAMETERS.nResultCode returns a code 3, but I have no clue as to what it means.

After the install is done, if I go to a command prompt and try either method, the program executes correctly.

Since this is working ok on Win2008, what can I look for to troubleshoot this?

I have verified that the executable and supporting files are the same on both systems.

As always, a quick response would be appreciated!