Hi
When i compile my program, using the ndis.h and ntddk.h on VC6, i get
the error message "Compiler version not supported by Windows DDK".
I'm not writing a driver, but a program that use a driver (therfore, i
think, compiling with the build program of the DDK is not the right
solution).
Is there another solution to that situation?

Thanks,
D

Re: Compiler version not supported by Windows DDK by Andy

Andy
Wed Sep 07 04:56:29 CDT 2005

Sounds like the problem I had with an old project when I tried to
compile it using VC6 and the new WinXP DDK. Think you need the later
compiler that comes with VS2003 or drop back to Win2000 DDK.
Am sure someone else in the group would know the exact compiler version
number


Re: Compiler version not supported by Windows DDK by Pavel

Pavel
Wed Sep 07 05:43:32 CDT 2005

Hi,
The .H files from the DDK indeed rely on certain features of the compiler
and therefore check for compatible version.
You might be doing something unusual, because normal usermode
programs don't include ndis.h or ntddk.h.

By the way, the DDK build utility can build usermode programs.
See the DDK samples, some of them do include test apps.
It uses the DDK compiler, headers and libraries for everything.
--PA

<e_shalom@walla.com> wrote in message news:1126084794.889822.81790@f14g2000cwb.googlegroups.com...
> Hi
> When i compile my program, using the ndis.h and ntddk.h on VC6, i get
> the error message "Compiler version not supported by Windows DDK".
> I'm not writing a driver, but a program that use a driver (therfore, i
> think, compiling with the build program of the DDK is not the right
> solution).
> Is there another solution to that situation?
>
> Thanks,
> D
>



Re: Compiler version not supported by Windows DDK by Mark

Mark
Wed Sep 07 06:01:05 CDT 2005

e_shalom@walla.com wrote:
> Hi
> When i compile my program, using the ndis.h and ntddk.h on VC6, i get
> the error message "Compiler version not supported by Windows DDK".
> I'm not writing a driver, but a program that use a driver (therfore, i
> think, compiling with the build program of the DDK is not the right
> solution).
> Is there another solution to that situation?
>
> Thanks,
> D
>
In addition to the other comments: ntddk.h is not appropriate for a user
mode application and I suspect that ndis.h has the same quality. You
should be looking elsewhere for the definitions you need from these files.

If you use the ddk include files you need to use the ddk supplied
compiler. If you are using the VS6 compiler you need to get your include
files from the SDK.

--

=====================
Mark Roddy DDK MVP
Windows 2003/XP/2000 Consulting
Hollis Technology Solutions 603-321-1032
www.hollistech.com

Re: Compiler version not supported by Windows DDK by e_shalom

e_shalom
Wed Sep 07 08:01:03 CDT 2005

What i'm trying to do is write within my project a component that
imitates the Wireless Zero Configuration service, but when I try to set
WEP key I fail.
I understood that the problem stems from the fact that I have to set
OID_802_3_MULTICAST_LIST as well as the wireless OIDs. In order to that
I need the ntddk.h and ndis.h.
Is there another way?
Thanks
D


Re: Compiler version not supported by Windows DDK by Alexander

Alexander
Wed Sep 07 08:53:45 CDT 2005

#include <ntddndis.h>

Those ntdd* files contain definitions for interfacing drivers and user mode.

<e_shalom@walla.com> wrote in message
news:1126098062.978699.264540@f14g2000cwb.googlegroups.com...
> What i'm trying to do is write within my project a component that
> imitates the Wireless Zero Configuration service, but when I try to set
> WEP key I fail.
> I understood that the problem stems from the fact that I have to set
> OID_802_3_MULTICAST_LIST as well as the wireless OIDs. In order to that
> I need the ntddk.h and ndis.h.
> Is there another way?
> Thanks
> D
>



Re: Compiler version not supported by Windows DDK by Norman

Norman
Wed Sep 07 19:44:14 CDT 2005

