Scripts not working on Windows 7 ?

[T0m4s]

I GET IT RUNNING ...

Very amazing. I have to start the compiled script as Administrator.

I am working in an active directory controlled company network. My account already have local administration rights, but it seems thats not enough.

Thanks for help anyway!

Edited September 27, 2012 by T0m4s

[water]

Glad you got it working

Edited September 27, 2012 by water

[water]

It looks like your setup application runs as administrator while an AutoIt script without "#RequireAdmin" runs with standard permissions. That's why the script can't access the controls.

But I don't understand why the ControlClick returns 1 (success) when it can't acess the controls

[Tripredacus]

Not to be a buzzkill or anything... But the USB driver is packaged with Nullsoft.

NSIS installers recognize /S for silent installation, /NCRC to suppress the CRC (verification) step, and /D=dir to specify the "output directory", which is where the program will be installed. These options are case-sensitive, so be sure to type them in upper case.

I didn't check the other one tho.

[water]

I always prefer to use the installation switches. That's more reliable than clicking through the installation process using AutoIt.

[Mechaflash]

You should ALWAYS use the installation switches when available.

Don't waste time trying to automate the GUI controls for a setup when there's already a system in place to automate the install.

[water]

Amen!

[Colyn1337]

I too had to use these options to perform an unattended install of a program which did not accept command line inputs. I'll include it here as it may be helpful to you.

#NoTrayIcon

AutoItSetOption("WinTitleMatchMode", 2)

Run("setup.exe", @ScriptDir)
WinWait("PetraPro Setup")
Sleep(1000)
ControlClick("PetraPro Setup", "&Next >", 1)
Sleep(1000)
ControlClick("PetraPro Setup", "&Yes", 6)
Sleep(1000)
ControlClick("PetraPro Setup", "&Next >", 1)
Sleep(1000)
ControlSetText("PetraPro Setup", "", 303, "Serial Number Goes Here - Redacted")
Sleep(1000)
ControlClick("PetraPro Setup", "&Next >", 1)
Sleep(1000)
ControlClick("PetraPro Setup", "&Next >", 1)
Sleep(1000)
ControlClick("PetraPro Setup", "&Next >", 1)
Sleep(1000)
ControlClick("PetraPro Setup", "&Next >", 1)
Do
$Finish = ControlGetHandle("PetraPro Setup", "Finish", 1)
Sleep(1000)
Until $Finish <> ""
ControlClick("PetraPro Setup", "Finish", 1)

Exit

[Mechaflash]

I too had to use these options to perform an unattended install of a program which did not accept command line inputs.

If you're going to do that, you might as well perform a WinWait() on the inner text of each window instead of Sleep()ing.

Sleeping for 1 second can still allow you to miss the window if it decides to lockup for an additional half a second before hitting the next screen. And also some screens move faster than 1 second.

So just performing a WinWait() targeting inner-text removes any additional delay, and also doesn't attempt to continue if it pauses for a longer-than-not duration of time.

[jdelaney]

It's also a good idea to wait for the control to be present, and enabled. Then focus on it prior to performing an action. Doing that solved almost all my issues with automation applications.