MyFSD_RegisterFileSystemFunction (Windows CE 5.0)

Send Feedback

This function is called by the FSD Manager to register a file or folder change notification function with an FSD to ensure that the shell maintains an accurate view of the file system. This function is obsolete as of Windows CE .NET 4.2.

BOOL MyFSD_RegisterFileSystemFunction( PVOLUMEpVolume,SHELLFILECHANGEFUNC_tpfn);

Parameters

  • pVolume
    [in] Pointer to the value that an 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.
  • pfn
    [in] Pointer to the function used for file or folder change notifications.

Return Values

TRUE indicates success. FALSE indicates failure.

Remarks

When a not NULL SHELLFILECHANGEFUNC_t address is registered, an FSD needs to fill in a FILECHANGEINFO structure with all the appropriate information every time a file or folder change occurs. At a minimum, fill FILECHANGEINFO for the following functions, assuming they succeed:

Register file information changes after the following calls:

SHELLFILECHANGEFUNC_t and FILECHANGEINFO are defined in Extfile.h.

An FSD exports this function, if it wants to support this functionality. All FSD functions can be called on re-entry; therefore, FSD developers must take this into account when developing an FSD.

The Fsdmgr component is a DLL that manages all OS 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 an 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.

Requirements

OS Versions: Windows CE 2.10 through 4.1.
Header: Fsdmgr.h.
Link Library: Fsdmgr.lib.

See Also

CreateDirectory | FSDMGR_CreateFileHandle | FSDMGR_CreateSearchHandle | FSDMGR_RegisterVolume | MyFSD_CloseFile | MyFSD_CreateDirectoryW | MyFSD_CreateFileW | MyFSD_DeleteFileW | MyFSD_FlushFileBuffers | MyFSD_MoveFileW | MyFSD_RemoveDirectoryW | MyFSD_SetFileAttributesW | FILECHANGEINFO | SHELLFILECHANGEFUNC_t

Send Feedback on this topic to the authors

Feedback FAQs

© 2006 Microsoft Corporation. All rights reserved.