Jump to content

mkornuser

Members
  • Posts

    8
  • Joined

  • Last visited

Everything posted by mkornuser

  1. Hello! I wanted to ask, how to exit a compiled AutoIT-Exe properly when the script crashes. My Problem is, that i get a msgbox "error in line xxx", but i dont want this. Instead i want the exe to exit, so another instance is able to run. I know how to "syntaxcheck prod" but i need this in case of any unpredictable bugs in the script code. Thanks!!
  2. Thank You! Where can I get an old Version from?
  3. Thank u for your answer! This is ok and running. But when it is compiled, i cant debug anymore. The .exe is standalone, so there is no connection to the Autoit Debugger. I am trying to debug a script which needs command line arguments to run. BTW what is this field for in the Autoit Debugger, which is called "command line arguments" (in Autoit Debugger Options)?
  4. First of all tnx to Stumpii for this excellent debugger!! Have some issue here: Please could someone explain how to use it with command line arguments. I read the manual but doesnt work. Tried it via "Autoit Debugger Options" too, but cmdline[0] still stays empty.
  5. Hello! I try to send an UDP-Packet to a machine xx port yy. UDPsend always returns the number of bytes sent, wether the target-Port on the server-side is listening, or not. (thats ok, just like stated in AutiIT-Help) When the Target-Port is not listening, the Target alway sends back an ICMP-packet containg "destination unreachable" and "port unreachable" . My question is, how to deal with this message to take action in autoit-script? How can i get a handle to this ICMP-message,? tnx!
  6. Its not the script and its not PSexec itself. Just copy any given autoit-compiled-exe to system32 on a 64bit-System and it wont work, cause it doesnt find its own decompressed script. Any hints for that?
  7. Hi there! Im having a problem with my Autoit-Script converted to 32-Bit-Exe to run on Windows 2003 Server X64 via PSExec. X64 converted Exe-Script hasnt any problem on X64-Windows, but i wanted to use the exe on x86 too, so this is no option. The problem occurs when exe is copied and run via Psexec to remote-machine (e.g. psexec \\serverX64 -c -f script.exe) The Exe then resides in system32-Folder and is executed. When its executed it then decompresses its script and trys to execute it in SysWOW64-Folder, but its not there. Then it shows an error message: Unable to open the script file. Executing the exe in any other folder than system32 works, but psexec always uses system32 as the remote-target for execution. So: Any ideas how to execute an 32bit-exe in system32 on WindowsX64? tnx for any suggestions!
×
×
  • Create New...