Forum Replies Created
-
Posts
-
See the “tutorials” section on WinCDEmu page (http://wincdemu.sysprogs.org/)
Unfortunately, named pipes will only work for VMs. If you are using 2 PCs, the best solution is to use the FireWire connection.
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)?
Please also try this build: http://visualddk.sysprogs.org/test/VisualDDK-1.5.3.exe
it should not have any references to VC9 runtime librariesHi, try this build: http://visualddk.sysprogs.org/test/VisualDDK-1.5.3.exe
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?
Have you specified the path to Debugging Tools in VisualDDK settings? (Tools->VisualDDK settings in VS).
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.
