Forum Replies Created
-
Posts
-
I assume, the problem is related to your German version of Visual Studio.
I would recommend downloading VisualDDK sources (https://sourceforge.net/projects/visualddk/files/visualddk/1.5.2/VisualDDK-1.5.2-src.zip/download), opening the DDKDebugLauncher project, setting breakpoint on OnConnection() method in Connect.cs and stepping through.
The LookupLocalizedName() method should automaticall fetch the German names for “Tools” and “Debug” menus. If this does not happen, or incorrect names are fetched, please tell me the correct ones, so that I can update them in the next release of VisualDDK.Unfortunately, AuthentiCode certificates are more than just SSL or usual code signing certificates. I have asked GoDaddy support about compatibility with Authenticode and received an answer that their certificates are not applicable.
Do you put the complete path including the version number (e.g. E:WinDDK7600.16385.0)?
If yes, could you please post a screenshot?Hi, John.
1) I will add an option for batchmnt to use the portable driver in the next version.
2) I assume, this could be related to some handles that Windows keeps open, so that the new driver cannot register itself in the system before those are released. However, when I tested it, installing/uninstalling/reinstalling the portable driver did not require a restart.Thank you for the WinPE image. I have downloaded it and tried on a VM.
It seems that WinPE does not support dynamic Plug-n-Play device recognition (e.g. USB disks). WinCDEmu relies on Plug-n-Play manager to create the virtual drives dynamically and will not work unless the OS supports it.
I would recommend using some third-party Windows LiveCD compilations with full Plug-n-Play support.I assume, the problem is with the VIRTUALKD_HOOKED_VBOX_DEVICE_NAME set to “pci” (see VBoxDD.cpp).
In your case you might have to change it to some other device loaded by VirtualBox.The sources are actual. The -1 in eax is even more strange.
I would suggest building a debug version of VBoxDD.DLL, copying it to VirtualBox dir, attaching to the VirtualBox process from Visual Studio and setting breakpoints on VirtualKDPortOutHandler() and VirtualKDPortInHandler(). These functions get called when the debug I/O port is read/written.
If VirtualKDPortInHandler() is not called, please try replacing 0x5658 (and 0x5659) with some other port number (note that 2 consequent ports are used). You will need to modify ConstructOverride() in VBoxDD.DLL and several .h/.asm files in kdvm directory.The problem is not about the format, it is about special SCSI commands that Windows uses to access non-data track. Anyway, I’ll consider supporting it in the future.
bcdedit /dbgsettings serial debugport:1
then, use VirtualKD entry
More details here: http://msdn.microsoft.com/en-us/windows/hardware/gg487520Go to VM properties, add select Ports, set COM1 to point to a local pipe (\.pipecom_1), start WinDbg with parameters: “-k com:pipe,port=.\pipedebug”.
