So far, I believe we've been advised of two security workarounds the involve
setting the kill bit for 3 controls. After the patch comes out, presumably
these controls could be re-enabled. If I apply the .reg file printed in the
article, it "slam dunks" 0x400 into the appropriate values for Compatibility
Flags. My question is what if some bits were already set? Should I be
checking before hand and or'ing the 0x400 bit into the DWORD?

ISTR an article that explains what each bit does, but I can't seem to find
it now.

Any help would be appreciated. I'm collecting .reg files that have been
applied, but their reversal would appear to be removing the key for that
control. Does that make sense?
--
Thank you
Jim

I'm reposting this, crossposting and with f/u set to,
microsoft.public.win2000.registry...

In news:uIbsKeL5GHA.2288@TK2MSFTNGP05.phx.gbl,
Jim Nugent <njim2k-nntp@yahoo.com> wrote:
> So far, I believe we've been advised of two security workarounds the
> involve setting the kill bit for 3 controls. After the patch comes
> out, presumably these controls could be re-enabled. If I apply the
> .reg file printed in the article, it "slam dunks" 0x400 into the
> appropriate values for Compatibility Flags. My question is what if
> some bits were already set? Should I be checking before hand and
> or'ing the 0x400 bit into the DWORD?
>
> ISTR an article that explains what each bit does, but I can't seem to
> find it now.
>
> Any help would be appreciated. I'm collecting .reg files that have
> been applied, but their reversal would appear to be removing the key
> for that control. Does that make sense?
> --
> Thank you
> Jim