Issues sending characters to command line.

[MUIT]

Hi All,

I've been wrestling with this for a few days now and would appreciate a bit of direction.

I'm trying to automate Adobe's AUSST, which syncs a local server with Adobe's updates, much like Microsoft's WSUS.

In their infinite wisdom, their AUSST tool is menu driven from the command line. No parameters exist... other than to specify the root directory. You have to type in a "2" and hit Enter, wait for the sync (could be quite long depending on the amount/size of updates available, no updates available still takes over a minute), then enter "4", hit ENTER to close.

So, here's what I've got currently (I've tried myriad other things)

AutoItSetOption("WinTitleMatchMode", 3)

;due to issues i had with necessary quotes in the launch parameter
local $parm = " --root=""C:\inetpub\www2root\AdobeUpdate\oobee"""

;execution does work, so I'm good to this point
ShellExecute('C:\inetpub\wwwroot\AdobeUpdate\AdobeUpdateServerSetupTool2.0.exe', $parm )

;make sure it is ready for input
sleep(4500)

;test for active
if WinWaitActive("C:\inetpub\wwwroot\AdobeUpdate\AdobeUpdateServerSetupTool2.0.exe") Then

   ;send commands
   Send("2", 1) 
   Send("{ENTER}",1)

   ;let me know an attempt was made
   msgbox (0, "sent", "sent")

EndIf

I plan on doing a very long sleep in place of the msgbox, and then doing the "4" and {ENTER} to quit.

I tried ControlCommand things, and ran into some issues with ControlID (seems it changes for every launch).

if it helps, this is on a Windows2k8 r2 x64 server.

Thanks!

[kylomas]

MUIT,

"Winwaitactive" waits on a "window". You seem to be waiting on a process. You might try using the "window" title or use the "processexists" function.

kylomas

[LarryDalooza]

Try getting the handle of the window and ControlSend to that handle. I believe that is how I used to do it.

Lar.

[MUIT]

So, now after more fiddling, I've got:

AutoItSetOption("WinTitleMatchMode", 3)

local $parm = " --root=""C:\inetpub\www2root\AdobeUpdate\oobee"""

ShellExecute('C:\inetpub\wwwroot\AdobeUpdate\AdobeUpdateServerSetupTool2.0.exe', $parm )

sleep(4500)


if WinWaitActive("C:\inetpub\wwwroot\AdobeUpdate\AdobeUpdateServerSetupTool2.0.exe") Then
WinActivate("C:\inetpub\wwwroot\AdobeUpdate\AdobeUpdateServerSetupTool2.0.exe")
Send("2", 1)

ControlSend("C:\inetpub\wwwroot\AdobeUpdate\AdobeUpdateServerSetupTool2.0.exe","","[CLASS:ConsoleWindowClass]","{ENTER}",1)

; Send("{ENTER}",1)
msgbox (0, "sent", "sent")

EndIf

The "2" shows up in the window, but it appears that no "enter" key is entered.

Per LarryDalooza, I managed to get the handle, and use it as a variable to do a control send, and ran into this same issue.

Kylomas, There is a window activated by this process, it's a console/CMD window. It must be able to reference it, since I can now get the "2" to appear.

MUIT

[BrewManNH]

ControlSend is only unreliable for command prompts as that works differently to normal windows (seems to check physical states rather than accepting the keystroke messages).