WDF 01.00.5033

Seems like the new beta drop has lot of compilation error !!!

Env(s) I tried –

3790.1414 ( the beta drop of ddk )
3790.1830 ( probably the latest RTM !!! ).

If I try to use just build the src that comes with the ddk, it is fine. And that is my first sanity check to see if the ddk env., is correct or not…

Now from any of the above build env. if I change to WDF folder ( on the command line ) and try to build wdf, I get a slew of error msg. SO I use bld ( note that bld produces red, turkish blue etc for error and other msgs ). It’s too many, and might have something to do with the env., vars being not set …

SO I GO TO USE DDKBUILD, next higher layer to get the files at fault by using mouse. Take the simple one, toaster\func\simple. I get it right.

Now I get to Ndisport ( along the area I like to roam around :). Here again, I get trouble. I see the wdfstrsafe.h any places we have (cchSrc > STRSAFE_MAX_CCH ) we have compiler flagging for signed/unsigned mismatch. IF I CAST THE LEFT SIDE TO (int) it goes fine …

Anybody noticed it ?. When would be the next drop of WDF ?. I would like to see if I could just say bld from command line and build all the wdf samples.

-pro

You have to run wdf_set_env.bat (iirc it is in wdf<ver>) first before you can compile any WDF sample.

d

________________________________________
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Prokash Sinha
Sent: Saturday, May 07, 2005 7:42 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] WDF 01.00.5033

Seems like the new beta drop has lot of compilation error !!!
?
Env(s) I tried? –
?
3790.1414? ( the beta drop of ddk )
3790.1830 ( probably the latest RTM !!! ).
?
If I try to use just build the src that comes with the ddk, it is fine. And that is my first sanity check to see if the ddk env., is correct or not…
?
Now from any of the above build env. if I change to WDF folder ( on the command line ) and try to build wdf, I get a slew of error msg. SO I use bld ( note that bld produces red, turkish blue etc for error and other msgs ). It’s too many, and might have something to do with the env., vars being not set …
?
SO I GO TO USE DDKBUILD, next higher layer to get the files at fault by using mouse. Take the simple one, toaster\func\simple. I get it right.
?
Now I get to Ndisport ( along the area I like to roam around :). Here again, I get trouble. I see the wdfstrsafe.h any places we have? (cchSrc > STRSAFE_MAX_CCH ) we have compiler flagging for signed/unsigned mismatch. IF I CAST THE LEFT SIDE TO? (int) it goes fine …
?
?
Anybody noticed it ?.?? When would be the next drop of WDF ?.? I would like to see if I could just say bld from command line and build all the wdf samples.
?
-pro

Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com

I don’t have it. It might be missing from the pkg !!!

I’ve an old WDF installed in %DDKTOOR%\WDF and the latest as a subdir of it
~\01.00.5033. CmdLine dir *.bat /s from root of all wdf shows nothing,
obviously it is not there at the root folder of wdf

-pro

----- Original Message -----
From: “Doron Holan”
To: “Windows System Software Devs Interest List”
Sent: Saturday, May 07, 2005 8:30 AM
Subject: RE: [ntdev] WDF 01.00.5033

You have to run wdf_set_env.bat (iirc it is in wdf<ver>) first before you
can compile any WDF sample.

d

________________________________________
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Prokash Sinha
Sent: Saturday, May 07, 2005 7:42 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] WDF 01.00.5033

Seems like the new beta drop has lot of compilation error !!!

Env(s) I tried –

3790.1414 ( the beta drop of ddk )
3790.1830 ( probably the latest RTM !!! ).

If I try to use just build the src that comes with the ddk, it is fine. And
that is my first sanity check to see if the ddk env., is correct or not…

Now from any of the above build env. if I change to WDF folder ( on the
command line ) and try to build wdf, I get a slew of error msg. SO I use bld
( note that bld produces red, turkish blue etc for error and other msgs ).
It’s too many, and might have something to do with the env., vars being not
set …

SO I GO TO USE DDKBUILD, next higher layer to get the files at fault by
using mouse. Take the simple one, toaster\func\simple. I get it right.

Now I get to Ndisport ( along the area I like to roam around :). Here again,
I get trouble. I see the wdfstrsafe.h any places we have (cchSrc >
STRSAFE_MAX_CCH ) we have compiler flagging for signed/unsigned mismatch. IF
I CAST THE LEFT SIDE TO (int) it goes fine …

Anybody noticed it ?. When would be the next drop of WDF ?. I would like to
see if I could just say bld from command line and build all the wdf samples.

-pro

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com

Maybe it was a .cmd file, I will look later today.

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Prokash Sinha
Sent: Saturday, May 07, 2005 9:14 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] WDF 01.00.5033

I don’t have it. It might be missing from the pkg !!!

I’ve an old WDF installed in %DDKTOOR%\WDF and the latest as a subdir of
it
~\01.00.5033. CmdLine dir *.bat /s from root of all wdf shows nothing,
obviously it is not there at the root folder of wdf

-pro

----- Original Message -----
From: “Doron Holan”
To: “Windows System Software Devs Interest List”
Sent: Saturday, May 07, 2005 8:30 AM
Subject: RE: [ntdev] WDF 01.00.5033

You have to run wdf_set_env.bat (iirc it is in wdf<ver>) first before
you
can compile any WDF sample.

d

________________________________________
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Prokash Sinha
Sent: Saturday, May 07, 2005 7:42 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] WDF 01.00.5033

Seems like the new beta drop has lot of compilation error !!!

Env(s) I tried –

3790.1414 ( the beta drop of ddk )
3790.1830 ( probably the latest RTM !!! ).

If I try to use just build the src that comes with the ddk, it is fine.
And
that is my first sanity check to see if the ddk env., is correct or
not…

Now from any of the above build env. if I change to WDF folder ( on the
command line ) and try to build wdf, I get a slew of error msg. SO I use
bld
( note that bld produces red, turkish blue etc for error and other msgs
).
It’s too many, and might have something to do with the env., vars being
not
set …

