The call to LoadLibrary(ext) failed, Win32 error 127

[Stephen Slezic]

I'm running Win2k. Had dbg_x86_6.5.3.8 installed and it ran just fine. Tried
upgrading to dbg_x86_6.6.03.5 and now I have problems loading ext.dll library.

Version command in WinDbg produces:

32-bit Full kernel dump: C:\Software\mem dump\MEMORY013006-00.DMP
command line: '"C:\Program Files\Debugging Tools for Windows\windbg.exe" '
Debugger Process 0x5CC
dbgeng: image 6.6.0003.5, built Wed Jan 18 18:06:52 2006
[path: C:\Program Files\Debugging Tools for Windows\dbgeng.dll]
dbghelp: image 6.6.0003.5, built Wed Jan 18 18:06:37 2006
[path: C:\Program Files\Debugging Tools for Windows\dbghelp.dll]
DIA version: 51108
Extension DLL search Path:
C:\Program Files\Debugging Tools for Windows\winext;C:\Program
Files\Debugging Tools for Windows\winext\arcade;C:\Program Files\Debugging
Tools for Windows\W2KFre;C:\Program Files\Debugging Tools for
Windows\pri;C:\Program Files\Debugging Tools for Windows;C:\Program
Files\Debugging Tools for
Windows\winext\arcade;C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem;C:\Program
Files\ATI Technologies\ATI Control
Panel;C:\PROGRA~1\MICROS~4\Common\MSDev98\Bin;C:\Program Files\Microsoft
Visual Studio\Common\Tools\WinNT;C:\Program Files\Microsoft Visual
Studio\Common\MSDev98\Bin;C:\Program Files\Microsoft Visual
Studio\Common\Tools;C:\Program Files\Microsoft Visual
Studio\VC98\bin;C:\Program Files\Debugging Tools for Windows
Extension DLL chain:
kext: image 6.6.0003.5, API 1.0.0, built Wed Jan 18 18:06:10 2006
[path: C:\Program Files\Debugging Tools for Windows\winext\kext.dll]
kdextx86: image 5.00.2195.6883, API 5.0.5, built Mon Feb 21 20:38:44 2005
[path: C:\Program Files\Debugging Tools for
Windows\W2KFre\kdextx86.dll]
Free Extension dll for Build 2195 debugging Free kernel for Build 2195
dbghelp: image 6.6.0003.5, API 6.0.6, built Wed Jan 18 18:06:37 2006
[path: C:\Program Files\Debugging Tools for Windows\dbghelp.dll]
The call to LoadLibrary(ext) failed, Win32 error 127
"The specified procedure could not be found."
Please check your debugger configuration and/or network access.
ext: (Not loaded)

Dependency Walker run on ext.dll (ver 6.6.3.5) reports the following
unresolved parent imports:

MSVCRT.DLL (ver 6.1.9844.0)
_strtoui64

DBGHELP.DLL (ver 5.0.2195.6613)
SymFindFileInPath

DBGENG.DLL/DBGHELP.DLL
DbgHelpCreateUserDump
FindExecutableImageExW
SymAddSymbol
SymAddSymbolW
SymDeleteSymbolW
SymEnumLinesW
SymEnumSourceLinesW
SymEnumSymbolsForAddrW
SymEnumSymbolsW
SymEnumTypesW
SymFindFileInPathW
SymFromAddrW
SymFromIndexW
SymFromNameW
SymFromTokenW
SymGetFileLineOffsets64
SymGetHomeDirectoryW
SymGetLineFromAddrW64
SymGetLineFromNameW64
SymGetSourceFileFromTokenW
SymGetSourceFileTokenW
SymGetSourceVarFromTokenW
SymGetTypeFromNameW
SymGetTypeInfo
SymGetTypeInfoEx
SymInitializeW
SymLoadModuleExW
SymMatchFileNameW
SymMatchStringA
SymMatchStringW
SymNextW
SymPrevW
SymRegisterCallbackW64
SymSearchW
SymSetContext
SymSetSearchPathW
dbghelp

Has anybody got any suggestions on how to resolve this?

--
(@)

[Drew Bliss [MSFT]]

This is a regression, we're looking at ways that we can try and get around
it.

"Stephen Slezic" <n...@email.com> wrote in message
news:6AEC8CA1-EF46-48BE...@microsoft.com...

[SreckoK]

I have to use windbg on a Windows 2000SP4 system. So I encounter the same
problem. Any news concerning this issue? Is there a solution or a bypass for
this problem available?
Thanks!

[Drew Bliss [MSFT]]

Send mail to wind...@microsoft.com.

"SreckoK" <Sre...@discussions.microsoft.com> wrote in message
news:12C19260-AF4B-482F...@microsoft.com...