INF DefaultInstall.Services Section
Note If you are building a universal or mobile driver package, this section is not valid. See Using a Universal INF File.
A DefaultInstall.Services section contains one or more AddService directives referencing additional INF-writer-defined sections in an INF file. This section is equivalent to the INF DDInstall.Services section, and is used in association with an INF DefaultInstall section.
[DefaultInstall.Services] | [DefaultInstall.nt.Services] | [DefaultInstall.ntx86.Services] | [DefaultInstall.ntia64.Services] | (Windows XP and later versions of Windows) [DefaultInstall.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]...]
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 devices covered by this DefaultInstall section.
For more information, see INF AddService Directive.
For more information, see INF DelService Directive.
This optional entry specifies one or more additional system-supplied INF files that contain sections needed to install this device. 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. Typically, such a named section is a DDInstall.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 DDInstall.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.
The AddService directive controls how and when the services of a particular driver are loaded, any dependencies on other services or on underlying (legacy) drivers it might have, and so forth. Optionally, it can set up event-logging services for the driver as well.
DefaultInstall.Services sections should have the same platform and operating system decorations as their related DefaultInstall sections. For example, a DefaultInstall.ntx86 section would have a corresponding DefaultInstall.ntx86.Services section. For more information about how to use the system-defined .nt, .ntx86, .ntia64, and .ntamd64 extensions, see Creating INF Files for Multiple Platforms and Operating Systems.
See the examples provided for the INF DDInstall.Services section.