{"id":75,"date":"2006-12-12T20:41:08","date_gmt":"2006-12-12T20:41:08","guid":{"rendered":"https:\/\/driverentry.com.br\/en\/2006\/12\/12\/wow-ddkbuild-out-of-vista\/"},"modified":"2026-07-24T19:17:50","modified_gmt":"2026-07-24T19:17:50","slug":"wow-ddkbuild-out-of-vista","status":"publish","type":"post","link":"https:\/\/driverentry.com.br\/en\/2006\/12\/12\/wow-ddkbuild-out-of-vista\/","title":{"rendered":"Wow!! DDKBuild out of Vista"},"content":{"rendered":"
\"\"<\/a><\/div>\n

\"\"<\/p>\n

About a year ago, I was reading the Windows Internals<\/a> when I came in the chapter about Wow64<\/strong>, so I thought to myself: “Oh my… That’s a sort of thing that will bring us some issues.”<\/em><\/p>\n

This week I’ve installed a Vista x64\u00a0copy on my computer to do some tests and I attempted to anticipate the problems I would have when it would be released. I almost\u00a0had no problems. Actually, I had to configure some shortcuts to certain programs with compatibility mode set to Windows XP SP2.\u00a0This is because these programs showed the message: “This program is not compatible with Windows 6.0”<\/em><\/p>\n

After installing the Visual Studio 2005<\/a>, DDK do Windows 2003 Server<\/a> and DDKBuild<\/a>, everything was working fine.\u00a0A project was created, compiled and debugged in Visual Studio without problems. I also compiled a DDK\u00a0example from the command line and also everything was OK.\u00a0But at the time I was compiling one of the examples that I’ve already made available at the site using DDKBuild, I got the following error message:<\/p>\n

\n
'ddkbuild' is not recognized as an internal or external command<\/pre>\n<\/div>\n
Executing the DDKBuild in a command prompt, it worked fine, but same error\u00a0was always showing at the Visual Studio.\u00a0After pooling out some hair, I tried to open the file DDKBuild.cmd from Visual Studio, that is, by selecting Open…<\/strong> from File<\/strong> menu and so on. When I got into the System32 directory, I saw that the file I was looking for was not there as it should be, at least, not for Visual Studio.<\/p>\n
It took some time, but the penny dropped.\u00a0Visual Studio is a 32 bit process and fell in the Wow64<\/strong> (Windows-on-Windows 64)\u00a0rules for File System\u00a0redirection.\u00a0For those who do not know, to maintain compatibility with the past, 64-bit platforms still use the directory C: \\Windows\\System32<\/em> folder to put the system DLLs, even though they were 64-bits.<\/p>\n
But what happens with 32-bit system DLLs? Thirty-two bit processes still need to load these DLLs. When  a 32-bit process tries to access the C:\\Windows\\System32 directory,  the access is redirected by Wow64<\/strong> to C:\\Windows\\SysWow64\u00a0  (C:\\Windows\\System32\\SysWow64 For Windows XP x64). Accesses to the registry are also reflected from 32 bits to 64 bits and vice versa. Please, refer to the MSDN<\/a> site for Wow64 <\/strong>details.<\/p>\n
Once the penny has dropped, it is ridiculous to solve the problem. Simply put a copy of DDKBuild.cmd in the C:\\Windows\\SysWow64 and everyone will live happily ever after.<\/p>\n","protected":false},"excerpt":{"rendered":"
About a year ago, I was reading the Windows Internals when I came in the chapter about Wow64, so I thought to myself: “Oh my… That’s a sort of thing that will bring us some issues.” This week I’ve installed a Vista x64\u00a0copy on my computer to do some tests and I attempted to anticipate […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"pagelayer_contact_templates":[],"_pagelayer_content":"","footnotes":""},"categories":[1],"tags":[],"class_list":["post-75","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/driverentry.com.br\/en\/wp-json\/wp\/v2\/posts\/75","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/driverentry.com.br\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/driverentry.com.br\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/driverentry.com.br\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/driverentry.com.br\/en\/wp-json\/wp\/v2\/comments?post=75"}],"version-history":[{"count":1,"href":"https:\/\/driverentry.com.br\/en\/wp-json\/wp\/v2\/posts\/75\/revisions"}],"predecessor-version":[{"id":76,"href":"https:\/\/driverentry.com.br\/en\/wp-json\/wp\/v2\/posts\/75\/revisions\/76"}],"wp:attachment":[{"href":"https:\/\/driverentry.com.br\/en\/wp-json\/wp\/v2\/media?parent=75"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/driverentry.com.br\/en\/wp-json\/wp\/v2\/categories?post=75"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/driverentry.com.br\/en\/wp-json\/wp\/v2\/tags?post=75"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}