However, no system-start driver is loaded until after all boot drivers have been loaded. These load order groups are described in detail in Load Order Groups for File System Filter Drivers.ĭriver whose start type is SERVICE_SYSTEM_START are also loaded in the order of the load order groups to which they belong. On Microsoft Windows XP and later systems, filters that are boot drivers generally belong to one of the FSFilter load order groups. On Microsoft Windows 2000 and earlier systems, most filters that are boot drivers belong to the "filter" group. Within the SERVICE_BOOT_START and SERVICE_SYSTEM_START start types, the relative order in which drivers are loaded is specified by each driver's load order group.ĭrivers whose start type is SERVICE_BOOT_START are called boot (or boot-start) drivers. This method is described in the reference entries for CreateService and ChangeServiceConfig in the Microsoft Windows SDK documentation. This method is described in the ServiceInstall Section of Creating an INF file for a filter driver.īy passing the desired start type for the dwStartType parameter when calling CreateService or ChangeServiceConfig from a user-mode installation program. Specifying start typeĪ driver writer can specify the start type for a driver at installation time in either of the following ways:īy specifying the desired start type for the StartType entry in the service-install-section referred to by an AddService directive in the driver's INF file. Within each start type category, the load order group determines when file system filter drivers (and legacy filter drivers) will be loaded. Also used to temporarily disable a driver during debugging.Īll drivers that specify a start type of SERVICE_BOOT_START will be loaded before drivers with a start type of SERVICE_SYSTEM_START or SERVICE_AUTO_START. Such file systems include CDFS, EFS, FastFat, NTFS, and UDFS. Used by file systems that are loaded by a file system recognizer (except when they are the boot file system) or (in the case of EFS) by another file system. Indicates a driver that is not started by the OS loader, Service Control Manager, or PnP Manager. Indicates a driver started on demand, either by the PnP Manager (for device drivers) or by the Service Control Manager (for file systems and file system filter drivers). Indicates a driver started by the Service Control Manager during system startup. This start type is also used by device drivers for PnP devices that are enumerated during system initialization but not required to load the system. Except for the file systems listed below under "SERVICE_DISABLED," file systems (including network file system components) commonly use this start type or SERVICE_DEMAND_START. This start type is used by the file system recognizer. Indicates a driver started during OS initialization. Legacy file system filters must use this start type see file system filter load order groups for more information. File system filter drivers commonly use this start type or SERVICE_DEMAND_START. Indicates a driver started by the operating system (OS) loader. There are five possible start types: Start Type Driver start typesĪ kernel-mode driver's start type specifies whether the driver is to be loaded during or after system startup. Note that a "minifilter" filter driver can be loaded at any time.īefore exploring when and how file system filter drivers are loaded during the system boot sequence, it is necessary to understand driver start types and load order groups. The concept of load order groups is required by file system filter drivers for interoperability with legacy file system filter drivers. The load order groups for file system filter drivers that are loaded at system startup.The driver's start type, where each start type represents phases of booting a system.The Windows operating system loads file system filter drivers based on:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |