Can we use eVC++ 3.0's Remote Registry Editor?

I am trying to use eVC++ 3.0's Remote Registry Editor to
create registry subkeys for my WinCE v3.0 NDIS protocol
driver DLL. But not successful.

The MSDN WinCE 3.0 document(Protocol-Driver Initialization
section) says that users must set the registry values for
the following registry key:
HKEY_LOCAL_MACHINE\Drivers\BuiltIn\MyDriver
Subkey DLL "Mydriver.dll"
Order dword:3
Keep dword:1
Entry MyDriverInitialize

The following were my detailed creation steps:
Tools
Remote Registry Editor
My Computer
HKEY_LOCAL_MICHINE
Edit
New
Key
Drivers --- I typed in the string for subkey here
OK
"Registry Error - Unable to create specified key."

However, creating the subkey "Drivers" under
\HKEY_LOCAL_MICHINE\SYSTEM or \HKEY_LOCAL_MICHINE\SOFTWARE
seems OK. This results in different subkey's tree
structure though.

Has anyone seen this problem before? What is the best way
to create and set the NDIS protocol driver's registry
subkeys and values?

Regards,
Gordon

Paul
Wed Sep 03 10:43:07 CDT 2003

Most of those keys already exist. If you use the capability of the remote
registry editor, you'll see that. If you try to create a key that already
exists, you'll get that error. Only create the keys and values which don't
already exist...

Paul T.

"Gordon" <gzhang@hotmail.com> wrote in message
news:06a201c371c7$9331f060$a401280a@phx.gbl...
> I am trying to use eVC++ 3.0's Remote Registry Editor to
> create registry subkeys for my WinCE v3.0 NDIS protocol
> driver DLL. But not successful.
>
> The MSDN WinCE 3.0 document(Protocol-Driver Initialization
> section) says that users must set the registry values for
> the following registry key:
> HKEY_LOCAL_MACHINE\Drivers\BuiltIn\MyDriver
> Subkey DLL "Mydriver.dll"
> Order dword:3
> Keep dword:1
> Entry MyDriverInitialize
>
> The following were my detailed creation steps:
> Tools
> Remote Registry Editor
> My Computer
> HKEY_LOCAL_MICHINE
> Edit
> New
> Key
> Drivers --- I typed in the string for subkey here
> OK
> "Registry Error - Unable to create specified key."
>
> However, creating the subkey "Drivers" under
> \HKEY_LOCAL_MICHINE\SYSTEM or \HKEY_LOCAL_MICHINE\SOFTWARE
> seems OK. This results in different subkey's tree
> structure though.
>
> Has anyone seen this problem before? What is the best way
> to create and set the NDIS protocol driver's registry
> subkeys and values?
>
> Regards,
> Gordon