This website uses cookies. By clicking Accept, 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.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: /Extract_All does not function with MSI pacakges
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 09, 2009
11:39 AM
/Extract_All does not function with MSI pacakges
I am trying to make use of the /extract_all parameter and having trouble with errors when I attempt to do so with packages produced from Basic MSI projects. The documentation does not seem to indicate that the parameter should not work with that project type but while the command works fine with an InstallScript project it produces the following errors when used with any 2009 Basic MSI project:
"1152: Error extracting 'xtract_all:'\Setup.INI' to the temporary location [OK]"
"Error reading setup initialization file. [OK]"
"1155: [OK]"
The setup package otherwise functions normally.
Thanks!
"1152: Error extracting 'xtract_all:
"Error reading setup initialization file. [OK]"
"1155: [OK]"
The setup package otherwise functions normally.
Thanks!
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 09, 2009
11:41 AM
That is correct and intended. The closest equivalent to /extract_all for MSI packages is an administrative install, run instead with /a.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 09, 2009
11:46 AM
That method does not appear to extract any pre-requisites that might also be included in the setup.exe. In this case I was hoping to be able to provide a useful way for a customer to be able to extract the various MSI packages from the setup.exe without having to go muck around in the temp directories.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 09, 2009
04:09 PM
Have you tried passing a path attached to the /a parameter -- something like setup.exe /a"C:\Temp" ?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 09, 2009
04:14 PM
Ah! That takes care of it. Thanks!
![](/skins/images/8C9D13A71C7F7695F3262372C0172D68/responsive_peak/images/icon_anonymous_message.png)