TRUE indicates success. FALSE indicates failure.

An FSD must be able to handle redundant calls to this function. It must determine from the media itself, not the value of hdsk,whether the disk is already mounted. This is required because the user media can have been removed or changed slots while the system was turned off. The value of hdskhas meaning only to FSDMGR functions, not to an FSD.

Use the FSDMGR_ReadDiskand the FSDMGR_WriteDiskfunctions for all I/O to the mounted disk.

A definition (.def) file for MyFSD.dll must export this function as FSD_MountDiskWhen determining how to load an FSD, Device.exe looks for FSD_MountDisk.

All FSD functions can be called on re-entry. Therefore, take this into account when developing an FSD.

FSDMGR is a DLL that manages all OS interaction with installable files systems. Each installable file system requires an FSD, which is a DLL that supports an installable file system. The name of the DLL for an FSD and the names of the functions it exports start with the name of the associated installable file system. For example, if the name of file system is MyFSD, its DLL is MyFSD.dll, and its exported functions are prefaced with MyFSD_*.

FSDMGR provides service functions to FSDs. The FSDMGR_RegisterVolume, the FSDMGR_CreateFileHandle, and the FSDMGR_CreateSearchHandlefunctions record a DWORDof volume-specific data that an FSD associates with a volume. This volume-specific data is passed as the first parameter of these three functions.

Applications that access an installable file system use standard Win32 functions. For example, when an application creates a folder on a device that contains an installable file system, it calls the CreateDirectoryfunction. FSDMGR recognizes that the path is to a device containing an installable file system and calls the appropriate function, which in the case of the MyFSD file system is MyFSD_CreateDirectoryW. That is, the application calls CreateDirectory, causing FSDMGR to call MyFSD_ CreateDirectoryW.