Prev: Help disabling a device using SetupDiXXX fns after WM_DEVICECHANGE
Next: Duplicating NDIS_PACKET
From: kimi on 24 Oct 2005 13:30
If I have the path \Registry\Machine\Software\a\b\c\d\e

My question, do I need to create a first, then b, then c, etc
or can I create them in one call?


From: Pavel A. on 24 Oct 2005 15:16
"kimi" wrote:
> If I have the path \Registry\Machine\Software\a\b\c\d\e
>
> My question, do I need to create a first, then b, then c, etc
> or can I create them in one call?

See RtlCreateRegistryKey

--

From: kimi on 24 Oct 2005 20:03
> See RtlCreateRegistryKey


Can you see what's wrong here,

pathWide= L"\\Registry\\Machine\\SOFTWARE\\aa\\bb\\cc\\dd";
ntstatus= RtlCreateRegistryKey(RTL_REGISTRY_ABSOLUTE, pathWide);


it's failling with,
STATUS_OBJECT_NAME_NOT_FOUND ((NTSTATUS)0xC0000034L)?


From: kimi on 24 Oct 2005 20:43

it can't be done pavel, r u trying to confuse???


From: Norman Diamond on 24 Oct 2005 21:58
<kimi> wrote in message news:OV2lR0P2FHA.892(a)TK2MSFTNGP12.phx.gbl...

> it can't be done pavel, r u trying to confuse???

Here's what he told you:

>> See RtlCreateRegistryKey

What do you think is confusing about that? Did you obey?

I looked at
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/Kernel_r/hh/Kernel_r/k109_9a163bcc-501d-453b-b426-a4267d04135c.xml.asp
and MSDN's silence on this question is pretty clear. MSDN is trying to
confuse. You have to experiment to see if it can be done. And if you rely
on the results of your experiments, Microsoft will blame you for relying on
undocumented behaviour. So when you want to complain about who's trying to
confuse, put the blame where it belongs, OK?

 |  Next  |  Last
Pages: 1 2
Prev: Help disabling a device using SetupDiXXX fns after WM_DEVICECHANGE
Next: Duplicating NDIS_PACKET