SO I GO TO USE DDKBUILD, next higher layer to get the files at fault by
using mouse. Take the simple one, toaster\func\simple. I get it right.

Now I get to Ndisport ( along the area I like to roam around :). Here
again,
I get trouble. I see the wdfstrsafe.h any places we have (cchSrc >
STRSAFE_MAX_CCH ) we have compiler flagging for signed/unsigned
mismatch. IF
I CAST THE LEFT SIDE TO (int) it goes fine …

Anybody noticed it ?. When would be the next drop of WDF ?. I would like
to
see if I could just say bld from command line and build all the wdf
samples.

-pro

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

I know it is in build 5054, but compiling the WDF/SAMPLES directory is still
a problem.

Gary

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Prokash Sinha
Sent: Saturday, May 07, 2005 11:14 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] WDF 01.00.5033

I don’t have it. It might be missing from the pkg !!!

I’ve an old WDF installed in %DDKTOOR%\WDF and the latest as a subdir of it
~\01.00.5033. CmdLine dir *.bat /s from root of all wdf shows nothing,
obviously it is not there at the root folder of wdf

-pro

----- Original Message -----
From: “Doron Holan”
To: “Windows System Software Devs Interest List”
Sent: Saturday, May 07, 2005 8:30 AM
Subject: RE: [ntdev] WDF 01.00.5033

You have to run wdf_set_env.bat (iirc it is in wdf<ver>) first before you
can compile any WDF sample.

d

______________________________
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Prokash Sinha
Sent: Saturday, May 07, 2005 7:42 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] WDF 01.00.5033

Seems like the new beta drop has lot of compilation error !!!

Env(s) I tried –

3790.1414 ( the beta drop of ddk )
3790.1830 ( probably the latest RTM !!! ).

If I try to use just build the src that comes with the ddk, it is fine. And
that is my first sanity check to see if the ddk env., is correct or not…

Now from any of the above build env. if I change to WDF folder ( on the
command line ) and try to build wdf, I get a slew of error msg. SO I use bld

( note that bld produces red, turkish blue etc for error and other msgs ).
It’s too many, and might have something to do with the env., vars being not
set …

SO I GO TO USE DDKBUILD, next higher layer to get the files at fault by
using mouse. Take the simple one, toaster\func\simple. I get it right.

Now I get to Ndisport ( along the area I like to roam around :). Here again,

I get trouble. I see the wdfstrsafe.h any places we have (cchSrc >
STRSAFE_MAX_CCH ) we have compiler flagging for signed/unsigned mismatch. IF

I CAST THE LEFT SIDE TO (int) it goes fine …

Anybody noticed it ?. When would be the next drop of WDF ?. I would like to
see if I could just say bld from command line and build all the wdf samples.

-pro

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: glittle@mn.rr.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

NOD32 1.1089 (20050505) Information

This message was checked by NOD32 antivirus system.
http://www.nod32.com

NOD32 1.1089 (20050505) Information __________

This message was checked by NOD32 antivirus system.
http://www.nod32.com

You and others might have a better ‘shortest path alogrithm’ :-), but I just
received the disk yesterday, and I ordered a week ago and got 5033. Well,
may be Minnesota is closer to redmond than from sillicon valley :-).

In any case Doran would be looking at it.

-pro

----- Original Message -----
From: “Gary G. Little”
To: “Windows System Software Devs Interest List”
Sent: Saturday, May 07, 2005 11:27 AM
Subject: RE: [ntdev] WDF 01.00.5033

I know it is in build 5054, but compiling the WDF/SAMPLES directory is still
a problem.

Gary

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Prokash Sinha
Sent: Saturday, May 07, 2005 11:14 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] WDF 01.00.5033

I don’t have it. It might be missing from the pkg !!!

I’ve an old WDF installed in %DDKTOOR%\WDF and the latest as a subdir of it
~\01.00.5033. CmdLine dir *.bat /s from root of all wdf shows nothing,
obviously it is not there at the root folder of wdf

-pro

----- Original Message -----
From: “Doron Holan”
To: “Windows System Software Devs Interest List”
Sent: Saturday, May 07, 2005 8:30 AM
Subject: RE: [ntdev] WDF 01.00.5033

You have to run wdf_set_env.bat (iirc it is in wdf<ver>) first before you
can compile any WDF sample.

d

______________________________
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Prokash Sinha
Sent: Saturday, May 07, 2005 7:42 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] WDF 01.00.5033

Seems like the new beta drop has lot of compilation error !!!

Env(s) I tried –

3790.1414 ( the beta drop of ddk )
3790.1830 ( probably the latest RTM !!! ).

If I try to use just build the src that comes with the ddk, it is fine. And
that is my first sanity check to see if the ddk env., is correct or not…

Now from any of the above build env. if I change to WDF folder ( on the
command line ) and try to build wdf, I get a slew of error msg. SO I use bld

( note that bld produces red, turkish blue etc for error and other msgs ).
It’s too many, and might have something to do with the env., vars being not
set …

SO I GO TO USE DDKBUILD, next higher layer to get the files at fault by
using mouse. Take the simple one, toaster\func\simple. I get it right.

Now I get to Ndisport ( along the area I like to roam around :). Here again,

I get trouble. I see the wdfstrsafe.h any places we have (cchSrc >
STRSAFE_MAX_CCH ) we have compiler flagging for signed/unsigned mismatch. IF

I CAST THE LEFT SIDE TO (int) it goes fine …

Anybody noticed it ?. When would be the next drop of WDF ?. I would like to
see if I could just say bld from command line and build all the wdf samples.

-pro

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: glittle@mn.rr.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

NOD32 1.1089 (20050505) Information

This message was checked by NOD32 antivirus system.
http://www.nod32.com

NOD32 1.1089 (20050505) Information __________

This message was checked by NOD32 antivirus system.
http://www.nod32.com


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com

I have 5054 (what we gave out at DDC). The script you must run is
wdf\01.00.5054\set_wdf_env.cmd.

