Safe strings usage ...

I’m trying to use safe strings in a DriverWorks class. I’m not saying
DrivereWorks is interferring with symbol resolution for safe string
functions, but I am seeing some really STUPID errors during linkage edit.

If I build with NTSTRSAFE_LIB I get LNK2019 on RtlUnicodeToMultiByteN and
RtlAnsiToUnicodeChar. If I use the inline version by removing NTSTRSAFE_LIB
I then get LNK2019 on vsnwprintf. Any one else encountered this, and how was
it resolved?


The personal opinion of
Gary G. Little

Dumb question, but just to rule it out… Are you linking with
ntstrsafe.lib; eg. TARGETLIBS=$(DDK_LIB_PATH)\ntstrsafe.lib in your
sources file?

On 21-Sep-04, at 10:33 AM, Gary G. Little wrote:

I’m trying to use safe strings in a DriverWorks class. I’m not saying
DrivereWorks is interferring with symbol resolution for safe string
functions, but I am seeing some really STUPID errors during linkage
edit.

If I build with NTSTRSAFE_LIB I get LNK2019 on RtlUnicodeToMultiByteN
and
RtlAnsiToUnicodeChar. If I use the inline version by removing
NTSTRSAFE_LIB
I then get LNK2019 on vsnwprintf. Any one else encountered this, and
how was
it resolved?


The personal opinion of
Gary G. Little


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

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

Cliff

Not sure about RtlAnsiToUnicodeChar (can’t find it in the WinXP lib dir, and
I did “dumpbin /symbols *.lib > all.txt”, maybe that is not sufficient).
For WinXP, RtlUnicodeToMultiByteN seems to be defined in ntoskrnl.lib and
not wdm.lib, so try linking to the former library. I did the dumpbin test
on Win server 2003 SP1 build 1218 DDK, WinXP lib dir.

Philip Lukidis < mailto:xxxxx@guillemot.com>
Software Engineer - Guillemot R&D inc. < http://www.guillemot.com
http:</http:> >
Tel: (514) 279-9960 ext:4111 Fax: (514) 279-2558
5800 St-Denis, Suite 1102, Montreal, Quebec, H2S 3L5, Canada

-----Original Message-----
From: Gary G. Little [mailto:xxxxx@sbcglobal.net]
Sent: Tuesday, September 21, 2004 1:33 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Safe strings usage …

I’m trying to use safe strings in a DriverWorks class. I’m not saying
DrivereWorks is interferring with symbol resolution for safe string
functions, but I am seeing some really STUPID errors during linkage edit.

If I build with NTSTRSAFE_LIB I get LNK2019 on RtlUnicodeToMultiByteN and
RtlAnsiToUnicodeChar. If I use the inline version by removing NTSTRSAFE_LIB
I then get LNK2019 on vsnwprintf. Any one else encountered this, and how was
it resolved?


The personal opinion of
Gary G. Little


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

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

Cliff,

Using NTSTRSAFE_LIB implies using the lib version and requires linking with
the NTSTRSAFE library. Yes, it is in my TARGETLIBS statement.


The personal opinion of
Gary G. Little

“Cliff Russell” wrote in message
news:xxxxx@ntdev…
> Dumb question, but just to rule it out… Are you linking with
> ntstrsafe.lib; eg. TARGETLIBS=$(DDK_LIB_PATH)\ntstrsafe.lib in your
> sources file?
>
> On 21-Sep-04, at 10:33 AM, Gary G. Little wrote:
>
> > I’m trying to use safe strings in a DriverWorks class. I’m not saying
> > DrivereWorks is interferring with symbol resolution for safe string
> > functions, but I am seeing some really STUPID errors during linkage
> > edit.
> >
> > If I build with NTSTRSAFE_LIB I get LNK2019 on RtlUnicodeToMultiByteN
> > and
> > RtlAnsiToUnicodeChar. If I use the inline version by removing
> > NTSTRSAFE_LIB
> > I then get LNK2019 on vsnwprintf. Any one else encountered this, and
> > how was
> > it resolved?
> >
> > –
> > The personal opinion of
> > Gary G. Little
> >
> >
> >
> > —
> > Questions? First check the Kernel Driver FAQ at
> > http://www.osronline.com/article.cfm?id=256
> >
> > You are currently subscribed to ntdev as: xxxxx@telus.net
> > To unsubscribe send a blank email to xxxxx@lists.osr.com
> >
> >
> –
>
> Cliff
>
>
>

One thing further … I’ve tried it with the NTSTRSAFE.LIB in front of and
after VDW_WDM.LIB.


The personal opinion of
Gary G. Little

