Block Load/Start of a driver

[anton_bassov]

There is often a, ah, reluctance I’d call it, among some of the devs on this list to accept that the reality of market requirements is often different than the academic exercise of creating an iron-clad solution. On such topics, many folks here would make the perfect the enemy of the possible.

At the risk of becoming boring, I am going, once again, to refer to the following comedy sketch

www.ecnmag.com/blog/2014/04/watch-engineer-deal-moronic-requests-marketing

If these “market requirements” include “drawing seven red lines that are strictly perpendicular to one another, with at least one of them having been drawn in a form of a kitten because customers like cute animals, and doing all the above partly with green ink and partly with transparent one”…well, then these requirements are, indeed, different from an " academic exercise" of creating a solution that may actually work…

And of course there’s the “who’s PC is this anyway” viewpoint. With those folks, you’ll get nowhere.

And where do you think one may get with a “solution” that renders most of the software installed on user’s machiue unusable, and, to make things even worse, does not allow a user to terminate(and sometimes even cleanly uninstall) itself???

…though that’s not quite as simple as it might sound, as I think you pointed out (who says the image has to be in \windows\system32\drivers? Who says it needs to be named *.sys? How do you know if it’s a driver, then?).

Well, parsing PE header seems(at least to me) to be a trivial and straightforward task…

Anton Bassov