|ARM Technical Support Knowledge Articles|
Applies to: uVision IDE
Information in this article applies to:
I need to configure an install program which copies add-on DLL's into the product folder. I have created AGDI and AGSI DLL's and now I would like to copy them into the path where uVision is installed. How can I automatically determine the install path of uVision on a computer?
Products released after April 2008 create the following registry key during installation:
The following product names are currently valid:
HKEY_LOCAL_MACHINE/SOFTWARE/Keil/Products/AR166 HKEY_LOCAL_MACHINE/SOFTWARE/Keil/Products/C166 HKEY_LOCAL_MACHINE/SOFTWARE/Keil/Products/C251 HKEY_LOCAL_MACHINE/SOFTWARE/Keil/Products/C51 HKEY_LOCAL_MACHINE/SOFTWARE/Keil/Products/MDK HKEY_LOCAL_MACHINE/SOFTWARE/Keil/Products/RLARM
Each of these registry keys stores:
Please note that 64-bit versions of Windows insert the sub-key 'Wow6432Node' after 'SOFTWARE' and before 'Keil' (i.e. HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Keil\Products\MDK) for 32-bit applications like uVision. However, if other 32-bit applications (i.e. your installer) queries this registry key the sub-key 'Wow6432Node' is not needed.
For products released before May 2008, the install path can be found via the uninstall information. Depending on your uVision version, one of the following registry keys contains the installation path:
AGDI and AGSI DLLs usually need to be copied into the BIN folder of the respective toolset (e.g. \C51\BIN, \C251\BIN\, \C166\BIN or \ARM\BIN).
Article last edited on: 2011-07-04 03:00:59
Did you find this article helpful? Yes No
How can we improve this article?