bradsmithsite

Why is this closed source when AutoIt is open sourced (at least was). Do you know the creator, is he/she saying it's closed source? Thanks for getting back to me guys. I can't view what TheSaint said because it says "Sorry, we can't show this content because you do not have permission to see it.".

Hi Ilya Shpigor, where can I get the source code for AUT2EXE? Please advise because it's not here: https://github.com/ellysh/au3src http://svn2.assembla.com/svn/anthraxinteractive/encrpytion/emdll/ Where can I find the latest source for this. Please advise. ConsoleWrite("Thank you for the excellent project." & @CRLF)

Excellent. Thanks for the quick response. Seems that was the problem.

Hello. It seems that one or more built-in AutoIt strings functions don't work properly with pipe characters ("|"). I've attatched the full source code. Everything works perfectly with the strings that contain "++" and "&&", but not the one with "||". Why? The ProcessCommandLine function doesn't reference a pipe character! Func Main() Local $TestCommandLineFirst Local $TestCommandLineSecond Local $TestCommandLineThird Local $CommandLineFirst Local $CommandLineSecond Local $CommandLineThird Local $Counter $TestCommandLineFirst = "Welcome to Windows ++ ""This is going to be cool""" ; Works perfectly. $TestCommandLineSecond = "Welcome to Windows || ""This is going to be cool""" ; Something goes wrong! $TestCommandLineThird = "Welcome to Windows && ""This is going to be cool""" ; Works perfectly. $CommandLineFirst = ProcessCommandLine($TestCommandLineFirst) $CommandLineSecond = ProcessCommandLine($TestCommandLineSecond) $CommandLineThird = ProcessCommandLine($TestCommandLineThird) ConsoleWrite("Count: " & $CommandLineFirst[0] & @CRLF) For $Counter = 1 To $CommandLineFirst[0] ConsoleWrite("[" & $CommandLineFirst[$Counter] & "]" & @CRLF) Next ConsoleWrite(@CRLF) ConsoleWrite("Count: " & $CommandLineSecond[0] & @CRLF) For $Counter = 1 To $CommandLineSecond[0] ConsoleWrite("[" & $CommandLineSecond[$Counter] & "]" & @CRLF) Next ConsoleWrite(@CRLF) ConsoleWrite("Count: " & $CommandLineThird[0] & @CRLF) For $Counter = 1 To $CommandLineThird[0] ConsoleWrite("[" & $CommandLineThird[$Counter] & "]" & @CRLF) Next ConsoleWrite(@CRLF) Exit(0) EndFunc Why is the output for the string with "||" broken? As you can see CommandLine.au3 (in the "Source Code.zip") doesn't reference the "|" character at all, but works perfectly when used with "&&" and "++". Count: 5 [Welcome] [to] [Windows] [++] [This is going to be cool] Count: 5 [Welcome] [to] [Windows] [] [] Count: 5 [Welcome] [to] [Windows] [&&] [This is going to be cool] Anyone know why? What am I missing? Source Code.zip

Not cared how old it is, if someone else finds this page, as I did, at least he'll/she'll come right. I landed up here because AutoIt ProcessExists doesn't natively support 16-bit processes, so I made my own. I needed to get a list of running 16-bit processes (if any) so that I could use a .BAT to change the screen resolution to 640x480x8, then run a Windows 3.1 (16-bit) game, wait for the game to finish, and finally restore the screen resolution. Both Process Wait and Sleep (see below) are excellent for running older games that will only run under certain circumstances. StarCraft needs to have EXPLORER.EXE terminated. Shivers must run in 8-bit color. Process Wait is nice because many games don't support the Command Prompt command "START /W". Enjoy! Both of these were written in AutoIt: Process Wait 1.0.1 Used for waiting for 16-bit, 32-bit or 64-bit processes. Includes binaries and source code. http://doropie.com/files/process_wait_1_0_1.zip Sleep 1.0.0 Used for putting the current thread to sleep for a specific number of seconds. Includes binaries and source code http://doropie.com/files/sleep_1_0_0.zip

