Use the command line interface
- Last Updated: February 11, 2026
- 1 minute read
- OpenEdge
- Version 13.0
- Documentation
To access the INI2REG utility and translate an initialization file from the command line, specify the INI2REG command using the following syntax:
Syntax
|
- -a
-
Automates the translation. That is, it processes the translation automatically without presenting the graphical user interface.
- -ao
-
Automates the translation and automatically overwrites existing Registry entries.
- -i ini-file-name
-
The pathname of the initialization file to translate.
- -b base-key
-
The base key under which the subkey is created. The value of
base-keymust be one of following:HKEY_CURRENT_USER(default).HKEY_USERSHKEY_LOCAL_MACHINEHKEY_CLASSES_ROOTHKEY_CURRENT_CONFIGHKEY_DYN_DATA
- -s subkey
-
The subkey under which entries are created. The subkey is created under the base key specified in the -b parameter.
Use -d to specify a default subkey for the translation destination.
- -d default-subkey
-
The default subkey under which entries are created. The default subkey is created under the base key specified in the -b parameter.
If the base key is
HKEY_LOCAL_MACHINEorHKEY_CURRENT_USER, INI2REG prependsSOFTWAREto the specified default subkey. If the initialization file name is not progress.ini, INI2REG appends the root name of the initialization file to the specified default subkey. If this parameter is not specified, INI2REG uses a default subkey ofPSC\PROGRESS\version.You can generalize this as follows:
base-key\[SOFTWARE]\default-subkey\[rootname]Use -s to specify a complete subkey for the translation destination.
By default, the INI2REG utility creates Registry key entries for 32-bit OpenEdge at the following location:
HKEY_CURRENT_USER\SOFTWARE\PSC\PROGRESS\versionBy default, the INI2REG utility creates Registry key entries for 64-bit OpenEdge at the following location:
HKEY_CURRENT_USER\SOFTWARE\PSC\PROGRESS\x64\version