Desktop Functions: Smart Device Functions:
|
Search Results for "ReadFile" in kernel32
private static extern bool ReadFile(IntPtr handle,
// first read the data into an internal buffer since ReadFile cannot read into a buf at
bool f = ReadFile(_handle, buf, (uint)count, ref read, IntPtr.Zero);
throw new Win32Exception(Marshal.GetLastWin32Error(), "ReadFile failed");
if (!Win32.ReadFile(handle, data, length, out len, IntPtr.Zero))
FsctlReadFileUsnData = (EFileDevice.FileSystem << 16) | (58 << 2) | EMethod.Neither | (0 << 14), 3: FreeLibrary
private void ReadFile() { Warning! GetOverlappedResult writes to the address of the buffer specified in the ORIGINAL OPERATION (ie/ ReadFile or WriteFile). .NET may move the address of the buffer before GetOverlappedResult returns, resulting in a buffer overflow. Use AllocHGlobal and FreeHGlobal or otherwise ensure the buffer is pinned between the two calls. 5: ReadFile
static extern bool ReadFile(IntPtr hFile, [Out] byte[] lpBuffer,
static extern unsafe int ReadFile(IntPtr handle, IntPtr bytes, uint numBytesToRead,
static extern bool ReadFile(IntPtr hFile, [Out] byte[] lpBuffer, uint nNumberOfBytesToRead,
static extern unsafe bool ReadFile(
Private Shared Function ReadFile(ByVal hFile As IntPtr, ByVal Buffer As IntPtr, _
<DllImport("kernel32.dll")> Friend Shared Function ReadFile( _ The documentation states that if using unbuffered IO, the memory must be "storage aligned" (aligned to the sector size of the storage device). Either this is not enforced, or managed allocations (specifically byte arrays) are automatically storage aligned because there seems to be no problem using it. Note that storage aligned and page aligned are not the same, and managed allocations are not in general page aligned (required for ReadFileScatter). Regarding the above note, my experience shows that failing to provide a storage-aligned buffer causes ReadFile to perform all IO synchronously. I.e. it always blocks until the operation is complete and never returns ERROR_IO_PENDING. Warning! GetOverlappedResult writes to the address of the buffer specified in the ORIGINAL OPERATION (ie/ ReadFile or WriteFile). .NET may move the address of the buffer before GetOverlappedResult returns, resulting in a buffer overflow. Use AllocHGlobal and FreeHGlobal or otherwise ensure the buffer is pinned between the two calls. The same applies to the overlapped structure.
If ReadFile(hDriver, ip, Marshal.SizeOf(erg), dwBytesReceived, Nothing) Then
public unsafe byte[] CT_ReadFile(int InputReportByteLength)
if (ReadFile(HidHandle, BufBytes, InputReportByteLength, ref BytesRead, null)) WriteFile, WriteFileGather, ReadFileScatter 6: ReadFileEx
static extern bool ReadFileEx(IntPtr hFile, [Out] byte [] lpBuffer, ReadFileCompletionDelegate <- need to define this 8: WriteFile Warning! GetOverlappedResult writes to the address of the buffer specified in the ORIGINAL OPERATION (ie/ ReadFile or WriteFile). .NET may move the address of the buffer before GetOverlappedResult returns, resulting in a buffer overflow. Use AllocHGlobal and FreeHGlobal or otherwise ensure the buffer is pinned between the two calls. |