Forum Replies Created
-
AuthorPosts
-
ping235Participant
Now it works well totally, no need to replace dbgeng.dll and dbghelp.dll anymore, i just restored the OS, maybe some other apps messed the OS up.
Thanks a lot. bazis.
ping235ParticipantHi bazis,
I tried VisualDDK 1.5.4, although there still have some problems, but it works finally. that is the steps:
1. uninstall WinDDK and VisualDDK
2. reinstall winddk except the debug tools
3. install debug tools manually by running {drive letter of WDK CD}:Debuggerssetup_x86.exe
4. copy dbgeng.dll and dbghelp.dll to system32, and replace the old one
5. install VisualDDK 1.5.4If missing step 4, it will complains that “The procedure entry point SymSetSearchPathW could not be located in the dynamic link library dbghelp.dll.” and then tell dbgeng.dll is not win32 version when install VisualDDK 1.5.4 at step 5.
Thanks so much for the nice tool and your patience.
ping235ParticipantI tried following your way, just get the same error.
I can run windbg in windows explorer just from the path: C:WinDDK7600.16385.1Debuggers, my OS is 32-bit WinXP, so the windbg must be 32-bit version, isn’t it?
In addition, the windbg works fine with VisualDDK’s vmmon.exe, just can not start debug from vs IDE, is there other possible question?
ping235ParticipantThank you, bazis,
I checked the debugging tools path, it is different from yours but it do point to the path where windbg.exe, kd.exe and dbgeng.dll reside in, the path: C:WinDDK7600.16385.1Debuggers is the default install path.
P.S. I don’t know if it is relevant or not, my windbg comes from winddk.
ping235ParticipantYes, I do,
I installed WinDDK 7600.16385.1 with debuggers(32-bit kd.exe and windbg.exe), i believe i have specified the correct path in VisualDDK settings.
that is the snapshot of VisualDDK settings and WinDDK directory. -
AuthorPosts