Microsoft Windows CE 3.0  

NdisRawReadPortBufferUlong

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 reads a specified number of ULONGs into a caller-supplied buffer.

VOID NdisRawReadPortBufferUlong(
IN ULONG
Port
,
OUT PULONG
Buffer
,
IN ULONG
Length
);

Parameters

Port
Specifies the I/O port. This address falls in a range that was mapped during initialization with the NdisMRegisterIoPortRangefunction.
Buffer
Pointer to a caller-allocated buffer, in resident memory, into which the ULONGs are transferred from the NIC. The caller must allocate a buffer at least ( sizeof(ULONG) * Length ).
Length
Specifies how many ULONGs to transfer from the NIC.

Remarks

This function reads each ULONGvalue, one at a time, from the specified I/O port into the specified buffer.

A driver that calls this function can run at any IRQL.

Requirements

Runs on Versions Defined in Include Link to
Windows CE OS 2.0 and later Ndis.h    
Note   This API is part of the complete Windows CE OS package as provided by Microsoft. The functionality of a particular platform is determined by the original equipment manufacturer (OEM) and some devices may not support this API.

See Also

NdisMRegisterIoPortRange, NdisRawReadPortBufferUchar, NdisRawReadPortBufferUshort, NdisRawReadPortUlong, NdisRawWritePortBufferUlong



 Last updated on Tuesday, July 13, 2004

© 2004 Microsoft Corporation. All rights reserved. 500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.