Leaderboard

It all depends upon how the "Setup.exe" was created. Was it created using the Wise installer? Inno Setup? NSIS setup? Once you know this you can easily set the proper command line switches to make the program install silently. The software itself likely has documentation on how to do this. In my experience, the macros within AutoIt seldom work when running another programs installation package.

I know this function but it don't help me in this case because the Ping function pause the whole script while the ping is sent.. So I can't refresh the progress bar during this time, even with ProgressSet. It's exactly the function needed to solve my problem ! Thanks ! And I wish you a happy new year to you all !

This is a generator to make valid sudoku (You can play with it to make easy normal hard games) Logic2.au3

Srry this will work the other had error Logic2.au3

If for range you mean something like those below "192.168.0.0-1" addresses: 192.168.0.0 and 192.168.0.1 "192.168.20.*" range from 192.168.20.1 to 192.168.20.255 "192.168.0-1.1-254" range from 192.168.0.1 to 192.168.1.254 Then you could use my Multiping.udf that, in addition to other functions, contains also _GetIpAddressList($sRange). It returns an 1D array containing all IP of the range: #include ".\MultiPing.au3" ; Get from https://www.autoitscript.com/forum/topic/156395-versatile-multi-ping/ #include <array.au3> $Range = "192.168.0-1.1-254" $aResult = _GetIpAddressList($Range) ; expand the range _ArrayDisplay($aResult)

Better use _FileListToArrayRec which allows multiple filters

This is categorically false. With the most recent versions of Office and their reliance on an underlying XML structure, it is easier than ever to break even a strong password on a worksheet. Both the hash and the salt are stored in the header of the worksheet itself, and easily readable.

@EddieR welcome to the forum. We have a number of people on the forum with experience repackaging and automating deployments of applications (some of us longer than we can remember). If you can share the application, we can probably do more to assist. With nothing more than "Setup.exe", though, it is a bit difficult.

it also works in AutoIt #include <Excel.au3> Local $o_Excel = _Excel_Open() Local $o_Workbook = _Excel_BookOpen($o_Excel, @DesktopDir & "\Book1.xlsx") With $o_Workbook.ActiveSheet .DrawingObjects = True .Contents = True .Scenarios = True .AllowFormattingCells = True .AllowFormattingColumns = True .AllowFormattingRows = True .AllowSorting = True .AllowFiltering = True .AllowUsingPivotTables = True .Protect("123") EndWith _Excel_BookClose($o_Workbook) _Excel_Close($o_Excel)

If the list of scripts is to keep expanding maybe use a listview with checkboxes. The script paths could be read to an array from a file, C:\Program Files (x86)\AutoIt3\AutoIt3.exe could be replaced with @AutoItExe and placed in the RunWait command. This should improve maintenance and save having to edit the script each time a new script needs to be added

2016.07.01b fixed the installer. At times the template on vista and newer goes to c:\users\All Users\.. ..\Templates 2016.07.01 ; https://www.autoitscript.com/forum/topic/149137-sign-your-exe-with-a-digital-signature-signtoolexe/?do=findComment&comment=1316935 after extensive testing, this is the best I can come up with, to simplify self signing the executable compiled with AutoIt3 from SciTE ( the editor ). Could have given the code more options but I felt at the time of coding that it was practical enough and if you ( the coder ) feel different, the code is in the file to tweak or just plain rewrite. In this ZIP are included the updated utility files from the original distribution of this package plus an installer of sorts called "copy all these to SciTE path.exe", to place the files in the path that the "#AutoIt3Wrapper_Run_After" command can find even if running as a portable setup. The path is %scitedir%\tools\SignThisFile\CertSigner.exe and it will also patch the Template.au3 ( if one is found ), to add the directive, with /NoPopup /NoLogfile ( therefore CertSigner.exe would otherwise write a log file and show a GUI with said log ), but the output is displayed at SciTE's console anyway, so what's the need for more bells and whistles. No need. Unless you run it in self standing mode, by dropping a file to it. Then you do want to have a feedback. In such case, a log is written and displayed. You may even add a shortcutr to "SendTo", to sign files from explorer. I tested the original code from Windows 2000 to Windows 10 and this compilation in english, spanish, french and korean, to assure uniform looks and functionality under every circumstance that I can think of at this moment. An ini file will be created as you first run CertSigner.exe, for you to edit and create your own self signed certificate. Do add the certificate to the store as trusted root ( otherwise what's the point ), and by doing so, the verification at the end of the signing will pass. Enjoy

Six years later, this is how I accessed the arguments within my script: $valueOne = _Args("/argumentOne", ":") $valueTwo = _Args("/argumentTwo", ":") ConsoleWrite($valueOne) ConsoleWrite($valueTwo) Func _Args($argument, $delimiter) If Ubound($CmdLine) > 1 Then For $i = 1 To UBound($CmdLine)-1 Step 1 If StringInStr($CmdLine[$i], $argument, 0) Then If StringInStr($CmdLine[$i], $delimiter, 0) Then $value = StringSplit($CmdLine[$i], $delimiter) Return $value[2] EndIf EndIf Next EndIf EndFunc And this is how I added the arguments when calling the script: "C:\install\AutoIt3.exe" "C:\ArgsTest.au3" /argumentOne:MyFirstValue /argumentTwo:MySecondValue

@UserName ?