Going nowhere

Sysprogs forums › Forums › VisualDDK/VirtualKD discussion › Going nowhere

Log In Register Lost Password
Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • February 8, 2010 at 17:02 #160
    Waldemar
    Participant

    Hi guys

    Need help as I can’t get this app. to work.

    1. Installed WDK 7600 on 2 machines.
    Both machines also have VS 2008 installed and VisualDDK.

    Working machine: 64 bit Windows 7
    Target machine: 32 bit Windows 7

    2. Connected machines with full rs232 cable.
    Tested with realterm at 115200 with and without any flow control -> all characters come through without any problem.
    So COM1 to COM1 port is working.

    3. Started …VisualDDKtargetx86DDKLaunchMonitor.exe on target machine.
    Firewall: allowed program to connect to local network (machines are on the same network group).

    4. Started VS2008 on working machine.

    5. Created the default test driver… no options were changed at VisualDDK wizard.

    6. Build driver without errors.

    7. Started “Driver Lunch Settings”

    8.
    Selected COM1 for Debugging Connection at 115200.
    Defined IP of the target machine.
    Everything else was left the same.

    9. Lunch ->
    get VisualDDK error MBox: Cannot start debugging. One of the library files needed to run this application cannot be found.

    DDKLaunchMonitor states: Discovery request from 192.168.0.192…

    I’ve also disabled firewalls on both machines and the result is the same.

    So any help?

    Peace
    Waldemar

    February 8, 2010 at 17:21 #1327
    airmax
    Participant

    Does you setup boot in debugging mode using COM port on “Target machine”?

    February 12, 2010 at 17:58 #1326
    Waldemar
    Participant

    1. I’ve tested the connection on COM1 to COM1 and it worked.
    2. I’m currently using WinDbg and Target in Debug mode over COM1 and it works perfectly… well slow as it can get… would like to use VDDK as VisualStudio
    is soooo much better than WinDbg.
    3. For VDDK I’ve tested target in normal operation, so that COM1 port wasn’t used by the system.

    Is there some flag I could use that VDDK would give some more detailed explanation why it doesn’t want to work… to have a logger or anything else?

    Thanks for help.

    Peace
    Waldemar

    February 13, 2010 at 10:28 #1328
    Waldemar
    Participant

    Another thing:

    Before:
    I’ve installed VDDK on target machine and then I’ve tested if it works -> it didn’t.

    Now:
    I’ve found there is another install file in target directory -> started installed… a new boot menu item was created.
    If machine boots with that menu the system crashes 5 seconds into windows initialization.

    So that doesn’t help either.

    Any more ideas?

    Peace
    Waldemar

    June 21, 2011 at 21:23 #1329
    Anonymous
    Participant

    Any resolution?

  • Author
    Posts
Log In Register Lost Password
Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.