Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- « Previous
-
- 1
- 2
- Next »
Default path for distribution kit
Mert_A.
Active Participant
08-10-2006 12:33 PM - edited 08-10-2006 12:33 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Hi Steve,
Creating a merge module from scratch in Orca is not particularly easy, so I created one for you using Wise for Windows Installer. You can still edit this .msm in Orca to your heart's delight. The significant entries are in the CustomAction, ModuleInstallExecuteSequence, and ModuleInstallUISequence tables. The CustomAction table defines an action CA_SetDirectory_INSTALLDIR that sets the INSTALLDIR property (this is the default installation path that is displayed) to "R:\StationSoftware". The module sequence tables define at which point in the installation this custom action should be run.
To merge the module into your distribution, create a file group named _MSMs_ and add the .msm file to the group. When you build the distribution kit, the module will be merged in.
Keep in mind that this new path is hardcoded. You will need to edit the .msm file (change the Target column of the CustomAction table entry) to make any changes. Also, if you try to run the installer on a machine without an R: drive, you will get an Invalid Drive error that will cause the installation to fail.
I hope this solution works out for you.
Mert A.
National Instruments
Creating a merge module from scratch in Orca is not particularly easy, so I created one for you using Wise for Windows Installer. You can still edit this .msm in Orca to your heart's delight. The significant entries are in the CustomAction, ModuleInstallExecuteSequence, and ModuleInstallUISequence tables. The CustomAction table defines an action CA_SetDirectory_INSTALLDIR that sets the INSTALLDIR property (this is the default installation path that is displayed) to "R:\StationSoftware". The module sequence tables define at which point in the installation this custom action should be run.
To merge the module into your distribution, create a file group named _MSMs_ and add the .msm file to the group. When you build the distribution kit, the module will be merged in.
Keep in mind that this new path is hardcoded. You will need to edit the .msm file (change the Target column of the CustomAction table entry) to make any changes. Also, if you try to run the installer on a machine without an R: drive, you will get an Invalid Drive error that will cause the installation to fail.
I hope this solution works out for you.
Mert A.
National Instruments
Message Edited by Mert A. on 08-10-2006 12:34 PM
Message Edited by Mert A. on 08-10-2006 12:34 PM
- « Previous
-
- 1
- 2
- Next »
