This function reads data from a file on a remote Windows Embedded CE–based device. The read operation starts the position indicated by the file pointer. After the read operation has been completed, the file pointer is adjusted by the number of bytes actually read.
BOOL CeReadFile ( HANDLE hFile, LPVOID lpBuffer, DWORD nNumberOfBytesToRead, LPDWORD lpNumberOfBytesRead, LPOVERLAPPED lpOverlapped );
[in] Handle to the file to be read. The file handle must have been created with GENERIC_READ access to the file. This parameter cannot be a socket handle.
[out] Pointer to the buffer that receives the data read from the file.
[in] Number of bytes to be read from the file.
[out] Pointer to the number of bytes read. CeReadFile sets this value to zero before doing any work or error checking.
[in] Unsupported; set to NULL.
The CeReadFile function returns when one of the following is true: the number of bytes requested has been read or an error occurs.
Nonzero indicates success. Zero indicates failure. If the return value is nonzero and the number of bytes read is zero, the file pointer was beyond the current end of the file at the time of the read operation. To get extended error information, call CeGetLastError and CeRapiGetError.
If part of the file is locked by another process and the read operation overlaps the locked portion, this function fails.
Accessing the input buffer while a read operation is using the buffer may lead to corruption of the data read into that buffer. Applications must not read from, write to, reallocate, or free the input buffer that a read operation is using until the read operation completes.
The ReadFile function may fail and return ERROR_INVALID_USER_BUFFER or ERROR_NOT_ENOUGH_MEMORY whenever there are too many outstanding asynchronous I/O requests.
When a synchronous read operation reaches the end of a file, ReadFile returns TRUE and sets *lpNumberOfBytesRead to zero. Windows Embedded CE does not support asynchronous read operations on files.