“Cliff Russell” wrote in message
news:xxxxx@ntdev…
> Dumb question, but just to rule it out… Are you linking with
> ntstrsafe.lib; eg. TARGETLIBS=$(DDK_LIB_PATH)\ntstrsafe.lib in your
> sources file?
>
> On 21-Sep-04, at 10:33 AM, Gary G. Little wrote:
>
> > I’m trying to use safe strings in a DriverWorks class. I’m not saying
> > DrivereWorks is interferring with symbol resolution for safe string
> > functions, but I am seeing some really STUPID errors during linkage
> > edit.
> >
> > If I build with NTSTRSAFE_LIB I get LNK2019 on RtlUnicodeToMultiByteN
> > and
> > RtlAnsiToUnicodeChar. If I use the inline version by removing
> > NTSTRSAFE_LIB
> > I then get LNK2019 on vsnwprintf. Any one else encountered this, and
> > how was
> > it resolved?
> >
> > –
> > The personal opinion of
> > Gary G. Little
> >
> >
> >
> > —
> > Questions? First check the Kernel Driver FAQ at
> > http://www.osronline.com/article.cfm?id=256
> >
> > You are currently subscribed to ntdev as: xxxxx@telus.net
> > To unsubscribe send a blank email to xxxxx@lists.osr.com
> >
> >
> –
>
> Cliff
>
>
>

Philip,

Including NTOSKRNL.LIB after NTSTRSAFE.LIB did the trick for building with
and without NTSTRSAFE_LIB. Yes I said “with and without”. The forced kernel
library inclusion satisfies the _vsnwprintf call also.

That’s a documentation bug since the documentation only mentions adding
NTSTRSAFE.LIB to the sources file and manipulating the positioning of the
header file to include functions that NTSTRSAFE flags as deprecated. I do
note that RtlStringCchPrintfW uses the deprecated function _vsnwprintf so it
might be a chicken/egg problem if _vsnwprintf has been deprecated by the
safe string header file.


The personal opinion of
Gary G. Little

“Philip Lukidis” wrote in message
news:xxxxx@ntdev…
> Not sure about RtlAnsiToUnicodeChar (can’t find it in the WinXP lib dir,
and
> I did “dumpbin /symbols *.lib > all.txt”, maybe that is not sufficient).
> For WinXP, RtlUnicodeToMultiByteN seems to be defined in ntoskrnl.lib and
> not wdm.lib, so try linking to the former library. I did the dumpbin test
> on Win server 2003 SP1 build 1218 DDK, WinXP lib dir.
>
> Philip Lukidis < mailto:xxxxx@guillemot.com>
> Software Engineer - Guillemot R&D inc. < http://www.guillemot.com
> http:</http:> >
> Tel: (514) 279-9960 ext:4111 Fax: (514) 279-2558
> 5800 St-Denis, Suite 1102, Montreal, Quebec, H2S 3L5, Canada
>
>
> -----Original Message-----
> From: Gary G. Little [mailto:xxxxx@sbcglobal.net]
> Sent: Tuesday, September 21, 2004 1:33 PM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] Safe strings usage …
>
>
> I’m trying to use safe strings in a DriverWorks class. I’m not saying
> DrivereWorks is interferring with symbol resolution for safe string
> functions, but I am seeing some really STUPID errors during linkage edit.
>
> If I build with NTSTRSAFE_LIB I get LNK2019 on RtlUnicodeToMultiByteN and
> RtlAnsiToUnicodeChar. If I use the inline version by removing
NTSTRSAFE_LIB
> I then get LNK2019 on vsnwprintf. Any one else encountered this, and how
was
> it resolved?
>
> –
> The personal opinion of
> Gary G. Little
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@guillemot.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>

Make sure your driver still loads on win2k. if you are using an XP or
later ntoskrnl.lib, it will have the symbol, but win2k will not have the
export and you could potentially not load.

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
Sent: Tuesday, September 21, 2004 11:49 AM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Safe strings usage …

Philip,

Including NTOSKRNL.LIB after NTSTRSAFE.LIB did the trick for building
with
and without NTSTRSAFE_LIB. Yes I said “with and without”. The forced
kernel
library inclusion satisfies the _vsnwprintf call also.

That’s a documentation bug since the documentation only mentions adding
NTSTRSAFE.LIB to the sources file and manipulating the positioning of
the
header file to include functions that NTSTRSAFE flags as deprecated. I
do
note that RtlStringCchPrintfW uses the deprecated function _vsnwprintf
so it
might be a chicken/egg problem if _vsnwprintf has been deprecated by the
safe string header file.


The personal opinion of
Gary G. Little

“Philip Lukidis” wrote in message
news:xxxxx@ntdev…
> Not sure about RtlAnsiToUnicodeChar (can’t find it in the WinXP lib
dir,
and
> I did “dumpbin /symbols *.lib > all.txt”, maybe that is not
sufficient).
> For WinXP, RtlUnicodeToMultiByteN seems to be defined in ntoskrnl.lib
and
> not wdm.lib, so try linking to the former library. I did the dumpbin
test
> on Win server 2003 SP1 build 1218 DDK, WinXP lib dir.
>
> Philip Lukidis < mailto:xxxxx@guillemot.com>
> Software Engineer - Guillemot R&D inc. < http://www.guillemot.com
> http:</http:> >
> Tel: (514) 279-9960 ext:4111 Fax: (514) 279-2558
> 5800 St-Denis, Suite 1102, Montreal, Quebec, H2S 3L5, Canada
>
>
> -----Original Message-----
> From: Gary G. Little [mailto:xxxxx@sbcglobal.net]
> Sent: Tuesday, September 21, 2004 1:33 PM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] Safe strings usage …
>
>
> I’m trying to use safe strings in a DriverWorks class. I’m not saying
> DrivereWorks is interferring with symbol resolution for safe string
> functions, but I am seeing some really STUPID errors during linkage
edit.
>
> If I build with NTSTRSAFE_LIB I get LNK2019 on RtlUnicodeToMultiByteN
and
> RtlAnsiToUnicodeChar. If I use the inline version by removing
NTSTRSAFE_LIB
> I then get LNK2019 on vsnwprintf. Any one else encountered this, and
how
was
> it resolved?
>
> –
> The personal opinion of
> Gary G. Little
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@guillemot.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@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

