Page tree
Skip to end of metadata
Go to start of metadata

Normally gmStudio is started by clicking the gmStudio icon (e.g., start menu) or by clicking a gmProj file.  Then, the OS finds the executable and starts the application.  gmStudio usually uses the folder where the running executable is located so it can find system configuration files.  This location is stored in the Registry. 

In special cases, a user might want to run a specific version of gmStudio rather than the last one installed. In that case, the location of the system configuration files can be determined by the Application.StartupPath.  The steps for running a specific version of gmStudio other than the installed version are as follows:

1. Select the desired gmStudio Installer (gmStudioSetup.msi file)

2. Extract files to a desired location using msiexec, for example:

msiexec /a gmStudioSetup.msi /qb /l* 1install.log TARGETDIR=c:\temp\gmStudio

3. If running a version prior to the October 2017 release, enter the name of the selected  install folder in the gmStudio.cfg configuration file, as follows:

"%AppExeFolder% -> install location

4. Run gmStudio using the custom configuration file:

c:\temp\gmStudio\gmStudio.exe /CFG=c:\temp\gmStudio\gmStudio.cfg


MSIEXEC Command Line

Windows ® Installer. V 5.0.7601.23593 

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 (unpack only?)
	/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 mode, no user interaction
		Unattended mode - progress bar only
		Sets user interface level
		n - No UI
		b - Basic UI
		r - Reduced UI
		f - Full UI (default)
		Help information
Restart Options
		Do not restart after the installation is complete
		Prompts the user for restart if necessary
		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



  • No labels