Re: Workarounds that kill Active-X controls.

In news:Xns9852BA1714263z9zzaQ2btw@xxxxxxxxxxxxxxxxxxxx,
Mark V <notvalid@xxxxxxxxxxx> wrote:

Making a Full Registry Backup in advance would be *good*!
Short of that an Export saved for reference would be also be
useful.

I make a lot of registry back ups but in this case I also export the key, if
it exists, as a workaround "undo" file before replacing the Compatibility
Flags value with 0x400.

Both the REG files I have seen and I believe the dedicated EXE
tools for this "set a kill bit" ignore the possibility of an
existing Compatibility Flag value might be present. Not so good.

Hmmm... Here's one: killWebView(926043)_undo.reg
------------------------
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX
Compatibility\{E5DF9D10-3B52-11D1-83E8-00A0C90DC849}]
"Compatibility Flags"=dword:00020000
-----------------------

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

I don't have that one, but may have seen it once. Let's see if
another posts a link.

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?

Not necessary. Just remove the "Compatibility Flags" Value. OR,
revert the value's data to the preexisting one, if appropriate.
The key itself can be removed in the case it did not previously
exist of course. Not entirely certain if "empty" Keys there

Yes, there are some empty keys in there. Exporting them before adding
Compatibility Flags would create a undo.reg file that would restore their
"empty" status.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX
Compatibility\
serve a purpose so tread lightly.

Yup. I tracked down the keys for the two outstanding workarounds on machines
without the w/a's. For the published workarounds, the key above is the only
key I found
present, complete with flags. But somebody should check my work.

One might write a batch file using REG.EXE to accomplish
search for existing value and save it
create/apply "kill bit" changes
==== demo data only ==(wrapped)=====
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\ActiveX
Compatibility\{D7A7D7C3-D47F-11D0-89
D3-00A0C90833E6}
Compatibility Flags REG_DWORD 0x400
_oldValue REG_DWORD 0x20
========================

I should mention a GUI tool: Nirsoft's ACM (ActiveX Compatibility
Manager) (free) nirsoft.net
This tool does _not_ save existing Compatibility Flags data when
"disable" is selected. Also has a limited CLI usage.

Also for anyone interested, their other tool, Active X Helper, "disables" a
control not with the kill bit but by munging the value name for the
control's path, e.g.

[HKEY_CLASSES_ROOT\CLSID\{D7A7D7C3-D47F-11D0-89D3-00A0C90833E6}\InprocServer
32]
"ThreadingModel"="Apartment"
@="C:\\WINNT\\system32\\daxctle.ocx"

becomes

[HKEY_CLASSES_ROOT\CLSID\{D7A7D7C3-D47F-11D0-89D3-00A0C90833E6}\InprocServer
32]
"ThreadingModel"="Apartment"
"~~Disabled~~"="C:\\WINNT\\system32\\daxctle.ocx"

Enabling returns it the former. I guess that would disable
the control for ANY use, including IE scripting.

Hope all this makes sense,
--
Jim





.

Relevant Pages

  • Re: Workarounds that kill Active-X controls.
    ... Short of that an Export saved for reference would be also be ... I make a lot of registry back ups but in this case I also export ... replacing the Compatibility Flags value with 0x400. ... the control for ANY use, ...
    (microsoft.public.win2000.registry)
  • Re: Problem changing registry to kill Macromedia
    ... changing the Windows registry, something which I've been doing since Win 98. ... But if I try to name it "Compatibility Flags", of course it tells me the name is already taken and doesn't allow it. ... a value of zero is the same as a string of bits all of which are zero. ...
    (microsoft.public.windowsxp.general)