[Driver N00b]

SOLUTION
OK all working now.
Thanks to the previous New By as i think this was what you were trying to tell me although it was not obvious to me.

1. You must WAIT at the OS Boot menu.
2. Then you can start the VisualDDK launcher on the Visual Studio side.
3. Then you can select the Virtual Machine. (you cannot do this until the VM is running, but you cannot boot the VM completely. You must wait at the boot menu.
4. Then Launch the DDK Launcher from VS.
5. Then select the Boot menu item for kernel debugging.
6. You will get errors while the kernel debugger looks for the kernel connection but at some point it will connect.
7. Then you can debug the driver. Everything starts working.
After you have connected you can stop and start the debug sessions and start new projects without rebooting the VM each time.

Thanks

[Driver N00b]

I am having issues here also, not with paths, but with connecting to virtual machine kernel. see http://forum.sysprogs.org/viewtopic.php?f=4&t=523
Did you manage to get everything going in the end?

[Driver N00b]

Thanks for your response, Can i break down your suggestions just to make sure i understand?

At the screen where you can select which ‘os’ you want to load (before windows loads), you should start the debugging. I assume you mean the VM XP pro. Yes i am selecting the [VirtualKD] when i start the OS? Or do you mean i need to start debugging mode on my x64 Windows 7 host?

You will see the window ‘Connecting to kernel debugging session…’ open with all fails calls. I do not see this, where am i meant to be seeing this?

Then you should select the ‘Microsoft Windows XP Professional [VirtualKD]’ at the ‘os’ selection window so windows starts. Not sure, you have mentioned this above. I am debugging from a real x64 Windows 7 box trying to debug a virtual machine kernel. Maybe you assume i am going from VM to VM.

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.
I understand i need the DDK Launch Monitor to be running to install the driver interactively, but i cant even connect to the kernel from the VisualDDK launcher.

I have x64 Windows 7, Visual Studio 2008 with VisualDDK installed.
I have installed the DDKLaunchMonitor on the VM target and are just trying to follow the quick start guide, step by step to just get a basic connection to the targets kernel. But im not getting that far. I can however use the VMMon.exe using windows KD.EXE command line debugger to connect to the kernel. But this is not ideal.
Im sure if i can get that working, i can get the visual environment working also.

[Author]

Posts