Compile errors with Full version of ScITE

[Jos]

where can i get v3.3.9?

'?do=embed' frameborder='0' data-embedContent>>

Jos

[iamtheky]

Jos, I have no doubt you are correct, I am sure myk3 is all over testing the beta.  That was more at the ridiculous antivirus conversation.

Edit:  oh nice, yall spoke while i was replying.

Edited November 18, 2013 by boththose

[Jos]

Jos, I have no doubt you are correct, I am sure myk3 is all over testing the beta.  That was more at the ridiculous antivirus conversation.

Understood and wasn't directed at you. You actually gave the key information for me to understand what was happening.

It just puzzles me how people are able to pollute a thread with posts while we were getting close to the solution/explanation.

Jos

Edited November 18, 2013 by Jos

[iamtheky]

I know.  Im busy trying to get to 1000 and people want to ruin threads with nonsense.

[iamtheky]

Edited November 18, 2013 by boththose

[Jos]

Only 20,846+1 to go

Edited November 18, 2013 by Jos

[myk3]

Selected "Beta: Ver.3.3.9.22" from the compile options with the same result.. 

>"C:\Program Files (x86)\AutoIt3\SciTE\AutoIt3Wrapper\AutoIt3Wrapper.exe" /ShowGui /in "C:\Images\Security Discs\Oct2013SecDisc\IAVA_Updates_OCT13_SecDisc.au3"
+>13:21:23 Starting AutoIt3Wrapper v.2.1.3.0 SciTE v.3.3.6.0 ;  Keyboard:00000409  OS:WIN_7/  CPU:X64 OS:X64    Environment(Language:0409  Keyboard:00000409  OS:WIN_7/  CPU:X64 OS:X64)
-> 1 Change(s) made.
>Running AU3Check (1.54.22.0)  from:C:\Program Files (x86)\AutoIt3
+>13:21:29 AU3Check ended.rc:0
>Running:(3.3.8.1):C:\Program Files (x86)\AutoIt3\aut2exe\aut2exe.exe  /in "C:\Images\Security Discs\Oct2013SecDisc\IAVA_Updates_OCT13_SecDisc.au3" /out "C:\Users\IMAGESVR\~AU3bqvgkfe.exe" /nopack /icon "C:\Images\Security Discs\Oct2013SecDisc\App.ico" /comp 2
+>13:26:41 Aut2exe.exe ended.C:\Users\IMAGESVR\~AU3bqvgkfe.exe. rc:0
>13:26:41 Performing the Program Resource Update steps:

why does it still say "Running:(3.3.8.1)"?

EDIT: that was odd... I got it to use the actual beta now, pending compile.. 

Edited November 18, 2013 by myk3

[iamtheky]

Even if it works.  That doesnt answer what is different between the current production full Scite and stock the version, such that the built-in version can compile this with the desired output but the Full Scite cannot.

Does Post #23 suggest that if we give the script no directives that it should compile fine because it is not encountering this resources issue?

Is there a fun compile directive or command that can be used to have it compile everytime in a similar fashion to the simple built in GUI and ignore any other fun directives we decided that we suddenly need.

Edited November 18, 2013 by boththose

[Jos]

@myk3: do Alt+F7 to compile with the Beta version.

@boththose: The difference is that the Full SciTE4AutoIt3 runs AutoIt3Wrapper which processes&performs the #AutoIt3_xxx Directives . The Lite version of SciTE coming with the AutoIt3 installer merely runs Aut2exe and won't do anything else.

So when you have a Directive in the script to change the Executionlevel it will only perform that action when AutoIt3Wrapper is ran.

Jos

Edited November 18, 2013 by Jos

[myk3]

@myk3: do Alt+F7 to compile with the Beta version.

Jos

 

This seems to have fixed the issue, but it takes about 15 10 min to compile, and i am compiling on a dual xeon system with 16GB ram.. the stock ScITE only takes maybe 5 min.. 