Gary, what problems are you seeing? Are you seeing missing libs,
headers, etc?

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Prokash Sinha
Sent: Saturday, May 07, 2005 11:57 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] WDF 01.00.5033

You and others might have a better ‘shortest path alogrithm’ :-), but I
just
received the disk yesterday, and I ordered a week ago and got 5033.
Well,
may be Minnesota is closer to redmond than from sillicon valley :-).

In any case Doran would be looking at it.

-pro

----- Original Message -----
From: “Gary G. Little”
To: “Windows System Software Devs Interest List”
Sent: Saturday, May 07, 2005 11:27 AM
Subject: RE: [ntdev] WDF 01.00.5033

I know it is in build 5054, but compiling the WDF/SAMPLES directory is
still
a problem.

Gary

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Prokash Sinha
Sent: Saturday, May 07, 2005 11:14 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] WDF 01.00.5033

I don’t have it. It might be missing from the pkg !!!

I’ve an old WDF installed in %DDKTOOR%\WDF and the latest as a subdir of
it
~\01.00.5033. CmdLine dir *.bat /s from root of all wdf shows nothing,
obviously it is not there at the root folder of wdf

-pro

----- Original Message -----
From: “Doron Holan”
To: “Windows System Software Devs Interest List”
Sent: Saturday, May 07, 2005 8:30 AM
Subject: RE: [ntdev] WDF 01.00.5033

You have to run wdf_set_env.bat (iirc it is in wdf<ver>) first before
you
can compile any WDF sample.

d

______________________________
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Prokash Sinha
Sent: Saturday, May 07, 2005 7:42 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] WDF 01.00.5033

Seems like the new beta drop has lot of compilation error !!!

Env(s) I tried –

3790.1414 ( the beta drop of ddk )
3790.1830 ( probably the latest RTM !!! ).

If I try to use just build the src that comes with the ddk, it is fine.
And
that is my first sanity check to see if the ddk env., is correct or
not…

Now from any of the above build env. if I change to WDF folder ( on the
command line ) and try to build wdf, I get a slew of error msg. SO I use
bld

( note that bld produces red, turkish blue etc for error and other msgs
).
It’s too many, and might have something to do with the env., vars being
not
set …

SO I GO TO USE DDKBUILD, next higher layer to get the files at fault by
using mouse. Take the simple one, toaster\func\simple. I get it right.

Now I get to Ndisport ( along the area I like to roam around :). Here
again,

I get trouble. I see the wdfstrsafe.h any places we have (cchSrc >
STRSAFE_MAX_CCH ) we have compiler flagging for signed/unsigned
mismatch. IF

I CAST THE LEFT SIDE TO (int) it goes fine …

Anybody noticed it ?. When would be the next drop of WDF ?. I would like
to
see if I could just say bld from command line and build all the wdf
samples.

-pro

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: glittle@mn.rr.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

NOD32 1.1089 (20050505) Information

This message was checked by NOD32 antivirus system.
http://www.nod32.com

NOD32 1.1089 (20050505) Information __________

This message was checked by NOD32 antivirus system.
http://www.nod32.com


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

On the latest beta there is no such *.cmd file. In bin directory there is
SourcesRename.cmd, if I execute then quite a few gets compiled. Here is a
partial list of the bld process (IN CASE ANYONE IS INTERESTED TO LOOK AT
IT ) …

gned mismatch
1>c:\winddk\3790.1830\wdf\inc\wdfstrsafe.h(1119) : error C4018: ‘>’ :
signed/uns
igned mismatch
1>c:\winddk\3790.1830\wdf\inc\wdfstrsafe.h(1249) : error C4018: ‘>’ :
signed/uns
igned mismatch
1>Linking Executable - samples\kbfiltr\sys\objchk_wxp_x86\i386\kbfiltr.sys
for i
386
1>LINK : error LNK1181: cannot open input file
‘objchk_wxp_x86\i386\ioctl.obj’
BUILD: Linking c:\winddk\wdf\01.00.5033\samples\1394\driver\1394vdev
directory
BUILD: Linking c:\winddk\wdf\01.00.5033\samples\1394\driver\1394diag
directory
2>Compiling - samples\ndisprot\sys\ntdisp.c for i386
1>Linking Executable -
samples\1394\driver\1394vdev\objchk_wxp_x86\i386\1394vdev
.sys for i386
2>c:\winddk\3790.1830\wdf\inc\wdfstrsafe.h(562) : error C2065:
‘STRSAFE_MAX_CCH’
: undeclared identifier
2>c:\winddk\3790.1830\wdf\inc\wdfstrsafe.h(562) : error C4018: ‘>’ :
signed/unsi
gned mismatch
2>c:\winddk\3790.1830\wdf\inc\wdfstrsafe.h(735) : error C4018: ‘>’ :
signed/unsi
gned mismatch
2>c:\winddk\3790.1830\wdf\inc\wdfstrsafe.h(862) : error C4018: ‘>’ :
signed/unsi
gned mismatch
2>c:\winddk\3790.1830\wdf\inc\wdfstrsafe.h(989) : error C4018: ‘>’ :
signed/unsi
gned mismatch
2>c:\winddk\3790.1830\wdf\inc\wdfstrsafe.h(1119) : error C4018: ‘>’ :
signed/uns
igned mismatch
2>c:\winddk\3790.1830\wdf\inc\wdfstrsafe.h(1249) : error C4018: ‘>’ :
signed/uns
igned mismatch
2>Linking Executable - samples\ndisprot\sys\objchk_wxp_x86\i386\ndisprot.sys
for
i386
2>LINK : error LNK1181: cannot open input file
‘objchk_wxp_x86\i386\ntdisp.obj’
2>Linking Executable -
samples\1394\driver\1394diag\objchk_wxp_x86\i386\1394diag
.sys for i386
BUILD: Done

213 files compiled - 392 Errors - 4816 LPS
27 executables built - 11 Errors

