RegistryPath passed to DriverEntry is incorrect.

NTDEV
1

I am debugging an NT4.0 driver and found a peculiar problem. My driver name
is “wcsccdrv.sys”. I have correctly defined the “wcsccdrv” key under
“HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services”. According to the NT
DDK documentation the RegistryPath argument to the Driver entry routine
should point to the string
“\Registry\Machine\System\CurrentControlSet\Services\wcsccdrv”. Instead I
get the string
"\REGISTRY\Machine\System\ControlSet001\Services\REGISTRY\Machine\System\Co
ntrolSet001\Services". Any ideas?

Thanks

WCSC(Willies Computer Software Co)
Web: http://www.wcscnet.com Email: xxxxx@wcscnet.com
Tel: (281)360-4232 Fax: (281)360-3231

You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

2

Berto,

Methinks thou doest use an elder version of Windbg. Older versions of WinDbg
“pervert” the truth sometimes, when looking at memory. You will note,
however, that if you use the RP string to build a name for a function call
such as IoCreateSymbolicLink, or copy it to a non-paged buffer, that it is
correct. If you aren’t using it, I would suggest you download the 2.0.0011.0
beta, or at least the last release.

Nathan,

However, Nathan, here is one for you. My bus driver (pdo) loads with a
RegistryPath (RP) from …\ControlSet, whereas the function driver (fdo)
loads with an RP from …\ControlSet002. Why?

Gary

-----Original Message-----
From: Berto [mailto:xxxxx@wcscnet.com]
Sent: Wednesday, January 03, 2001 11:41 AM
To: NT Developers Interest List
Subject: [ntdev] RegistryPath passed to DriverEntry is incorrect.

I am debugging an NT4.0 driver and found a peculiar problem.
My driver name
is “wcsccdrv.sys”. I have correctly defined the “wcsccdrv” key under
“HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services”.
According to the NT
DDK documentation the RegistryPath argument to the Driver
entry routine
should point to the string
“\Registry\Machine\System\CurrentControlSet\Services\wcsccdrv”
. Instead I
get the string
"\REGISTRY\Machine\System\ControlSet001\Services\REGISTRY\Mac
hine\System\Co
ntrolSet001\Services". Any ideas?

Thanks

WCSC(Willies Computer Software Co)
Web: http://www.wcscnet.com Email: xxxxx@wcscnet.com
Tel: (281)360-4232 Fax: (281)360-3231

You are currently subscribed to ntdev as: xxxxx@delphieng.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

3

Another interesting thing to note is that the “CurrentControlSet” is only a
symbolic link to the actual control set in use. You can determine which one
by looking at the registry key HKLM\System\Select key. It’s usually
ControlSet001. See the Jan. 2001 Window’s Developer’s Journal, the
“Understanding NT” section, for more info on this.

Ed Lau

MidCore Software, Inc.
900 Straits Tpke
Middlebury, CT 06762

www.midcore.com

----- Original Message -----
From: “Gary Little”
To: “NT Developers Interest List”
Sent: Wednesday, January 03, 2001 3:29 PM
Subject: [ntdev] RE: RegistryPath passed to DriverEntry is incorrect.

> Berto,
>
> Methinks thou doest use an elder version of Windbg. Older versions of
WinDbg
> “pervert” the truth sometimes, when looking at memory. You will note,
> however, that if you use the RP string to build a name for a function call
> such as IoCreateSymbolicLink, or copy it to a non-paged buffer, that it is
> correct. If you aren’t using it, I would suggest you download the
2.0.0011.0
> beta, or at least the last release.
>
> Nathan,
>
> However, Nathan, here is one for you. My bus driver (pdo) loads with a
> RegistryPath (RP) from …\ControlSet, whereas the function driver (fdo)
> loads with an RP from …\ControlSet002. Why?
>
> Gary
>
> > -----Original Message-----
> > From: Berto [mailto:xxxxx@wcscnet.com]
> > Sent: Wednesday, January 03, 2001 11:41 AM
> > To: NT Developers Interest List
> > Subject: [ntdev] RegistryPath passed to DriverEntry is incorrect.
> >
> >
> > I am debugging an NT4.0 driver and found a peculiar problem.
> > My driver name
> > is “wcsccdrv.sys”. I have correctly defined the “wcsccdrv” key under
> > “HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services”.
> > According to the NT
> > DDK documentation the RegistryPath argument to the Driver
> > entry routine
> > should point to the string
> > “\Registry\Machine\System\CurrentControlSet\Services\wcsccdrv”
> > . Instead I
> > get the string
> > "\REGISTRY\Machine\System\ControlSet001\Services\REGISTRY\Mac
> > hine\System\Co
> > ntrolSet001\Services". Any ideas?
> >
> > Thanks
> >
> > —
> > WCSC(Willies Computer Software Co)
> > Web: http://www.wcscnet.com Email: xxxxx@wcscnet.com
> > Tel: (281)360-4232 Fax: (281)360-3231
> >
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@delphieng.com
> > To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> >
>
> —
> You are currently subscribed to ntdev as: xxxxx@midcore.com
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com