SCSI miniports do support some WMI functionality, and that might allow your
driver to play nicely in the sandbox.

You cannot include NTDDK.H in your SCSI miniport source files, for the
reason you discovered. You can however, define a lateral edge to your
miniport that provides DDK functionality. Simply create a source file that
includes NTDDK.H and exports functionality to the miniport. You would not
call ZwOpenKey directly, instead you would provide a function in this
lateral edge source file that would call ZwOpenKey. Now for the other
gotcha. A SCSI miniport loads very early in the boot process, and if you are
not careful where you put these keys, the path you want to use may not
exist.

Overall what you are trying to do is frowned upon by the community. It's
been tried many many times and almost always results in lots of postings
with minimal and disappointing results. What seems like a simple solution
now, will grow into a slathering monster that consumes time and resources.

However, you have a need to do something. I would encourage you to check out
existing functionality such as using event logs, WMI and/or WPP tracing.

--
Gary G. Little
Seagate Technologies, LLC

"Evgeny & Nir" <sjenbogo@t2.technion.ac.il> wrote in message
news:0c8201c37d1b$130d3ed0$a301280a@phx.gbl...