Doc bug at the very least. wdm.lib should export this, I should think at
least. Maybe I’m missing something?

Philip Lukidis < mailto:xxxxx@guillemot.com>
Software Engineer - Guillemot R&D inc. < http://www.guillemot.com
http:</http:> >
Tel: (514) 279-9960 ext:4111 Fax: (514) 279-2558
5800 St-Denis, Suite 1102, Montreal, Quebec, H2S 3L5, Canada

-----Original Message-----
From: Gary G. Little [mailto:xxxxx@sbcglobal.net]
Sent: Tuesday, September 21, 2004 2:49 PM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Safe strings usage …

Philip,

Including NTOSKRNL.LIB after NTSTRSAFE.LIB did the trick for building with
and without NTSTRSAFE_LIB. Yes I said “with and without”. The forced kernel
library inclusion satisfies the _vsnwprintf call also.

That’s a documentation bug since the documentation only mentions adding
NTSTRSAFE.LIB to the sources file and manipulating the positioning of the
header file to include functions that NTSTRSAFE flags as deprecated. I do
note that RtlStringCchPrintfW uses the deprecated function _vsnwprintf so it
might be a chicken/egg problem if _vsnwprintf has been deprecated by the
safe string header file.


The personal opinion of
Gary G. Little

“Philip Lukidis” wrote in message
news:xxxxx@ntdev…
> Not sure about RtlAnsiToUnicodeChar (can’t find it in the WinXP lib dir,
and
> I did “dumpbin /symbols *.lib > all.txt”, maybe that is not sufficient).
> For WinXP, RtlUnicodeToMultiByteN seems to be defined in ntoskrnl.lib and
> not wdm.lib, so try linking to the former library. I did the dumpbin test
> on Win server 2003 SP1 build 1218 DDK, WinXP lib dir.
>
> Philip Lukidis < mailto:xxxxx@guillemot.com>
> Software Engineer - Guillemot R&D inc. < http://www.guillemot.com
> http:</http:> >
> Tel: (514) 279-9960 ext:4111 Fax: (514) 279-2558
> 5800 St-Denis, Suite 1102, Montreal, Quebec, H2S 3L5, Canada
>
>
> -----Original Message-----
> From: Gary G. Little [mailto:xxxxx@sbcglobal.net]
> Sent: Tuesday, September 21, 2004 1:33 PM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] Safe strings usage …
>
>
> I’m trying to use safe strings in a DriverWorks class. I’m not saying
> DrivereWorks is interferring with symbol resolution for safe string
> functions, but I am seeing some really STUPID errors during linkage edit.
>
> If I build with NTSTRSAFE_LIB I get LNK2019 on RtlUnicodeToMultiByteN and
> RtlAnsiToUnicodeChar. If I use the inline version by removing
NTSTRSAFE_LIB
> I then get LNK2019 on vsnwprintf. Any one else encountered this, and how
was
> it resolved?
>
> –
> The personal opinion of
> Gary G. Little
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@guillemot.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@guillemot.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

Just for my curiosity: using “dumpbin /exports” on the Win2k ntoskrnl.lib
from the 3790 server 2003 DDK, RtlUnicodeToMultiByteN at least is exported.
Is this in error, and the actual ntoskrnl.exe does not export this? Just
curious…

Philip Lukidis < mailto:xxxxx@guillemot.com>
Software Engineer - Guillemot R&D inc. < http://www.guillemot.com >
Tel: (514) 279-9960 ext:4111 Fax: (514) 279-2558
5800 St-Denis, Suite 1102, Montreal, Quebec, H2S 3L5, Canada

-----Original Message-----
From: Doron Holan [mailto:xxxxx@windows.microsoft.com]
Sent: Tuesday, September 21, 2004 2:58 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Safe strings usage …

Make sure your driver still loads on win2k. if you are using an XP or
later ntoskrnl.lib, it will have the symbol, but win2k will not have the
export and you could potentially not load.

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
Sent: Tuesday, September 21, 2004 11:49 AM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Safe strings usage …

Philip,

Including NTOSKRNL.LIB after NTSTRSAFE.LIB did the trick for building
with
and without NTSTRSAFE_LIB. Yes I said “with and without”. The forced
kernel
library inclusion satisfies the _vsnwprintf call also.

