Does not work with WDK 7600.16385.1

Sysprogs forums › Forums › VisualDDK/VirtualKD discussion › Does not work with WDK 7600.16385.1

Log In Register Lost Password
Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • July 8, 2010 at 16:53 #208
    Anonymous
    Participant

    Does not work with WDK 7600.16385.1

    July 8, 2010 at 17:15 #1454
    Anonymous
    Participant

    It looks like recent WDKs unified ntddk.h and is not anymore inside target specific directory. Visual DDK is expecting the wrong path for ntddk.h (wxp, w2k, etc
    ) for these wdk’s

    August 11, 2010 at 22:20 #1455
    Driver N00b
    Participant

    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?

    September 3, 2010 at 11:38 #1456
    Anonymous
    Participant

    I have the same problem. Is there any solution for it? There’ll be version for this WDK?

    October 14, 2010 at 22:14 #1457
    Anonymous
    Participant

    Just mkdir C:WinDDK7600.16385.1incddkwxp and copy ntddk.h into it. Then retry installation

    October 19, 2010 at 20:05 #1458
    Anonymous
    Participant

    @msbroadf wrote:

    Just mkdir C:WinDDK7600.16385.1incddkwxp and copy ntddk.h into it. Then retry installation

    Tried what you suggested – Installer still does not commence. Is visualddk any good at all if I get past the installation issues or is it incompatible with the current WDK anyway?

    November 4, 2010 at 14:57 #1459
    Anonymous
    Participant

    Dunno if this is an issue anymore, but I just declared WDKPATH to C:WinDDK7600.16385.1.
    Then I reconfigured VisualDDK and it all went OK. (I didn’t do any mkdir, just declared the environment variable above)

    (Running Windows 7, x64)

    January 31, 2011 at 10:03 #1460
    Anonymous
    Participant

    hey PLI, thanks for that info… worked like charm…

    May 16, 2011 at 10:54 #1461
    Anonymous
    Participant

    Fixing the WDK path fixed the issue.

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