Hi all
I am working on Vista Callout Driver and I have the 5384 release of wdk…
But The MSDN documentation if different … many of Api Looks changed and
many of Api looks added… here I am unable to make the network clone
at FWPM_LAYER_ALE_FLOW_ESTABLISHED_V4
…
Is I am using Wrong WDK version … Please Say What is the
Version of wdk which have the all latest api and documentation what MSDN
have currently…
Thanks
Niraj Jha
> I am working on Vista Callout Driver and I have the 5384 release of wdk…
But The MSDN documentation if different … many of Api Looks changed and
many of Api looks added…
It has nothing to do with WDK version - huge discrepancies between MSDN documentation and callout sample can be found in WDK RTM as well…
Anton Bassov
> It has nothing to do with WDK version - huge discrepancies between MSDN
documentation and callout sample can be found in WDK RTM as well…
I agree. But I would suggest to pick up WDK 6000. Don’t use the doc that
ship with WDK (if you want to write a callout driver). The most current doc
I found is online:
Hi Frank thanks a lot… Now I am not in confusion…
On 1/8/07, frank wrote:
>
> > It has nothing to do with WDK version - huge discrepancies between MSDN
> > documentation and callout sample can be found in WDK RTM as well…
>
> I agree. But I would suggest to pick up WDK 6000. Don’t use the doc that
> ship with WDK (if you want to write a callout driver). The most current
> doc
> I found is online:
>
> http://msdn2.microsoft.com/en-gb/library/ms796358.aspx
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
> Don’t use the doc that ship with WDK (if you want to write a callout driver).
In fact, I would suggest exactly the opposite - although documentation may be wrong sometimes,
it is still supposed to be more reliable that a sample code that ships with WDK.
In actuality, the OP put it the wrong way - he said that “Api Looks changed and
many of Api looks added”. In actuality, this is not the case - the only thing callout sample does
is using some functions that are not documented on MSDN…
Anton Bassov
Hi Anton
I said because i found some change in some api… like in my
documentation the api for making clone is
NTSTATUS NTAPI
FwpsAllocateCloneNetBufferList0(
IN HANDLE *injectionHandle*,
IN OUT NET_BUFFER_LIST **originalNetBufferList*,
IN NDIS_HANDLE *netBufferListPoolHandle* OPTIONAL,
IN NDIS_HANDLE *netBufferPoolHandle* OPTIONAL,
IN ULONG *allocateCloneFlags*,
IN FWPS_INJECT_COMPLETE0 *completionFn*,
IN void **completionCtxt* OPTIONAL,
OUT NET_BUFFER_LIST ***netBufferList*
);
and in msdn2 it is NTSTATUS NTAPI
FwpsAllocateCloneNetBufferList0(
IN OUT NET_BUFFER_LIST **originalNetBufferList*,
IN NDIS_HANDLE *netBufferListPoolHandle* OPTIONAL,
IN NDIS_HANDLE *netBufferPoolHandle* OPTIONAL,
IN ULONG *allocateCloneFlags*,
OUT NET_BUFFER_LIST ***netBufferList*
);
and many api like FwpsQueryPacketInjectionState0 and some more which i have
not find in that… I think that is only due to i am using wdk 5384… there
is also a sample which is not much efficient to deal with callouts logics…
I would like to thank you for have response on my
question…Is this a stable release on callout module so that i would follow
that for my driver…
Regards
Niraj Jha
On 1/9/07, xxxxx@hotmail.com wrote:
>
> > Don’t use the doc that ship with WDK (if you want to write a callout
> driver).
>
> In fact, I would suggest exactly the opposite - although documentation may
> be wrong sometimes,
> it is still supposed to be more reliable that a sample code that ships
> with WDK.
>
> In actuality, the OP put it the wrong way - he said that “Api Looks
> changed and
> many of Api looks added”. In actuality, this is not the case - the only
> thing callout sample does
> is using some functions that are not documented on MSDN…
>
> Anton Bassov
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>