For the application's Design XP Design Logo "Designed for Microsoft Windows XP" application technical specifications for application technical requirements to help vast manufacturers have qualified for the "Designed for Microsoft Windows XP" logo. The following content provides a summary summary of the key technical requirements for the application "Designed for Windows XP" logo plan. table of Contents:
1.0 Windows Basics: Technical Requirements Summary 2.0 Installation / Delete: Technical Requirements Summary 3.0 Data and Setup Management: Technical Requirements Summary See also Reference: Supplementary Guidelines provided by recommendations and future technical requirements Download Resources: Designed for Microsoft Windows XP Design Applications Technical Specifications 1.0 Windows Basics: Technical Requirements Abstract Through customers can believe that products that meet the logo plan technical requirements will be operating normally on Microsoft® Windows® XP and will not have a negative impact on operating system reliability. Performing the main function and maintaining a stability application must perform primary functional characteristics without the cost of sacrificing the operating system or its own stability. All kernel mode drivers installed by the application must pass the Kernel Mode driver that is crude-based on the Verification of the Windows XP platform is often a hidden danger that causes the system crash. In view of this, any application containing the kernel mode driver (such as backup, copy protection, and CD burning) must accept a comprehensive technical test to ensure that the above risks are minimized - this is critical. If the application contains a kernel mode driver, each driver included in the application must be verified by technical validation executed by the Windows Driver Verifier Manager (Verifier.exe) tool (VERIFIER.EXE). That is, Driver Verifier does not report any stop error messages during the run, otherwise it means that there is a hidden danger that may result in system unstable. You have a responsibility to make sure that all components submitted with the application are in line with the above requirements. All devices or filter drivers included in the application must pass through the Windows HCT. If the product you submits If the product contains a hardware device driver or filter driver, you must ensure that these drivers are passed by Windows Hardware Compatibility Test (Windows Hardware) Compatibility Test, HCT) 10.0 or higher. For a particular type of driver, Windows XP will make an alert to the end user without having a Microsoft digital signature driver attempting to install a Microsoft Digital Signature. For any driver type that requires a digital signature, its components must obtain digital signatures granted by Microsoft. You should make sure that all components submitted with the application are in line with the above requirements. Correctly performing a Windows version detection application must be verified on the case where the relevant operating system meets its minimum version. The app must also be installed and run on all Windows subsequent versions. In some particular circumstances, it is acceptable to prevent the application from installing the following upsessment. If you decide to do this, you must prompt users while blocking the installation or execution process, the relevant application is not prompted to the user for the relevant applications of the Windows subsequent version. Supporting Fast User Switching Features In Windows XP, fast user handover features will allow multiple users of the same computer to have their own configuration scenarios, and can implement interchangements in their current workspace without performing logout operations. Each manufacturer must ensure that the relevant application does not have a loss of system crashes or data (or settings) when the customer uses FAST User Switching features. For example, if the first user is using a editing application, and the second user also launches the editing application, then it is necessary to ensure that the first instance of the application will neither close the program. The editing content of the first user will not be lost. On the basis of meeting the requirements made by the data and setting management, your application is unlikely to have fault issues related to fast user switching characteristics.
Of course, it should be excluded from the conflicts that may occur between the shared resources such as CD drivers, printers, modems, and sound cards. If additional instances running by different users can cause failure of the primary function, you must re-modify the product design to ensure that the occurrence of similar situations. When a feature is disabled in order to prevent fast users from switching failure, the relevant application must inform the user to do so. Supporting the latest visual style If the application is lost in the case where the user selects some of the latest visual style, you will have to disable the relevant visual style for the application. Since applications with full-screen graphics modes generally do not have a negative impact on the modified visual style in Windows, this product does not need to perform special processing for such applications for satisfying the above requirements. Support Task Switching is neither the application to mask Alt Tab, Ctrl Alt Del, and other task handover functions, nor allowing applications to disable the above mechanism in any way. 2.0 Installation / Delete: Technical Requirements Summary Customers can believe that the product you develop will not have a negative impact on the operating system or other applications when installing to the Windows XP platform. Do not try to perform a replacement operation application for files that are protected by Windows file protection, no replacement operations are performed on files protected by Windows File Protection (WFP) feature. To avoid the related application trigger the WFP, the program should call the sfcisfileprotected function when installing any files created by it yourself. Windows Installer (Windows Installer) service will perform the above processing in an automated manner. Windows file protection is a Windows XP feature that prevents replacement of the necessary system files without authorization. The WFP will run on Windows XP as a background processing process and monitor specific files. When the WFP detects that a protected file has been replaced, it will return to the initial state. Protection documents mainly include the following documents sold with WINDOWS XP products CD:: Most .sys, .dll, .exe and .ocx files. The following font file: micross.ttf, tahoma.ttf, tahomabd.ttf, dosapp.fon, fixedsys.fon, modern.fon, script.fon, and VgaOem.fon. If the relevant application requires an updated version of the above components, you must update the above components by using the Microsoft service package responsible for installing the required version. Early versions from Windows must be able to ensure that the operating system can still function properly in the case of upgrading the operating system from Windows 98, Windows ME, Windows NT® or Windows 2000 to Windows XP. We strongly recommend that the relevant applications can achieve the above requirements without performing uninstallation or reinstallation. If the application you have developed requires a Windows version dedicated code (such as kernel mode drivers and VXD, you must ensure that users can get a corresponding solution by downloading or retrieving the operating system to Windows subsequent versions. .
Applications must not have crash or data loss in the case where the operating system is upgraded to the latest version. The solution must be available for free. The implementation process of the solution must not contain any professional technical operations. Instead, it must be used and face end users. For example, the solution must not be required to modify the registry item or INI setting. To meet the above requirements, related applications must have the ability to make dynamic responses for operating system changes at runtime. Many applications are detected on the Windows version during the installation process and determine the components required to install on this basis. This usually means that the installed application has a targeted system and will not function properly when the system is upgraded to Windows. Applications only need to be migrated from its supported Windows version. For example, if the application cannot be installed in Windows 98 or Windows Me, then there is no need to implement migration from these two versions. Do not rewrite the installation of non-private file applications with earlier versions must perform the detection operation correctly to ensure that the latest file versions are installed. The installation operation of the application must not cause the file it created or is not created by it, and the file shared by other applications retracted to the older version. Do not prompt the user to upgrade unless the version upgrade must be executed. The correct file version information will make you good benefits, including the requirements of "rewriting files without early version" more easily. Corresponding to this is that all executable images you distribute must contain valid file versions. When you display or get an executable (such as EXE, DLL, OCX, and CPL, etc.) properties, you must make sure it contains an accurate product name), the company name and file version avoids unnecessary restart to require extreme in Windows XP There is less information to reboot the system. Restart is a welcome from our customers, in some cases, even possible to become an obstacle for application deployment. The application must not be requested or suggested that the user performs system restart during the installation process or after the installation is completed. The following is required to perform system restart: Windows Service Pack (Windows Service Pack) or Authorized System Replies The function can be restarted. Graphical Identification and Authentication (Graphical Identification and Validation, Gina) Dynamic Link Library The installation requires the system restart. Gina is a replaceable DLL component loaded by Winlogon. GINA is mainly used to implement the verification strategy of interactive login mode, and is expected to perform all identification and verify user interaction. For example, replacing the Gina DLL will be used to implement smart cards, retinal scans and other authentication mechanisms that can replace standard Windows XP user names and password verification methods. No need to perform system restart:
DLL registration. Update service components. If necessary, you must prompt to the user, and the specific service will be terminated during the update. Replace existing files for applications. You must provide users with information related to the application that has been implemented with the required update resource files, and is still open, so that the user is to close the file and perform file replacement operations without system restart. In addition, for many components, in order to avoid this, you should perform it in a side by side, or use the MoveFileEx with the "Delay to Restart" option. If you really need to execute the system reboot, you must provide the user to postpone the selection of the execution of the restart. Installing to the Program Files directory in the default, you must install an application to a suitable subdirectory for storing the current user program file.
If you do not use Windows Installer (Windows Installer), it is recommended that you use the SHGETFolderPath API to return the string represented by the csidl_program_files value. In an English version of the system, the folder path is usually "c: / program files". However, even in English systems, don't move hard sleeve on the path, because it does not have versatility. If you do not use a Windows installer, it is recommended that you use the SHGETFolderPath API to retrieve strings represented by CSIDL_PROGRAM_FILES values. In English systems, this folder path is usually c: / program files. However, even in English systems, don't move hard sleeve on the path because it does not have versatility. If you are upgrading a pre-installed version of an application, the folder where the existing version is located is the default path. And if you have developed without performing the installation process (you can do it without installing any files to the relevant system), you don't have to apply the above technical requirements. Installing non-side Side shared files to the correct location Windows-based application-dependent data for code, applications, components in the registry, application-specific data in the file system, and Windows API that can reveal global namespace Sharing. The shared feature allows for high efficiency of limited hardware resources, and reduces the exposure front end that must accept the Quality Assurance group test. Of course, there is still cost costs that need to be worked. The shared feature will result in the relationship between the application, thereby forming the weakness of the system. Under extreme conditions, the original operation of the original operation will be inexplicably functional or even run. In a typical case, the application mainly depends on special versions or implementations of shared components. If the shared component is upgraded (or dropped) due to the installation of other applications, the previous application will be destroyed. Windows XP, Windows 2000, Windows 98 SECOND Edition and Windows ME provide side by side to minimize the above application weakness. Squainable shared features will allow multiple versions of the same Win32® component to run simultaneously in system memory. This means that the application will be used for specific components as its design and test benchmarks; this is not affected even if other applications require different versions of the same components, they will not be affected. This will enable developers to create more reliability applications, which is the main reason that developers can choose from the components required to use without considering other application requirements on the same system. The appropriate location of non-complicated shared components depends primarily on whether these components are shared across enterprise methods:
A exclusive single software vendor must be installed in one of the following locations: General File Directory or Publisher Directory under the PROGRAM Files folder. Please do not store these files in the System directory. The new control panel object must be installed in the application directory of Windows XP. The service function and device driver must be placed in the system directory. Non-side OCX and DLL shared by multiple software vendors should be placed in the System directory to ensure backward compatibility for related applications. Provides appropriate support applications to "Add or Remove Programs" must provide information such as product name and uninstall program location to enable the "Add or Remove Programs" in the control panel to obtain information related to the application as needed. You can write this information directly to the registry during the installation process, or in the case of the installation system based on Windows Installer (Windows Installer) service, by providing a software package based on Windows Installer (Windows Installer) Related properties are set to these values. The above requirements do not apply to applications that do not have to perform installation - that is, such applications can be saved in the system without installing components, writing registry, modifying system settings or will save any files outside of the user to generate files in the system. Under the premise, it realizes the normal operation. The application's uninstaller must be able to remove this application correctly and comprehensively from the system. Support "All User" installation mode applications tend to be used by multiple users on the same computer. The installer you develop must be set to "all users" mode in the default state, or "all users" methods are provided as a installation option. For example, a setup program may be set to install an application only for current users in a default, but the application must also provide options for all users. Users who do not have special permissions may also try to install the relevant applications. If the restricted user cannot install the application or to perform the installation for "all users", the installer must also perform the downgrade operation properly. AUTORUN (Auto Run) feature supporting CD and DVDs For applications that are sold through CD, DVD, or other removable media and support autorun feature, the relevant application must be able to Start using Autorun (Auto Run) feature, or prompts the user to perform the installation process. In the case where the application is sold in multi-disk, subsequent discs must also have the ability to continue running the installation process after the drive is inserted into the drive or continues to run the installation process without prompting the user buttons and performing other operations. The user is not allowed to start the application installation process from the CD or DVD by clicking "Start" / "Run" in order. After the application is successfully installed, the action of re-inserting the drive will not cause the installer to start again, but allow the installation option to update or modify whether to update or modify the user. 3.0 Data and Setup Management: Technical Requirements Summary Windows XP is equipped with an infrastructure that provides relevant support for user data, user settings, and computer setting status separation. Applications that properly use this infrastructure will provide you with the following benefits:
The application does not have a malfunction in the event of a Limited Users (restricted user, non-administrator) to ensure that family members or friends can share computers in a simple and secure way. Parents can allow children to use computers without having to grant management priority to their children, thereby avoiding infinite access necessary to modify computer settings. Users can perform backup operations for personal documents without having to back up applications or operating system files. Multiple users can share a single computer and have their respective preferences and settings, respectively.
Allow multi-family members to share the same computer and help to achieve fast user switching characteristics. Implement the operations related to business activities (such as roaming and offline storage) and provide security for the operating system and its applications. Make sure the consistency of user data, abstract storage location, and separate the application data in units of users. Composition factors that make up the application remote call. Properly dealing with "Deny Access" situation on the Window XP operating system platform, default, restricted user accounts (such as the Limited User (restricted user) on Windows XP Home Edition) cannot be in each unit such as HKLM and Windows directories. Writing is performed at a location owned by a computer. Only those applications that can correctly classify and store data can avoid denial of access errors and run in a secure environment. However, there are also some applications that can correctly classify and store data to refuse access to errors. Supporting applications supporting identity by restricted users should not require users to have free access (such as Administrator permissions) to modify system or other files and settings. In other words, the application must work normally in a secure Windows environment. Compliance with the original technical requirements will help ensure that the application meets this technical requirements. Applications that do not have installation (no need to install any components can be implemented) still need to support restricted users. A secure Windows environment is defined as an environment that is exposed to a restricted user (non-administrator) on a new installed NTFS system. In this environment, users can only perform write operations at a particular location of the local computer:
Their own registry section (HKEY_CURRENT_USER) their own user profile directory (HKEY_CURRENT_USER) Shared document location (csidl_common_documents) User created files created in the system drive root directory, default, using these folders, not Comply with other technical requirements of this part. The user can also perform a write operation in the sub-bile and subdirectory of these locations. For example, since csid1_personal (My Documents) is a subdirectory of CSIDL_PROFILE, the user can write it. For the rest of the system, users are read-only access. The secondary feature allows malfunctions when the main feature of the application can be successfully run by non-privileged users. These secondary features must not be installed by the default mode (e.g., minimizing installation or typical installation) except the fully installed, and may not be an important part of the program operation. Examples of this secondary feature include components that support the original file format. Restricted users cannot perform system management functions such as disk defragmentation, backup / recovery, and modify system time. When most of the major features of the application are system management, the application must be able to run through the Limited User account and inform users why he cannot use any features.
