Automation

AutoIt has had a steady year. It is still the same small, practical Windows automation language, but the recent v3.3.6.x updates make it a little nicer for real work: better file handling, better Unicode support, more control over Windows controls, and useful fixes for 64-bit systems. If you already use AutoIt for installers, log collection, desktop shortcuts, or help desk tools, this is not a dramatic rewrite. It is more like a maintenance release that removes a few daily annoyances. ...

Windows automation in 2005 is a two-tool world for many of us: batch files for command-line friendly tasks, and AutoIt when the job requires clicking through GUI dialogs. Neither is “better.” They solve different problems, and most experienced admins use both. When Batch Files Win Batch is ideal when: Programs expose command-line switches — xcopy, robocopy on XP Pro, net use, installers with /silent or /S You schedule tasks with Task Scheduler You chain simple steps: map drive, copy logs, start service, exit You want zero extra runtime installed on the target machine Example — nightly log backup: ...

If you spend a lot of time on Windows machines, you probably have a few jobs that are boring enough to be annoying but too small to justify writing a full application. Clicking through installers, copying log files, filling out the same dialog boxes, starting a group of tools every morning, or checking whether a window appeared correctly are all good examples. That is exactly where AutoIt is useful. AutoIt is a small Windows scripting language designed for automating the graphical user interface. It can run programs, wait for windows, send keystrokes, click buttons, work with files, show message boxes, read and write simple configuration files, and compile scripts into standalone executables. The syntax is BASIC-like, which makes it approachable even if you do not think of yourself as a programmer. ...