Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results
The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.
Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/
My NDIS is failing at HLK Hyper-V readiness, because of the following error:
Non-zero Code Integrity statistic found: Execute-Write Section Count: == 1
Checked the .sys file, turns out the INIT section is RWX.
We are not changing the attribute of the INIT anywhere so this seems to be the default, we are only using
LINKERFLAGS = $(LINKER_FLAGS) /SECTION,INIT,RX
To the sources file, no luck, Tried adding
#pragma comment(linker, "/section:INIT,RX")
To the source code, still no luck. We are building it using DDK 7600.
How can i force the INIT section to not be RWX?
|Upcoming OSR Seminars|
|OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead!|
|Internals & Software Drivers||19-23 June 2023||Live, Online|
|Writing WDF Drivers||10-14 July 2023||Live, Online|
|Kernel Debugging||16-20 October 2023||Live, Online|
|Developing Minifilters||13-17 November 2023||Live, Online|
Why are you using such an old DDK? Seems like you will run into multiple problems trying to get that build environment to produce binaries compatible with the latest generations of HLK tests. When I build a driver with the latest WDK, also not changing any attributes, dumpbin /section:INIT reports "Execute Read"
And why bother using an INIT section at all? That made sense back 20 years ago… today, with big memory machines, not such a big deal.