Forum Replies Created
-
Posts
-
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.
The 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.
The 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.
Version history is shown in the installer.
Command-line parameters help can be retrieved by running batchmnt.exe without any arguments.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.
