Hi all,

I am using VisualDDK to debug Storage Driver on another machine through COM port.
I have came up with the following question and problems I ran into:

1. When debug starts, sometimes I see debug asserts !m_bNextEvent.., especially AFTER the first attempt to debug, i.e. when the session is already created.
2. When I change the driver, obviously I need symbols to get reloaded and the session recreated, but that doesn’t happen and as the result the debugging through sources doesn’t work, is this normal ? The only known solution is to restart VS… I need it to reconnect and reload symbols
3. How can I find / enable VisualDDK console ? Windows XP SP3 and VS2008
4. The driver package I am trying to debug contains 3 files, is there a way to re-install such a package properly ? only active project is copied and the installation doesn’t really reload the driver because debugging (PBD changed) doesn’t work and I have to do this thing manually (through devcon – full remove and reinstall) anyway. Any advises on how can I at least properly reinstall the driver ? BTW, I was NOT able to properly REINSTALL the test driver compiled from project generated by VisualDDK.
5. When I reinstall / remove the driver on test machine, the debugging doesn’t work or VS instance hangs ( I see bunch of asserts )
6. Is there any VisualDDK project macroses available (sort of $(ProjectDir) ) ? Precisely is there a way to use macroses instead of absolute paths for test machine temporary folder (wizard parameters) ?
7. Looks like VisualDDK debugging works slower than WinDbg through the same COM connection… is it normal ?

Please help if you have any advises…