Jump to content
Barrtrek

Aut2exe.exe ended errors when compiling with large fileinstall

Recommended Posts

I get the "Unable to add resources" error related to AppData\Local\AutoIt v3\Aut2Exe when compiling with a large FileInstall of a 1.5GB file.  Is there a size limit I need to be aware of?  I've also disabled or removed Trend from three different machines and had the same results.  I've had issues like this in the past but have compiled after the Aut2Exe folder was excluded in AV.  That doesn't seem to be the problem this time around.  If I comment out the FileInstall the script compiles successfully.

Edited by Barrtrek

Share this post


Link to post
Share on other sites

I regularly compile large AutoIt applications with lots of files totalling around 25 Mb for the compiled exe. One cause may be your anti virus program trying to check you newly compiled application before AutoIt has finished including all the files needed for fileinstall.  


"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to build bigger and better idiots. So far, the universe is winning."- Rick Cook

Share this post


Link to post
Share on other sites

I would never make a compiled script with a 1.5gb "attachment"!
What I have done is the past is zip up 1.5Gb file and distribute that together with the installer script to all PC's for a software upgrade.The advantage of that approach was that I could update the script logic without have to distribute the large installer file again.

Why do you want to include this size file in the actual compiled script?  

Jos

Edited by Jos

Share this post


Link to post
Share on other sites

Bowmore... I've already exhausted AV as the cause by having the folder excluded and also testing on a machine with no AV.

Jos... Management wanted one installer (O365) for low bandwidth locations in South America.  I was initially able to compile with large fileinstalls but have had this error crop up more recently.  As it turns out we have already started to go in the direction you did by separating the large fileinstall from the main script.  they just have to place the file in the right spot for the script to find it.

Thanks for the input guys!

 

Share this post


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

  • Similar Content

    • By SgtHugoStiglitz
      HI people,
                        I got a questions, I maintain code in autoIT and every time I compile a new version or modification, Scite generate 2 folders. One folder is finish by released and the other is tentative. I try to make some google search, but never find answer would satisfied myself. The dev who was maintain it before were using AutoIt3Wrapper_GUI, and I don't know if it's related. I look both folder, but they seem pretty identical, but I would like to know what it's the difference between those to folder. Anyone have a clue?
    • By Rhidlor
      I don't have any experience compiling AutoIt scripts or know of any best practices regarding said scripts so I was wondering, what are some of the options for passing data to complied scripts? Here's an example of what I mean by "option": Writing data to a text file, then running a script which reads the data from that text file.
      Thanks!
      I apologize if this topic is a little lackluster
    • By lonardd
      Hi,
      I have a source Script where I inserted the following code lines to be able to extract the script source code anytime later if I run it with the /ExtractSourceCode:
      #Region ;**** Directives created by AutoIt3Wrapper_GUI ****
      #AutoIt3Wrapper_UseX64=n
      #AutoIt3Wrapper_Change2CUI=y
      #AutoIt3Wrapper_Res_SaveSource=Y
      #EndRegion ;**** Directives created by AutoIt3Wrapper_GUI ****
      If StringInStr($cmdlineRaw, "/ExtractSourceCode") Then
          FileInstall(@ScriptFullPath, @ScriptDir & "\" & @ScriptName & ".txt", 1)  
          ;FileInstall("C:\Test.txt", @ScriptDir & "\Test.txt")
          Exit
      EndIf
      I used to be able to compile it on another computer some years ago without problems.
      Now I wanted to modify the code, so I extracted it, renamed the file *.au3, performd my little modification and rebuild.
      Strangely, I get this popup with Caption: Aut2Exe Error and Invalid FileInstall() function.
      BEfore I hit the OK button on the Popup, I can see the file is actually Built as I can see that an EXE file is created, but as I hit OK in that error dialog, the EXE disappears.
      Any advice?
      Thanks
      David
      I can't remember if I did it with Autoit 2 
      EPP_NF_Replacer_UBI.au3
    • By Skeletor
      Hey All,
      Yes, this is an odd request. 
      But is there a way to bulk up the size of the compiled program? 
      I know many want to reduce it's size, but I want to increase it.
      What methods do you suggest?
    • By dimm
      Is it possible to compile script without any icon resources included?
      When I make exe it uses default system icon of current OS even if I compile as console application.
      On other versions of Windows it looks a little strange

       
      Update:
      It seems that the only way is remove icons from exe after compilation using resource editors like ResHacker.

       
      another bad solution:
      Using corrupted 35 bytes icon file. Windows can't load it and shows default system icon.
      #pragma compile(Icon, broken.ico) broken.ico
×
×
  • Create New...