Prev: BSOD memory.dmp deleted by Windows 7
Next: Allocate isoch resource failed for 1394b driver on windows 7 x64
From: Neel on 9 Feb 2010 16:56
Hi,


In my application (VC++ 2008 SP1 & WDK 6001.18000) I am using
"Get_Next_Res_Des" to get device information. But the UMDH (User-Mode heap
dump) call stack shows:
CFGMGR32!CM_Detect_Resource_Conflict+00000065
CFGMGR32!CM_Get_Next_Res_Des_Ex+00000278
CFGMGR32!CM_Get_Next_Res_Des+00000017
.................................


And MSDN says "CM_Detect_Resource_Conflict:This function is obsolete and no
longer supported in Windows 2000 and later versions of Windows. Use
CM_Query_Resource_Conflict_List instead."
http://msdn.microsoft.com/en-us/library/ms789519.aspx


Since I am not calling this "CM_Detect_Resource_Conflict"
1. Why "CM_Get_Next_Res_Des" is calling "CM_Get_Next_Res_Des_Ex" and
"CM_Get_Next_Res_Des_Ex" is calling "CM_Detect_Resource_Conflict"?
2. How should avoid this happening? Any project settings needed?


Thanks,
Neelesh

From: Maxim S. Shatskih on 10 Feb 2010 00:55
> 1. Why "CM_Get_Next_Res_Des" is calling "CM_Get_Next_Res_Des_Ex" and
> "CM_Get_Next_Res_Des_Ex" is calling "CM_Detect_Resource_Conflict"?

This is the internal implementation detail, which does not care.

Even if the function is deprecated as _public_, it can still live as internal one.

--
Maxim S. Shatskih
Windows DDK MVP
maxim(a)storagecraft.com
http://www.storagecraft.com

 | 
Pages: 1
Prev: BSOD memory.dmp deleted by Windows 7
Next: Allocate isoch resource failed for 1394b driver on windows 7 x64