| UID | title | description | old-location | tech.root | ms.date | keywords | ms.keywords | req.header | req.include-header | req.target-type | req.target-min-winverclnt | req.target-min-winversvr | req.kmdf-ver | req.umdf-ver | req.ddi-compliance | req.unicode-ansi | req.idl | req.max-support | req.namespace | req.assembly | req.type-library | req.lib | req.dll | req.irql | targetos | req.typenames | f1_keywords | topic_type | api_type | api_location | api_name | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
NF:ndis.NdisFSynchronousOidRequest |
NdisFSynchronousOidRequest function (ndis.h) |
Filter drivers call the NdisFSynchronousOidRequest function to originate a new Synchronous OID request and issue it to underlying drivers. |
netvista\ndisfsynchronousoidrequest.htm |
netvista |
05/02/2018 |
|
NdisFSynchronousOidRequest, NdisFSynchronousOidRequest function [Network Drivers Starting with Windows Vista], ndis/NdisFSynchronousOidRequest, netvista.ndisfsynchronousoidrequest |
ndis.h |
Ndis.h |
Universal |
Windows 10, version 1709 |
Ndis.lib |
<= DISPATCH_LEVEL |
Windows |
|
|
|
|
|
Filter drivers call the NdisFSynchronousOidRequest function to originate a new Synchronous OID request and issue it to underlying drivers.
This function is supported in NDIS 6.81 and later.
An NDIS handle that identifies a filter module. NDIS passed the handle to the filter driver in a call to the FilterAttach function.
A pointer to an NDIS_OID_REQUEST structure that specifies the operation that is requested with a given OID_Xxx code. The structure can specify an OID query, set, or method request.
This function returns the same values as NdisDirectOidRequest except that NDIS_STATUS_PENDING is never returned from this function.
The NdisFSynchronousOidRequest function cannot be used for general OID requests. For general OID requests, use the NdisFOidRequest function instead. NdisFSynchronousOidRequest can be used only for OIDs that NDIS supports for use with the Synchronous OID interface. Most filter drivers do not need to call NdisFSynchronousOidRequest.
Filter drivers must not complete FilterDetach until any Synchronous OID requests originated by the filter driver are completed.
Filter drivers are not required to implement FilterOidRequestComplete, FilterDirectOidRequestComplete, FilterSynchronousOidRequest, or FilterSynchronousOidRequestComplete in order to call NdisFSynchronousOidRequest. As its name suggests, a Synchronous OID request always completes synchronously, so there is no asynchronous callback.