Important: |
---|
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist. |
This function, an event notification handler, is called by the application to notify a file system driver (FSD) on a per-volume basis.
Syntax
void MyFSD_Notify( PVOLUME pVolume, DWORD dwFlags ); |
Parameters
- pVolume
-
[in] Pointer to the value that an FSD defines and passes to the FSDMGR_RegisterVolumefunction when registering the volume. The definition of this parameter can point to private structures.
- dwFlags
-
[in] Event. The following table shows possible values.
Flag Description FSNOTIFY_DEVICES_ON
Indicates that that the device has resumed after a suspended mode, and the PC card devices are now available for use.
FSNOTIFY_POWER_OFF
Indicates that the device is entering a suspended state. No system calls can be made at this point, and FSDMGR calls the application on a single thread.
FSNOTIFY_POWER_ON
Indicates that the device has resumed operations from a suspended mode. FSDMGR calls the application on a single thread. Therefore, the application returns quickly, and other file systems can resume.
Return Value
None.
Remarks
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 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 services to FSDs. The FSDMGR_RegisterVolume, the FSDMGR_CreateFileHandle, and the FSDMGR_CreateSearchHandlefunctions record a DWORD of volume-specific data that an FSD associates with avolume. 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 FAT file system is FATFSD_CreateDirectoryW. That is, the application calls CreateDirectory, causing FSDMGR to call FATFSD_CreateDirectoryW.
Requirements
Header | fsdmgr.h |
Library | Fsdmgr.lib |
Windows Embedded CE | Windows CE 2.10 and later |
Windows Mobile | Windows Mobile Version 5.0 and later |