This function, an event notification handler, is called by the application to notify a file system driver (FSD) on a per-volume basis.
At a Glance
| Header file: | Fsdmgr.h |
| Windows CE versions: | 2.10 and later |
Syntax
void MyFSD_Notify( PVOLUME pVolume, DWORD dwFlags);
Parameters
pVolume
Pointer to the value that the FSD defines in its DLL and passes to the FSDMGR_RegisterVolume function when registering the volume. The definition of pVolume can point to private structures.
dwFlags
Specifies the event. It is one of the following flags, included in Fsdmgr.h from the Extfile.h file:
Indicates that the device has resumed operations from a suspended mode. The file system manager calls the application on a single thread, therefore, the application should return quickly so other file systems can resume.
Indicates that the device is entering a suspended state. No system calls can be made at this point, and the file system manager calls the application on a single thread.
Indicates that that the device has resumed after a suspended mode, and the PC card devices are now available for use.
Return Values
None.
Remarks
All FSD functions can be called reentryly, therefore, FSD developers must take this into account when developing an FSD.
The Fsdmgr component is a dynamic-link library (DLL) that manages all operating system interaction with installable files systems. Each installable file system requires an FSD, which is a DLL that exports an API needed to support an installable file system. The name of the DLL 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, then its DLL is MyFSD.dll and its exported functions are prefaced with MyFSD_*.
Fsdmgr provides services to FSDs. The FSDMGR_RegisterVolume, FSDMGR_CreateFileHandle, and FSDMGR_CreateSearchHandle functions record a DWORD of volume-specific data the FSD needs to keep associated with 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 wants to create a folder on a device that contains an installable file system, it calls CreateDirectory. 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 FAT file system is FATFSD_CreateDirectoryW. That is, the application calls CreateDirectory, causing Fsdmgr to call FATFSD_CreateDirectoryW.
See Also