ntdll: Add NtCreateKey tests

[James Hawkins]

On 03 Mar 2005 11:02:24 +0100, Alexandre Julliard <julliard at winehq.org> wrote:
> James Hawkins <truiken at gmail.com> 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 does check for this case and returns a
> > STATUS_INVALID_PARAMETER.
> 
> This is going to break registry initialisation. Do you really have an
> app that depends on that?
> 

I was attempting to bring the behaviour of CreateKey more in line with
win32's implementation, but I'd rather not create a problem.  I'm
trying to reproduce this break though, but I'm not seeing it.  I
removed my .wine directory and immediately ran the ntdll test:

wine: creating configuration directory '/home/truiken/.wine'...
wine: '/home/truiken/.wine' created successfully.
reg.c:148:**Test 0**
reg.c:161:ValueName: (null)
reg.c:166:ValueType: REG_NONE
reg.c:167:ValueData: 0
reg.c:195:ValueLength: 0
reg.c:148:**Test 1**
reg.c:158:ValueName: deletetestvar=01a
reg.c:191:ValueType: REG_DWORD
reg.c:192:ValueData: 2009272024
reg.c:195:ValueLength: 4
reg: 14 tests executed, 0 marked as todo, 0 failures.

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 implement a different
create_key that has little restrictions and would only be used
internally, or would this just be scrapped entirely?

-- 
James Hawkins