C:\WINDDK\WDF\01.00.5033>dir *.sys /s
Volume in drive C has no label.
Volume Serial Number is 419C-DB67

Directory of
C:\WINDDK\WDF\01.00.5033\samples\amcc5933\sys\objchk_wxp_x86\i386

05/07/2005 03:39 PM 25,984 AMCC5933.sys
1 File(s) 25,984 bytes

Directory of
C:\WINDDK\WDF\01.00.5033\samples\plx9x5x\sys\objchk_wxp_x86\i386

05/07/2005 03:39 PM 29,440 Pci9x5x.sys
1 File(s) 29,440 bytes

Directory of C:\WINDDK\WDF\01.00.5033\samples\ndisedge\objchk_wxp_x86\i386

05/07/2005 03:39 PM 53,120 ndisedge.sys
1 File(s) 53,120 bytes

Directory of C:\WINDDK\WDF\01.00.5033\samples\echo\sys\objchk_wxp_x86\i386

05/07/2005 03:39 PM 9,472 echo.sys
1 File(s) 9,472 bytes

Directory of
C:\WINDDK\WDF\01.00.5033\samples\toaster\func\simple\objchk_wxp_x8
6\i386

05/07/2005 03:39 PM 7,168 wdfsimple.sys
1 File(s) 7,168 bytes

Directory of
C:\WINDDK\WDF\01.00.5033\samples\toaster\toastmon\objchk_wxp_x86\i
386

05/07/2005 03:39 PM 14,848 wdftoastmon.sys
1 File(s) 14,848 bytes

Directory of
C:\WINDDK\WDF\01.00.5033\samples\usbsamp\sys\objchk_wxp_x86\i386

05/07/2005 03:39 PM 32,128 usbsamp.sys
1 File(s) 32,128 bytes

Directory of
C:\WINDDK\WDF\01.00.5033\samples\1394\driver\1394diag\objchk_wxp_x
86\i386

05/07/2005 03:39 PM 70,784 1394DIAG.sys
1 File(s) 70,784 bytes

Directory of
C:\WINDDK\WDF\01.00.5033\samples\1394\driver\1394vdev\objchk_wxp_x
86\i386

05/07/2005 03:39 PM 70,784 1394VDEV.sys
1 File(s) 70,784 bytes

Total Files Listed:
9 File(s) 313,728 bytes
0 Dir(s) 211,896,958,976 bytes free

-pro

C:\WINDDK\WDF\01.00.5033>
----- Original Message -----
From: “Doron Holan”
To: “Windows System Software Devs Interest List”
Sent: Saturday, May 07, 2005 2:43 PM
Subject: RE: [ntdev] WDF 01.00.5033

I have 5054 (what we gave out at DDC). The script you must run is
wdf\01.00.5054\set_wdf_env.cmd.

Gary, what problems are you seeing? Are you seeing missing libs,
headers, etc?

d

The #define for STRSAFE_MAX_CCH is missing. You have an older version
of WDF b/c we didn’t ship sourcesrename.cmd in the latest beta bits.
Sourcesrename.cmd is meant to be executed only on older drivers written
by the beta customer, the samples themselves do not need any updating.
If sourcesrename.cmd got them building, then that also indicates that
the beta bits you downloaded are not the latest version.

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Prokash Sinha
Sent: Saturday, May 07, 2005 3:44 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] WDF 01.00.5033

On the latest beta there is no such *.cmd file. In bin directory there
is
SourcesRename.cmd, if I execute then quite a few gets compiled. Here is
a
partial list of the bld process (IN CASE ANYONE IS INTERESTED TO LOOK AT

IT ) …

gned mismatch
1>c:\winddk\3790.1830\wdf\inc\wdfstrsafe.h(1119) : error C4018: ‘>’ :
signed/uns
igned mismatch
1>c:\winddk\3790.1830\wdf\inc\wdfstrsafe.h(1249) : error C4018: ‘>’ :
signed/uns
igned mismatch
1>Linking Executable -
samples\kbfiltr\sys\objchk_wxp_x86\i386\kbfiltr.sys
for i
386
1>LINK : error LNK1181: cannot open input file
‘objchk_wxp_x86\i386\ioctl.obj’
BUILD: Linking c:\winddk\wdf\01.00.5033\samples\1394\driver\1394vdev
directory
BUILD: Linking c:\winddk\wdf\01.00.5033\samples\1394\driver\1394diag
directory
2>Compiling - samples\ndisprot\sys\ntdisp.c for i386
1>Linking Executable -
samples\1394\driver\1394vdev\objchk_wxp_x86\i386\1394vdev
.sys for i386
2>c:\winddk\3790.1830\wdf\inc\wdfstrsafe.h(562) : error C2065:
‘STRSAFE_MAX_CCH’
: undeclared identifier
2>c:\winddk\3790.1830\wdf\inc\wdfstrsafe.h(562) : error C4018: ‘>’ :
signed/unsi
gned mismatch
2>c:\winddk\3790.1830\wdf\inc\wdfstrsafe.h(735) : error C4018: ‘>’ :
signed/unsi
gned mismatch
2>c:\winddk\3790.1830\wdf\inc\wdfstrsafe.h(862) : error C4018: ‘>’ :
signed/unsi
gned mismatch
2>c:\winddk\3790.1830\wdf\inc\wdfstrsafe.h(989) : error C4018: ‘>’ :
signed/unsi
gned mismatch
2>c:\winddk\3790.1830\wdf\inc\wdfstrsafe.h(1119) : error C4018: ‘>’ :
signed/uns
igned mismatch
2>c:\winddk\3790.1830\wdf\inc\wdfstrsafe.h(1249) : error C4018: ‘>’ :
signed/uns
igned mismatch
2>Linking Executable -
samples\ndisprot\sys\objchk_wxp_x86\i386\ndisprot.sys
for
i386
2>LINK : error LNK1181: cannot open input file
‘objchk_wxp_x86\i386\ntdisp.obj’
2>Linking Executable -
samples\1394\driver\1394diag\objchk_wxp_x86\i386\1394diag
.sys for i386
BUILD: Done

