This newsletter contains archived content. No warranty is made as to technical accuracy of content or currency of URLs.
The WHQL & Logo Newsletter provides up to date information about WHQL hardware testing issues/submissions and the Windows Logo Program. Did you get this newsletter from a friend? Subscribe to the WHQL Newsletter.
Top Story
Best Practices For Logo Testing -- Avoiding Test Failures
The Microsoft Logo and CSS teams would like to offer these recommendations and proactive steps to avoid logo test failure. Please follow these steps to improve your logo testing.
Avoid these common issues:
- Do not change the client hardware during setup unless advised.
- Before starting another submission using the same client on another OS, complete the submission, make the client unsafe, and uninstall the client.
- Launch all tests intended for logo through the device console submission view.
- Select a device if required, make sure the driver is loaded on the client, and load the INF through the device console.
- Check submission and test status through the DTM submission status window or the DTM log viewer after a test or submission completes.
- Avoid generic VGA drivers for video and other old or de-featured drivers; load advised system bios and drivers.
- Do not change the AutoLogon settings on the client.
- Do not use the job monitor rerun option.
- Do not alter or change jobs in the database.
- Do not place errata numbers in the Readme without getting them directly from Microsoft.
Take these proactive steps after setup:
Download the latest errata update for your controller from Winqual.
- Uncheck the default Startup/Shutdown OS option on the DTM client to reboot on system crash. This will make a system crash more obvious. Do not follow this step before running the Crashdump test if required for storage testing.
- Review the DTM maintenance best practices.
Windows Logo Program for Hardware -- Logo License Agreement 10.0
The New Designed for Windows Logo License Agreement 10.0 is now posted on Winqual and ready for signing. This document replaces the Designed for Windows Logo License Agreement 9.3 which is no longer available. There were several changes made to the new version 10.0, including removal of the Capable Logo Program language, a simplified format, including a new separate style specification guide which includes additional details for ultra-mobile PC and ultra-portable PC form factor specifications.
Please refer to Winqual (scroll to Helpful Links, then select Legal Agreements) for the new DFWLLA 10.0 and the new logo style guide. Please sign version 10.0 now if your agreement is expiring or if you are new to the Windows Logo Program.
VeriSign Organizational Certificate Enrollment
With the latest Winqual deployment (scheduled for July 17, 2007), links to Organizational Certificates now point to an updated enrollment site on VeriSign.com. Purchasers of the VeriSign Organizational Certificate from this updated enrollment site will have to install a root certificate on their machines in order to digitally sign their files properly. In addition, a new signing tool (signtool.exe) has replaced the previous tool (signcode.exe). Note that signtool.exe is available as part of the WDK and that signcode.exe is no longer supported by Microsoft.
- Download the WDK and signtool.exe along with many other useful code-signing tools by starting here.
- Check Help under Introduction > FAQ > Digital Certificate > Code-sign files with your VeriSign ID for instructions on how to sign code using signtool.exe.
|
