Most likely the problem was that an older build of the new windbg was
not uninstalled before installing the beta 1 release. You should always
uninstall an older interim build before installing a new build. Often
during the beta cycle, we do not support “upgrading” to or from interim
builds.
Also, the Windows 2000 SP1 / Datacenter DDK does contain the new windbg
on the CD in a separate directory, with a separate install program. And
the old windbg is still installed as part of the DDK. However, the new
windbg is not included when you download the SP1 DDK from the web. It
must be downloaded separately from
http://www.microsoft.com/ddk/debugging.
Sandy Spinrad
Device Driver Evangelist
Microsoft Corporation
-----Original Message-----
From: Graham, Simon [mailto:xxxxx@stratus.com]
Sent: Wednesday, August 23, 2000 9:09 AM
To: NT Developers Interest List
Subject: [ntdev] RE: WinDBG beta
Well, don’t forget that this version of windbg is the Whistler version;
perhaps there have been changes in dbghelp for Whistler that were not
incorporated into SP1…
-----Original Message-----
From: Ed Lau [mailto:xxxxx@midcore.com]
Sent: Wednesday, August 23, 2000 9:29 AM
To: NT Developers Interest List
Subject: [ntdev] RE: WinDBG beta
Graham -
Thanks; that did the trick. I find it somewhat odd that the Win 2K SP1
DDK
does not include this updated DBGHELP.DLL, though …
Ed
MidCore Software, Inc.
www.midcore.com
----- Original Message -----
From: “Graham, Simon”
To: “NT Developers Interest List”
Sent: Tuesday, August 22, 2000 10:54 PM
Subject: [ntdev] RE: WinDBG beta
> I got this as well; I fixed it by right clicking on the msi file and
> selecting repair and then telling it to repair everything… worked
fine
> after that…
>
> /simgr
>
>
> -----Original Message-----
> From: xxxxx@midcore.com [mailto:xxxxx@midcore.com]
> Sent: Tuesday, August 22, 2000 12:21 PM
> To: NT Developers Interest List
> Subject: [ntdev] WinDBG beta
>
>
> I recently installed the latest version (as of today) of WinDBG posted
at
> www.microsoft.com/ddk/debugging - I think the version is 5.1.2250.3
(that
> is the version displayed on the properties page of windbg.exe) on a
Win
> 2000 PC version 5.00.2195 SP1, and receive the following error when
> starting WinDBG - “The procedure entry point SymSetContext could not
be
> located in the dynamic link library DBGHELP.DLL” - that entry point
> certainly does not exist in DBGHELP.DLL, and I have only one copy of
the
> DLL (disregarding the identical copy in the DLL cache directory).
>
> Does anyone have any insight into this? I have searched past archives
in
> the windbg listserver to no avail, and couldn’t find anything usefull
in
> the release notes or debugger documentation.
>
>
> Thanks in Advance,
>
> Ed
>
> MidCore Software, Inc.
> www.midcore.com
>
> —
> You are currently subscribed to ntdev as: xxxxx@stratus.com
> To unsubscribe send a blank email to $subst(‘Email.Unsub’)
>
> —
> You are currently subscribed to ntdev as: xxxxx@midcore.com
> To unsubscribe send a blank email to $subst(‘Email.Unsub’)
>
—
You are currently subscribed to ntdev as: xxxxx@stratus.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)
—
You are currently subscribed to ntdev as: xxxxx@exchange.microsoft.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)