213 files compiled - 392 Errors - 4816 LPS
27 executables built - 11 Errors

C:\WINDDK\WDF\01.00.5033>dir *.sys /s
Volume in drive C has no label.
Volume Serial Number is 419C-DB67

Directory of
C:\WINDDK\WDF\01.00.5033\samples\amcc5933\sys\objchk_wxp_x86\i386

05/07/2005 03:39 PM 25,984 AMCC5933.sys
1 File(s) 25,984 bytes

Directory of
C:\WINDDK\WDF\01.00.5033\samples\plx9x5x\sys\objchk_wxp_x86\i386

05/07/2005 03:39 PM 29,440 Pci9x5x.sys
1 File(s) 29,440 bytes

Directory of
C:\WINDDK\WDF\01.00.5033\samples\ndisedge\objchk_wxp_x86\i386

05/07/2005 03:39 PM 53,120 ndisedge.sys
1 File(s) 53,120 bytes

Directory of
C:\WINDDK\WDF\01.00.5033\samples\echo\sys\objchk_wxp_x86\i386

05/07/2005 03:39 PM 9,472 echo.sys
1 File(s) 9,472 bytes

Directory of
C:\WINDDK\WDF\01.00.5033\samples\toaster\func\simple\objchk_wxp_x8
6\i386

05/07/2005 03:39 PM 7,168 wdfsimple.sys
1 File(s) 7,168 bytes

Directory of
C:\WINDDK\WDF\01.00.5033\samples\toaster\toastmon\objchk_wxp_x86\i
386

05/07/2005 03:39 PM 14,848 wdftoastmon.sys
1 File(s) 14,848 bytes

Directory of
C:\WINDDK\WDF\01.00.5033\samples\usbsamp\sys\objchk_wxp_x86\i386

05/07/2005 03:39 PM 32,128 usbsamp.sys
1 File(s) 32,128 bytes

Directory of
C:\WINDDK\WDF\01.00.5033\samples\1394\driver\1394diag\objchk_wxp_x
86\i386

05/07/2005 03:39 PM 70,784 1394DIAG.sys
1 File(s) 70,784 bytes

Directory of
C:\WINDDK\WDF\01.00.5033\samples\1394\driver\1394vdev\objchk_wxp_x
86\i386

05/07/2005 03:39 PM 70,784 1394VDEV.sys
1 File(s) 70,784 bytes

Total Files Listed:
9 File(s) 313,728 bytes
0 Dir(s) 211,896,958,976 bytes free

-pro

C:\WINDDK\WDF\01.00.5033>
----- Original Message -----
From: “Doron Holan”
To: “Windows System Software Devs Interest List”
Sent: Saturday, May 07, 2005 2:43 PM
Subject: RE: [ntdev] WDF 01.00.5033

I have 5054 (what we gave out at DDC). The script you must run is
wdf\01.00.5054\set_wdf_env.cmd.

Gary, what problems are you seeing? Are you seeing missing libs,
headers, etc?

d


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

Doron,
I understand it’s beta, and a slight mistake may not compile the tree. So
I’m not really expecting a concrete answer.

What I see is that STR_MAX_CCH is defined and could be brought in from -
C:\WINDDK\3790.1830\inc\ddk\wxp\ntstrsafe.h(84):#define NTSTRSAFE_MAX_CCH
2147483647 // max # of characters we support (same as INT_MAX)

When I bring it in I’ve the signed unsigned problem as I stated earlier.

In any case, I will look bit more to see …

-pro

----- Original Message -----
From: “Doron Holan”
To: “Windows System Software Devs Interest List”
Sent: Saturday, May 07, 2005 3:51 PM
Subject: RE: [ntdev] WDF 01.00.5033

The #define for STRSAFE_MAX_CCH is missing. You have an older version
of WDF b/c we didn’t ship sourcesrename.cmd in the latest beta bits.
Sourcesrename.cmd is meant to be executed only on older drivers written
by the beta customer, the samples themselves do not need any updating.
If sourcesrename.cmd got them building, then that also indicates that
the beta bits you downloaded are not the latest version.

d

Oops, the beta 3 ( 5054 is already out there, I just checked, and 'm
downloading ). The 5033 is not even two wks old :-).

Okay I will try 5054, soon.

Thank !

-pro
----- Original Message -----
From: “Prokash Sinha”
To: “Windows System Software Devs Interest List”
Sent: Saturday, May 07, 2005 4:17 PM
Subject: Re: [ntdev] WDF 01.00.5033

> Doron,
> I understand it’s beta, and a slight mistake may not compile the tree. So
> I’m not really expecting a concrete answer.
>
> What I see is that STR_MAX_CCH is defined and could be brought in from -
> C:\WINDDK\3790.1830\inc\ddk\wxp\ntstrsafe.h(84):#define NTSTRSAFE_MAX_CCH
> 2147483647 // max # of characters we support (same as INT_MAX)
>
>
>
> When I bring it in I’ve the signed unsigned problem as I stated earlier.
>
> In any case, I will look bit more to see …
>
> -pro
>
> ----- Original Message -----
> From: “Doron Holan”
> To: “Windows System Software Devs Interest List”
> Sent: Saturday, May 07, 2005 3:51 PM
> Subject: RE: [ntdev] WDF 01.00.5033
>
>
> The #define for STRSAFE_MAX_CCH is missing. You have an older version
> of WDF b/c we didn’t ship sourcesrename.cmd in the latest beta bits.
> Sourcesrename.cmd is meant to be executed only on older drivers written
> by the beta customer, the samples themselves do not need any updating.
> If sourcesrename.cmd got them building, then that also indicates that
> the beta bits you downloaded are not the latest version.
>
> d
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@garlic.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>