There you go. Compile and run a Console so that ConsoleWrite works. #NoTrayIcon #RequireAdmin Opt("MustDeclareVars", 1) Func VDMEnumProcessWOW($fp, $lparam) Local $buffer SetError(0) $buffer = DllCall("vdmdbg.dll", "INT", "VDMEnumProcessWOW", "ptr", $fp, "LPARAM", $lparam) If @error <> 0 Then SetError(1) Return 0 EndIf Return $buffer[0] EndFunc Func VDMEnumTaskWOWEx($dwProcessId, $fp, $lparam) Local $buffer ConsoleWrite("PID: " & $dwProcessId & @CRLF) ; Of the 32-bit process. ConsoleWrite(@CRLF) SetError(0) $buffer = DllCall("vdmdbg.dll", "INT", "VDMEnumTaskWOWEx", "DWORD", $dwProcessId, "ptr", $fp, "LPARAM", $lparam) If @error <> 0 Then SetError(1) Return 0 EndIf Return $buffer[0] EndFunc Func TASKENUMPROCEX($dwThreadId, $hMod16, $hTask16, $pszModName, $pszFileName, $lpUserDefined) Local $ModuleName, $FileName Local $Index = StringInStr($pszModName, Chr(0)) ConsoleWrite("Module Handle: " & $hMod16 & @CRLF) ConsoleWrite("Task Handle: " & $hTask16 & @CRLF) ConsoleWrite("Module Name: " & $pszModName & @CRLF) ConsoleWrite("File Name: " & $pszFileName & @CRLF) ConsoleWrite(@CRLF) EndFunc Func PROCESSENUMPROC($dwProcessId, $dwAttributes, $lpUserDefined) Local $Handle2 $Handle2 = DllCallbackRegister("TASKENUMPROCEX", "BOOLEAN", "DWORD;WORD;WORD;str;str;LPARAM") VDMEnumTaskWOWEx($dwProcessId, DllCallbackGetPtr($Handle2), $lpUserDefined) DllCallbackFree($Handle2) EndFunc Local $Handle $Handle = DllCallbackRegister("PROCESSENUMPROC", "BOOLEAN", "DWORD;DWORD;LPARAM") VDMEnumProcessWOW(DllCallbackGetPtr($Handle), 0) DllCallbackFree($Handle) Output sample: PID: 3672 Module Handle: 5919 Task Handle: 5903 Module Name: JMAN File Name: C:PROGRA~1JMANJMAN.EXE Module Handle: 895 Task Handle: 911

AutoIt3.exe is a GUI application so a console isn't allocated for it when it is runs. All console output (i.e. ConsoleWrite) is ignored. We need a console AutoIt3Console.exe that can be called from the command prompt. .au3c files (or whatever) could be registered to run AutoIt3Console so that you could natively run .au3c files from a command prompt by simply typing "clean_temp.au3c". I think using AutoIt to make command line programs would make AutoIt way more useful for creating administrative and miscellaneous utilities. Can't believe a AutoIt3 console interpreter isn't available! Will file a feature request. AutoIt3 isn't made for GUIs. I mean, it's difficult to use AutoIt to create a proper GUI application that's event driven. Message boxes aren't event driven from a coding point of view: Display message box, wait for input (input box), process, show message. Same as console write, wait for input, process and write console. First C/C++ program "Hello World" is usually a console program! Are most AutoIt3 scripts event GUI applications? Mine aren't. Most would run better as console apps, hence why I believe the feature should be added.

I believe the source code for AutoIt is available. I searched the forums but only found a topic written in 2005 that provides a link that's there, but the full source code for the latest version is not. Can someone indicate where to get it?

Thanks for the info. Wasn't sure where to post.

Hi. Can one of the developers please add a #UseConsole condition (or whatever) that forces a call to the Windows AllocConsole API for running console applications without having to compile the code everytime. Also, if a #UseConsole is specified, running a Test.au3 file from the command prompt should attach to the existing console instead of opening a new console, just like a AU3 compiled as "Console". Really driving me crazy to debug. Can one of the developers add it?