INF ClassInstall32.Services Section
[ClassInstall32.Services] | [ClassInstall32.nt.Services] | [ClassInstall32.ntx86.Services] | [ClassInstall32.ntia64.Services] | (Windows XP and later versions of Windows) [ClassInstall32.ntamd64.Services] (Windows XP and later versions of Windows) AddService=ServiceName,[flags],service-install-section [,event-log-install-section[,[EventLogType][,EventName]]]... [DelService=ServiceName[,[flags][,[EventLogType][,EventName]]]...] [Include=filename.inf[,filename2.inf]...] [Needs=inf-section-name[,inf-section-name]...]
A ClassInstall32 section installs a new device setup class (and possibly a class installer) for devices in the new class.
Starting with Windows 2000, each ClassInstall32.Services section contains one or more INF AddService directives that reference additional INF-writer-defined sections in an INF file.
INF files typically use the ClassInstall32.Services section with at least one AddService directive to control how and when the services of a particular device class are loaded, any dependencies it might have on other services, and so forth. Optionally, they can also set up event-logging services for the device class.
This directive references an INF-writer-defined service-install-section and, possibly, an event-log-install-section elsewhere in the INF file for the drivers of the device class covered by the ClassInstall32 section. For more information, see INF AddService Directive.
This directive removes a previously installed service from the target computer. This directive is very rarely used. For more information, see INF DelService Directive.
This optional entry specifies one or more additional system-supplied named INF files that contain sections needed to install this device class. If this entry is specified, usually so is a Needs entry.
For more information about the Include entry and restrictions on its use, see Specifying the Source and Target Locations for Device Files.
This optional entry specifies the particular named section that must be processed during the installation of this device class. Typically, such a named section is an ClassInstall32.Services section within a system-supplied INF file that is listed in an Include entry. However, it can be any section that is referenced within such a ClassInstall32.Services section.
Needs entries cannot be nested. (For more information about the Needs entry and restrictions on its use, see Specifying the Source and Target Locations for Device Files).
ClassInstall32.Services sections should have the same platform and operating system decorations as their related ClassInstall32 sections. For example, a ClassInstall32.ntx86 section would have a corresponding ClassInstall32.ntx86.Services section.
The case-insensitive .nt, .ntx86, .ntia64, and .ntamd64 extensions can be inserted into a ClassInstall32.Services section name in cross-platform INF files, as shown in the formal syntax statement. For more information, see Creating INF Files for Multiple Platforms and Operating Systems.