[izpack-devel] Writing a TopLevel Registry Key...
bartzkau at gmx.net
Tue Nov 28 19:03:30 CET 2006
see context related...
Am 28.11.2006, 17:09 Uhr, schrieb Markus Schlegel
<markus.schlegel at pulinco.com>:
> Well, I did not knew that the HKCR is a merged view of
> HKLM/Software/Classes and HKCU/Software/Classes.
> In this case, I could simply write to HKLM/Software/Classes instead of
> HKCR ?
I think so. I think also that this will be really done if you set via HKCR.
Test it with an registry editor (e.g. regedit).
Create .aaa under HKCR (if not exist) and look under HKLM/Software/Classes
(may be after a refresh with F5). The new key is also under HKLM. There you
can add a new subkey and play vice versa. Test to create a key in the
> Apart from that, there is no problem for me to change the code to allow
> writing to the root, expect for some roots like HKLM. Are there other
> roots where it is not liked to create toplevel keys?
HKEY_USERS; it seems so that all old real roots are not writeable. HKCR is
view, HKCU also (its a view to HKEY_USERS\<SID of current user>)
I do not know the intention of HKEY_CURRENT_CONFIG; there you can create
something in the root.
> Thanks for your help
> Von: izpack-devel-bounces at lists.berlios.de im Auftrag von Bartz, Klaus
> Gesendet: Di 28.11.2006 16:13
> An: izpack-devel at lists.berlios.de
> Betreff: Re: [izpack-devel] Writing a TopLevel Registry Key...
> Hi Markus,
> in fact the registry stuff is an example for the custom action stuff. A
> more complicated and more
> functional as the simple one. It is a more or less fast port of the
> stuff I have written for our installations
> (about that the changed package path).
> I have blocked root changes because there are some roots where nobody
> have to write (e.g. HKLM).
> You know that HKCR is a merked view of HKLM/Software/Clases and
> HKCU/Software/Clases. A
> HKCU key crossfade the HKLM one. Therefore you can set the needed keys.
> I remember that I have read elsewhere that a setting at toplevel should
> not be performed. But in the
> moment I do not know where and whether it should be so only in old OS
> versions or not.
> Therefore I have no pricipiell problem to change it, I have only less
> The native part will be not a big problem because I have written it.
> __________ NOD32 1.1392 (20060202) Information __________
> Diese E-Mail wurde vom NOD32 Antivirus System geprüft
Erstellt mit Operas revolutionärem E-Mail-Modul: http://www.opera.com/mail/
More information about the izpack-devel