Custom Query (3933 matches)

I want to dynamically change proxy settings inside IE. I cannot find any dedicated functions inside Autoit to do this, so I must change directly values inside Windows registry.

I am using Microsoft Windows 2000 Professionnal 5.00.2195 SP4 and the latest version of AutoIt3 (v3.3.0.0)

:) If I create a new registry entry with a registry editor, RegRead() will return the right value.

:) If I change the value in the editor, RegRead will return the changed value.

:( If I change the value with RegWrite, the actual value seen with the registry editor is not changed (even after a refresh - restart of the editor). Autoit returns no error (error code is 1)

:( If I change the value with the registry editor, then RegRead does not report the new value, sticks to the last value changed with RegWrite.

:( Even if I delete the entry from the registry, RegRead keeps reporting the value changed by RegWrite.

It seems that RegRead/RegWrite is totally disconnected from the actual registry database.

Could you look into this as having access to the registry with AutoIt is one of its key features.

Please email me back, I need a quick fix.

Somepeople had problems with my autoit program because a folder in the appdata dir was not found. Today I heard they have got all Vista 64bit. I said he should create a little program msgbox(0,"test",@appdatadir), but the window is empty. The @appdatadir function returns nothing. I can't find out more about the problem because i don't use a 64bit operatingsysteme.

I have written a script that will elevate an uninstall process to admin credentials. This works nicely when run from a local drive. However when run from a network path, the scripts pauses.

RunAs Command line reads:

RunAs($Admin, @LogonDomain, $AdminPwd,1,@ComSpec & ' /c ' & $RemoveOld) As I'm using the @ComSpec /c, when running from local drive the command line box appears. When running same script (absolutely no changes) from a network path, this command line box does not appear.

To get around this I have created a .cmd file that copies the script file from the network path to the local drive and run script locally. Bit of a bummer!