Adding some personal notes and additional info as promised, this is not the extent of my notes.
"Somewhere I have some really detailed notes while experimenting with .msi intergration into .scripts."
I will probably have to scour some of my older .scripts to find more details.
Anywho, here it is
***** Additional .msi notes ************************************************
Here are some tools to help with .msi files:
--------------------------------------------
MSIDIFF compares or decompiles Windows Installer Databases (MSI, MSM etc)
MSIDIFF is freeware to compare or disassemble Windows Installer databases (a "MSI to TEXT" utility). While it is a command line based tool,
the installer creates shell extensions so that the decompile operations can be invoked by right clicking on a file in Explorer.
The output is very easy to read and can be processed by my MAKEMSI tool or can be further processed via my PPWIZARD preprocessor.
************************************************************************************************************************************
From: Universal Extractor\docs\msi_readme.txt
msi plugin v1.2 for Total Commander
installation:
- unzip the msi.wcx to your Total Commander installation directory
- choose the menu configuration - options
- choose the packer tab
- click the configure packer extension dlls button
- type msi as new extension
- click new type, and select msi.wcx
- click ok
- type msp as new extension
- select msi.wcx
- click ok
usage:
the plugin provides basic support for browsing and extracting from
msi (microsoft installer) database files.
note: some msi files don't contain any actual data. they only contain
references to external (mostly) cab files (which in turn are described
in another table of the msi file). those can be viewed with the normal
capability of Total Commander and may be on different volumes, in the
same directory (most likely) or elsewhere. the plugin just displays the
files actually contained within the msi file (as ole data stream). msi
files which don't contain any actual data are displayed as empty. msi
files may contain data of any type, but most of the time they just
contain one or more cab files.
update:
version 1.2 now also opens msp files (requested by some users). the same as
to msi files also applies to msp files with the addition, that the ole
streams contained in msp files don't have to be entire files, but can
only be patches. the plugin now displays all data streams contained in
the file (also on user request), whatever good it may do.
note:
if you receive an error message indicating that msi.wcx is not a valid
packer plugin (happens on older systems), then you most likely need
to install the msi dlls on your system. you can get these free of
charge from microsoft:
written by:
alexander gretha
mailto:developer@chicken.sh
**********************************************************************************************************************************************************
Windows ® Installer. V 3.00.3790.2180
msiexec /Option <Required Parameter> [Optional Parameter]
Install Options
</package | /i> <Product.msi>
Installs or configures a product
/a <Product.msi>
Administrative install - Installs a product on the network
/j<u|m> <Product.msi> [/t <Transform List>] [/g <Language ID>]
Advertises a product - m to all users, u to current user
</uninstall | /x> <Product.msi | ProductCode>
Uninstalls the product
Display Options
/quiet
Quiet mode, no user interaction
/passive
Unattended mode - progress bar only
/q[n|b|r|f]
Sets user interface level
n - No UI
b - Basic UI
r - Reduced UI
f - Full UI (default)
/help
Help information
Restart Options
/norestart
Do not restart after the installation is complete
/promptrestart
Prompts the user for restart if necessary
/forcerestart
Always restart the computer after installation
Logging Options
/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <LogFile>
i - Status messages
w - Nonfatal warnings
e - All error messages
a - Start up of actions
r - Action-specific records
u - User requests
c - Initial UI parameters
m - Out-of-memory or fatal exit information
o - Out-of-disk-space messages
p - Terminal properties
v - Verbose output
x - Extra debugging information
+ - Append to existing log file
! - Flush each line to the log
* - Log all information, except for v and x options
/log <LogFile>
Equivalent of /l* <LogFile>
Update Options
/update <Update1.msp>[;Update2.msp]
Applies update(s)
/uninstall <PatchCodeGuid>[;Update2.msp] /package <Product.msi | ProductCode>
Remove update(s) for a product
Repair Options
/f[p|e|c|m|s|o|d|a|u|v] <Product.msi | ProductCode>
Repairs a product
p - only if file is missing
o - if file is missing or an older version is installed (default)
e - if file is missing or an equal or older version is installed
d - if file is missing or a different version is installed
c - if file is missing or checksum does not match the calculated value
a - forces all files to be reinstalled
u - all required user-specific registry entries (default)
m - all required computer-specific registry entries (default)
s - all existing shortcuts (default)
v - runs from source and recaches local package
Setting Public Properties
[PROPERTY=PropertyValue]
Consult the Windows ® Installer SDK for additional documentation on the
command line syntax.
Copyright © Microsoft Corporation. All rights reserved.
Portions of this software are based in part on the work of the Independent JPEG Group.
**********************************************************************************************************************************************************
Regards
RoyM