File System Boot Process

Other versions of this page are also available for the following:

• Windows Embedded CE 6.0 R3

8/28/2008

After the kernel starts the Filesys.dll process, Filesys.dll must initialize its state before the kernel finishes its initialization. The kernel must wait because it is dependent on the registry, which is initialized by Filesys.dll. The following steps show the boot process for Filesys.dll.

1. Filesys.dll detects whether this is a cold or warm boot.
   For a cold boot, the object store memory is initialized and then mapped for Filesys.dll. For a warm boot, memory is not initialized before being mapped for Filesys.dll.
2. Filesys.dll loads the OEM Certification DLL from ROM.
3. If a cold boot is required on a system that had previously warm booted, Filesys.dll calls the OEM adaptation layer (OAL) function pNotifyForceCleanboot.
4. For a cold boot, Filesys.dll initializes the real-time clock by calling the OEMIoControl function with the IOCTL_HAL_INIT_RTC I/O control.
5. Filesys.dll initializes the following APIs in the order listed:
   • Database APIs
   • File system APIs
   • Point-to-point message queue APIs
   • Event log APIs
   • Registry APIs
     For a cold boot, Filesys.dll initializes the registry data. The data initialization process varies, depending on whether the RAM-based or hive-based registry is in use.
     If a default user profile is specified in the registry, Filesys.dll loads the default user profile and initializes data under HKEY_CURRENT_USER.
6. If Device.dll is not started and HKEY_LOCAL_MACHINE\System\StorageManager points to a DLL that can be loaded, Filesys.dll loads Storage Manager.
   If Storage Manager is loaded, Filesys.dll creates a thread to initialize it. The thread exits when it is completed.
7. Filesys.dll initializes national language support (NLS) data.
8. For a clean boot, Filesys.dll reviews the Initobj.dat file and copies files from ROM into the root file system.
9. Filesys.dll initializes the time zone and sets daylight saving time (DST), if necessary.
10. For a cold boot, Filesys.dll sets the locale to use with the database engine by calling the CeChangeDatabaseLCID (EDB) for EDB databases**, or CeChangeDatabaseLCID (CEDB) for CEDB databases**.
    In addition, for a cold boot, Filesys.dll populates the object store databases by loading data from the Initdb.ini file.
11. Filesys.dll communicates to the kernel that Filesys.dll is ready. Filesys.dll then waits for the kernel to signal that Filesys.dll can boot the rest of the OS.
12. Filesys.dll creates named events for all event names in the HKEY_LOCAL_MACHINE\System\Events registry location. These events are set by the processes that own them. For more information, see Ready-Event Registration.
13. Filesys.dll runs the applications listed in HKEY_LOCAL_MACHINE\Init.
    If Device.dll is located in HKEY_LOCAL_MACHINE\Init and has already started, Filesys.dll opens the SYSTEM/BOOTPHASE2 event and signals Device.dll.
    This action enables Device.dll to reread the registry and perform the final driver initialization phase. Any driver can also wait for the same event, to be notified when the real registry comes online. By doing so, the driver can reread registry data, if necessary.

During a normal boot process, Filesys.dll and other components create a number of files and store them in user storage. These files can use as much as 1.8 MB of available user storage.

Files Created on Boot

The following table provides descriptions of files that are normally created in the process of initialization and cold boot.

All paths in the Location column of the following table are provided relative to the persistent storage root on the device.

See Also

Concepts

Hive-based Registry Setup
OAL Initialization of RAM-based Registry
Hive-based Registry Initialization

Other Resources

File Systems
Nk.exe Boot Process