Including <ntstrsafe.h> won't work with DRIVER_TYPE=WDM

When I add "DRIVER_TYPE = WDM" in my SOURCES file, the compiler can't
find <ntstrsafe.h> any more.

I suspect DRIVER_TYPE mess with the include directories so my question
is : Should I manually add the missing include path or simply drop the
DRIVER_TYPE option ? What is its purpose anyway ?

Thanks for your time.

pavel_a
Sun Sep 10 13:33:01 CDT 2006

"Your Name" wrote:
> When I add "DRIVER_TYPE = WDM" in my SOURCES file, the compiler can't
> find <ntstrsafe.h> any more.

Don't add "DRIVER_TYPE = WDM".
Use the documented macro, TARGETTYPE.

--PA

Your
Mon Sep 11 04:19:35 CDT 2006

Do you guys use DRIVER_TYPE at all in your SOURCES files ?

Your Name a écrit :
> When I add "DRIVER_TYPE = WDM" in my SOURCES file, the compiler can't
> find <ntstrsafe.h> any more.
>
> I suspect DRIVER_TYPE mess with the include directories so my question
> is : Should I manually add the missing include path or simply drop the
> DRIVER_TYPE option ? What is its purpose anyway ?
>
> Thanks for your time.

Eliyas
Mon Sep 11 09:16:18 CDT 2006

This directive is no longer useful. This was introduced when DDK supported
building single binary compatible driver for Win9x and NT. Those days are
gone. So using this driver doesn't buy you anything. Hardly any drivers in
MS using this directive so this is largely an untested directive. I will
make sure that we get rid of this from DDK in the next release.

-Eliyas

"Your Name" <user@example.com> wrote in message
news:45052a27$0$1783$636a55ce@news.free.fr...
> Do you guys use DRIVER_TYPE at all in your SOURCES files ?
>
> Your Name a écrit :
>> When I add "DRIVER_TYPE = WDM" in my SOURCES file, the compiler can't
>> find <ntstrsafe.h> any more.
>>
>> I suspect DRIVER_TYPE mess with the include directories so my question is
>> : Should I manually add the missing include path or simply drop the
>> DRIVER_TYPE option ? What is its purpose anyway ?
>>
>> Thanks for your time.

Maxim
Mon Sep 11 14:15:12 CDT 2006

Am I correct that some power management stuff depends on it?

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@storagecraft.com
http://www.storagecraft.com

"Eliyas Yakub [MSFT]" <eliyasy@online.microsoft.com> wrote in message
news:OIVcU0a1GHA.4392@TK2MSFTNGP04.phx.gbl...
> This directive is no longer useful. This was introduced when DDK supported
> building single binary compatible driver for Win9x and NT. Those days are
> gone. So using this driver doesn't buy you anything. Hardly any drivers in
> MS using this directive so this is largely an untested directive. I will
> make sure that we get rid of this from DDK in the next release.
>
> -Eliyas
>
> "Your Name" <user@example.com> wrote in message
> news:45052a27$0$1783$636a55ce@news.free.fr...
> > Do you guys use DRIVER_TYPE at all in your SOURCES files ?
> >
> > Your Name a écrit :
> >> When I add "DRIVER_TYPE = WDM" in my SOURCES file, the compiler can't
> >> find <ntstrsafe.h> any more.
> >>
> >> I suspect DRIVER_TYPE mess with the include directories so my question is
> >> : Should I manually add the missing include path or simply drop the
> >> DRIVER_TYPE option ? What is its purpose anyway ?
> >>
> >> Thanks for your time.
>
>

Your
Tue Sep 12 09:04:41 CDT 2006

Thank you, I'll mimic the DDK samples.

Eliyas Yakub [MSFT] a écrit :
> This directive is no longer useful. This was introduced when DDK supported
> building single binary compatible driver for Win9x and NT. Those days are
> gone. So using this driver doesn't buy you anything. Hardly any drivers in
> MS using this directive so this is largely an untested directive. I will
> make sure that we get rid of this from DDK in the next release.
>
> -Eliyas
>
> "Your Name" <user@example.com> wrote in message
> news:45052a27$0$1783$636a55ce@news.free.fr...
>> Do you guys use DRIVER_TYPE at all in your SOURCES files ?
>>
>> Your Name a écrit :
>>> When I add "DRIVER_TYPE = WDM" in my SOURCES file, the compiler can't
>>> find <ntstrsafe.h> any more.
>>>
>>> I suspect DRIVER_TYPE mess with the include directories so my question is
>>> : Should I manually add the missing include path or simply drop the
>>> DRIVER_TYPE option ? What is its purpose anyway ?
>>>
>>> Thanks for your time.
>
>

Eliyas
Tue Sep 12 09:21:58 CDT 2006

We discussed this issue years ago. Here is my google search on this topic:

http://groups.google.com/groups/search?hl=en&q=Is+legacy+driver+Eliyas+WDM&qt_s=Search

-Eliyas