That’s a documentation bug since the documentation only mentions adding
NTSTRSAFE.LIB to the sources file and manipulating the positioning of
the
header file to include functions that NTSTRSAFE flags as deprecated. I
do
note that RtlStringCchPrintfW uses the deprecated function _vsnwprintf
so it
might be a chicken/egg problem if _vsnwprintf has been deprecated by the
safe string header file.


The personal opinion of
Gary G. Little

“Philip Lukidis” wrote in message
news:xxxxx@ntdev…
> Not sure about RtlAnsiToUnicodeChar (can’t find it in the WinXP lib
dir,
and
> I did “dumpbin /symbols *.lib > all.txt”, maybe that is not
sufficient).
> For WinXP, RtlUnicodeToMultiByteN seems to be defined in ntoskrnl.lib
and
> not wdm.lib, so try linking to the former library. I did the dumpbin
test
> on Win server 2003 SP1 build 1218 DDK, WinXP lib dir.
>
> Philip Lukidis < mailto:xxxxx@guillemot.com>
> Software Engineer - Guillemot R&D inc. < http://www.guillemot.com
> http:</http:> >
> Tel: (514) 279-9960 ext:4111 Fax: (514) 279-2558
> 5800 St-Denis, Suite 1102, Montreal, Quebec, H2S 3L5, Canada
>
>
> -----Original Message-----
> From: Gary G. Little [mailto:xxxxx@sbcglobal.net]
> Sent: Tuesday, September 21, 2004 1:33 PM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] Safe strings usage …
>
>
> I’m trying to use safe strings in a DriverWorks class. I’m not saying
> DrivereWorks is interferring with symbol resolution for safe string
> functions, but I am seeing some really STUPID errors during linkage
edit.
>
> If I build with NTSTRSAFE_LIB I get LNK2019 on RtlUnicodeToMultiByteN
and
> RtlAnsiToUnicodeChar. If I use the inline version by removing
NTSTRSAFE_LIB
> I then get LNK2019 on vsnwprintf. Any one else encountered this, and
how
was
> it resolved?
>
> –
> The personal opinion of
> Gary G. Little
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@guillemot.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@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,

Then we need a clarification. The docs specifically state that inline can be
used for XP, but W2K should use the library version. I’m compiling for XP
SP2 right now but expect to build for 2K SP5 when it is released so I’m
using the library form. You’re telling me I will have the same problem for
2K. So what libraries, not mentioned in the documentation, should be
included in the TARGETLIBS statement?


The personal opinion of
Gary G. Little

“Doron Holan” wrote in message
news:xxxxx@ntdev…
Make sure your driver still loads on win2k. if you are using an XP or
later ntoskrnl.lib, it will have the symbol, but win2k will not have the
export and you could potentially not load.

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
Sent: Tuesday, September 21, 2004 11:49 AM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Safe strings usage …

Philip,

Including NTOSKRNL.LIB after NTSTRSAFE.LIB did the trick for building
with
and without NTSTRSAFE_LIB. Yes I said “with and without”. The forced
kernel
library inclusion satisfies the _vsnwprintf call also.

That’s a documentation bug since the documentation only mentions adding
NTSTRSAFE.LIB to the sources file and manipulating the positioning of
the
header file to include functions that NTSTRSAFE flags as deprecated. I
do
note that RtlStringCchPrintfW uses the deprecated function _vsnwprintf
so it
might be a chicken/egg problem if _vsnwprintf has been deprecated by the
safe string header file.


The personal opinion of
Gary G. Little

“Philip Lukidis” wrote in message
news:xxxxx@ntdev…
> Not sure about RtlAnsiToUnicodeChar (can’t find it in the WinXP lib
dir,
and
> I did “dumpbin /symbols *.lib > all.txt”, maybe that is not
sufficient).
> For WinXP, RtlUnicodeToMultiByteN seems to be defined in ntoskrnl.lib
and
> not wdm.lib, so try linking to the former library. I did the dumpbin
test
> on Win server 2003 SP1 build 1218 DDK, WinXP lib dir.
>
> Philip Lukidis < mailto:xxxxx@guillemot.com>
> Software Engineer - Guillemot R&D inc. < http://www.guillemot.com
> http:</http:> >
> Tel: (514) 279-9960 ext:4111 Fax: (514) 279-2558
> 5800 St-Denis, Suite 1102, Montreal, Quebec, H2S 3L5, Canada
>
>
> -----Original Message-----
> From: Gary G. Little [mailto:xxxxx@sbcglobal.net]
> Sent: Tuesday, September 21, 2004 1:33 PM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] Safe strings usage …
>
>
> I’m trying to use safe strings in a DriverWorks class. I’m not saying
> DrivereWorks is interferring with symbol resolution for safe string
> functions, but I am seeing some really STUPID errors during linkage
edit.
>
> If I build with NTSTRSAFE_LIB I get LNK2019 on RtlUnicodeToMultiByteN
and
> RtlAnsiToUnicodeChar. If I use the inline version by removing
NTSTRSAFE_LIB
> I then get LNK2019 on vsnwprintf. Any one else encountered this, and
how
was
> it resolved?
>
> –
> The personal opinion of
> Gary G. Little
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@guillemot.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@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

