Jump to content

Recommended Posts

I have automated an install process by using the below code.

 

Func _WinWaitActivate($title,$text,$timeout=0)
    WinWait($title,$text,$timeout)
    If Not WinActive($title,$text) Then WinActivate($title,$text)
    WinWaitActive($title,$text,$timeout)
EndFunc

$win1 = "Text 1"
$win2 = "Text 2"

_WinWaitActivate($win1,"WARNING: This progra")
Send("{ALTDOWN}n{ALTUP}");Send("{SPACE}")
_WinWaitActivate($win1,"I DISAGREE and &do n")
Send("{UP}n")
_WinWaitActivate($win1,"Customer Information")
Send("{ALTDOWN}n{ALTUP}");Send("{TAB}{TAB}n")
_WinWaitActivate($win1,"Click Next to instal")
Send("{ALTDOWN}n{ALTUP}");Send("n")
_WinWaitActivate($win1,"This feature require")
Send("{ALTDOWN}n{ALTUP}");Send("{TAB}n")
_WinWaitActivate($win1,"Ready to Install the")
Send("{ALTDOWN}i{ALTUP}");Send("i")
_WinWaitActivate($win1,"The InstallShield Wi")
Send("{ALTDOWN}f{ALTUP}");Send("f")
_WinWaitActivate($win2,"You must restart you")
Send("{ALTDOWN}n{ALTUP}");Send("n")

Now if any new screen comes in the middle of installation, like some VC++ installation error or like that.

The AutoIT is waiting in the background.

Is there any way to skip the new screens with just "enter" and continue the installation??

Link to post
Share on other sites

If its installshield why use send keys?  Use silent uninstall strings, also a number of InstallShield setups will allow you to create a response file so that it's preconfigured.  Whats the name of the program?

Link to post
Share on other sites
7 minutes ago, Subz said:

If its installshield why use send keys?  Use silent uninstall strings, also a number of InstallShield setups will allow you to create a response file so that it's preconfigured.  Whats the name of the program?

Thanks @Subz for the help.

But we want to test the installation in all scenarios before releasing it to end users.

Silent, we have done already.

This part is for GUI, as to check all the GUI screens are coming as expected.

Link to post
Share on other sites

Normally when I package software for deployment, I would do the following:

  1. Check for processes running, ask user to close if open, or if required force close the application
  2. Check for previous installations
    • True - Check Version
      • Same or Newer Version - Perform a repair of the software or Exit Script
      • Older Version - Uninstall previous installations
  3. Install pre-requisites for software, VC++, .Net etc...
  4. Install software product
  5. Configure software product - User profile settings etc...

 

Edited by Subz
Link to post
Share on other sites

What I meant by my question above was, if you have configured the package correctly the user should never have to run the installer manually.  If they did I would normally have the script from my last post in the same installation directory so they just run this, I normally call it something like JavaRuntimeInstaller.exe with the actual Java Runtime exes in the same folder for x86 and x64 just as an example.

Link to post
Share on other sites

Hi @Subz

I think this going out of the conversation, sorry if I miss any information to specify previously while creating the thread.

The scenario with process steps you mentioned above is for end user deployment using some tool like SCCM.

But in my case, we are releasing our product installer in our website and the enduser may deploy as you mentioned if needed for multiple machines or he can install only on few machines using the GUI screens when you launch the setup file.

We need to test both GUI installation and silent installation before releasing in our website.

So, can you give any other suggestion for GUI installation instead of the silent installation (as that part is already handled). 

Edited by ur
Link to post
Share on other sites

All of the vendors I deal with normally have the silent install and installation instructions, I've never seen a third option for clicking the buttons, I wouldn't recommend setting up an installer with send keys as there are just so many possibilities of failure, for example a user clicks another window, or another application takes focus.

Just my 2 cents.

Link to post
Share on other sites
1 minute ago, Subz said:

All of the vendors I deal with normally have the silent install and installation instructions, I've never seen a third option for clicking the buttons, I wouldn't recommend setting up an installer with send keys as there are just so many possibilities of failure, for example a user clicks another window, or another application takes focus.

Just my 2 cents.

I agree with you.

But I think you don't understand the scenario.

We are not giving for one particular customer.

It is for multiple customers.

As we are giving both silent and UI mode installation, we need to do prior testing before delivery in both the cases.

If there is a silent installation means it doesn't mean we should not test or support UI mode installation, right?

So coming to the present issue, can we skip any extra UI screens by clicking on enter button or something like that? to continue the installation.

Link to post
Share on other sites

You would have to run the installer on a clean machine, find out what windows popup and use an If WinExists(...) Then do something.  Still doesn't make much sense to me, if the script is for your own use only, shouldn't you know what prereqs will pop-up and keeping an eye on the install to check for issues?

Link to post
Share on other sites

The project ism file is same, but the data or files changes on daily basis, so to automate that testing part I need this.

