[izpack-devel] Writing a TopLevel Registry Key...

Markus Schlegel markus.schlegel at pulinco.com
Tue Nov 28 17:09:44 CET 2006

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 ?
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?
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 time.
The native part will be not a big problem because I have written it.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/ms-tnef
Size: 5522 bytes
Desc: not available
Url : https://lists.berlios.de/pipermail/izpack-devel/attachments/20061128/4246c122/attachment.bin 

More information about the izpack-devel mailing list