On a related topic, I have not yet released the update to ddkbuild that
supports the 5054 beta of WDF. I’ll try to get this done this weekend, it is
a minor change that I have working already. The current release of ddkbuild
will not work correctly with 5054.

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

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Prokash Sinha
Sent: Saturday, May 07, 2005 7:24 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] WDF 01.00.5033

Oops, the beta 3 ( 5054 is already out there, I just checked,
and 'm downloading ). The 5033 is not even two wks old :-).

Okay I will try 5054, soon.

Thank !

-pro
----- Original Message -----
From: “Prokash Sinha”
> To: “Windows System Software Devs Interest List”
> Sent: Saturday, May 07, 2005 4:17 PM
> Subject: Re: [ntdev] WDF 01.00.5033
>
>
> > Doron,
> > I understand it’s beta, and a slight mistake may not
> compile the tree. So
> > I’m not really expecting a concrete answer.
> >
> > What I see is that STR_MAX_CCH is defined and could be
> brought in from -
> > C:\WINDDK\3790.1830\inc\ddk\wxp\ntstrsafe.h(84):#define
> NTSTRSAFE_MAX_CCH
> > 2147483647 // max # of characters we support (same as INT_MAX)
> >
> >
> >
> > When I bring it in I’ve the signed unsigned problem as I
> stated earlier.
> >
> > In any case, I will look bit more to see …
> >
> > -pro
> >
> > ----- Original Message -----
> > From: “Doron Holan”
> > To: “Windows System Software Devs Interest List”
>
> > Sent: Saturday, May 07, 2005 3:51 PM
> > Subject: RE: [ntdev] WDF 01.00.5033
> >
> >
> > The #define for STRSAFE_MAX_CCH is missing. You have an
> older version
> > of WDF b/c we didn’t ship sourcesrename.cmd in the latest beta bits.
> > Sourcesrename.cmd is meant to be executed only on older
> drivers written
> > by the beta customer, the samples themselves do not need
> any updating.
> > If sourcesrename.cmd got them building, then that also
> indicates that
> > the beta bits you downloaded are not the latest version.
> >
> > d
> >
> >
> >
> > —
> > Questions? First check the Kernel Driver FAQ at
> > http://www.osronline.com/article.cfm?id=256
> >
> > You are currently subscribed to ntdev as: xxxxx@garlic.com
> > To unsubscribe send a blank email to xxxxx@lists.osr.com
> >
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@hollistech.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>

NTSTRSAFE_MAX_CCH is jus a number, there is no type to it. Comparing it
against a size_t should yield no errors.

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Prokash Sinha
Sent: Saturday, May 07, 2005 4:17 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] WDF 01.00.5033

Doron,
I understand it’s beta, and a slight mistake may not compile the tree.
So
I’m not really expecting a concrete answer.

What I see is that STR_MAX_CCH is defined and could be brought in from

C:\WINDDK\3790.1830\inc\ddk\wxp\ntstrsafe.h(84):#define
NTSTRSAFE_MAX_CCH
2147483647 // max # of characters we support (same as INT_MAX)

When I bring it in I’ve the signed unsigned problem as I stated earlier.

In any case, I will look bit more to see …

-pro

----- Original Message -----
From: “Doron Holan”
To: “Windows System Software Devs Interest List”
Sent: Saturday, May 07, 2005 3:51 PM
Subject: RE: [ntdev] WDF 01.00.5033

The #define for STRSAFE_MAX_CCH is missing. You have an older version
of WDF b/c we didn’t ship sourcesrename.cmd in the latest beta bits.
Sourcesrename.cmd is meant to be executed only on older drivers written
by the beta customer, the samples themselves do not need any updating.
If sourcesrename.cmd got them building, then that also indicates that
the beta bits you downloaded are not the latest version.

d


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

Thanks Mark, Doron, and Gary. Gary dropped the hint that I did not catch
properly.

Mark, please flush the news of your update, then I will download.

-pro

----- Original Message -----
From: “Mark Roddy”
To: “Windows System Software Devs Interest List”
Sent: Saturday, May 07, 2005 5:14 PM
Subject: RE: [ntdev] WDF 01.00.5033

