Forum Replies Created
-
AuthorPosts
-
support
KeymasterIt is generally possible, but you would need to hack VirtualKD code for that. I could give you more details if you’re interested.
support
KeymasterYou can create the dump file by opening Task Manager, finding the error message, selecting “switch to process” from the context menu and finally right-clicking on the process (should be devenv.exe) and selecting “create dump file”.
support
KeymasterSeems to be a WinCDEmu bug. Can also be some weird incompatibility issue. Could you please create a dump file and send it to me?
support
KeymasterOops. Copying both to system32 was a bad idea. WinDBG uses some very special version of dbghelp.dll that is incompatible with most other clients.
Please restore the original versions and specify the debugging tools location in VisualDDK properties. VIsualDDK will automatically use the correct versions.support
KeymasterPlease install the 32-bit debugger from the WDK disc manually.
support
KeymasterTry looing at file properties -> details of any EXE/DLL in WinCDEmu folder.
support
KeymasterIn fact, I’m travelling around till August and only checking my messages once or twice per day. I assume, somewhat in the August I will probably have some time. But definitely not before. If you have good C++ background, I could show you what to hack in WinCDEmu sources to add this feature.
support
KeymasterIt can be also implemented by adding a small change to WinCDEmu driver. I’ll consider it in the future versions.
support
KeymasterDoes pressing “refresh” in Visual Studio change anything?
support
KeymasterDid you run VisualDDK monitor on the virtual machine? Are you sure the firewall is not blocking the port?
support
KeymasterYou need to open project settings and set the “output file name” there. VisualDDK uses it to find which driver to load.
support
KeymasterOK, 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.
support
KeymasterInstalling C# fixes the missing stdole.dll bug present in VS2010.
I’ve added a workaround for that in VisualDDK 1.5.4support
KeymasterPlease 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.
support
KeymasterPlease 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.
-
AuthorPosts