Hi,
I waz reading the DDK manual for DriverEntry…I got some doubt please
clarify it…
here …
In this section it is written that memory sholud be allocated…
3.1.2 Registering the Miniport
[This is preliminary documentation and subject to change.]
After the DriverEntry function has called NdisMInitializeWrapper to create
an association with the NDIS library, DriverEntry must:
…Call NdisAllocateMemory to allocate a structure of type
NDIS_MINIPORT_CHARACTERISTICS
another one …
Here it is written that structure is copied in internal storage…
NdisMRegisterMiniport
…
This structure is copied in the NdisMRegisterMiniport request to the NDIS
library’s internal storage…
In sample code memory is not being allocated…Please clarify what is
correct???
***************************************************************************
This message is proprietary to Future Software Limited (FSL)
and is intended solely for the use of the individual to whom it
is addressed. It may contain privileged or confidential information
and should not be circulated or used for any purpose other than for
what it is intended.
If you have received this message in error, please notify the
originator immediately. If you are not the intended recipient,
you are notified that you are strictly prohibited from using,
copying, altering, or disclosing the contents of this message.
FSL accepts no responsibility for loss or damage arising from
the use of the information transmitted by this email including
damage from virus.
***************************************************************************
I am not sure which version of the DDK documentation you are reading. It
certainly doesn’t seem to be the same as the current Windows XP DDK
documentation for sure. None of us are working with “preliminary
documentation subject to change” for any currently released Windows OS
version. You’ve got old Beta documentation…
The samples are correct. It is not necessary to call NdisAllocateMemory to
allocate memory for NDIS_MINIPORT_CHARACTERISTICS.
The comment about “copied in the NdisMRegisterMiniport request to the NDIS
library’s internal storage” just means that 1.) you pass in a pointer to a
structure that you have initialized and 2.) NDIS makes its own copy of the
information.
Regards,
Thomas F. Divine
PCAUSA - Tools & Resources For Network Software Developers
NDIS Protocol/Intermediate/Hooking - TDI Client/Filter
http: - http:
“Manish K” wrote in message news:xxxxx@ntdev…
>
> Hi,
> I waz reading the DDK manual for DriverEntry…I got some doubt please
> clarify it…
>
> here …
>
> In this section it is written that memory sholud be allocated…
>
> 3.1.2 Registering the Miniport
> [This is preliminary documentation and subject to change.]
>
> After the DriverEntry function has called NdisMInitializeWrapper to create
> an association with the NDIS library, DriverEntry must:
>
> …Call NdisAllocateMemory to allocate a structure of type
NDIS_MINIPORT_CHARACTERISTICS
>
> another one …
>
> Here it is written that structure is copied in internal storage…
>
> NdisMRegisterMiniport
> …
> This structure is copied in the NdisMRegisterMiniport request to the NDIS
> library’s internal storage…
>
> In sample code memory is not being allocated…Please clarify what is
> correct???</http:></http:>
> …Call NdisAllocateMemory to allocate a structure of type
NDIS_MINIPORT_CHARACTERISTICS
IIRC this structure can be declared on stack.
Max
The documentation now says “it must initialize a structure of type
NDIS_MINIPORT_CHARACTERISTICS…”. If it once said that it must
allocate, then it was using the term generically, to include
‘allocating’ the structure on the stack as a local variable.
Bryan S. Burgin
xxxxx@microsoft.com
This posting is provided “AS IS” with no warranties, and confers no
rights
-----Original Message-----
From: Thomas F. Divine [mailto:xxxxx@hotmail.com]
Sent: Thursday, May 23, 2002 12:28 AM
To: NT Developers Interest List
Subject: [ntdev] Re: NDIS-DriverEntry
I am not sure which version of the DDK documentation you are reading. It
certainly doesn’t seem to be the same as the current Windows XP DDK
documentation for sure. None of us are working with “preliminary
documentation subject to change” for any currently released Windows OS
version. You’ve got old Beta documentation…
The samples are correct. It is not necessary to call NdisAllocateMemory
to
allocate memory for NDIS_MINIPORT_CHARACTERISTICS.
The comment about “copied in the NdisMRegisterMiniport request to the
NDIS
library’s internal storage” just means that 1.) you pass in a pointer to
a
structure that you have initialized and 2.) NDIS makes its own copy of
the
information.
Regards,
Thomas F. Divine
PCAUSA - Tools & Resources For Network Software Developers
NDIS Protocol/Intermediate/Hooking - TDI Client/Filter
http: - http:
“Manish K” wrote in message
news:xxxxx@ntdev…
>
> Hi,
> I waz reading the DDK manual for DriverEntry…I got some doubt please
> clarify it…
>
> here …
>
> In this section it is written that memory sholud be allocated…
>
> 3.1.2 Registering the Miniport
> [This is preliminary documentation and subject to change.]
>
> After the DriverEntry function has called NdisMInitializeWrapper to
create
> an association with the NDIS library, DriverEntry must:
>
> …Call NdisAllocateMemory to allocate a structure of type
NDIS_MINIPORT_CHARACTERISTICS
>
> another one …
>
> Here it is written that structure is copied in internal storage…
>
> NdisMRegisterMiniport
> …
> This structure is copied in the NdisMRegisterMiniport request to the
NDIS
> library’s internal storage…
>
> In sample code memory is not being allocated…Please clarify what
is
> correct???
—
You are currently subscribed to ntdev as: xxxxx@microsoft.com
To unsubscribe send a blank email to %%email.unsub%%</http:></http:>
DDK docs are online here:
http://www.osr.com/ddk/ddk.htm
Stephan
On Thu, 23 May 2002 03:28:20 -0400, “Thomas F. Divine”
wrote:
>I am not sure which version of the DDK documentation you are reading. It
>certainly doesn’t seem to be the same as the current Windows XP DDK
>documentation for sure. None of us are working with “preliminary
>documentation subject to change” for any currently released Windows OS
>version. You’ve got old Beta documentation…
>
>The samples are correct. It is not necessary to call NdisAllocateMemory to
>allocate memory for NDIS_MINIPORT_CHARACTERISTICS.
>
>The comment about “copied in the NdisMRegisterMiniport request to the NDIS
>library’s internal storage” just means that 1.) you pass in a pointer to a
>structure that you have initialized and 2.) NDIS makes its own copy of the
>information.
>
>Regards,
>–
>Thomas F. Divine
>
>PCAUSA - Tools & Resources For Network Software Developers
>NDIS Protocol/Intermediate/Hooking - TDI Client/Filter
>http: - http:
>
>
>
>“Manish K” wrote in message news:xxxxx@ntdev…
>>
>> Hi,
>> I waz reading the DDK manual for DriverEntry…I got some doubt please
>> clarify it…
>>
>> here …
>>
>> In this section it is written that memory sholud be allocated…
>>
>> 3.1.2 Registering the Miniport
>> [This is preliminary documentation and subject to change.]
>>
>> After the DriverEntry function has called NdisMInitializeWrapper to create
>> an association with the NDIS library, DriverEntry must:
>>
>> …Call NdisAllocateMemory to allocate a structure of type
>NDIS_MINIPORT_CHARACTERISTICS
>>
>> another one …
>>
>> Here it is written that structure is copied in internal storage…
>>
>> NdisMRegisterMiniport
>> …
>> This structure is copied in the NdisMRegisterMiniport request to the NDIS
>> library’s internal storage…
>>
>> In sample code memory is not being allocated…Please clarify what is
>> correct???</http:></http:>