"Pavel A." <pavel_a@NOwritemeNO.com> wrote in message
news:umPFBk5sFHA.3080@TK2MSFTNGP15.phx.gbl...
> You might be doing something unusual, because normal usermode programs
> don't include ndis.h or ntddk.h.

and "Mark Roddy" <markr@hollistech.com> wrote in message
news:eW7ezt5sFHA.420@TK2MSFTNGP15.phx.gbl...
> In addition to the other comments: ntddk.h is not appropriate for a user
> mode application and I suspect that ndis.h has the same quality.

Microsoft doesn't seem to feel that way.

In newsgroup microsoft.public.win32.programmer.kernel
thread subject "More MSDN lies: RtlStringCchLength"
starting 2005年8月24日 14:25 in the time zone of Microsoft's news server,
one subthread arose because ntddk.h and wdk.h provide declarations for TCHAR
and some other stuff, but not as many declarations as user mode programs
usually get from other headers. Microsoft said that ntddk.h and wdk.h
export declarations of TCHAR for use by user mode programs, not for use by
kernel mode programs.

(On reading that, I suggested adding separate header files for use by new
kernel mode programs in the future, which would not export declarations of
identifiers that should not be used by kernel mode programs. Microsoft did
not reply.)

Anyway, if ntddk.h and wdk.h were not appropriate for user mode applications
then they would not export declarations of TCHAR at all, and Microsoft would
not have said that these headers are for use by both kernel mode and user
mode applications.


Re: Compiler version not supported by Windows DDK by Mark

Mark
Wed Sep 07 22:02:32 CDT 2005

Norman Diamond wrote:
> "Pavel A." <pavel_a@NOwritemeNO.com> wrote in message
> news:umPFBk5sFHA.3080@TK2MSFTNGP15.phx.gbl...
>
>> You might be doing something unusual, because normal usermode programs
>> don't include ndis.h or ntddk.h.
>
>
> and "Mark Roddy" <markr@hollistech.com> wrote in message
> news:eW7ezt5sFHA.420@TK2MSFTNGP15.phx.gbl...
>
>> In addition to the other comments: ntddk.h is not appropriate for a user
>> mode application and I suspect that ndis.h has the same quality.
>
>
> Microsoft doesn't seem to feel that way.
>
> In newsgroup microsoft.public.win32.programmer.kernel
> thread subject "More MSDN lies: RtlStringCchLength"
> starting 2005年8月24日 14:25 in the time zone of Microsoft's news server,
> one subthread arose because ntddk.h and wdk.h provide declarations for
> TCHAR
> and some other stuff, but not as many declarations as user mode programs
> usually get from other headers. Microsoft said that ntddk.h and wdk.h
> export declarations of TCHAR for use by user mode programs, not for use by
> kernel mode programs.
>
> (On reading that, I suggested adding separate header files for use by new
> kernel mode programs in the future, which would not export declarations of
> identifiers that should not be used by kernel mode programs. Microsoft did
> not reply.)
>
> Anyway, if ntddk.h and wdk.h were not appropriate for user mode
> applications
> then they would not export declarations of TCHAR at all, and Microsoft
> would
> not have said that these headers are for use by both kernel mode and user
> mode applications.
>
Microsoft misspoke. TCHAR is defined in ntdef.h by the way.

--

=====================
Mark Roddy DDK MVP
Windows 2003/XP/2000 Consulting
Hollis Technology Solutions 603-321-1032
www.hollistech.com

Re: Compiler version not supported by Windows DDK by Doron

Doron
Thu Sep 08 02:32:17 CDT 2005

i didn't misspeak, i was misunderstood. i said that ntdef.h was used for
both environments. i never said ntddk.h or wdm.h was meant to be used by
UM.

d

--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.


