Leaderboard

Au3toCmd --- Avoid false virus positives Since many virus scanners sometimes prevent a "compiled autoit EXE" from being executed as "false positive", the "*.A3X" format is a suitable format to avoid this problem. See here for more information. In order to simplify this procedure, I wrote the Au3toCmd script. Here a *.Cmd file is generated from a *.Au3 file. The necessary files Autoit3.exe and *.A3x are added to the "*.Cmd" file as "alternate data streams" "Base64" encoded data. Now the Autoit Script can be called by clicking on the cmd file and the anti-virus scanners do not recognize the "false positive". If the short-term flashing of the CMD window bothers you, you can click the desktop shutcut that runs in a minimized window. Unfortunately, because the "alternate data streams", this CMD file cannot be distributed via FTP or email. Only a USB sti ck or removable disk formatted with NTFS can be used. As the new version now uses Base64 data instead of ADS, this statement is out of date. For reasons of compatibility, the old version was sunk into the spoiler here. The script can be called with a file name of an AU3 script as a parameter. If no name is entered, a query is made. For more information, see the header of the script. Suggestions, improvements and bug reports are welcome. Here the versions using base64 data Version: 2022.05.12 (Support blanks in pathnames) Version: 2022.06.23 (Support release candidates. Changed @CrLf to @Lf. Annual cleaning. Optimized #AutoIt3Wrapper handling) Version: 2022.07.22 (Support scripts with the same name but different content in different directories) Version: 2022.07.27 (Support blanks in usernames) Au3toCmd.au3 Version: 2022.09.01 (Optimized annual cleaning) Au3toCmd.au3

Just think about what I have stated and test with it so you understand... Jos

Thank you, Exit. I appreciate your detailed explanation. I knew it was something simple I had read earlier that I didn't properly test. I love AutoIt so much. This will allow me to share what I've created over the years with so many non-programmer people. You are the best. taurus905

Here my directions: ;~ Global $p_Example_Folder = @ScriptDir & "\Example\"   Global $p_Example_Folder = @WorkingDir ;~ $p_Ini_File = @ScriptDir & "\" & $s_Program_Name & ".ini"    $p_Ini_File = @WorkingDir & "\" & $s_Program_Name & ".ini" Because *.a3x is in the @scriptdir but *.cmd is in the @workingdir And you want the *.ini file in the *.cmd directory. I hope it helps.

Likely a WorkDir issue as your file references are relative! so make sure you do a FileChangeDir(@ScriptDir) at the start of your script.

Dlls for windows are here and here, for Windows CE here, as detailed on the very zlib homepage you referred to (and apparently didn't read; there are also .NET implementations, including dll wrapper in C# if that floats your boat). Since zlib is (and I quote) it would make sense that the authors provided the source code first and foremost, not a particular platform-specific implementation. You could just compile it as a dll yourself; I did this a few months ago for my Eigen4AutoIt environment; works great.

Added a link to this thread to the AutoIt wiki.

Why not reset $Image_Dowhile_Loop_Break after the Do/Until loop?

I may be a wee bit late to the party, but I just wanted to show my appreciation for this awesome project! It's quite remarkable what can be done with only a CMD file. 😲

Part of what you need could be provided by CodeScanner (link in my signature), notably: all code entry & exit points all user function definitions and function calls (native and UDF) all loops (type, start point, end point) all conditional evaluations (branching points), referrred to here as "phrases" EDIT: you would have to run CodeScanner on your target script (with all relevant options enabled) and then analyse/trace through the "references.txt" array in the generated CS subdirectory.

Search for larsj topic on colors in LV...