An ActiveX control might be unsafe to interact with other parts of the page. Do you w

[sebouh181]

I am writing to registry using javascript.

var wsh = new ActiveXObject("WScript.Shell");
var key = "HKLM\\Software\\Neos\\2.0\\LightMode\\my-script";
wsh.RegWrite (key, 1999, "REG_SZ");

when i run this javascript code in my HTML page the following warning message appears
An ActiveX control might be unsafe to interact with other parts of the page. Do you want to allow this interaction?

I want to remove this message.

Any Help?

Thanks

[acoder]

You will have to change the settings in your IE browser to allow scripts to run without prompting. Only do this if you are sure that it's not unsafe and only for trusted websites.

[sebouh181]

I've changed the following IE settings but still the Message is appearing.

Tools>>Internet Options...
Security Tab
Local Intranet - Cutom Level...
ActiveX controls and plug-ins
Automatic prompting for ActiveX controls (Enable)
Binary and script behaviours (Enable)
Download signed ActiveX controls (Enable)
Download unsigned ActiveX controls (Enable)
Initialize and script ActiveX controls not marked as safe (Enable)
RUN ActiveX controls and plug-ins (Enable)
Script ActiveX controls marked safe for scripting (Enable)

Any other suggestions??

thanks

[acoder]

I think you may want to disable automatic prompting.

[sebouh181]

I disabled automatic prompting and still does not work!

[rnd me]

I disabled automatic prompting and still does not work!

it will always prompt for registry edit outside of trusted or local zones.

[sebouh181]

No other choice??????
I dont want to create an IIS, so i dont have trusted sites!!!

[aryalink]

@sebouh181

thanx for these postes.
i have a VB6 project. in one form i use microsoft internet control activex (IE frame) and this object navigae "test.html" contain javascript fso script.
i need disable this message with VB6 code.
plz suggest a solution for automaticaly disable with VB6

[acoder]

If you want a solution in VB6, you might have better luck in the VB forum.

If you make sure that it's in the trusted zone/local, you should be able to avoid this message with appropriate settings.