"Mark Roddy" <markr@hollistech.com> wrote in message
news:OjOUDHCtFHA.2076@TK2MSFTNGP14.phx.gbl...
> Norman Diamond wrote:
>> "Pavel A." <pavel_a@NOwritemeNO.com> wrote in message
>> news:umPFBk5sFHA.3080@TK2MSFTNGP15.phx.gbl...
>>
>>> You might be doing something unusual, because normal usermode programs
>>> don't include ndis.h or ntddk.h.
>>
>>
>> and "Mark Roddy" <markr@hollistech.com> wrote in message
>> news:eW7ezt5sFHA.420@TK2MSFTNGP15.phx.gbl...
>>
>>> In addition to the other comments: ntddk.h is not appropriate for a user
>>> mode application and I suspect that ndis.h has the same quality.
>>
>>
>> Microsoft doesn't seem to feel that way.
>>
>> In newsgroup microsoft.public.win32.programmer.kernel
>> thread subject "More MSDN lies: RtlStringCchLength"
>> starting 2005年8月24日 14:25 in the time zone of Microsoft's news server,
>> one subthread arose because ntddk.h and wdk.h provide declarations for
>> TCHAR
>> and some other stuff, but not as many declarations as user mode programs
>> usually get from other headers. Microsoft said that ntddk.h and wdk.h
>> export declarations of TCHAR for use by user mode programs, not for use
>> by
>> kernel mode programs.
>>
>> (On reading that, I suggested adding separate header files for use by new
>> kernel mode programs in the future, which would not export declarations
>> of
>> identifiers that should not be used by kernel mode programs. Microsoft
>> did
>> not reply.)
>>
>> Anyway, if ntddk.h and wdk.h were not appropriate for user mode
>> applications
>> then they would not export declarations of TCHAR at all, and Microsoft
>> would
>> not have said that these headers are for use by both kernel mode and user
>> mode applications.
>>
> Microsoft misspoke. TCHAR is defined in ntdef.h by the way.
>
> --
>
> =====================
> Mark Roddy DDK MVP
> Windows 2003/XP/2000 Consulting
> Hollis Technology Solutions 603-321-1032
> www.hollistech.com



Re: Compiler version not supported by Windows DDK by e_shalom

e_shalom
Thu Sep 08 03:35:08 CDT 2005

The ntddndis.h doesn't contain the definitions for setting
OID_802_3_MULTICAST_LIST (like NDIS_HANDLE, PMP_ADAPTER,PVELAN) and
include the files where they defined (ndis.h, ntddk.h) is impossible in
user mode programs in VC6 as far as I know...


Re: Compiler version not supported by Windows DDK by Norman

Norman
Thu Sep 08 04:59:07 CDT 2005

OK. Then there needs to be an ntkerneldef.h (oops that isn't an MS-DOS
compatible name, but there needs to be something like that). Let ntdef.h
continue to export a subset of the TCHAR stuff for some unknown subset of
user mode applications that use that subset of TCHAR stuff. Let ntddk.h and
wdm.h do a nested include of the new def header instead of ntdef.h.

