Re: Strange ddk lib unresolved external and kludgy fix
- From: "Eliyas Yakub [MSFT]" <eliyasy@xxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 18 Apr 2006 10:56:20 -0700
You should Server SP1 DDK.
F:\WINDDK\3790.1830\inc>findstr /s GUID_SDBUS_INTERFACE_STANDARD *
ddk\wnet\ntddsd.h:DEFINE_GUID( GUID_SDBUS_INTERFACE_STANDARD, 0x6bb24d81L,
0xe92
4, 0x4825, 0xaf, 0x49, 0x3a, 0xcd, 0x33, 0xc1, 0xd8, 0x20 );
ddk\wxp\ntddsd.h:DEFINE_GUID( GUID_SDBUS_INTERFACE_STANDARD, 0x6bb24d81L,
0xe924
, 0x4825, 0xaf, 0x49, 0x3a, 0xcd, 0x33, 0xc1, 0xd8, 0x20 );
The build you are using (3790.1230) is probably Server gold or some beta
version.
--
-Eliyas
This posting is provided "AS IS" with no warranties, and confers no rights.
http://www.microsoft.com/whdc/driver/kernel/KB-drv.mspx
.
- Follow-Ups:
- Re: Strange ddk lib unresolved external and kludgy fix
- From: QuasiCodo
- Re: Strange ddk lib unresolved external and kludgy fix
- References:
- Strange ddk lib unresolved external and kludgy fix
- From: QuasiCodo
- Re: Strange ddk lib unresolved external and kludgy fix
- From: Skywing
- Strange ddk lib unresolved external and kludgy fix
- Prev by Date: Re: How to force AllocateCommonBuffer in the lower 4Gbytes
- Next by Date: Re: Strange ddk lib unresolved external and kludgy fix
- Previous by thread: Re: Strange ddk lib unresolved external and kludgy fix
- Next by thread: Re: Strange ddk lib unresolved external and kludgy fix
- Index(es):