The export in question is _vsnwprintf, not RtlUnicodeToMultiByteN

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Philip Lukidis
Sent: Tuesday, September 21, 2004 12:23 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Safe strings usage …

Just for my curiosity: using “dumpbin /exports” on the Win2k
ntoskrnl.lib
from the 3790 server 2003 DDK, RtlUnicodeToMultiByteN at least is
exported.
Is this in error, and the actual ntoskrnl.exe does not export this?
Just
curious…

Philip Lukidis < mailto:xxxxx@guillemot.com>
Software Engineer - Guillemot R&D inc. < http://www.guillemot.com >
Tel: (514) 279-9960 ext:4111 Fax: (514) 279-2558
5800 St-Denis, Suite 1102, Montreal, Quebec, H2S 3L5, Canada

-----Original Message-----
From: Doron Holan [mailto:xxxxx@windows.microsoft.com]
Sent: Tuesday, September 21, 2004 2:58 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Safe strings usage …

Make sure your driver still loads on win2k. if you are using an XP or
later ntoskrnl.lib, it will have the symbol, but win2k will not have the
export and you could potentially not load.

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
Sent: Tuesday, September 21, 2004 11:49 AM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Safe strings usage …

Philip,

Including NTOSKRNL.LIB after NTSTRSAFE.LIB did the trick for building
with
and without NTSTRSAFE_LIB. Yes I said “with and without”. The forced
kernel
library inclusion satisfies the _vsnwprintf call also.

That’s a documentation bug since the documentation only mentions adding
NTSTRSAFE.LIB to the sources file and manipulating the positioning of
the
header file to include functions that NTSTRSAFE flags as deprecated. I
do
note that RtlStringCchPrintfW uses the deprecated function _vsnwprintf
so it
might be a chicken/egg problem if _vsnwprintf has been deprecated by the
safe string header file.


The personal opinion of
Gary G. Little

“Philip Lukidis” wrote in message
news:xxxxx@ntdev…
> Not sure about RtlAnsiToUnicodeChar (can’t find it in the WinXP lib
dir,
and
> I did “dumpbin /symbols *.lib > all.txt”, maybe that is not
sufficient).
> For WinXP, RtlUnicodeToMultiByteN seems to be defined in ntoskrnl.lib
and
> not wdm.lib, so try linking to the former library. I did the dumpbin
test
> on Win server 2003 SP1 build 1218 DDK, WinXP lib dir.
>
> Philip Lukidis < mailto:xxxxx@guillemot.com>
> Software Engineer - Guillemot R&D inc. < http://www.guillemot.com
> http:</http:> >
> Tel: (514) 279-9960 ext:4111 Fax: (514) 279-2558
> 5800 St-Denis, Suite 1102, Montreal, Quebec, H2S 3L5, Canada
>
>
> -----Original Message-----
> From: Gary G. Little [mailto:xxxxx@sbcglobal.net]
> Sent: Tuesday, September 21, 2004 1:33 PM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] Safe strings usage …
>
>
> I’m trying to use safe strings in a DriverWorks class. I’m not saying
> DrivereWorks is interferring with symbol resolution for safe string
> functions, but I am seeing some really STUPID errors during linkage
edit.
>
> If I build with NTSTRSAFE_LIB I get LNK2019 on RtlUnicodeToMultiByteN
and
> RtlAnsiToUnicodeChar. If I use the inline version by removing
NTSTRSAFE_LIB
> I then get LNK2019 on vsnwprintf. Any one else encountered this, and
how
was
> it resolved?
>
> –
> The personal opinion of
> Gary G. Little
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@guillemot.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@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


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 am just trying to clarify from you which version of ntoskrnl.lib are
you linking against? If you want to be backwards compat to win2k, use
the win2k build env in the DDK (if that is even the env you are using, I
can’t tell). Ntstrsafe.lib should be the only lib you need to link
against (along with the defining NTSTRSAFE_LIB). As for the link
errors, I have not encountered them and I am linking against
ntstrsafe.lib to load on win2k, just like you.

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
Sent: Tuesday, September 21, 2004 12:46 PM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Safe strings usage …

Doron,

Then we need a clarification. The docs specifically state that inline
can be
used for XP, but W2K should use the library version. I’m compiling for
XP
SP2 right now but expect to build for 2K SP5 when it is released so I’m
using the library form. You’re telling me I will have the same problem
for
2K. So what libraries, not mentioned in the documentation, should be
included in the TARGETLIBS statement?


The personal opinion of
Gary G. Little

“Doron Holan” wrote in message
news:xxxxx@ntdev…
Make sure your driver still loads on win2k. if you are using an XP or
later ntoskrnl.lib, it will have the symbol, but win2k will not have the
export and you could potentially not load.

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
Sent: Tuesday, September 21, 2004 11:49 AM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Safe strings usage …

Philip,

