- Re: Unresolved symbol in 2000 build
- Posted by Calvin Guan on September 10th, 2004
If you meant to use safe string replacement for vsnwprintf,
RtlStringCchVPrintfExW is the way to go. To include safe string lib:
TARGETLIBS= \
$(DDK_LIB_PATH)\ntstrsafe.lib
-
Calvin Guan Software Engineer
ATI Technologies Inc. www.ati.com
"Ben Geib" <BenGeib@discussions.microsoft.com> wrote in message
news:8162AFE8-E00E-48C4-8778-3073CF2597A4@microsoft.com...
- Posted by Don Burn on September 10th, 2004
No, use the 3790 DDK completely, it includes a ntstrsafe.lib for Windows
2000. Don't mix stuff from two DDK's this is a disaster in the making.
--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply
"Ben Geib" <BenGeib@discussions.microsoft.com> wrote in message
news:EE505D6B-712A-4B3F-A64C-BD0D7197DD56@microsoft.com...
- Posted by Eliyas Yakub [MSFT] on September 12th, 2004
The following steps are *REQUIRED* if ntstrsafe.h is used for drivers on:
Windows 2000
Windows Millennium Edition
Windows 98 Second Edition
Windows 98
1. #define NTSTRSAFE_LIB before including this header file.
2. Add ntstrsafe.lib to the TARGET_LIBS line in SOURCES
Drivers running on XP and later can skip these steps to create a smaller
driver.
--
--
-Eliyas
This posting is provided "AS IS" with no warranties, and confers no rights.
http://www.microsoft.com/whdc/driver/default.mspx
http://www.microsoft.com/whdc/driver/kernel/KB-drv.mspx
"Ben Geib" <BenGeib@discussions.microsoft.com> wrote in message
news:69E2BA9D-E74D-4372-8DEC-1C8F292ED608@microsoft.com...