This website uses cookies. By clicking OK, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
AndrewRich
Pilgrim
Oct 13, 2011
06:17 PM
I have two MSMs with the same Module ID. One includes x64 files and the other includes x86 files. I would like to include them both into a single Basic MSI installer and set a condition so that one or the other is installed based on the target system. The problem is that I can't seem to get both MSMs to appear in the Redistributables view. I can fiddle with the search directory order in Tools -> Options -> Merge Modules, and I can manually specify one or the other by right-clicking in the Redistributables view and navigating to it, but doing so invariably removes the other. I can't get them to appear at the same time. Is this due to them having the same Module ID? They do have different file names and live in different source directories, and since they have different contents would have different MD5 signatures. Changing the Module ID of just one of the MSMs would be difficult considering how they are built (a single WiX script which substitutes contents based on platform) and also that those are "owned" by another group. It would be ideal if I could simply include both MSMs in my Basic MSI project as they exist now. Thanks in advance.
... View more
Labels
Oct 03, 2011
04:50 PM
MichaelU wrote: Launch Conditions. If a launch condition of the format NOT VersionNT64 is present, the package would exit on 64-bit machines. It was a Launch Condition. Thank you for your help!
... View more
Sep 30, 2011
05:37 PM
I have a Basic MSI installer that was targeted to x86 platforms (with a companion installer targeted to x64). We have removed the 64-bit components and would like to have a single installer that works on both platforms. However, the x86 installer refuses to run on x64 platforms. The Platforms value on the x86 installer reads "Intel;1033" which according to what I've read should work for both. The Platforms value in the Release view is blank. Where else can I look to remove the platform specificity and allow the single installer to work on x86 and x64?
... View more
Labels
Sep 06, 2011
10:02 PM
Robert, You're still a genius. The path for one component in that merge module was missing "INSTALLDIR" before the destination directory name. Your analysis helped me find it. Thanks as always.
... View more
Sep 06, 2011
05:51 PM
Here is the msiexec log for running the installation on XP. I'm not entirely sure what I'm looking for but I do notice these: Action start 15:46:05: CostInitialize. Action ended 15:46:05: CostInitialize. Return value 1. Action 15:46:05: FileCost. Computing space requirements Action start 15:46:05: FileCost. Action ended 15:46:05: FileCost. Return value 1. Action 15:46:05: ResolveSource. Action start 15:46:05: ResolveSource. Action ended 15:46:05: ResolveSource. Return value 1. Action 15:46:05: CostFinalize. Computing space requirements Action start 15:46:05: CostFinalize. Action ended 15:46:53: CostFinalize. Return value 1. I've also uploaded the log with "vx" options turned on. I'd really appreciate some assistance on this urgent problem.
... View more
Sep 02, 2011
08:44 PM
When doing a fresh install of our product on XP, the "Computing space requirements" dialog is shown for an extended period of time and then an "Out of Disk Space" dialog is shown. Note that there is plenty of space, even as shown on the dialog itself. When installing the same product on Win7, again the "Computing space requirements" is shown for much longer than it should and then a "Could not access network location" error is shown. This is a self-contained downloadable .exe installer so there are no network locations that should be necessary. Please see the attached screen shots. I will happily provide any logging or other data but I'll need to know how to generate them.
... View more
Labels
Jun 13, 2011
03:17 PM
TsungH wrote: Try the following. setup.exe /v"ISSCRIPTDEBUG=1 ISSCRIPTDEBUGPATH=\"C:\\Users\\Andrew Rich\\Downloads\\PreReqs\\Script Files\"" I tried doubling the backslashes (as you showed) but still don't get the debugger.
... View more
Jun 08, 2011
05:08 PM
I have an InstallScript Custom Action in a Basic MSI setup. I know the CA is called when setup.exe is run (it's a very simple CA that just shows a MessageBox). I am attempting to debug the CA on a remote machine. I have copied ISDbg.exe and SciLexer.dll to the remote machine, which is running Windows 7-64. I ran ISDbg /regserver. I verified that the InstallScript Debugger was correctly registered by remotely debugging a pure InstallScript setup. When I try to debug the InstallScript CA in my Basic MSI setup, the InstallScript debugger never launches. The CA runs and then the setup continues. I suspect the problem lies in the command-line I am passing to setup.exe. Information from the InstallShield help ("Setup.exe and Update.exe Command-Line Parameters" topic) suggests there are two ways to debug InstallScript CAs: /v"ISSCRIPTCMDLINE=\" \"" : pass arguments that should be passed to the script Basic MSI projects that have InstallScript custom actions This option specifies command-line parameters to be passed to the script. Any property supported by InstallScript MSI (where appropriate) can be specified. (The most common ones are /d and /z.) For example, the following indicates that you want to debug the script, and that the CMDLINE variable should contain TEST. Setup.exe /v"ISSCRIPTCMDLINE=\"-d -zTEST\"" Note that as shown above, when you want to specify that a double quote character is not a delimiter for the command line but a delimiter for the property, use \". Note also that as with any public Windows Installer property, this property should be specified with all uppercase letters. I tried: "\\vmware-host\Shared Folders\Downloads\setup.exe" /v"ISSCRIPTCMDLINE=\"-d\\WEBOS-IS-DEV\ISProjects\PreReqs\Script Files\"" /d : debug InstallScript Basic MSI projects with InstallScript custom actions, InstallScript, InstallScript MSI For an InstallScript project, running the command Setup.exe /d runs the installation program with the InstallScript Debugger. Debugging InstallScript code requires the debug-information file Setup.dbg to be available. To debug an InstallScript project on a system other than the development system: Copy the InstallScript Debugger executable file ISDbg.exe (located in the System folder of your InstallShield distribution) to the test system, and register it by launching the executable with the /REGSERVER command-line option. Copy Setup.dbg to the test system. Run Setup.exe with the command Setup.exe /d" ", where path is the directory containing Setup.dbg. For a Basic MSI project, the following command runs your InstallScript custom actions in the InstallScript Debugger: Setup.exe /v"ISSCRIPTDEBUG=1 ISSCRIPTDEBUGPATH=\"path-to-Setup.dbg\"" I copied the entire project folder to the remote machine and, from the DISK1 directory where setup.exe was built, tried: setup.exe /v"ISSCRIPTDEBUG=1 ISSCRIPTDEBUGPATH=\"C:\Users\Andrew Rich\Downloads\PreReqs\Script Files\"" In both cases, setup.exe launched and the InstallScript CA executed but the debugger never fired. What is the really correct way to debug InstallScript CAs in a Basic MSI setup?
... View more
Labels
Apr 13, 2011
04:22 PM
Solved. The project had been designed such that the base target directory was never exposed in the Custom Install. Only the sub-features' target directories could be changed. Since changing those targets didn't change INSTALLDIR, it makes sense that later references to INSTALLDIR would use the default value. I solved it by adding a base feature to the project, moving the other features below it and removing the ability to change the target directory for the sub-features. Thanks for your help.
... View more
Apr 12, 2011
08:25 PM
TsungH wrote: For Basic MSI, you can pass your .msi file to msiexec.exe as a parameter. Use double quotes if there is whitespace in the path. msiexec.exe /i \your.msi /l*vx \verbose.log Thanks. I've attached verboselog.txt. Interestingly, I can't find a mention of changing the value of INSTALLDIR when I change it in the "Custom Install" dialog. The secondary INSTALLDIR from an included merge module is changed but not the primary one. However, all the files are installed to the location I selected.
... View more
Apr 12, 2011
03:28 PM
Screenshots attached. I may be a grizzled veteran with InstallScript, but I'm admittedly pretty raw with MSI projects. Any help is appreciated.
... View more
Apr 07, 2011
02:39 PM
Basic MSI project in InstallShield 2011. There's a need to set some user environment variables. Under System Configuration -> Environment Variables, I configured the name and value. The value needs to be a subdirectory named "SDK" under the installed directory so I set it to "[INSTALLDIR]SDK". This works fine as long as the user doesn't change the default install directory. If they do, the environment variable is still set to the default instead of the custom. I tried using an InstallScript custom action, setting the environment variable into the "Environment" key of HKEY_CURRENT_USER. The values are set (let's hear it for InstallScript) but again, it always uses the default value of INSTALLDIR even if I choose a custom install directory. What is the proper way to specify the true value of INSTALLDIR whether customized or default? By the way, Hi everyone. I'm back. Again.
... View more
Labels
Oct 22, 2008
08:32 PM
The KB article says: InstallShield does not support adding unsupported languages to an InstallScript project type. It doesn't say it's not possible, it says it's not supported. So is it possible? If so, how? I've just been advised I need to add support for EN-GB (English - United Kingdom) and ES-CO (Spanish - Colombia) to our pure InstallScript project. Changing the project type is not an option.
... View more
Sep 17, 2008
12:32 PM
joshstechnij wrote: I've attached a zipped copy of the uncompressed files for IS 2008. You can make a backup copy of the existing files and replace them with the ones from the attached zip. Now that's what I call customer service! Much appreciated. I'm trying to get approval to buy IS 2009 -- 2008 was a free upgrade under our maintenance plan, but 2009 would be a paid upgrade. Meanwhile, those files will get me back up and running under 2008. Thanks!
... View more
Latest posts by AndrewRich
Subject | Views | Posted |
---|---|---|
1547 | Oct 13, 2011 06:17 PM | |
353 | Oct 03, 2011 04:50 PM | |
1902 | Sep 30, 2011 05:37 PM | |
867 | Sep 06, 2011 10:02 PM | |
867 | Sep 06, 2011 05:51 PM | |
2770 | Sep 02, 2011 08:44 PM | |
1004 | Jun 13, 2011 03:17 PM | |
8764 | Jun 08, 2011 05:08 PM | |
766 | Apr 13, 2011 04:22 PM | |
766 | Apr 12, 2011 08:25 PM |
Activity Feed
- Posted Include two MSMs with same Module ID on InstallShield Forum. Oct 13, 2011 06:17 PM
- Posted Re: Remove platform-specificity from x86-targeted MSI on InstallShield Forum. Oct 03, 2011 04:50 PM
- Posted Remove platform-specificity from x86-targeted MSI on InstallShield Forum. Sep 30, 2011 05:37 PM
- Posted Re: False "Out of Disk Space" error on InstallShield Forum. Sep 06, 2011 10:02 PM
- Posted Re: False "Out of Disk Space" error on InstallShield Forum. Sep 06, 2011 05:51 PM
- Posted False "Out of Disk Space" error on InstallShield Forum. Sep 02, 2011 08:44 PM
- Posted Re: Debugging InstallScript Custom Action in Basic MSI on InstallShield Forum. Jun 13, 2011 03:17 PM
- Posted Debugging InstallScript Custom Action in Basic MSI on InstallShield Forum. Jun 08, 2011 05:08 PM
- Posted Re: Custom-install value of INSTALLDIR on InstallShield Forum. Apr 13, 2011 04:22 PM
- Posted Re: Custom-install value of INSTALLDIR on InstallShield Forum. Apr 12, 2011 08:25 PM
- Posted Re: Custom-install value of INSTALLDIR on InstallShield Forum. Apr 12, 2011 05:15 PM
- Posted Re: Custom-install value of INSTALLDIR on InstallShield Forum. Apr 12, 2011 03:28 PM
- Posted Custom-install value of INSTALLDIR on InstallShield Forum. Apr 07, 2011 02:39 PM
- Posted Re: Help~~New Language Wizard not functioning? on InstallShield Forum. Oct 22, 2008 08:32 PM
- Posted Re: IS 2008 Skins _IsRes.dll on InstallShield Forum. Sep 17, 2008 12:32 PM
- Posted IS 2008 Skins _IsRes.dll on InstallShield Forum. Sep 16, 2008 02:52 PM
- Posted Re: Where is the Package Stub setup.exe? on InstallShield Forum. Sep 16, 2008 02:39 PM
- Posted Re: How to change the defualt STATUSEX message box? on InstallShield Forum. Sep 15, 2008 07:01 PM
- Posted Where is the Package Stub setup.exe? on InstallShield Forum. Sep 15, 2008 05:04 PM
- Posted Re: Printing the license agreement from SdLicense on InstallShield Forum. Jun 27, 2008 05:40 PM
Contact Me
Online Status |
Offline
|
Date Last Visited |
Mar 18, 2019
12:10 PM
|