Just had this “mysterious” case of DDKBUILD not properly working. I could swear everything worked fine before, but the unconscious creation of a script named build.cmd would take precedence over the build utility from the DDK. Now batch and NT scripts have this peculiar feature that scripts called from within scripts without using the call command will actually swallow the rest of the “parent” script, because the child script will never return. Anyway, mystery solved.
Hint: never put a file named foo.cmd into your local folder if you’re going to execute a script which relies on foo (e.g. as foo.exe) from within that folder.
// Oliver