On Mon, 17 Oct 2005 09:53:20 +0530, "Ramesh, MS-MVP"
Hello Chris
Hi!
1400 (Active Scripting) is actually a REG_DWORD and not a REG_BINARY.
As I understand it, the difference defines how the data is displayed
(e.g. binary as 00 00 00 00, DWord as 00000000) rather than how it is
used - AFAIK, it is not the registry or registry API that defines
content interpretation, but rather whatever it is that stores and
reads the data through those APIs.
the Value data is 0 by default when a clean installation is done.
The user may have strengthened settings in the interests of greater
safety (in fact, this is basically the source of the problem, i.e.
sounds like the patch was tested only with duhfault settings) and if
that is the case, the wider the settings loss, the more regrettable.
Description of Internet Explorer security zones registry entries:
Brilliant article, thanks! I wish I'd seen this when last I was
climbing that particular rockface, I deduced what I needed to know via
observed behaviour. The article confirms that the settings are in
fact bitmapped; let's look for the specifics...
1400 = 1010.... i.e. two bits set
Ahhh.... now I see where I'm confused; 1400 is the value name, not the
value data! OK, then there's a one-on-one correspondence and the
concerns about bitmapping don't apply. Gotcha.
BTW, the article also illustrates some bad-by-design safety issues
that I'd rather discuss privately.