"Doron Holan [MS]" <doronh@nospam.microsoft.com> wrote in message
news:OKuNxdEtFHA.1172@TK2MSFTNGP11.phx.gbl...
>i didn't misspeak, i was misunderstood. i said that ntdef.h was used for
>both environments. i never said ntddk.h or wdm.h was meant to be used by
>UM.
>
> d
>
> --
> Please do not send e-mail directly to this alias. this alias is for
> newsgroup purposes only.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
>
> "Mark Roddy" <markr@hollistech.com> wrote in message
> news:OjOUDHCtFHA.2076@TK2MSFTNGP14.phx.gbl...
>> Norman Diamond wrote:
>>> "Pavel A." <pavel_a@NOwritemeNO.com> wrote in message
>>> news:umPFBk5sFHA.3080@TK2MSFTNGP15.phx.gbl...
>>>
>>>> You might be doing something unusual, because normal usermode programs
>>>> don't include ndis.h or ntddk.h.
>>>
>>>
>>> and "Mark Roddy" <markr@hollistech.com> wrote in message
>>> news:eW7ezt5sFHA.420@TK2MSFTNGP15.phx.gbl...
>>>
>>>> In addition to the other comments: ntddk.h is not appropriate for a
>>>> user
>>>> mode application and I suspect that ndis.h has the same quality.
>>>
>>>
>>> Microsoft doesn't seem to feel that way.
>>>
>>> In newsgroup microsoft.public.win32.programmer.kernel
>>> thread subject "More MSDN lies: RtlStringCchLength"
>>> starting 2005年8月24日 14:25 in the time zone of Microsoft's news
>>> server,
>>> one subthread arose because ntddk.h and wdk.h provide declarations for
>>> TCHAR
>>> and some other stuff, but not as many declarations as user mode programs
>>> usually get from other headers. Microsoft said that ntddk.h and wdk.h
>>> export declarations of TCHAR for use by user mode programs, not for use
>>> by
>>> kernel mode programs.
>>>
>>> (On reading that, I suggested adding separate header files for use by
>>> new
>>> kernel mode programs in the future, which would not export declarations
>>> of
>>> identifiers that should not be used by kernel mode programs. Microsoft
>>> did
>>> not reply.)
>>>
>>> Anyway, if ntddk.h and wdk.h were not appropriate for user mode
>>> applications
>>> then they would not export declarations of TCHAR at all, and Microsoft
>>> would
>>> not have said that these headers are for use by both kernel mode and
>>> user
>>> mode applications.
>>>
>> Microsoft misspoke. TCHAR is defined in ntdef.h by the way.
>>
>> --
>>
>> =====================
>> Mark Roddy DDK MVP
>> Windows 2003/XP/2000 Consulting
>> Hollis Technology Solutions 603-321-1032
>> www.hollistech.com
>
>


Re: Compiler version not supported by Windows DDK by Mark

Mark
Thu Sep 08 06:49:10 CDT 2005

Doron Holan [MS] wrote:
> i didn't misspeak, i was misunderstood. i said that ntdef.h was used for
> both environments. i never said ntddk.h or wdm.h was meant to be used by
> UM.
>
> d
>
I was being generous to the poster.

--

=====================
Mark Roddy DDK MVP
Windows 2003/XP/2000 Consulting
Hollis Technology Solutions 603-321-1032
www.hollistech.com

Re: Compiler version not supported by Windows DDK by Maxim

Maxim
Thu Sep 08 15:04:15 CDT 2005

Just copy/paste the definition to some user mode header file of your own.

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

<e_shalom@walla.com> wrote in message
news:1126168508.052078.298740@g49g2000cwa.googlegroups.com...
> The ntddndis.h doesn't contain the definitions for setting
> OID_802_3_MULTICAST_LIST (like NDIS_HANDLE, PMP_ADAPTER,PVELAN) and
> include the files where they defined (ndis.h, ntddk.h) is impossible in
> user mode programs in VC6 as far as I know...
>



Re: Compiler version not supported by Windows DDK by pavel_a

pavel_a
Thu Sep 08 19:42:03 CDT 2005

"Maxim S. Shatskih" wrote:
> Just copy/paste the definition to some user mode header file of your own.

I wish this is the biggest problem it the OP's project.
Welcome to the club of wireless hackers :-(

--PA


Re: Compiler version not supported by Windows DDK by Maxim

Maxim
Thu Sep 08 19:53:35 CDT 2005

Did some job for wireless on Pocket PC 2003 :)

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

