Forum Replies Created
-
AuthorPosts
-
support
KeymasterIs your driver root-enumerated, or do you rely on some bus driver?
support
KeymasterHi, could you please create a dump file as described above? Without it it’s impossible for me to determine the cause of the problem.
support
KeymasterThe 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.
support
Keymasterhost machine
support
KeymasterI mean, the debugging tools path here:
[attachment=0:v89idxtl]dbgtools.png[/attachment:v89idxtl]support
KeymasterThe 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.
support
KeymasterVersion history is shown in the installer.
Command-line parameters help can be retrieved by running batchmnt.exe without any arguments.support
KeymasterSee the “tutorials” section on WinCDEmu page (http://wincdemu.sysprogs.org/)
support
KeymasterDid you install the 32-bit Debugging tools?
support
KeymasterUnfortunately, named pipes will only work for VMs. If you are using 2 PCs, the best solution is to use the FireWire connection.
support
Keymasterok, 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
KeymasterPlease also try this build: http://visualddk.sysprogs.org/test/VisualDDK-1.5.3.exe
it should not have any references to VC9 runtime librariessupport
KeymasterHi, try this build: http://visualddk.sysprogs.org/test/VisualDDK-1.5.3.exe
support
Keymastermsdbg.h should be in the Debugging Tools directory
support
Keymasteroops. you need the DIA SDK from Microsoft.
-
AuthorPosts