[NeWbY]

What’s your setup like?

[NeWbY]

That seems to work, jospalau!

Thanks for posting your solution 🙂

[NeWbY]

I don’t think the expression versions are supported.

[NeWbY]

At the screen where you can select which ‘os’ you want to load (before windows loads), you should start the debugging. You will see the window ‘Connecting to kernel debugging session…’ open with all fails calls. Then you should select the ‘Microsoft Windows XP Professional [VirtualKD]’ at the ‘os’ selection window so windows starts. This might take a while before windows start, but when windows is starting you should see the ‘Connecting to kernel debugging session…’ show different logs and it should start the kernel debugging session.
You can’t debug yet until windows has fully started and the DDKLaunch monitor has connected with the debugging session.

[NeWbY]

Could you post your patched version maybe? Or send an url to it in PM to me?
I’ve got the same problem, and it’s kind of annoying having to click OK the whole time when it tries to load the PDBs >_>

[NeWbY]

I’m in a similar position. Not using Linux as host OS but Windows 7 though.
I’ve got the following setup:
Host (vmware): Windows 7
Dev Machine (virtual machine #1): Windows XP
Test Machine (virtual machine #2): Windows XP
I use debugport=COM1 in the debug settings in boot.ini on the Test Machine, and using a named pipe from the Dev Machine as \hostpipecom_1 to connect from the Dev Machine to the Test Machine with WinDbg.
The named pipe from the Test Machine (configured in the vmware settings) creates the named pipe from the virtual machine to the host machine, so I need to connect from the dev machine to the host machine as well to reach the named pipe.
I haven’t been able to get VisualDDK to work yet in this setup, and according to your reply, it will never work?
Will this setup get supported in the future?

[Author]

Posts