Forum Replies Created
-
Posts
-
Hi, please run the following commands:
devenv /resetaddin VisualGDB.AddIn
devenv /resetaddin DDKDebugConsole.Connect
devenv /resetaddin DDKDebugLauncher.Connect
devenv /resetaddin DDKProjectProperties.ConnectIt will reset all addin settings.
If this does not help, please execute the Tools->Addins command in Visual Studio and ensure that all VisualDDK addins are enabled.
Note that if you import previously saved Visual Studio settings after installing VisualGDB/VisualDDK, the newly created menus will be reset. Running /resetaddin will always restore the add-in menus to their default state.
Hi,
I will add the possibility to choose associated extensions to the next version.
However, has WinCDEmu never associated itself with RAR file. If you’re getting problems with them, they are probably caused by the Universal Extractor, not WinCDEmu.Hi, Step 7 is very important. You need to replace the original version of VBoxDD.dll by the special version provided by VirtualKD. This will force VirtualBox to create a special virtual device that will allow the OS to communicate with VisualDDK.
Note that the original VBoxDD.dll should be renamed to VBoxDD0.dll, so that the modified version can actually find it.Hi,
getenv() is a function for normal applications, not drivers.
To get process environment from the driver you’ll probably need to parse the PEB structure.
Try googling or looking into ReactOS sources for more details.Hi.
I’m currently under very heavy load releasing BazisLib 3.0, several commercial projects that depend on it and making the new website.
I also have a list of features to add to WinCDEmu and I will hopefully find time around summer to do that.
As for the forum spam, I’m testing a semi-automated tool for cleaning it up, but again, I cannot promise to find time before summer to look more into it.The installer checks for {Visual Studio directory}VCvcprojects. If it does not exist, you are missing the Visual C++ component and VisualDDK won’t work.
Please attach the DDKDebugger-dbg.log file from VisualDDK directory. It would probably contain the reason for hanging.
Not 100% sure, but I think I’ve stumbled upon some article from Microsoft explaining that the loader debugging is only possible using COM1. I would suggest googling around to see if anyone managed to set up other protocol for the bootloader (e.g. FireWire).
Maybe, it’s related to the way child processes are created. Try making a batch file that starts KD using “start” command and tell VMMON to use it (the “custom:” radio button).
This bug was caused by a recent output format change in latest versions of WinDbg.
Fixed in VisualDDK 1.5.6How did you integrate VirtualKD into VirtualBox? Could you have accidentally left VBoxDD0.dll from an older VirtualBox version? (e.g. just replaced VBoxDD.dll after updating VirtualBox, but did not update VBoxDD0.dll)?
Try reinstalling VirtualBox and reintegrating VirtualKD with it (since VisualDDK 1.5.6 it can be done by running VirtualKDSetup.exe). This will ensure that all files have correct versions.Thanks for the minidump. I think, I’ve found the problem. Please check this version: http://wincdemu.sysprogs.org/temp/BazisVirtualCDBus.sys
