James Hawkins wrote:
On 03 Mar 2005 11:02:24 +0100, Alexandre Julliard [EMAIL PROTECTED] wrote:
James Hawkins [EMAIL PROTECTED] writes:
I've been discerning the behavior of RegCreateKey and NtCreateKey when
creating a key directly under HKLM or HKU, and this test reveals that
NtCreateKey
On Thu, 03 Mar 2005 11:37:48 -0600, Robert Shearman [EMAIL PROTECTED] wrote:
It looks like Windows only uses RegLoadKey to create keys under HKLM and
HKU. Maybe we should do the same.
Rob
I agree we should use RegLoadKey as well to be consistent. Where is
the registry initialisation code?
James Hawkins wrote:
On Thu, 03 Mar 2005 11:37:48 -0600, Robert Shearman [EMAIL PROTECTED] wrote:
It looks like Windows only uses RegLoadKey to create keys under HKLM and
HKU. Maybe we should do the same.
Rob
I agree we should use RegLoadKey as well to be consistent. Where is
the registry
James Hawkins wrote:
On Thu, 03 Mar 2005 11:37:48 -0600, Robert Shearman [EMAIL PROTECTED] wrote:
It looks like Windows only uses RegLoadKey to create keys under HKLM and
HKU. Maybe we should do the same.
Rob
I agree we should use RegLoadKey as well to be consistent. Where is
the registry
On Thu, 03 Mar 2005 13:15:46 -0600, Robert Shearman [EMAIL PROTECTED] wrote:
I agree we should use RegLoadKey as well to be consistent. Where is
the registry initialisation code? I'd like to look around in there
and see what can be done.
It is in misc/registry.c. Changing wine to using
James Hawkins [EMAIL PROTECTED] writes:
What are the steps I need to take to break registry initialisation? I
did wonder how anything in the real win32 registry could be created
though if you can't create a key directly under HKLM or HKU. If this
really does break initialisation, can we
