Re^2: automation on windows

Cool, thanks for pointing out "/t".

But assuming I do not want this script to run all the time, how would I start it from the host? Would I install an ssh-server on the XP-machine and use that to start it or is there a better way on windows?

And how would I automate things that I cannot handle with a command-line switch?

I mean what are the proper tools on Windows when you have to synthesize keyboard or mouse-events? On X I can use e.g. xdotool but I have no idea what to use on Windows - autoit maybe?

Comment on Re^2: automation on windows

Replies are listed 'Best First'.
Re^3: automation on windows by Corion (Patriarch) on Nov 02, 2014 at 08:44 UTC
If you want to send keystrokes or mouse events, you want to use Win32::GuiTest. This usually conflicts with processes started through a service though, becuase Windows permissions disallow sending events from processes started through a service to the desktop (or so I think). If you want to launch a process from the outside, either have an SSH daemon running on the target machine or use WMI (if you are Administrator in your domain) or write a small HTTP server that then launches the target process.	[reply]
Re^3: automation on windows by dissident (Beadle) on Nov 02, 2014 at 17:18 UTC
If you want a quick solution, I'd advise to use the perl script in Corion's first post and autoit for the other stuff. You save yourself the hassle of compiling the package. In autoit you'd have to write just a small script that when acroread windows pop up prints the contents and then closes the acreoreads. A few lines, simple like BASIC. If time is a concern I'd really suggest that heretic, quick and dirty solution..."	[reply]