"Pavel A." <pavel_a@NOwritemeNO.com> wrote in message
news:5EB0EE8B-DC4C-40D3-9C87-A5120779DCEE@microsoft.com...
> "Maxim S. Shatskih" wrote:
> > Just copy/paste the definition to some user mode header file of your
own.
>
> I wish this is the biggest problem it the OP's project.
> Welcome to the club of wireless hackers :-(
>
> --PA
>



Re: Compiler version not supported by Windows DDK by Pavel

Pavel
Fri Sep 09 08:02:48 CDT 2005

<e_shalom@walla.com> wrote in message news:1126168508.052078.298740@g49g2000cwa.googlegroups.com...
> The ntddndis.h doesn't contain the definitions for setting
> OID_802_3_MULTICAST_LIST (like NDIS_HANDLE, PMP_ADAPTER,PVELAN) and
> include the files where they defined (ndis.h, ntddk.h) is impossible in
> user mode programs in VC6 as far as I know...

This is for a reason. Nobody except of protocol sets multicast list.
And protocols are NDIS kernel mode drivers.
Usermode apps can get MC list by WMI query for MSNdis_EthernetMulticastList.

--PA



Re: Compiler version not supported by Windows DDK by Pavel

Pavel
Fri Sep 09 06:35:22 CDT 2005

"Maxim S. Shatskih" <maxim@storagecraft.com> wrote in message news:uK29hiNtFHA.2008@TK2MSFTNGP10.phx.gbl...
> Did some job for wireless on Pocket PC 2003

But not writing a supplicant? :)

--P



Re: Compiler version not supported by Windows DDK by e_shalom

e_shalom
Sun Sep 11 02:24:23 CDT 2005

I have to SET the MC list (so a WMI query won't help) cause I
understood that some device drivers (WL cards) doesn't do it on the
right timing, and therefore setting WEP key to those cards fails...


Re: Compiler version not supported by Windows DDK by Isaac

Isaac
Tue Sep 13 03:16:37 CDT 2005

Could you please name some UM "components" or header files that use
(include) this header file (ntdef.h)? Or any documentation that states
it is intended to be used in both UM and KM environments?

I failed to find it used (included) in VC6 or platform SDK.

Thank you,

Isaac Chen

"Doron Holan [MS]" <doronh@nospam.microsoft.com> wrote in message
news:OKuNxdEtFHA.1172@TK2MSFTNGP11.phx.gbl...
> i didn't misspeak, i was misunderstood. i said that ntdef.h was used for
> both environments. i never said ntddk.h or wdm.h was meant to be used by
> UM.
>
> d
>


Re: Compiler version not supported by Windows DDK by Doron

Doron
Tue Sep 13 10:39:34 CDT 2005

i am pretty sure that windows.h includes it eventually, even if it is in a
subsidiary header.

d

--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.


"Isaac Chen" <isaachen@delete-this.pchome.com.tw> wrote in message
news:OLQr6tDuFHA.3896@TK2MSFTNGP15.phx.gbl...
> Could you please name some UM "components" or header files that use
> (include) this header file (ntdef.h)? Or any documentation that states
> it is intended to be used in both UM and KM environments?
>
> I failed to find it used (included) in VC6 or platform SDK.
>
> Thank you,
>
> Isaac Chen
>
> "Doron Holan [MS]" <doronh@nospam.microsoft.com> wrote in message
> news:OKuNxdEtFHA.1172@TK2MSFTNGP11.phx.gbl...
>> i didn't misspeak, i was misunderstood. i said that ntdef.h was used for
>> both environments. i never said ntddk.h or wdm.h was meant to be used by
>> UM.
>>
>> d
>>
>



Re: Compiler version not supported by Windows DDK by Isaac

Isaac
Tue Sep 13 21:49:59 CDT 2005

It's not used in my DDK 3790, so maybe you're talking about
newer DDK? Or VS.NET 2002/2003/2005? In my environment,
it's only included (directly) by wdm.h and ntddk.h.

By the way, ntdef.h is not even part of Platform SDK and VC 6,
so I believe windows.h (there) won't be able to include it,
directly or not.

Thank you,

Isaac Chen

"Doron Holan [MS]" <doronh@nospam.microsoft.com> wrote in message
news:ed30XlHuFHA.2792@tk2msftngp13.phx.gbl...
> i am pretty sure that windows.h includes it eventually, even if it is in a
> subsidiary header.
>
> d