Forum Replies Created
-
Posts
-
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.
Hi, did you install the 32-bit version of Debugging tools for Windows and specify the correct path in VisualDDK settings?
As far as I know, it is only possible for the USB devices.
However, you can try making a “dummy PCI driver” that will forward the requests to a named pipe and then develop the high-level logic in user-mode. However, for certain device types this might be impossible due to performance constraints.