Including NTOSKRNL.LIB after NTSTRSAFE.LIB did the trick for building
with
and without NTSTRSAFE_LIB. Yes I said “with and without”. The forced
kernel
library inclusion satisfies the _vsnwprintf call also.

That’s a documentation bug since the documentation only mentions adding
NTSTRSAFE.LIB to the sources file and manipulating the positioning of
the
header file to include functions that NTSTRSAFE flags as deprecated. I
do
note that RtlStringCchPrintfW uses the deprecated function _vsnwprintf
so it
might be a chicken/egg problem if _vsnwprintf has been deprecated by the
safe string header file.


The personal opinion of
Gary G. Little

“Philip Lukidis” wrote in message
news:xxxxx@ntdev…
> Not sure about RtlAnsiToUnicodeChar (can’t find it in the WinXP lib
dir,
and
> I did “dumpbin /symbols *.lib > all.txt”, maybe that is not
sufficient).
> For WinXP, RtlUnicodeToMultiByteN seems to be defined in ntoskrnl.lib
and
> not wdm.lib, so try linking to the former library. I did the dumpbin
test
> on Win server 2003 SP1 build 1218 DDK, WinXP lib dir.
>
> Philip Lukidis < mailto:xxxxx@guillemot.com>
> Software Engineer - Guillemot R&D inc. < http://www.guillemot.com
> http:</http:> >
> Tel: (514) 279-9960 ext:4111 Fax: (514) 279-2558
> 5800 St-Denis, Suite 1102, Montreal, Quebec, H2S 3L5, Canada
>
>
> -----Original Message-----
> From: Gary G. Little [mailto:xxxxx@sbcglobal.net]
> Sent: Tuesday, September 21, 2004 1:33 PM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] Safe strings usage …
>
>
> I’m trying to use safe strings in a DriverWorks class. I’m not saying
> DrivereWorks is interferring with symbol resolution for safe string
> functions, but I am seeing some really STUPID errors during linkage
edit.
>
> If I build with NTSTRSAFE_LIB I get LNK2019 on RtlUnicodeToMultiByteN
and
> RtlAnsiToUnicodeChar. If I use the inline version by removing
NTSTRSAFE_LIB
> I then get LNK2019 on vsnwprintf. Any one else encountered this, and
how
was
> it resolved?
>
> –
> The personal opinion of
> Gary G. Little
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@guillemot.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@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: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

OK, I guess my original reply was of no use to a Win2k and higher driver.
ntstrsafe.lib should be all that one needs, and not ntoskrnl.lib (as far as
safe string functions go). I guess then that _vsnwprintf is implemented in
the Win2k version of ntstrsafe.lib.

Thanks for making me realize my error.

Philip Lukidis < mailto:xxxxx@guillemot.com>
Software Engineer - Guillemot R&D inc. < http://www.guillemot.com
http:</http:> >
Tel: (514) 279-9960 ext:4111 Fax: (514) 279-2558
5800 St-Denis, Suite 1102, Montreal, Quebec, H2S 3L5, Canada

-----Original Message-----
From: Doron Holan [mailto:xxxxx@windows.microsoft.com]
Sent: Tuesday, September 21, 2004 3:47 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Safe strings usage …

The export in question is _vsnwprintf, not RtlUnicodeToMultiByteN

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Philip Lukidis
Sent: Tuesday, September 21, 2004 12:23 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Safe strings usage …

Just for my curiosity: using “dumpbin /exports” on the Win2k
ntoskrnl.lib
from the 3790 server 2003 DDK, RtlUnicodeToMultiByteN at least is
exported.
Is this in error, and the actual ntoskrnl.exe does not export this?
Just
curious…

Philip Lukidis < mailto:xxxxx@guillemot.com>
Software Engineer - Guillemot R&D inc. < http://www.guillemot.com >
Tel: (514) 279-9960 ext:4111 Fax: (514) 279-2558
5800 St-Denis, Suite 1102, Montreal, Quebec, H2S 3L5, Canada

-----Original Message-----
From: Doron Holan [mailto:xxxxx@windows.microsoft.com]
Sent: Tuesday, September 21, 2004 2:58 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] Safe strings usage …

Make sure your driver still loads on win2k. if you are using an XP or
later ntoskrnl.lib, it will have the symbol, but win2k will not have the
export and you could potentially not load.

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
Sent: Tuesday, September 21, 2004 11:49 AM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Safe strings usage …

Philip,

Including NTOSKRNL.LIB after NTSTRSAFE.LIB did the trick for building
with
and without NTSTRSAFE_LIB. Yes I said “with and without”. The forced
kernel
library inclusion satisfies the _vsnwprintf call also.

That’s a documentation bug since the documentation only mentions adding
NTSTRSAFE.LIB to the sources file and manipulating the positioning of
the
header file to include functions that NTSTRSAFE flags as deprecated. I
do
note that RtlStringCchPrintfW uses the deprecated function _vsnwprintf
so it
might be a chicken/egg problem if _vsnwprintf has been deprecated by the
safe string header file.


The personal opinion of
Gary G. Little

