Jump to content

Search the Community

Showing results for tags 'no upx'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Announcements and Site News
    • Administration
  • AutoIt v3
    • AutoIt Help and Support
    • AutoIt Technical Discussion
    • AutoIt Example Scripts
  • Scripting and Development
    • Developer General Discussion
    • Language Specific Discussion
  • IT Administration
    • Operating System Deployment
    • Windows Client
    • Windows Server
    • Office

Categories

  • AutoIt Team
    • Beta
    • MVP
  • AutoIt
    • Automation
    • Databases and web connections
    • Data compression
    • Encryption and hash
    • Games
    • GUI Additions
    • Hardware
    • Information gathering
    • Internet protocol suite
    • Maths
    • Media
    • PDF
    • Security
    • Social Media and other Website API
    • Windows
  • Scripting and Development
  • IT Administration
    • Operating System Deployment
    • Windows Client
    • Windows Server
    • Office

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Member Title


Location


WWW


Interests

Found 1 result

  1. New simple script written today. Runs/works perfectly run on the commandline, or double-clicked from Windows Explorer, or right-clicked run as administrator from Windows explorer. Just doesn't run in the context I need it to; called from a compiled Wise script, also 32bit. Have used AutoIT for some years though not a developer or an expert. Almost no errors or problems ever, with any version, so this is weird. So; if I kick off this Wise script/installer wrapper, it tries to run this compiled AutoIT script without waiting for it to return, so that can float around until the user gets a dialog our users have proven to be incapable of following the onscreen directions for; it waits for 1 dialog, next's to the next dialog, unclicks a selection, and clicks next before exiting, so the rest of the wise script can run a 2nd part of the overall install. As said; if I just kick off the AutoIT program manually, then run the installer manually that AutoIT is waiting for the dialog from, it detects those dialogs, does its job, and exits. Compiler output and code follow (I am unable to turn off a/v at work, but if the program was broken by a/v, would it run in the contexts it DOES run in? >"C:\Program Files (x86)\AutoIt3\SciTE\AutoIt3Wrapper\AutoIt3Wrapper.exe" /NoStatus /prod /in "G:\Techlog_Delivery\2011.2.2_AllInOne\AutoIT\TL_RTFI.au3" +>14:40:37 Starting AutoIt3Wrapper v.14.801.2025.0 SciTE v.3.4.4.0 Keyboard:00000409 OS:WIN_7/Service Pack 1 CPU:X64 OS:X64 Environment(Language:0409) +> SciTEDir => C:\Program Files (x86)\AutoIt3\SciTE UserDir => C:\Users\schustec\AppData\Local\AutoIt v3\SciTE\AutoIt3Wrapper SCITE_USERHOME => C:\Users\schustec\AppData\Local\AutoIt v3\SciTE >Running AU3Check (3.3.12.0) from:C:\Program Files (x86)\AutoIt3 input:G:\Techlog_Delivery\2011.2.2_AllInOne\AutoIT\TL_RTFI.au3 +>14:40:37 AU3Check ended.rc:0 >Running:(3.3.12.0):C:\Program Files (x86)\AutoIt3\aut2exe\aut2exe.exe /in "G:\Techlog_Delivery\2011.2.2_AllInOne\AutoIT\TL_RTFI.au3" /out "C:\Users\schustec\AppData\Local\AutoIt v3\Aut2exe\~AU3uhvqhjz.exe" /nopack /comp 2 +>14:40:39 Aut2exe.exe ended.C:\Users\schustec\AppData\Local\AutoIt v3\Aut2exe\~AU3uhvqhjz.exe. rc:0 >14:40:39 Performing the Program Resource Update steps: ...>Updating Program Version information. ...>Setting Program ExecutionLevel Manifest information to asInvoker ...>Setting Program Compatibility Manifest information to Windows8.1 ...>Updating Program Manifest information. >14:40:39 Program Resource updating finished successfully. +>14:40:39 Created program:G:\Techlog_Delivery\2011.2.2_AllInOne\AutoIT\TL_RTFI.exe +>14:40:40 AutoIt3Wrapper Finished. >Exit code: 0 Time: 2.728 #Region ;**** Directives created by AutoIt3Wrapper_GUI **** #AutoIt3Wrapper_Outfile=TL_RTFI.exe #AutoIt3Wrapper_Res_Fileversion=1.0 #AutoIt3Wrapper_Res_Language=1033 #AutoIt3Wrapper_Res_requestedExecutionLevel=asInvoker #EndRegion ;**** Directives created by AutoIt3Wrapper_GUI **** ; ; TL RTFI ; Written: Steve Schumacher ; History: ; 07May2017 Written ; Dialog-Related Const $IAM = "TL_RTFI" Const $TL_COMPLETE_TITLE = "Techlog 2011.2.2 (r100227) Setup" Const $TL_COMPLETE_TEXT = "Installation Complete" Const $TL_RUN_TITLE = "Techlog 2011.2.2 (r100227) Setup" Const $TL_RUN_TEXT = "&Run Techlog 2011.2.2 (r100227)" Const $WAIT_FOR_DIALOG = "300" ; ************************************** ; Techlog completed, block input and ; click Next ; ************************************** $RC = WinWaitActive ($TL_COMPLETE_TITLE, $TL_COMPLETE_TEXT) If $RC = 0 Then MsgBox ( 0, $IAM, "Expected dialog not detected; proceed manually per onscreen instructions" ) Exit (9) Else BlockInput(1) WinActivate ($RC) ;NEXT ControlClick($RC,"",1) EndIf ; ************************************** ; Techlog Finished click OK to run title ; ************************************** $RC = WinWaitActive ($TL_RUN_TITLE, $TL_RUN_TEXT, 10) If $RC = 0 Then BlockInput(0) MsgBox ( 0, $IAM, "Expected dialog not detected; proceed manually per onscreen instructions" ) Exit (9) Else WinActivate ($RC) ; Deselect Run Techlog ControlClick($RC,"",1203) ; Finish ControlClick($RC,"",1) ;Return mouse/keyboard control BlockInput(0) MsgBox ( 0, $IAM, "The rest of the install will now proceed...",6) EndIf Would appreciate any suggestions. While I can't turn off a/v at work, I can rebuild this at home tonight, retest this on a PC that does have a/v turned off, etc. And run what I've already compiled on other Win7-64 PCs and in a Win10 VM this needs to support also. Recompiled 32bit and 64bit, tried 32bit exe from a remote share, this worked perfectly in the desired context on original PC and a Win10 VM. Copied same files to a local directory on the original PC, reran, "Unable to open the script file" again. The directory I created is C:\software\subdir, nothing special about it, no disk errors logged, will retry local on that Win10 VM in a couple of minutes... 5:29pm [7May2017] Copied same exact install files including the AutoIT-built one into a local directory on the Win10 VM, works perfectly, so running local isn't causing the breakage, will try local on another Win7-64bit box...
×
×
  • Create New...