AutoIT on Win 7 VM {.exe wont run}

[9252Survive]

Hi All, 

Once again returning back to this great community for much needed help. I am sure that I wont be disappointed and you guys will point me in the right direction. 

To begin with, I am very new here and I have been learning AutoIT. Few months ago I was able to write a script to automate a program to perform some desired task and it has been working great. But, all hell broke lose when I moved this to a Windows 7 VM the script wont even perform the first key commands and after few changes in the code it started working but break intermittently also the compiled scripts wont work at all.  Any help will be much appreciated.  

 

 

Edited March 11, 2016 by 9252Survive

[AutoBert]

Quote

C:\Users\Bert\AutoIt3.My\Temp\asdf.au3"(22,10) : error: can't open include file <_SingleScript.au3>.

Why using a UDF wich isn't standard? And why this UDF isn't attached?

[JohnOne]

EDIT: never mind.

Edited March 9, 2016 by JohnOne

[water]

2 hours ago, 9252Survive said:

But, all hell broke lose when I moved this to a Windows 7 VM the script wont even perform the first key commands and after few changes in the code it started working but break intermittently also the compiled scripts wont work at all.

Can you please be a bit more specific what happens? Do you get any error messages, does the compiled script crash?

[9252Survive]

As you can see there are couple of winwaitactivate in the script...the script keeps waiting for the window even when the window is active and sometimes it detects some other window. The version which works perfectly wont go past that point and the only way I was able to get it working was by re declaring the variable that stores the window title by    WinGetTitle("[ACTIVE]")    ( $TalpacTitle2 = WinGetTitle("[ACTIVE]"))   ( not the best way to do it but this is the only way I was able to get it to see the active window and move forward). Another way would be to create the array of absolute names and then loop through them. I haven't tried that yet but I am so confused now that why wont this work now. This has been working perfectly on workstations and the only difference now is that its on a WIN 7 Virtual Machine. 

[water]

You could add

AutoItSetOption("TrayIconDebug", 1)

at the top of your script so you can see the line number where the script is waiting when moving the mouse over the tray icon.

[9252Survive]

I have this in the script and it shows me where it is pausing. Is this not the same as yours?

 

Opt("TrayIconDebug", 1) ;0=no info, 1=debug line info

[9252Survive]

6 hours ago, AutoBert said:

Why using a UDF wich isn't standard? And why this UDF isn't attached?

AutoBert.... I wanted to use a UDF to keep only on instance running at a time and this seems to work really well.  Is there a standard way to do this? Please advise. 

 

Thanks 

 

 

http://h--e.de/autoit/UDF/_SingleScript.html

[water]

1 hour ago, 9252Survive said:

I have this in the script and it shows me where it is pausing. Is this not the same as yours?

 

Opt("TrayIconDebug", 1) ;0=no info, 1=debug line info

I didn't check your code: tl;dr.
As you know where the problem occurs you could use _ArrayDisplay to show the list of windows returned by WinList and check what AutoIt sees.

 

[AutoBert]

1 hour ago, 9252Survive said:

AutoBert.... I wanted to use a UDF to keep only on instance running at a time and this seems to work really well.  Is there a standard way to do this? Please advise. 

I use therefor _Singleton

[9252Survive]

15 hours ago, water said:

I didn't check your code: tl;dr.
As you know where the problem occurs you could use _ArrayDisplay to show the list of windows returned by WinList and check what AutoIt sees.

 

I think I found the problem ...testing now. But I will also use WinList to test in case the problem persists. 

Thanks 

[Exit]

On 3/9/2016 at 10:33 PM, 9252Survive said:

 

http://h--e.de/autoit/UDF/_SingleScript.html

Source location of _SingleScript() changed to:

http://www.autoitscript.com/forum/index.php?showtopic=178681