This is a problem with 6.6.03.5, please update to the 6.6.07.5 release.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Martin O’Brien
Sent: Monday, September 18, 2006 6:04 AM
To: Kernel Debugging Interest List
Subject: Re: [windbg] How to resolve error “The call to LoadLibrary(ext)
failed, Win32 error 127”
VIMAL:
I’ve usually seen this when trying to load an extension that relies on a
dll it can not find in the search path. In that case, I use Depends to
open the extension and see what is missing. 90% of the time, it turns
out to be MSVCRT80.DLL, at which point I generally just give up and find
another way to do something, rather than deal with this installation
issue.
I can’t say I know what is going on in your case. Perhaps WinDbg is
auto loading an extension?
MM
>> xxxxx@gmail.com 2006-09-18 02:27 >>>
hi all,
I am getting an error like
The call to LoadLibrary(ext) failed, win32 error 127 “The specified
procedure could not be found”
So please advice me what went wrong…
Details
Microsoft (R) Windows Debugger Version 6.6.0003.5 Copyright (c)
Microsoft Corporation. All rights reserved.
Opened \.\com1
Waiting to reconnect…
Connected to Windows 2000 2195 x86 compatible target, ptr64 FALSE Kernel
Debugger connection established.
Symbol search path is: C:\WINNT\Symbols;SRV*C:\WebSymbols*
http://msdl.microsoft.com/download/symbols
Executable search path is: C:\Vimal\Realtek\objchk_w2k_x86\i386
Windows 2000 Kernel Version 2195 UP Free x86 compatible Kernel base =
0x80400000 PsLoadedModuleList = 0x8046e1b8 System Uptime: not available
The call to LoadLibrary(ext) failed, Win32 error 127
“The specified procedure could not be found.”
thanks in advance,
vimal
You are currently subscribed to windbg as: xxxxx@evitechnology.com To
unsubscribe send a blank email to xxxxx@lists.osr.com
You are currently subscribed to windbg as: xxxxx@winse.microsoft.com To
unsubscribe send a blank email to xxxxx@lists.osr.com