NDIS5.0 trashing MiniportReservedEx

NTDEV
1

My NDIS5.1 driver is using MiniportReservedEx[3 * sizeof(PVOID)] to
store context information between NdisMIndicateReceivePacket and
MiniportReturnPacket. When I build the driver for NDIS5.0 to run under
Windows 2000, MiniportReservedEx is getting written over.

All the docs say that my deserialised miniport driver should be able to
use MiniportReservedEx for whatever it wants, but maybe that isn’t true
for NDIS 5.0???

Any suggestions?

Can I tell the debugger to break when certain memory is touched?

Thanks

James

2

See “ba w1” documentation in the debugger docs for breaking in when memory is written to (assuming it’s the processor that does the write, and that the write happens through that VA mapping).

  • S

From: xxxxx@lists.osr.com [xxxxx@lists.osr.com] On Behalf Of James Harper [xxxxx@bendigoit.com.au]
Sent: Tuesday, October 19, 2010 11:23 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] NDIS5.0 trashing MiniportReservedEx

My NDIS5.1 driver is using MiniportReservedEx[3 * sizeof(PVOID)] to
store context information between NdisMIndicateReceivePacket and
MiniportReturnPacket. When I build the driver for NDIS5.0 to run under
Windows 2000, MiniportReservedEx is getting written over.

All the docs say that my deserialised miniport driver should be able to
use MiniportReservedEx for whatever it wants, but maybe that isn’t true
for NDIS 5.0???

Any suggestions?

Can I tell the debugger to break when certain memory is touched?

Thanks

James

NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer