Paul <> wrote in
news:jf5461$fin$:
> DanS wrote:
>
>> My beef isn't directly with all the shiny little gadgets
>> and new 'neat' little features, but rather with the
>>
>> This particular method of turning off libraries is 10 or
>> 12 registry edits, having virtually no meaning to anyone
>> other than like a bunch of bizarro hex strings.
>>
>> There can't be checkbox in a dialog somewhere that's
>> captioned: Use 'Libraries' ?
>>
>
> When you see bizarro hex strings, sometimes that's not hex.
> It's actually text, where every second character is 0x00
> hex, and the other character next to it is ASCII. If I take
> a bizarro hex string, edit out all the 0x00 things, then
> load the string into my hex editor, it'll translate it
> into text so I can read it.
>
> The real question would be, what loaded that registry entry
> in the first place. It probably wasn't done with regedit,
> if the user had to add the string as hex. It was probably
> done by some other registry adding tool, that supports
> unicode translation as needed.
>
> I have seen blocks of hex in the registry, where they
> appeared to just be a binary dump. But I've noticed more
> recently, the dumping of things like paths
> "C:\WINDOWS\blah" as a unicode string.
>
> Where this is really a pain, is if someone asks "does the
> string helloworld appear in Windows", at one time all you'd
> have to do is search for "helloworld" with a text search.
> But now, you also need to search for the unicode version "
> h e l l o w o r l d" where the space is the 0x00 character,
> when it is actually being stored as 16 bit unicode. It
> really depends on whether your tool flow or tool choice,
> happens to properly support unicode or not.
>
> Heaven help us, if more of the flavors of unicode are
> actively promoted in Windows...
>
> As it is, I've written a simple minded custom search tool,
> when I actually need to find things like " h e l l o w o r
> l d" somewhere on a Windows partition. Sometimes a person
> will say, "I'm getting the error message 'Helloworld'" and
> the only way to get a hint about the source, is to scan the
> entire partition.
>
> Just a guess,
In this particular case, they're CLSIDs that belong to the exe
or dll, or whatever module somewhere that provides the library
function. I haven't researched it, but Libraries are probably
implemented as a shell extension.
|