[support]

Version history is shown in the installer.
Command-line parameters help can be retrieved by running batchmnt.exe without any arguments.

[support]

See the “tutorials” section on WinCDEmu page (http://wincdemu.sysprogs.org/)

[support]

Did you install the 32-bit Debugging tools?

[support]

Unfortunately, named pipes will only work for VMs. If you are using 2 PCs, the best solution is to use the FireWire connection.

[support]

ok, do you actually tell the VM to create a local pipe (not connect to an existing one or create a pipe in another VM)?

[support]

Please also try this build: http://visualddk.sysprogs.org/test/VisualDDK-1.5.3.exe
it should not have any references to VC9 runtime libraries

[support]

Hi, try this build: http://visualddk.sysprogs.org/test/VisualDDK-1.5.3.exe

[support]

msdbg.h should be in the Debugging Tools directory

[support]

oops. you need the DIA SDK from Microsoft.

[support]

Please use DDKDebugger.sln. DDKDebugLauncher is just a wrapper that starts driver projects.

[support]

DDKDebugLauncher is a .Net module and should not be causing missing DLL problems. Could you download VisualDDK sources from SourceForge, compile DDKDebugLauncher (it will register itself automatically), set a breakpoint in BasicMSDbgSession::CreateClient() and step through to see what fails?

[support]

The DLL names are dbghelp.dll and dbgeng.dll both located in the debugging tools directory.

[support]

Have you specified the path to Debugging Tools in VisualDDK settings? (Tools->VisualDDK settings in VS).

[support]

Hi, did you specify the path to a 32-bit version of Debugging tools?

[support]

You can either create a new “make project” so that Visual Studio will invoke “build”, or use VisualDDK project wizard and select “use existing files” to have the project created for you.

[Author]

Posts