Search the Community
Showing results for tags 'exit code'.
I was looking at an example and it would Exit 1 on error. So what's wrong with that. Well, we can get an error from different aspects of the script, been the stub errored, or the wrapper errored, or finally, the script. What I propose is to start script errors on 3 onwards. Been 1 the error of AutoIt3, 2 of the wrapper, and finally the script. If you agree vote for me: "argumentum 2021" Really, if the concept is sound then say it and if not ... well, say it too PS: this is in regard to Exit codes of a script and not that of Return in a Function.
Hi, I have a problem in that one script runs successfully and gets to this line MsgBox(0x40,$UpdateID,"Successfully installed update " & $UpdateID) Exit(1) This script was started by another at this point: $InstallationResult = RunWait($ExeFileFullPath & " " & $InstallerParameters) ProcessWaitClose(StringReplace($FileName,"mmupdate","exe")) SplashOff() If $InstallationResult = $DesiredResult Then FileMove($ExeFileFullPath, $FileFullPath & ".done") LogWrite("Update succeeded") Else ; the update failed