>"C:\Program Files (x86)\AutoIt3\SciTE\AutoIt3Wrapper\AutoIt3Wrapper.exe" /beta /in "C:\Images\Security Discs\Oct2013SecDisc\IAVA_Updates_OCT13_SecDisc.au3"
+>13:43:27 Starting AutoIt3Wrapper v.2.1.3.0 SciTE v.3.3.6.0 ;  Keyboard:00000409  OS:WIN_7/  CPU:X64 OS:X64    Environment(Language:0409  Keyboard:00000409  OS:WIN_7/  CPU:X64 OS:X64)
>Running AU3Check (3.3.9.22)  from:C:\Program Files (x86)\AutoIt3\Beta
+>13:43:28 AU3Check ended.rc:0
>Running:(3.3.9.22):C:\Program Files (x86)\AutoIt3\Beta\aut2exe\aut2exe.exe  /in "C:\Images\Security Discs\Oct2013SecDisc\IAVA_Updates_OCT13_SecDisc.au3" /out "C:\Users\IMAGESVR\~AU3xzxjuao.exe" /nopack /icon "C:\Images\Security Discs\Oct2013SecDisc\App.ico" /comp 2
+>13:51:57 Aut2exe.exe ended.C:\Users\IMAGESVR\~AU3xzxjuao.exe. rc:0
>13:51:57 Performing the Program Resource Update steps:
...>Setting Program ExecutionLevel Manifest information to asInvoker
...>Updating Program Manifest information.
>13:53:21 Program Resource updating finished successfully.
+>13:53:22 Created program:C:\Images\Security Discs\Oct2013SecDisc\Oct2013SecDisc\IAVA_Updates\IAVA_Updates_OCT13_SecDisc.exe
>Exit code: 0    Time: 594.905

Edited November 18, 2013 by myk3

[myk3]

@myk3: do Alt+F7 to compile with the Beta version.

@boththose: The difference is that the Full SciTE4AutoIt3 runs AutoIt3Wrapper which processes&performs the #AutoIt3_xxx Directives . The Lite version of SciTE coming with the AutoIt3 installer merely runs Aut2exe and won't do anything else.

So when you have a Directive in the script to change the Executionlevel it will only perform that action when AutoIt3Wrapper is ran.

Jos

 

Does that include having #requireadmin? 

I have done that in the past with the stock ScITE and it forced admin..

EDIT: Never mind im an idiot... 

Edited November 18, 2013 by myk3

[Jos]

Does that include having #requireadmin? 

I have done that in the past with the stock ScITE and it forced admin..

I was solely talking about the #AutoIt3Wrappe_*****  directives! These are added by me and supported via AutoIt3Wrapper.

Look at the SciTE4AutoIt3 helpfile for the list of supported AutoIt3Wrapper Directives. Ctrl+f1

Look at the Autoit3 Helpfile for the AutoIt3 internal supported Directive. F1

Any none supported Directive is ignored by AutoIt3 which allows other tools to recognise their own directive.

I also have #Tidy_** and #Obfuscator_** directives which are used by the respective programs.

 

Jos

Edited November 18, 2013 by Jos

[myk3]

Speed comparison ...

No directives on 3.3.8.1 Only 5 min.. 

>"C:\Program Files (x86)\AutoIt3\SciTE\AutoIt3Wrapper\AutoIt3Wrapper.exe" /ShowGui /in "C:\Images\Security Discs\Oct2013SecDisc\IAVA_Updates_OCT13_SecDisc.au3"
+>14:01:06 Starting AutoIt3Wrapper v.2.1.3.0 SciTE v.3.3.6.0 ;  Keyboard:00000409  OS:WIN_7/  CPU:X64 OS:X64    Environment(Language:0409  Keyboard:00000409  OS:WIN_7/  CPU:X64 OS:X64)
-> No changes made..
>Running AU3Check (1.54.22.0)  from:C:\Program Files (x86)\AutoIt3
+>14:01:14 AU3Check ended.rc:0
>Running:(3.3.8.1):C:\Program Files (x86)\AutoIt3\aut2exe\aut2exe.exe  /in "C:\Images\Security Discs\Oct2013SecDisc\IAVA_Updates_OCT13_SecDisc.au3" /out "C:\Users\IMAGESVR\~AU3muveosh.exe" /nopack /comp 2
+>14:06:27 Aut2exe.exe ended.C:\Users\IMAGESVR\~AU3muveosh.exe. rc:0
+>14:06:27 Created program:C:\Images\Security Discs\Oct2013SecDisc\IAVA_Updates_OCT13_SecDisc.exe
>Exit code: 0    Time: 320.979

