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
Default path for distribution kit
blockst
Member
08-09-2006 11:18 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
I would like my distribution kit to install by default to a path that is on a drive other than c:. How do I set my distribution kit to do this?
Mert_A.
Active Participant
08-09-2006 12:05 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Hello,
Because you cannot know a priori what drives will be available on any given system that your distribution might be installed to, all installation locations are typically described using a symbolic base location (like Program Files directory, or Windows directory, or Windows Volume Root) and a relative path. The system might not even have a C: drive; the symbolic locations are resolved to the proper drives and paths at installation time. For this reason, the only way to guarantee a valid default installation path is to use these symbolic base locations.
It is possible to work around (read "hack") this limitation, but it requires that you do some post-build, hand-editting of the .msi installer file using a tool like Orca (comes with the Microsoft SDK, a free download). If you think this is something you are interested in, I can explain what needs to be done.
Hope this helps.
Mert A.
National Instruments
Because you cannot know a priori what drives will be available on any given system that your distribution might be installed to, all installation locations are typically described using a symbolic base location (like Program Files directory, or Windows directory, or Windows Volume Root) and a relative path. The system might not even have a C: drive; the symbolic locations are resolved to the proper drives and paths at installation time. For this reason, the only way to guarantee a valid default installation path is to use these symbolic base locations.
It is possible to work around (read "hack") this limitation, but it requires that you do some post-build, hand-editting of the .msi installer file using a tool like Orca (comes with the Microsoft SDK, a free download). If you think this is something you are interested in, I can explain what needs to be done.
Hope this helps.
Mert A.
National Instruments
08-09-2006 12:49 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Mert A.,
Please do, as we need to assure that nothing accidentally gets installed to the C: drive. Thanks.
Steve
08-09-2006 12:50 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Actually, instead of hacking the MSI file. Is there a way to setup a custom symbolic base location for the station I need to install it on?
Mert_A.
Active Participant
08-09-2006 01:42 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Hi Steve,
In order to figure out what the best/easiest workaround is for you, it would be helpful to get a little more about what your needs are, and what version of CVI you're using.
1. Which version of CVI are you using? If 8.0 or later, are you including any other drivers? If so, the situation may be complicated by the location of your National Instruments directory.
2. You mentioned that you want to assure that nothing gets installed to the C:\ drive. Is it sufficient to change the default installation directory, or does it concern you that the user can still change this path to some directory on C:\ at install time?
3. Do you know for certain that all your target machines have a particular drive letter?
Mert A.
National Instruments
In order to figure out what the best/easiest workaround is for you, it would be helpful to get a little more about what your needs are, and what version of CVI you're using.
1. Which version of CVI are you using? If 8.0 or later, are you including any other drivers? If so, the situation may be complicated by the location of your National Instruments directory.
2. You mentioned that you want to assure that nothing gets installed to the C:\ drive. Is it sufficient to change the default installation directory, or does it concern you that the user can still change this path to some directory on C:\ at install time?
3. Do you know for certain that all your target machines have a particular drive letter?
Mert A.
National Instruments
08-09-2006 03:24 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
I am using version 7.1. It is sufficient to just change the default directory.
08-09-2006 03:25 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
All machines have this drive letter that I am trying to use.
Mert_A.
Active Participant
08-09-2006 04:05 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
In this case, I would recommend just setting the default installation path via a command line argument to setup.exe:
>> setup.exe INSTALLDIR=E:\
Replace "E:\" with whatever path you want. You can create a batch file or other script to run instead of directly running setup.exe.
The other option would be to create a custom action (in the .msi's CustomAction table) and add a call to that custom action in the InstallUISequence and InstallExecuteSequence tables. You could create a simple merge module to do this, then add the module to your distribution kit via a specially-named file group. The module will get merged into the .msi when the distribution is built.
If for whatever reason you don't want to use a script, I can create the merge module for you (just tell me what default path you want) and tell you how to add it to your distribution kit.
Hope this helps.
Mert A.
National Instruments
>> setup.exe INSTALLDIR=E:\
Replace "E:\" with whatever path you want. You can create a batch file or other script to run instead of directly running setup.exe.
The other option would be to create a custom action (in the .msi's CustomAction table) and add a call to that custom action in the InstallUISequence and InstallExecuteSequence tables. You could create a simple merge module to do this, then add the module to your distribution kit via a specially-named file group. The module will get merged into the .msi when the distribution is built.
If for whatever reason you don't want to use a script, I can create the merge module for you (just tell me what default path you want) and tell you how to add it to your distribution kit.
Hope this helps.
Mert A.
National Instruments
08-09-2006 04:21 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Getting closer. How would I create a r:\StationSoftware merge module?
08-09-2006 04:35 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Is there anyway to set this directory in the setup.ini file?
