Forum Replies Created
-
AuthorPosts
-
supportKeymaster
You need to open project settings and set the “output file name” there. VisualDDK uses it to find which driver to load.
supportKeymasterOK, 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.
supportKeymasterInstalling C# fixes the missing stdole.dll bug present in VS2010.
I’ve added a workaround for that in VisualDDK 1.5.4supportKeymasterPlease 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.
supportKeymasterPlease 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.
supportKeymasterIs your driver root-enumerated, or do you rely on some bus driver?
supportKeymasterHi, could you please create a dump file as described above? Without it it’s impossible for me to determine the cause of the problem.
supportKeymasterThe windbg that comes with WDK is probably 64-bit. You need to install the 32-bit WinDbg by running V:Debuggerssetup_x86.exe, where V: is your WDK disc.
supportKeymasterhost machine
supportKeymasterI mean, the debugging tools path here:
[attachment=0:v89idxtl]dbgtools.png[/attachment:v89idxtl]supportKeymasterThe portable version does not have a command-line interface and is inteded for users that want to quickly mount an image without installing the full version.
supportKeymasterVersion history is shown in the installer.
Command-line parameters help can be retrieved by running batchmnt.exe without any arguments.supportKeymasterSee the “tutorials” section on WinCDEmu page (http://wincdemu.sysprogs.org/)
supportKeymasterDid you install the 32-bit Debugging tools?
supportKeymasterUnfortunately, named pipes will only work for VMs. If you are using 2 PCs, the best solution is to use the FireWire connection.
-
AuthorPosts