I apologize for asking such a basic question, but I really want to make
sure before I play around with the registry.
I thought that once upon a time the path to the registry key for the driver
was passed into the driver. However, from reading around the net and the
WDM DDK, I am confused. Where should I look to unconfuse myself? Is it
true that I should not use that path? I am resurrecting an NT 4 driver and
hoping that getting it to work under Win2K won’t be impossible. We have
several parameters that need to be accessed by the driver and I would think
that the registry would be the place for them. My device driver coding is
really from NT4, but I know that we are going to go to WinXP so I would
like to do this “right” if possible. I was going to put the parameters in
HKLM\System\CurrentControlSet\Services\MyDriver\Parameters(keys/values
here). Is that not correct anymore (if it ever was)? If not, where is the
normal place to put device driver parameters?
Also, where is the normal/standard/whatever place to put device driver data
that is too large to fit in the registry? We load hex files into our card
and I don’t know if \Winnt\System32\drivers is the correct place or
not. If not, then where?
If anyone has any advice or knowledge I sure would appreciate you passing
it on.
Also, I have Walter Oney’s book “Programming the Microsoft Windows Driver
Model” from 1999. Is there a later release or another book that I should
read? This one is fine, but I know that I am going to have to move this
driver to XP eventually and I don’t know what has changed. And I think
that Walter Oney’s book was published in 1999, before XP. Or are the
changes for XP so small that there really is no need?
Thanks very much,
Michael
The second release of the Oney’s should be out on
December 9, 2002.
http://www.microsoft.com/mspress/books/6262.asp
I am wondering if the second release will cover
NDIS. Could the author let us know?
Thanks
— Michael Wade wrote:
> I apologize for asking such a basic question, but I
> really want to make
> sure before I play around with the registry.
>
> I thought that once upon a time the path to the
> registry key for the driver
> was passed into the driver. However, from reading
> around the net and the
> WDM DDK, I am confused. Where should I look to
> unconfuse myself? Is it
> true that I should not use that path? I am
> resurrecting an NT 4 driver and
> hoping that getting it to work under Win2K won’t be
> impossible. We have
> several parameters that need to be accessed by the
> driver and I would think
> that the registry would be the place for them. My
> device driver coding is
> really from NT4, but I know that we are going to go
> to WinXP so I would
> like to do this “right” if possible. I was going to
> put the parameters in
>
HKLM\System\CurrentControlSet\Services\MyDriver\Parameters(keys/values
>
> here). Is that not correct anymore (if it ever
> was)? If not, where is the
> normal place to put device driver parameters?
>
> Also, where is the normal/standard/whatever place to
> put device driver data
> that is too large to fit in the registry? We load
> hex files into our card
> and I don’t know if \Winnt\System32\drivers is the
> correct place or
> not. If not, then where?
>
> If anyone has any advice or knowledge I sure would
> appreciate you passing
> it on.
>
> Also, I have Walter Oney’s book “Programming the
> Microsoft Windows Driver
> Model” from 1999. Is there a later release or
> another book that I should
> read? This one is fine, but I know that I am going
> to have to move this
> driver to XP eventually and I don’t know what has
> changed. And I think
> that Walter Oney’s book was published in 1999,
> before XP. Or are the
> changes for XP so small that there really is no
> need?
>
> Thanks very much,
> Michael
>
>
>
>
> —
> You are currently subscribed to ntdev as:
> xxxxx@yahoo.com
> To unsubscribe send a blank email to
%%email.unsub%%
__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
Phong Ho wrote:
The second release of the Oney’s should be out on
December 9, 2002.
http://www.microsoft.com/mspress/books/6262.asp
I am wondering if the second release will cover
NDIS. Could the author let us know?
It does not cover NDIS, sorry. The market for an NDIS book is probably
too small to attract any publisher. Several of us with knowledge of the
parts that go into an NDIS driver talked about a collaboration a few
years ago, but we couldn’t figure out how to pay the bills while writing
the book.
On the subject of registry keys that started this thread: the key passed
into DriverEntry is the so-called “service” key. WDM drivers don’t
ordinarily need to put anything there. Usually, you would store
parameter information in either the hardware key or the driver key,
which are accessible using IoOpenDeviceRegistryKey. The 2d edition has
(in my opinion, anyway) a better organized discussion about registry
keys in the chapter on distributing device drivers.
–
Walter Oney, Consulting and Training
Basic and Advanced Driver Programming Seminars
Now teaming with John Hyde for USB Device Engineering Seminars
Check out our schedule at http://www.oneysoft.com