Appendix E: Revision History
Summary of changes from version 1.0 to version 1.0a
- Updated intro Welcome section
- Added exemption to win.ini requirement for applications that must support 16-bit code
- Clarified long file names requirement. Exemptions may be allowed for certain characters in some cases; long file names must support lengths to MAX_PATH. Added language regarding double byte language versions
- Updated long printer names requirement: Windows 2000 and Windows NT support long printer names up to 220 characters
- Added language regarding double byte language versions.
- Updated pre-test steps for using Driver Verifier to reflect changes in UI between Beta 3 and final code
- Renamed "Install/Uninstall" chapter to "Windows Installer Service"
- Clarified that advertising requirement is only for app-level on-demand install. On demand install at feature level is not required; also updated which datafields are required for advertising: Only shortcut, extensions, icon, and verb
- Clarified the "Classify and store application data correctly" requirement: Applications must not store more than 128K across HKCU and HKLM at install time (HKCR is excluded)
- Compliance with this system metric is no longer required: SPI_GETCARETWIDTH
- Clarified the multiple monitor requirement for images that span monitors
- Updated the requirement: "Adhere to system-level Group Policy settings" as follows:
- Updated the registry information for the following policy: "Do not keep history of recently open documents" (the correct value is NoRecentDocsHistory)
- Updated the policy name: "Remove Common Dialog MRU dropdown" is now "Hide the dropdown list of recent files"
- For the policy "Run Only Allowed Windows applications," removed the following clause (this does not apply when launching applications via OLE/COM/DCOM).
- Clarified that SHFOLDER.DLL is installed by the MSI redistributable
- Updated OnNow requirements:
- Clarified Requirement 6.1, regarding usage of SetThreadExecutationState to indicate busy status; also corrected language on use of ES_CONTINUOUS flag
- Handling sleep and wake notifications was expanded to consider connected vs non-connected state
- Clarified that apps must allow sleep in the "non-connected" state; this includes when files are being used offline via Client Side Caching
- Clarified acceptable behavior for when in the "connected" state
- Clarified the language in Requirement 6.4: "Handle wake from normal sleep without losing data"
- Clarified the requirement to recover from critical sleep
- Corrected bug in Terminal Services Best Practice: The correct flag to append to names of objects is \\GLOBAL
- Added Appendix B "Product Distribution Issues"
- Added Appendix C "Development Tools"
- Added Appendix D "International and Localized Versions"
- Updated references and URLs throughout the Specification