[ClassInstall32.Services] |
[ClassInstall32.nt.Services] |
[ClassInstall32.ntx86.Services] |
[ClassInstall32.ntia64.Services]
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]...]
Each ClassInstall32.Services section contains one or more AddService directives referencing additional INF-writer-defined sections in a Windows 2000 or later INF file.
INF files commonly 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 set up event-logging services for the device class as well.
ClassInstall32.Services sections should have the same platform and OS decorations as their related ClassInstall32 sections. For example, a ClassInstall32.ntx86 section would have a corresponding ClassInstall32.ntx86.Services section.
This section is irrelevant to exclusively Windows 9x/Me installations.
Needs entries cannot be nested. (For further information on the Needs entry and restrictions on its use, see Specifying the Source and Target Locations for Device Files).
The case-insensitive .nt, .ntx86, and .ntia64 extensions can be inserted into a ClassInstall32.Services section name in dual-OS and/or cross-platform INF files, as shown in the formal syntax statement. For more information, see Creating INF Files for Multiple Platforms and Operating Systems.
ClassInstall32, AddService, DDInstall, DDInstall.HW, DelService, Models