Am 31.10.2012 04:14, schrieb Patrick Elliott:

>> 2. You can write your own application to access the registry. Hell, it's
>> probably quite easy to throw something together in VB to do a quick
>> search or two...
> :snark: and how much of what that is supposed to do is "undocumented",
> in the same way that, prior to completely changing the system, you
> couldn't find any documentation on how the hell ActiveX interfaced with
> the scripting system, in their own editor, and Informal Exploder, so you
> could move them around on your "form"? :/snark:
[lots of ranting about ActiveX deleted]

What, exactly, does that have to do with accessing the registry?

> So, sure.. You can probably write something to access the registry,
> but... will it actually do what it claims to?

The question is not whether it will actually do what it claims to, but 
whether you know what you want it to do.


Your list of things you'd like to be able to do includes "listing all 
related keys". Guess what - per definition of the registry, regedit does 
that already: The only "native" relationship of registry keys is in the 
hierarchical tree structure of sections.

Each and every other relationship between registry keys is only by 
convention of individual services and applications - such as the Windows 
explorer assigning file extensions to file types, and file types to 
applications. Or the device manager linking drivers to devices. Or what 
the heck.

At the end of the day, you DO need service- or application-specific 
knowledge if you want to edit the registry, because it's services and 
applications that assign semantics to the raw data they store in there.

Post a reply to this message