Info request on x86-64 7zip msi

[crashfly]

I am trying to add some tools to my installation CD. Being that 7zip is an excellent archival program, I would like to silently install the installation. At 7zip's website, only an msi file is available for the x86-64 platform. Being I do not have the appropriate aynalization programs for the msi, can someone tell me what command line parameters it would take to silently install the msi?

[5eraph]

MSIs should take /qn as a parameter to make them completely silent, if they're made to support it.

[crashfly]

Meh .... I answered my own question. It took me a bit to get to it. I just ran the 7z464-x64.msi installer with the /? option.

Here is what I got:

Code: Select all

Windows ® Installer. V 3.01.4000.3959 

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.

Edit: Now ... only to figure out how to get it into a different directory and the shortcuts where *I* want them. Muh hahhahahaha ....

// As the mad scientist runs to his lab to experiment .... //

[code65536]

Configuring the target path, if the MSI supports it:
msiexec foo.msi TARGETDIR=C:\bar\baz

[crashfly]

Hmmm ... that looks to be for the actual program directory. I will have to test that. Do you know if there is a similar msi option for the shortcuts?