[myk3]

 

Speed comparison ...

No directives on 3.3.8.1 Only 5 min.. 

>"C:\Program Files (x86)\AutoIt3\SciTE\AutoIt3Wrapper\AutoIt3Wrapper.exe" /ShowGui /in "C:\Images\Security Discs\Oct2013SecDisc\IAVA_Updates_OCT13_SecDisc.au3"
+>14:01:06 Starting AutoIt3Wrapper v.2.1.3.0 SciTE v.3.3.6.0 ;  Keyboard:00000409  OS:WIN_7/  CPU:X64 OS:X64    Environment(Language:0409  Keyboard:00000409  OS:WIN_7/  CPU:X64 OS:X64)
-> No changes made..
>Running AU3Check (1.54.22.0)  from:C:\Program Files (x86)\AutoIt3
+>14:01:14 AU3Check ended.rc:0
>Running:(3.3.8.1):C:\Program Files (x86)\AutoIt3\aut2exe\aut2exe.exe  /in "C:\Images\Security Discs\Oct2013SecDisc\IAVA_Updates_OCT13_SecDisc.au3" /out "C:\Users\IMAGESVR\~AU3muveosh.exe" /nopack /comp 2
+>14:06:27 Aut2exe.exe ended.C:\Users\IMAGESVR\~AU3muveosh.exe. rc:0
+>14:06:27 Created program:C:\Images\Security Discs\Oct2013SecDisc\IAVA_Updates_OCT13_SecDisc.exe
>Exit code: 0    Time: 320.979

 

the question now is how do I include things like an icon and destination path without directives.. 

[Jos]

the question now is how do I include things like an icon and destination path without directives.. 

 

I am not sure why the new Beta takes 8:29 minutes compared to Production using 5:13, but as I mentioned before earlier in this thread, I wouldn't add a larger file to the AutoIt3 compiled script but use it as a separate selfextracting EXE to avoid having to add it and need for redistribution of the larger updated script.

I also further indicated that only resource updates would give you the error, si updating the ICON or Outputpath by using the #AutoIt3Wrapper directive won't give you the issue.

It is only when you use any of the Version;Addfile or Manifest update #AutoIt3Wrapper directive you get the issue.

Jos

[mLipok]

Sorry for urgency and stupid questions.

But as I said I had the same problem a long time ago.

I wanted to help, and understand.

 

Now I can only apologize for the confusion.

 

mlipok

[Jos]

 

Sorry for urgency and stupid questions.

But as I said I had the same problem a long time ago.

I wanted to help, and understand.

 

Now I can only apologize for the confusion.

 

mlipok

 

No worries, I know you mean well.

[myk3]

I am not sure why the new Beta takes 8:29 minutes compared to Production using 5:13, but as I mentioned before earlier in this thread, I wouldn't add a larger file to the AutoIt3 compiled script but use it as a separate selfextracting EXE to avoid having to add it and need for redistribution of the larger updated script.

I also further indicated that only resource updates would give you the error, si updating the ICON or Outputpath by using the #AutoIt3Wrapper directive won't give you the issue.

It is only when you use any of the Version;Addfile or Manifest update #AutoIt3Wrapper directive you get the issue.

Jos

 

Looks like with just these two options it works..

#Region ;**** Directives created by AutoIt3Wrapper_GUI ****
#AutoIt3Wrapper_Icon=App.ico
#AutoIt3Wrapper_Outfile=Oct2013SecDisc\IAVA_Updates\IAVA_Updates_OCT13_SecDisc.exe
#EndRegion ;**** Directives created by AutoIt3Wrapper_GUI ****

[iamtheky]

Jos ,

In this manner we limit and control what the user sees on the disc.  A single file that does it all regardless of your flavor of our system.  Our instructions could literally consist of  "double click everything on the disc because you are going to anyway, when you get to the one executable item it will patch your system and restart."