On chapter 2 page 40, you show a screenshot assigning COM2 to \\.\pipe\pipe2. I had trouble getting the kernel debugger to attach using these settings. It turns out to work fine using COM1.

If you open Device Manager in a Virtual PC system, it only shows COM1. Maybe that's the reason you can't debug using COM2.

Question is, why is the example using COM2?

Thank you for reporting this and I'm glad you found the resolution.

I cannot confirm the problem you are experiencing because my VPC installation (using the latest download from Microsoft) offers two COM ports to each guest. When the kernel debugger is enabled in the guest OS on emulated COM2 ( as it was when the screen shoot has been taken ) you must redirect the same port into a name pipe, to kernel mode debug the VPC.

Because this port has been claimed at boot time by the kernel debugger, it will show in the guest OS as not working properly. If you experience a different scenario, please let us know.

Thanks,