MyFSD_WriteFileWithSeek (Windows CE 5.0)
This function writes data to a file in an installable file system. The function starts writing data at a specified position in the file indicated by the caller. After the write operation has been completed, the file pointer is adjusted by the number of bytes actually written. This function is exported by an implementation of FSD and is called indirectly by FSDMGR.
BOOL MyFSD_WriteFileWithSeek( PFILE pFile, PCVOID pBuffer, DWORD cbWrite, PDWORD pcbWritten, OVERLAPPED* pOverlapped,DWORD dwLowOffset, DWORD dwHighOffset);
Parameters
pFile
[in] Pointer to the value that an FSD passes to the FSDMGR_CreateFileHandle function when creating the file handle.pBuffer
[in] Pointer to the buffer containing the data to be written to the file.cbWrite
[in] Number of bytes to write to the file.A value of zero specifies a null write operation. A null write operation does not write any bytes but does cause the time stamp to change.
pcbWritten
[out] Pointer to the number of bytes written by this function call. WriteFile sets this value to zero before doing any work or error checking. This parameter cannot be NULL.pOverlapped
Not supported.dwLowOffset
[in] Low part of a 64-bit address that identifies the start position for the write operation.dwHighOffset
[in] High part of the 64bit address that identifies the start position of the write operation. Together the dwLowOffset and dwHighOffset form the 64-bit address to begin the write operation.
Return Values
Nonzero indicates success. Zero indicates failure. To get extended error information, call GetLastError.
Remarks
The OS does not support asynchronous write operations. The lpOverlapped parameter is ignored and should be set to NULL before calling WriteFile.
If an FSD needs to support paging from the file system then this function must be implemented. If it is implemented, the pager and memory mapped file support utilize this function. If an FSD does not supported paging from the file system, then the fallback position is to page the entire file into memory when it is a module or a file that is being mapped.
The kernel determines whether your FSD can support paging by making the following call: ReadFileWithSeek(oeptr->hf,0,0,0,0,0,0). If your FSD returns TRUE, then paging is supported for this file; otherwise, paging is not supported.
The kernel determines whether an FSD supports write operations for use with memory-mapped files by making the following call.
WriteFileWithSeek(hFile,&testbyte,1,&len,0,0,0)
An FSD returns TRUE, if write operations are allowed on the file. An FSD returns FALSE, if write operations are not permitted on the file. If WriteFileWithSeek is not supported, then WriteFile is used to determine whether an FSD supports write operations on memory mapped files.
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. In other words, the application calls CreateDirectory, causing Fsdmgr to call FATFSD_CreateDirectoryW.
An application must meet the following requirements when working with files opened with FILE_FLAG_NO_BUFFERING:
- File access must begin at byte offsets within the file that are integer multiples of the volume's sector size. To determine a volume's sector size, call the GetDiskFreeSpaceEx function.
- File access must be for numbers of bytes that are integer multiples of the volume's sector size. For example, if the sector size is 512 bytes, an application can request reads and writes of 512, 1024, or 2048 bytes, but not of 335, 981, or 7171 bytes.
- Buffer addresses for read and write operations must be sector aligned on addresses in memory that are integer multiples of the volume's sector size. One way to sector align buffers is to use the VirtualAlloc function to allocate the buffers. This function allocates memory that is aligned on addresses that are integer multiples of the system's page size. Because both page and volume sector sizes are powers of 2, memory aligned by multiples of the system's page size is also aligned by multiples of the volume's sector size.
The implementation of FILE_FLAG_NO_BUFFERING is optional and is determined by an FSD.
If part of the file is locked by another process and the write operation overlaps the locked portion, this function fails.
Accessing the output buffer while a write operation is using the buffer may lead to corruption of the data written from that buffer. Applications must not read from, write to, reallocate, or free the output buffer that a write operation is using until the write operation completes.
The system interprets zero bytes to write as specifying a null write operation and WriteFile does not truncate or extend the file. To truncate or extend a file, use the SetEndOfFile function.
Requirements
OS Versions: Windows CE 2.10 and later.
Header: Fsdmgr.h.
Link Library: Fsdmgr.lib.
See Also
CreateDirectory | CreateFile | FSDMGR_CreateFileHandle | FSDMGR_CreateSearchHandle | FSDMGR_RegisterVolume | ReadFile | SetEndOfFile | VirtualAlloc | WriteFile
Send Feedback on this topic to the authors