[support]

Were you able to set breakpoints/use the “forcible break-in” option?

[support]

Do you put the complete path including the version number (e.g. E:WinDDK7600.16385.0)?
If yes, could you please post a screenshot?

[support]

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.

[support]

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.

[support]

The workaround for iTunes problem was added in version 3.4.

[support]

OK, thanks for the fix. I’ll include it in the next version.

[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.

[support]

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.

[support]

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.

[support]

ok, thanks for the reference walkthrough.

[support]

bcdedit /dbgsettings serial debugport:1
then, use VirtualKD entry
More details here: http://msdn.microsoft.com/en-us/windows/hardware/gg487520

[support]

Go 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”.

[support]

OK, will add it to the roadmap.

[support]

This is very strange. I have just tested VirtualBox 4.0.8 with Win7 x64 guest and found no problems.
I assume something went wrong with installing the guest-side transport DLL. Can you try doing dynamic patching (described in http://virtualkd.sysprogs.org/ under “Manual Installation”)?

[support]

OK, try it in the following sequence:
1. Start your VM. Do not start Windows
2. Start virtual machine monitor. Wait until the VM appears in the list and press “Start debugger”
3. Wait until WinDbg loads and says “connecting to pipe…”
4. Now start the VirtualKD version of Windows.
5. If nothing happens, look at the “packets, resets, OS, debugger and poll rate” fields in VMMON and post the values here.

[Author]

Posts