“Philip Lukidis” wrote in message
news:xxxxx@ntdev…
> Not sure about RtlAnsiToUnicodeChar (can’t find it in the WinXP lib
dir,
and
> I did “dumpbin /symbols *.lib > all.txt”, maybe that is not
sufficient).
> For WinXP, RtlUnicodeToMultiByteN seems to be defined in ntoskrnl.lib
and
> not wdm.lib, so try linking to the former library. I did the dumpbin
test
> on Win server 2003 SP1 build 1218 DDK, WinXP lib dir.
>
> Philip Lukidis < mailto:xxxxx@guillemot.com>
> Software Engineer - Guillemot R&D inc. < http://www.guillemot.com
> http:</http:> >
> Tel: (514) 279-9960 ext:4111 Fax: (514) 279-2558
> 5800 St-Denis, Suite 1102, Montreal, Quebec, H2S 3L5, Canada
>
>
> -----Original Message-----
> From: Gary G. Little [mailto:xxxxx@sbcglobal.net]
> Sent: Tuesday, September 21, 2004 1:33 PM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] Safe strings usage …
>
>
> I’m trying to use safe strings in a DriverWorks class. I’m not saying
> DrivereWorks is interferring with symbol resolution for safe string
> functions, but I am seeing some really STUPID errors during linkage
edit.
>
> If I build with NTSTRSAFE_LIB I get LNK2019 on RtlUnicodeToMultiByteN
and
> RtlAnsiToUnicodeChar. If I use the inline version by removing
NTSTRSAFE_LIB
> I then get LNK2019 on vsnwprintf. Any one else encountered this, and
how
was
> it resolved?
>
> –
> The personal opinion of
> Gary G. Little
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@guillemot.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@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


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

Since the driver requires ATA pass-through, I am currently compiling using a
WNET environment for the proper pass through structure definitions, and
targeting XP SP2. When SP5 for 2K is released I will at that time produce a
driver for 2K. I’m linking against
\Winddk\3790.1218\lib\wnet\i386\ntoskrnl.lib.


The personal opinion of
Gary G. Little

“Doron Holan” wrote in message
news:xxxxx@ntdev…
I am just trying to clarify from you which version of ntoskrnl.lib are
you linking against? If you want to be backwards compat to win2k, use
the win2k build env in the DDK (if that is even the env you are using, I
can’t tell). Ntstrsafe.lib should be the only lib you need to link
against (along with the defining NTSTRSAFE_LIB). As for the link
errors, I have not encountered them and I am linking against
ntstrsafe.lib to load on win2k, just like you.

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
Sent: Tuesday, September 21, 2004 12:46 PM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Safe strings usage …

Doron,

Then we need a clarification. The docs specifically state that inline
can be
used for XP, but W2K should use the library version. I’m compiling for
XP
SP2 right now but expect to build for 2K SP5 when it is released so I’m
using the library form. You’re telling me I will have the same problem
for
2K. So what libraries, not mentioned in the documentation, should be
included in the TARGETLIBS statement?


The personal opinion of
Gary G. Little

“Doron Holan” wrote in message
news:xxxxx@ntdev…
Make sure your driver still loads on win2k. if you are using an XP or
later ntoskrnl.lib, it will have the symbol, but win2k will not have the
export and you could potentially not load.

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
Sent: Tuesday, September 21, 2004 11:49 AM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Safe strings usage …

Philip,

Including NTOSKRNL.LIB after NTSTRSAFE.LIB did the trick for building
with
and without NTSTRSAFE_LIB. Yes I said “with and without”. The forced
kernel
library inclusion satisfies the _vsnwprintf call also.

That’s a documentation bug since the documentation only mentions adding
NTSTRSAFE.LIB to the sources file and manipulating the positioning of
the
header file to include functions that NTSTRSAFE flags as deprecated. I
do
note that RtlStringCchPrintfW uses the deprecated function _vsnwprintf
so it
might be a chicken/egg problem if _vsnwprintf has been deprecated by the
safe string header file.


The personal opinion of
Gary G. Little

“Philip Lukidis” wrote in message
news:xxxxx@ntdev…
> Not sure about RtlAnsiToUnicodeChar (can’t find it in the WinXP lib
dir,
and
> I did “dumpbin /symbols *.lib > all.txt”, maybe that is not
sufficient).
> For WinXP, RtlUnicodeToMultiByteN seems to be defined in ntoskrnl.lib
and
> not wdm.lib, so try linking to the former library. I did the dumpbin
test
> on Win server 2003 SP1 build 1218 DDK, WinXP lib dir.
>
> Philip Lukidis < mailto:xxxxx@guillemot.com>
> Software Engineer - Guillemot R&D inc. < http://www.guillemot.com
> http:</http:> >
> Tel: (514) 279-9960 ext:4111 Fax: (514) 279-2558
> 5800 St-Denis, Suite 1102, Montreal, Quebec, H2S 3L5, Canada
>
>
> -----Original Message-----
> From: Gary G. Little [mailto:xxxxx@sbcglobal.net]
> Sent: Tuesday, September 21, 2004 1:33 PM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] Safe strings usage …
>
>
> I’m trying to use safe strings in a DriverWorks class. I’m not saying
> DrivereWorks is interferring with symbol resolution for safe string
> functions, but I am seeing some really STUPID errors during linkage
edit.
>
> If I build with NTSTRSAFE_LIB I get LNK2019 on RtlUnicodeToMultiByteN
and
> RtlAnsiToUnicodeChar. If I use the inline version by removing
NTSTRSAFE_LIB
> I then get LNK2019 on vsnwprintf. Any one else encountered this, and
how
was
> it resolved?
>
> –
> The personal opinion of
> Gary G. Little
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@guillemot.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@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: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

