Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
The following table shows the Filesys.exe IOCTLs. Implementing these IOCTLs is optional. Only Filesys.exe should call these IOCTLs.
| Programming element | Description |
|---|---|
| IOCTL_HAL_GET_HIVE_CLEAN_FLAG | This IOCTL queries the OAL about whether the registry hives and user profiles should be deleted and recreated. It is used by Filesys.exe. |
| IOCTL_HAL_GET_HIVE_RAM_REGION | This IOCTL specifies a region of RAM to hold the registry hive instead of using it as a memory-mapped file on a file system. |
| IOCTL_HAL_GETREGSECUREKEYS | This IOCTL extends the list of registry paths that should be protected from non-trusted applications. |
| IOCTL_HAL_INITREGISTRY | This IOCTL signals that the registry is active and that data from the OAL can now be propagated to the registry. It is called by Filesys.exe. |
| IOCTL_HAL_QUERY_FORMAT_PARTITION | This IOCTL indicates whether a specific partition should be formatted when it is mounted. |
| IOCTL_HAL_SAVE_HIVE_RAM_REGION | This IOCTL gives the OEM a chance to copy the registry RAM region to persistent storage while the registry is in a steady state. It is called by Filesys.exe when an application calls RegSaveKey, if the registry hive is stored in a region of RAM specified by the OEM. |
See Also
Send Feedback on this topic to the authors