Forum Replies Created
-
Posts
-
Oops. Copying both to system32 was a bad idea. WinDBG uses some very special version of dbghelp.dll that is incompatible with most other clients.
Please restore the original versions and specify the debugging tools location in VisualDDK properties. VIsualDDK will automatically use the correct versions.In fact, I’m travelling around till August and only checking my messages once or twice per day. I assume, somewhat in the August I will probably have some time. But definitely not before. If you have good C++ background, I could show you what to hack in WinCDEmu sources to add this feature.
It can be also implemented by adding a small change to WinCDEmu driver. I’ll consider it in the future versions.
Did you run VisualDDK monitor on the virtual machine? Are you sure the firewall is not blocking the port?
You need to open project settings and set the “output file name” there. VisualDDK uses it to find which driver to load.
OK, I am assuming the problem occurs because the launcher cannot find the compiled sys file. You can try experimenting with the launcher settings, or installing the driver manually and using the Debug->Attach dialog to attach to the target machine.
Installing C# fixes the missing stdole.dll bug present in VS2010.
I’ve added a workaround for that in VisualDDK 1.5.4Please download VisualDDK 1.5.4, select “register debug version of DDKDebugger.dll” in installer, run Visual Studio as administrator, attempt debugging and post the DDKDebugger.log file from VisualDDK directory here. The log file should contain problem details.
Please download VisualDDK 1.5.4, select “register debug version of DDKDebugger.dll” in installer, run Visual Studio as administrator, attempt debugging and post the DDKDebugger.log file from VisualDDK directory here. The log file should contain problem details.
Hi, could you please create a dump file as described above? Without it it’s impossible for me to determine the cause of the problem.