And the winexists logic i didn't understand, can you please elaborate it

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By HoangDung
      This is the function that returns the result from cmd, initially i connect to the network wait then i make a call to the above _GetDOSOutput($sCommand) function i want to wait 1 period of time netsh wlan connect name="name" actually but after starting to execute the netsh wlan show interfaces command i tried adding a timeout command it seems to have ignored the timeout command?
      #include <WindowsConstants.au3> #include <Constants.au3> Func _GetDOSOutput($sCommand) Run('"' & @ComSpec & '" /c ' & $sCommand, "", @SW_HIDE, $STDERR_CHILD + $STDOUT_CHILD) Local $sOutput = '' Local $iPID = Run('"' & @ComSpec & '" /c ' & $sCommand, "", @SW_HIDE, $STDERR_CHILD + $STDOUT_CHILD) While 1 $sOutput &= StdoutRead($iPID, False, False) If @error Then ExitLoop EndIf Sleep(10) WEnd Return $sOutput EndFunc Local $sCommand= 'netsh wlan delete profile name="wait" & netsh wlan connect name="name" interface="Wi-fi" & netsh wlan show interfaces' MsgBox(0,0,_GetDOSOutput($sCommand))  
    • By D3fr0s7
      I'm trying to make one tray item delete another, but when I do this, all tray items that were created after the deleted item don't work as intended, as if their controlID's were all shifted down one value, and their corresponding tray items now (after deletion) run the code of the tray item before it. Am I missing something? Is there a better way to accomplish what I'm trying to do?
      #include <TrayConstants.au3> #include <Array.au3> HotKeySet ( "{ESC}", "Abort" ) Opt ( "TrayMenuMode", 3 ) TraySetState($TRAY_ICONSTATE_SHOW) ; Show the tray menu. Global $aTray[8] ; Defines array to hold tray items. $aTray[0] = TrayCreateItem ( "Test 1 (Name Test 5)" ) $aTray[1] = TrayCreateItem ( "Test 2 (Delete Test 5)" ) $aTray[2] = TrayCreateItem ( "Test 3 (Restore Test 5)" ) $aTray[3] = TrayCreateItem ( "Test 4 (Check if Test 5 is blank or space)" ) $aTray[4] = TrayCreateItem ( "Test 5 Delete Me" ) $aTray[5] = TrayCreateItem ( "Test 6 (Check Test 5 Text)" ) $aTray[6] = TrayCreateItem ( "Test 7 (Read Values)" ) $aTray[7] = TrayCreateItem ( "Test 8 (Count Blanks)" ) While 1 Switch TrayGetMsg() Case $aTray[0] ; "Test 1" Change Test 5 Text. If TrayItemGetText ( $aTray[0] ) <> "" Then Global $TrayText = InputBox ( "Test", "Choose text for Test 5", "Test 5 Delete Me" ) TrayItemSetText ( $aTray[4], $TrayText) EndIf Case $aTray[1] ; "Test 2" Deletes "Test 5". If TrayItemGetText ( $aTray[1] ) <> "" Then Global $TrayDeletedName = TrayItemGetText ( $aTray[4] ) TrayItemDelete ( $aTray[4] ) _ArrayInsert ( $aTray, 4 ) EndIf Case $aTray[2] ; "Test 3" Restores "Test 5". If TrayItemGetText ( $aTray[2] ) <> "" Then $aTray[4] = TrayCreateItem ( $TrayDeletedName ) EndIf Case $aTray[3] ; "Test 4" Check if Test 5 value is blank, space, or filled. If TrayItemGetText ( $aTray[3] ) <> "" Then If TrayItemGetText ( $aTray[4] ) = "" Then MsgBox ( 0, "Test", "Test 5 is blank" ) ElseIf TrayItemGetText ( $aTray[4] ) = " " Then MsgBox ( 0, "Test", "Test 5 is not blank (space)" ) Else MsgBox ( 0, "Test", "Test 5 is assigned a value" ) EndIf EndIf Case $aTray[4] ; "Test 5" (Item to test for, during, and after deletion). If TrayItemGetText ( $aTray[4] ) <> "" Then MsgBox ( 0, "Test", "I'm here!" ) EndIf Case $aTray[5] ; "Test 6" Displays Text from Test 5 item. If TrayItemGetText ( $aTray[5] ) <> "" Then $Test5Text = TrayItemGetText ( $aTray[4] ) MsgBox ( 0, "Test", "Test 5 Text: " & $Test5Text ) EndIf Case $aTray[6] ; "Test 7" Displays all item values. If TrayItemGetText ( $aTray[6] ) <> "" Then MsgBox ( 0, "Test", "$aTray[0]: " & $aTray[0] & @CRLF & _ "$aTray[1]: " & $aTray[1] & @CRLF & _ "$aTray[2]: " & $aTray[2] & @CRLF & _ "$aTray[3]: " & $aTray[3] & @CRLF & _ "$aTray[4]: " & $aTray[4] & @CRLF & _ "$aTray[5]: " & $aTray[5] & @CRLF & _ "$aTray[6]: " & $aTray[6] & @CRLF & _ "$aTray[7]: " & $aTray[7] & @CRLF ) EndIf Case $aTray[7] ; "Test 8" Counts all blanks in tray values. If TrayItemGetText ( $aTray[7] ) <> "" Then Global $blankCount = _ArrayFindAll ( $aTray, "" ) If $blankCount = -1 Then If @error = 6 Then MsgBox ( 0, "Test", "Error, No blanks present") EndIf Else MsgBox ( 0, "Test", "# of blanks: " & $blankCount ) EndIf EndIf EndSwitch WEnd Func Abort() Exit EndFunc Here is a test script I created to try to troubleshoot the problem on my own, with no luck. pay specific attention to "Test 2" ($aTray[1]), "Test 5" ($aTray[4]), and how every tray item after "Test 5" ($aTray[4]) behaves after deletion. Clicking "Test 2" will delete tray item "Test 5", after deletion every item runs the code of the tray item that was established before it (ex. "Test 3" and "Test 4" run their respective code, "Test 5" no longer exists, "Test 6" runs "Test 7", "Test 7" runs "Test 8"), and the last item ("Test 8" $aTray[7]) has no effect when the tray item is clicked. 

      I understand that deleting the tray item changes the controlID, but I don't know in what way it does, and therefore how I can fix it to be able to achieve what I want it to. I appreciate any help or guidance with this problem.

      To clarify, what I'm ultimately trying to do is create a 'while' loop with switch case functions that can exist without necessarily being linked to a tray item, so that I can add and delete them at liberty using the script's functions, without having to differentiate switch case functions with if functions (if $aTray[x] exists, then use this set of switch case functions, etc.). 

      Please, I am in pain. Water come school me again pls
    • By PeterVerbeek
      This topic give you access to an AutoIt functions library I maintain which is called PAL, Peter's AutoIt Library. The latest version 1.26 contains 214 functions divided into these topics:
      window, desktop and monitor GUI, mouse and color GUI controls including graphical buttons (jpg, png) GUI numberbox controls for integer, real, binary and hexadecimal input logics and mathematics include constants string, xml string and file string dialogues and progress bars data lists: lists, stacks, shift registers and key maps (a.ka. dictionaries) miscellaneous: logging/debugging, process and system info Change log and files section  on the PAL website (SourceForge).
      A lot of these functions were created in the development of Peace, Peter's Equalizer APO Configuration Extension, which is a user interface for the system-wide audio driver called Equalizer APO.
    • By Zaoka
      HI,
      for couple of years I'm using  Jos script for sending reports, email with excel attachment. But from last week i'm getting this error when sending excel or word attachment
      message has lines too long for transport jpeg, pdf works with no problems, any sugestion ?
    • By diepfeile
      I'm using the following:
      Autoit 3.3.14.5
      newly installed Beta 3.3.15.5
      SQlite version 3380000 aka 3.38.0
      I put sqlite3.dll and sqlite3_x64.dll in C:\Windows\System32 since many scripts depend on them.


      I extended the output of _SQLite_Startup()
      with:
      ConsoleWrite("@AutoItX64 " & @AutoItX64 & @CRLF) ConsoleWrite("$sDll_Filename " & $sDll_Filename & @CRLF) ConsoleWrite("_SQLite_LibVersion=" & _SQLite_LibVersion() & @CRLF)

      Also using the script from https://www.autoitscript.com/autoit3/docs/libfunctions/_SQLite_Startup.htm for testing.

       
      >Running:(3.3.14.5):C:\Program Files (x86)\AutoIt3\autoit3.exe "R:\Download\aasdf.au3" @AutoItX64 0 $sDll_Filename sqlite3.dll _SQLite_LibVersion=0 >Running:(3.3.14.5):C:\Program Files (x86)\AutoIt3\autoit3_x64.exe "R:\Download\aasdf.au3" @AutoItX64 1 $sDll_Filename sqlite3_x64.dll _SQLite_LibVersion=3.38.0 >Running:(3.3.15.5):C:\Program Files (x86)\AutoIt3\Beta\autoit3.exe "R:\Download\aasdf.au3" @AutoItX64 0 $sDll_Filename sqlite3.dll _SQLite_LibVersion=0 >Running:(3.3.15.5):C:\Program Files (x86)\AutoIt3\Beta\autoit3_x64.exe "R:\Download\aasdf.au3" @AutoItX64 1 $sDll_Filename sqlite3_x64.dll _SQLite_LibVersion=3.38.0


      Why doesn't it work in 32bit, despite me having the 32bit sqlite.dll? Autoit urges running scripts in 32bit mode and Scite starts scripts just in 32bit mode without the flag?
      With #AutoIt3Wrapper_UseX64=Y it just works, both normal Autoit and beta!
      sqlite3.dll sqlite3_x64.dll
×
×
  • Create New...