> On a related topic, I have not yet released the update to ddkbuild that
> supports the 5054 beta of WDF. I’ll try to get this done this weekend, it
> is
> a minor change that I have working already. The current release of
> ddkbuild
> will not work correctly with 5054.
>
> =====================
> Mark Roddy
> Windows .NET/XP/2000 Consulting
> Hollis Technology Solutions 603-321-1032
> www.hollistech.com
>
>> -----Original Message-----
>> From: xxxxx@lists.osr.com
>> [mailto:xxxxx@lists.osr.com] On Behalf Of Prokash Sinha
>> Sent: Saturday, May 07, 2005 7:24 PM
>> To: Windows System Software Devs Interest List
>> Subject: Re: [ntdev] WDF 01.00.5033
>>
>> Oops, the beta 3 ( 5054 is already out there, I just checked,
>> and 'm downloading ). The 5033 is not even two wks old :-).
>>
>> Okay I will try 5054, soon.
>>
>> Thank !
>>
>> -pro
>> ----- Original Message -----
>> From: “Prokash Sinha”
>> To: “Windows System Software Devs Interest List”
>> Sent: Saturday, May 07, 2005 4:17 PM
>> Subject: Re: [ntdev] WDF 01.00.5033
>>
>>
>> > Doron,
>> > I understand it’s beta, and a slight mistake may not
>> compile the tree. So
>> > I’m not really expecting a concrete answer.
>> >
>> > What I see is that STR_MAX_CCH is defined and could be
>> brought in from -
>> > C:\WINDDK\3790.1830\inc\ddk\wxp\ntstrsafe.h(84):#define
>> NTSTRSAFE_MAX_CCH
>> > 2147483647 // max # of characters we support (same as INT_MAX)
>> >
>> >
>> >
>> > When I bring it in I’ve the signed unsigned problem as I
>> stated earlier.
>> >
>> > In any case, I will look bit more to see …
>> >
>> > -pro
>> >
>> > ----- Original Message -----
>> > From: “Doron Holan”
>> > To: “Windows System Software Devs Interest List”
>>
>> > Sent: Saturday, May 07, 2005 3:51 PM
>> > Subject: RE: [ntdev] WDF 01.00.5033
>> >
>> >
>> > The #define for STRSAFE_MAX_CCH is missing. You have an
>> older version
>> > of WDF b/c we didn’t ship sourcesrename.cmd in the latest beta bits.
>> > Sourcesrename.cmd is meant to be executed only on older
>> drivers written
>> > by the beta customer, the samples themselves do not need
>> any updating.
>> > If sourcesrename.cmd got them building, then that also
>> indicates that
>> > the beta bits you downloaded are not the latest version.
>> >
>> > d
>> >
>> >
>> >
>> > —
>> > Questions? First check the Kernel Driver FAQ at
>> > http://www.osronline.com/article.cfm?id=256
>> >
>> > You are currently subscribed to ntdev as: xxxxx@garlic.com
>> > To unsubscribe send a blank email to xxxxx@lists.osr.com
>> >
>>
>>
>> —
>> Questions? First check the Kernel Driver FAQ at
>> http://www.osronline.com/article.cfm?id=256
>>
>> You are currently subscribed to ntdev as: xxxxx@hollistech.com
>> To unsubscribe send a blank email to xxxxx@lists.osr.com
>>
>
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@garlic.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>

I will definitely try on 5054, but what I had on this 5033 ( of course using
ddkbuild ) is this

Error 2 error C4018: ‘>’ : signed/unsigned mismatch
c:\winddk\3790.1830\wdf\inc\wdfstrsafe.h 562
Error 1 error C2065: ‘STRSAFE_MAX_CCH’ : undeclared identifier
c:\winddk\3790.1830\wdf\inc\wdfstrsafe.h 562
Error 3 error C4018: ‘>’ : signed/unsigned mismatch
c:\winddk\3790.1830\wdf\inc\wdfstrsafe.h 735
Error 4 error C4018: ‘>’ : signed/unsigned mismatch
c:\winddk\3790.1830\wdf\inc\wdfstrsafe.h 862
Error 5 error C4018: ‘>’ : signed/unsigned mismatch
c:\winddk\3790.1830\wdf\inc\wdfstrsafe.h 989
Error 6 error C4018: ‘>’ : signed/unsigned mismatch
c:\winddk\3790.1830\wdf\inc\wdfstrsafe.h 1119
Error 7 error C4018: ‘>’ : signed/unsigned mismatch
c:\winddk\3790.1830\wdf\inc\wdfstrsafe.h 1249
Error 8 error C2065: ‘STRSAFE_MAX_CCH’ : undeclared identifier
c:\winddk\3790.1830\wdf\inc\wdfstrsafe.h 562
Error 9 error C4018: ‘>’ : signed/unsigned mismatch
c:\winddk\3790.1830\wdf\inc\wdfstrsafe.h 562
Error 10 error C4018: ‘>’ : signed/unsigned mismatch
c:\winddk\3790.1830\wdf\inc\wdfstrsafe.h 735
Error 11 error C4018: ‘>’ : signed/unsigned mismatch
c:\winddk\3790.1830\wdf\inc\wdfstrsafe.h 862
Error 12 error C4018: ‘>’ : signed/unsigned mismatch
c:\winddk\3790.1830\wdf\inc\wdfstrsafe.h 989
Error 13 error C4018: ‘>’ : signed/unsigned mismatch
c:\winddk\3790.1830\wdf\inc\wdfstrsafe.h 1119
Error 14 error C4018: ‘>’ : signed/unsigned mismatch
c:\winddk\3790.1830\wdf\inc\wdfstrsafe.h 1249
Error 15 error C2065: ‘STRSAFE_MAX_CCH’ : undeclared identifier
c:\winddk\3790.1830\wdf\inc\wdfstrsafe.h 562
Error 16 error C4018: ‘>’ : signed/unsigned mismatch
c:\winddk\3790.1830\wdf\inc\wdfstrsafe.h 562
Error 17 error C4018: ‘>’ : signed/unsigned mismatch
c:\winddk\3790.1830\wdf\inc\wdfstrsafe.h 735
Error 18 error C4018: ‘>’ : signed/unsigned mismatch
c:\winddk\3790.1830\wdf\inc\wdfstrsafe.h 862
Error 19 error C4018: ‘>’ : signed/unsigned mismatch
c:\winddk\3790.1830\wdf\inc\wdfstrsafe.h 989
Error 20 error C4018: ‘>’ : signed/unsigned mismatch
c:\winddk\3790.1830\wdf\inc\wdfstrsafe.h 1119
Error 21 error C4018: ‘>’ : signed/unsigned mismatch
c:\winddk\3790.1830\wdf\inc\wdfstrsafe.h 1249
Error 22 error LNK1181: cannot open input file
‘objchk_wxp_x86\i386\ntdisp.obj’ Ndisprot

I TRIED TO CAST TO (int) on the left as I mentioned only for line 562 to
see if goes to 735, and sure it took and went down to 735. At that point I
stopped. If the problem is bogus, it should go away for 5054.

For 5054, I will try again to see and this time with the ddk build
environment ( w/o Mark’s ddkbuild). Hope I dont have to pull in any
directory for include, if so then I will try to do that in the sources. But
eventually I will be using ddkbuild for better managibilty, just a personal
preference…

-pro

----- Original Message -----
From: “Doron Holan”
To: “Windows System Software Devs Interest List”
Sent: Saturday, May 07, 2005 5:16 PM
Subject: RE: [ntdev] WDF 01.00.5033

NTSTRSAFE_MAX_CCH is jus a number, there is no type to it. Comparing it
against a size_t should yield no errors.

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Prokash Sinha
Sent: Saturday, May 07, 2005 4:17 PM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] WDF 01.00.5033

Doron,
I understand it’s beta, and a slight mistake may not compile the tree.
So
I’m not really expecting a concrete answer.

