Now, there are sources for the driver available :
A filesystem interface to the Windows registry
The registry interface is very similar to the filesystem interface in that they are both hierarchical databases that have data-less nodes (keys/directories) and data leaves (key values/files). Unforutnately, the registry is accessed through an entirely different API than files are, which can be a pain in portable software, especially those designed to edit and transfer configuration, expecting the data to be stored in files (like it is on most other OSes).Regfs provides a filesystem interface to the registry, allowing programs that aren't aware of the registry to access it anyway.
Even though the interfaces are similar, there are differences between the registry and a standard filesystem that may not be reconcilable; Regfs is NOT designed to be a general-purpose filesystem, as there are important features that cannot be implemented and interfaces differences that may be difficult to work-around at best. (See the known issues) Instead, regfs should be used to access and store basic configuration information in a unified place for all apps-- even those that don't normally use the registry. In any case, RegFS is an interesting as a NT filesystem interface wrapper.
Would it be too much to ask any of the programmers with a DDK to compile it, in order to try it?
Also very worth of note:
Security Descriptor Editor
Since the first release of Windows NT, security descriptors have been used to control authorization for system resources in a unified way. Security descriptors can be applied to every file, key, process, thread, event, mutex, semaphore, desktop, job, section, Active Directory object, and many other object types that exist on a NT system.
The original security descriptor editor that shipped with NT 3.1 was barely functional. Even the new editor introduced in Windows 2000 has limitations.
SD Edit is designed to expose the full functionality of security descriptors by presenting them in a direct form and by giving you full control over the details. It presents the elements of a security descriptor in a more direct form than the shell editor, and so requires you to better understand how they work at a low level.