All I can say is to be very diligent about exports that you pick up in
your driver. Walter’s book has a tool which can do the cross checking
of imports in the driver vs what is exported from the kernel/hal so at
least you don’t have to constantly try to load the driver to see what is
missing.

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
Sent: Tuesday, September 21, 2004 1:35 PM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Safe strings usage …

Since the driver requires ATA pass-through, I am currently compiling
using a
WNET environment for the proper pass through structure definitions, and
targeting XP SP2. When SP5 for 2K is released I will at that time
produce a
driver for 2K. I’m linking against
\Winddk\3790.1218\lib\wnet\i386\ntoskrnl.lib.


The personal opinion of
Gary G. Little

“Doron Holan” wrote in message
news:xxxxx@ntdev…
I am just trying to clarify from you which version of ntoskrnl.lib are
you linking against? If you want to be backwards compat to win2k, use
the win2k build env in the DDK (if that is even the env you are using, I
can’t tell). Ntstrsafe.lib should be the only lib you need to link
against (along with the defining NTSTRSAFE_LIB). As for the link
errors, I have not encountered them and I am linking against
ntstrsafe.lib to load on win2k, just like you.

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
Sent: Tuesday, September 21, 2004 12:46 PM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Safe strings usage …

Doron,

Then we need a clarification. The docs specifically state that inline
can be
used for XP, but W2K should use the library version. I’m compiling for
XP
SP2 right now but expect to build for 2K SP5 when it is released so I’m
using the library form. You’re telling me I will have the same problem
for
2K. So what libraries, not mentioned in the documentation, should be
included in the TARGETLIBS statement?


The personal opinion of
Gary G. Little

“Doron Holan” wrote in message
news:xxxxx@ntdev…
Make sure your driver still loads on win2k. if you are using an XP or
later ntoskrnl.lib, it will have the symbol, but win2k will not have the
export and you could potentially not load.

d

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
Sent: Tuesday, September 21, 2004 11:49 AM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Safe strings usage …

Philip,

Including NTOSKRNL.LIB after NTSTRSAFE.LIB did the trick for building
with
and without NTSTRSAFE_LIB. Yes I said “with and without”. The forced
kernel
library inclusion satisfies the _vsnwprintf call also.

That’s a documentation bug since the documentation only mentions adding
NTSTRSAFE.LIB to the sources file and manipulating the positioning of
the
header file to include functions that NTSTRSAFE flags as deprecated. I
do
note that RtlStringCchPrintfW uses the deprecated function _vsnwprintf
so it
might be a chicken/egg problem if _vsnwprintf has been deprecated by the
safe string header file.


The personal opinion of
Gary G. Little

“Philip Lukidis” wrote in message
news:xxxxx@ntdev…
> Not sure about RtlAnsiToUnicodeChar (can’t find it in the WinXP lib
dir,
and
> I did “dumpbin /symbols *.lib > all.txt”, maybe that is not
sufficient).
> For WinXP, RtlUnicodeToMultiByteN seems to be defined in ntoskrnl.lib
and
> not wdm.lib, so try linking to the former library. I did the dumpbin
test
> on Win server 2003 SP1 build 1218 DDK, WinXP lib dir.
>
> Philip Lukidis < mailto:xxxxx@guillemot.com>
> Software Engineer - Guillemot R&D inc. < http://www.guillemot.com
> http:</http:> >
> Tel: (514) 279-9960 ext:4111 Fax: (514) 279-2558
> 5800 St-Denis, Suite 1102, Montreal, Quebec, H2S 3L5, Canada
>
>
> -----Original Message-----
> From: Gary G. Little [mailto:xxxxx@sbcglobal.net]
> Sent: Tuesday, September 21, 2004 1:33 PM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] Safe strings usage …
>
>
> I’m trying to use safe strings in a DriverWorks class. I’m not saying
> DrivereWorks is interferring with symbol resolution for safe string
> functions, but I am seeing some really STUPID errors during linkage
edit.
>
> If I build with NTSTRSAFE_LIB I get LNK2019 on RtlUnicodeToMultiByteN
and
> RtlAnsiToUnicodeChar. If I use the inline version by removing
NTSTRSAFE_LIB
> I then get LNK2019 on vsnwprintf. Any one else encountered this, and
how
was
> it resolved?
>
> –
> The personal opinion of
> Gary G. Little
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@guillemot.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@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: 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: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com