What I see is that STR_MAX_CCH is defined and could be brought in from
-
C:\WINDDK\3790.1830\inc\ddk\wxp\ntstrsafe.h(84):#define
NTSTRSAFE_MAX_CCH
2147483647 // max # of characters we support (same as INT_MAX)

When I bring it in I’ve the signed unsigned problem as I stated earlier.

In any case, I will look bit more to see …

-pro

----- Original Message -----
From: “Doron Holan”
To: “Windows System Software Devs Interest List”
Sent: Saturday, May 07, 2005 3:51 PM
Subject: RE: [ntdev] WDF 01.00.5033

The #define for STRSAFE_MAX_CCH is missing. You have an older version
of WDF b/c we didn’t ship sourcesrename.cmd in the latest beta bits.
Sourcesrename.cmd is meant to be executed only on older drivers written
by the beta customer, the samples themselves do not need any updating.
If sourcesrename.cmd got them building, then that also indicates that
the beta bits you downloaded are not the latest version.

d


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com

Doron,

Here is the opening errors I receive. This is after opening a CHECKED 1830
environment and running set_wdf_env.

C:\WINDDK\WDF\samples\fileio\sys>
bld
BUILD: Adding /Y to COPYCMD so xcopy ops won’t hang.
BUILD: Object root set to: ==> objchk_wxp_x86
BUILD: Compile and Link for i386
BUILD: Loading C:\WINDDK\3790~1.183\build.dat…
BUILD: Computing Include file dependencies:
BUILD: Examining c:\winddk\wdf\samples\fileio\sys directory for files to
compile
.
c:\winddk\wdf\samples\fileio\sys - 2 source files (1,404 lines)
BUILD: Saving C:\WINDDK\3790~1.183\build.dat…
BUILD: Compiling (NoSync) c:\winddk\wdf\samples\fileio\sys directory
Compiling - fileio.rc for i386
Compiling - fileio.c for i386
errors in directory c:\winddk\wdf\samples\fileio\sys
fileio.h(70) : error C2061: syntax error : identifier ‘FileIoDeviceAdd’
fileio.h(70) : error C2059: syntax error : ‘;’
fileio.h(71) : error C2059: syntax error : ‘type’
fileio.c(60) : error C2157: ‘FileIoDeviceAdd’ : must be declared before use
in p
ragma list
fileio.c(96) : error C2065: ‘WDFSTATUS’ : undeclared identifier
fileio.c(96) : error C2146: syntax error : missing ‘;’ before identifier
'status

The dates an the files in \WinDDK\WDF\SAMPLES\FILEIO\SYS are all 4/14/04.

Mark,

I see the same thing with DDKBUILD.


The personal opinion of
Gary G. Little

“Doron Holan” wrote in message
news:xxxxx@ntdev…
I have 5054 (what we gave out at DDC). The script you must run is
wdf\01.00.5054\set_wdf_env.cmd.

Gary, what problems are you seeing? Are you seeing missing libs,
headers, etc?

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Prokash Sinha
Sent: Saturday, May 07, 2005 11:57 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] WDF 01.00.5033

You and others might have a better ‘shortest path alogrithm’ :-), but I
just
received the disk yesterday, and I ordered a week ago and got 5033.
Well,
may be Minnesota is closer to redmond than from sillicon valley :-).

In any case Doran would be looking at it.

-pro

----- Original Message -----
From: “Gary G. Little”
To: “Windows System Software Devs Interest List”
Sent: Saturday, May 07, 2005 11:27 AM
Subject: RE: [ntdev] WDF 01.00.5033

I know it is in build 5054, but compiling the WDF/SAMPLES directory is
still
a problem.

Gary

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Prokash Sinha
Sent: Saturday, May 07, 2005 11:14 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] WDF 01.00.5033

I don’t have it. It might be missing from the pkg !!!

I’ve an old WDF installed in %DDKTOOR%\WDF and the latest as a subdir of
it
~\01.00.5033. CmdLine dir *.bat /s from root of all wdf shows nothing,
obviously it is not there at the root folder of wdf

-pro

----- Original Message -----
From: “Doron Holan”
To: “Windows System Software Devs Interest List”
Sent: Saturday, May 07, 2005 8:30 AM
Subject: RE: [ntdev] WDF 01.00.5033

You have to run wdf_set_env.bat (iirc it is in wdf<ver>) first before
you
can compile any WDF sample.

d

______________________________
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Prokash Sinha
Sent: Saturday, May 07, 2005 7:42 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] WDF 01.00.5033

Seems like the new beta drop has lot of compilation error !!!

Env(s) I tried –

3790.1414 ( the beta drop of ddk )
3790.1830 ( probably the latest RTM !!! ).

If I try to use just build the src that comes with the ddk, it is fine.
And
that is my first sanity check to see if the ddk env., is correct or
not…

Now from any of the above build env. if I change to WDF folder ( on the
command line ) and try to build wdf, I get a slew of error msg. SO I use
bld

( note that bld produces red, turkish blue etc for error and other msgs
).
It’s too many, and might have something to do with the env., vars being
not
set …

SO I GO TO USE DDKBUILD, next higher layer to get the files at fault by
using mouse. Take the simple one, toaster\func\simple. I get it right.

Now I get to Ndisport ( along the area I like to roam around :). Here
again,

I get trouble. I see the wdfstrsafe.h any places we have (cchSrc >
STRSAFE_MAX_CCH ) we have compiler flagging for signed/unsigned
mismatch. IF

I CAST THE LEFT SIDE TO (int) it goes fine …

Anybody noticed it ?. When would be the next drop of WDF ?. I would like
to
see if I could just say bld from command line and build all the wdf
samples.

-pro

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: glittle@mn.rr.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

NOD32 1.1089 (20050505) Information

This message was checked by NOD32 antivirus system.
http://www.nod32.com

NOD32 1.1089 (20050505) Information __________

This message was checked by NOD32 antivirus system.
http://www.nod32.com


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: unknown lmsubst tag argument:
‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com