0

It is wanted to catch a driver removal event within .INF (by having it to call custom dll/exe via some directive), neither by driver itself nor by userspace watchdog application.

Any hints on that?

UPD: seems that it can be somehow accomplished with either co-installers or by hacking around notify objects (which are also the answer for my other question about NDIS driver's property pages in network connection configuration)

(This is my third sequential question about that .INF files: #1, #2; guessing I just need to find a good place to discuss it - any recommendations (not MSDN please)?)

Community
  • 1
  • 1
kagali-san
  • 2,964
  • 7
  • 48
  • 87
  • You can do it with co-installers. Co-installers are just dlls which get called at several points of the installation of a driver. There is not much magic involved in writing one. – Christopher Nov 30 '11 at 14:12
  • @Christopher, thanks for confirmation. Yes, it seems that http://www.osronline.com/ddkx/install/dif-codes_79pu.htm does the trick – kagali-san Dec 02 '11 at 20:21

1 Answers1

1

http://www.osronline.com/ddkx/install/dif-codes_79pu.htm

As Christopher confirmed my researches, would take into writing co-installer.

kagali-san
  • 2,964
  • 7
  • 48
  • 87