@Doron_Holan said:
Why must you be above Mouclass? The moufiltr example was designed to filter BELOW mouclass, not above it. You can’t just move the filters around and expect it to work. Everything you have described in this and the previous post leads me to believe you don’t need to be above mouclass, rather you don’t know how the stack works and are grasping for solutions and getting frustrated when it doesn’t work. Take a step back and learn how the mouse stack works. You can look at old WDKs which included mouclass as an example.The service callback only works for drivers below mouclass. Mouclass is the driver that sends IOCTL_INTERNAL_MOUSE_CONNECT down the stack. So if you are above mouclass you won’t see this ioctl because it is not sent to the top of the stack.
Why are you asking me why it has to be above Mouclass? I was just stating a fact that it ONLY works when its above despite the example being designed for it being bellow. This whole question is asking how to get it to work with it BELLOW like the example. This is not me complaining about it not working above because it works perfectly above when, this post is me asking how to get it to work with it bellow.
I provided an example of print statements that shows you that Connect Device is not called hence the CallBack is never registered making my filter driver not work. Having it bellow does not work at all because a device is never passed in while it works perfectly above. Stop stating the same thing over again and provide evidence to support your claim like my print examples above.