Please see Windows Driver Kit Version 7 Release Notes for the most recent version of the WDK Release Notes. On This PageTARGETPATH in Sources file not supportedThe Windows 7 Beta build of the Windows Driver Kit (WDK) does not support the use of TARGETPATH in the Sources file. TARGET PATH will be supported in the RC and RTM builds of the WDK. As a workaround for the Beta, comment this line out of your Sources file. Kitsetup has an "Unknown Publisher"When you run Kitsetup.exe from the Windows 7 Beta version of the Windows Driver Kit (WDK), a dialog appears that says Kitsetup.exe is from an unknown publisher. This is a known bug. Kitsetup.exe has a valid signature, which you can examine by looking at the Digital Signatures tab on the Properties dialog box. Selfsign_example.cmd Had an Invalid Path for the Toaster Sample The Toaster sample has moved to a different location and the Selfsign_example.cmd file was not updated with the new location.
Workaround:
To use Selfsign_example.cmd, before you run it, edit the file to replace all occurrences of: %PROJECT_ROOT%\general\toaster\toastpkg\toastcd with %PROJECT_ROOT%\general\toaster\wdm\toastpkg\toastcd Win7 Beta Release WinUSB Co-installerThere is an updated release of the WinUSB co-installers on the WDK Connect Web site. The version of the WinUSB co-installer on the Connect Web site contains several changes since the Windows 7 Beta version for the WDK was published. The co-installer itself will install on all platforms starting with Windows XP. In addition, there are some bug fixes in WinUSB itself. It is a good idea to use the new co-installer to test your drivers for USB devices. If you encounter problems or have questions about the new co-installer, contact Microsoft at WDFINFO@microsoft.com.
Permission Denied Exception During Verification, Which Results in a Tool Error When an antivirus application is running and the driver source code directory is not excluded from a runtime scan, SDV may stop verification with the "Sys_error("slam.bp: Permission denied")" exception.
In addition, when there is simultaneous access of the same file, permission may be denied during the driver verification process. Workaround: Disable the simultaneous access of the driver source code source tree. For example, add the driver verification path in the exclude directories list for the antivirus application.
Installing the Windows SideShow Sample DriverThe instructions in the WDK documentation for installing the Windows SideShow sample driver is incomplete. Workaround: | • | The directory for the sample driver is located at src\sideshow, not src\umdf\sideshow. | | • | The sample driver requires the UMDF 1.9 co-installer (WUDFUpdate_01009.dll). You must copy the co-installer binary to the directory where you put the INF file and driver binary, so that the system can locate the co-installer binary when it installs the sample driver. WUDFUpdate_01009.dll is located at path redist\wdf\x86 under the WDK root directory for x86 (similarly for other architectures). | | • | If you are installing the driver on Windows Vista, the UMDF 1.9 co-installer will update UMDF to version 1.9, if it has not already been done for the computer. If an update is necessary, you must reboot the computer for the driver installation to complete. | | • | In Windows 7, it is no longer possible to manually install a non-PnP device through Device Manager, so the devcon WDK tool must be used to install the sample driver on Windows 7. To do this, follow these steps: 1. | Copy Devcon.exe to the directory where you put the INF file and driver binaries. Devcon.exe is located at path tools\devcon\i386 under the WDK root directory for x86 (similarly for other architectures).
[If you are installing the driver on a computer with the WDK installed, instead of copying the tool, you can run the command line in step 3 in a WDK Build Environment command prompt window that corresponds to the operating system architecture (x86/amd64/ia64).] | 2. | Go to the directory where you copied the INF file and driver binaries. | 3. | Run the following command at the command prompt:
devcon install WindowsSideShowBasicDriver.inf UMB\WindowsSideShowNoDevice |
|
Internal Compiler Error was Encountered when using PREƒast for Drivers (PFD) for Building on Windows Server 2003 or Windows XPWhen using Windows Server 2003 or Windows XP (all SKUs, both 32-bit and 64-bit editions), there is a low probability that PREfast for Drivers (Prefast.exe, PFD) will report an internal compiler error while it processes the build. The rate at which this occurs is very low, and is not reliably reproduced. This issue has been observed when building larger drivers, especially those that use the Windows Driver Framework (WDF) for UMDF and KMDF drivers. When this issue occurs, the added memory overhead that is required by PFD and the size of the driver build will cause the compiler (Cl.exe) to exhaust its allocated heap space. The allocated memory to that instance of Cl.exe can be as high as 1.5 GB. Workaround: Due to the very low frequency of this error, the workaround is to restart the build process when it occurs.
Troubleshooting Static Driver VerifierWhen you run Static Driver Verifier (SDV) on your driver source code, SDV reports Timeouts, GiveUps, or Spaceouts. Workaround: If Static Driver Verifier (SDV) reports Timeouts, GiveUps, or Spaceouts, try the following steps. 1. | Run SDV using the /refine command option. For example: staticdv /refine /rule:*
(The next two steps require changes to the options file, Sdv-defaults.xml. The default file is specific to the driver model and can be found in the \tools\sdv\data\model\ directory, where model is WDM, WDF, or NDIS.) | 2. | If your computer has a multicore processor, reduce the number of threads that are used during verification to 1. In the SDV defaults file, change the value for SDV_SlamConfig_NumberOfTheads to 1. | 3. | If SDV reports timeouts, increase the timeout limit. For example, double the value of SDV_SlamConfig_Timeout to 4000. |
If applying each step alone does not work, try using all of the techniques together.
Note that these techniques increase the actual duration of a run, but they also make it easier for SDV to finish its job with a useful result (Pass or Defect).
| |
