{"id":2233,"date":"2017-01-21T11:54:32","date_gmt":"2017-01-21T11:54:32","guid":{"rendered":"http:\/\/www.gssezisoft.com\/main\/?page_id=2233"},"modified":"2018-07-23T22:25:46","modified_gmt":"2018-07-23T22:25:46","slug":"batchtools","status":"publish","type":"page","link":"http:\/\/www.gssezisoft.com\/main\/batchtools\/","title":{"rendered":"Batch Tools"},"content":{"rendered":"

\"BatchTools\"\n<\/p>\n

Batch files are a fast and simple way of automating mundane things. There’s not a lot to them – if you can type in a command, you can type up a batch file. It’s about as easy as it gets and it has been built into every version of Windows since before even Windows.<\/p>\n

There are a lot of pluses to batch files. They don’t need compiling so updates are simple: just edit the file and rerun it. In a sense, they’re even portable between devices and operating systems. The "in a sense" is that all operating systems support them. Again, this also goes back to before Windows existed; and even to before MSDOS existed.<\/p>\n

Paths<\/h2>\n

The downside to batch files is that in a modern era of large hard disk sizes, we typically have very long paths to find a specific file.<\/p>\n

The workarounds normally involve starting your batch file in the right directory and that simplifies paths to the required files; but it also means you can’t run the same batch file to do the same things with a different set of files elsewhere. You can end up with two (or three, or four, …) copies of the same batch file. The one batch file gets saved with each set of files that might need it. Updating the batch file becomes complicated because you have to find and update all the copies. Shortcuts to a single copy but with different "Start in" directories work better; but you are still left wondering, "which set of files is this shortcut going to process?"<\/p>\n

Wouldn’t it be easier if you could just pick the set of files when you run the batch file? Wouldn’t that save having to have a copy (or a shortcut) for every directory that might ever contain a set of files?<\/p>\n

User Input<\/h2>\n

In the Windows environment, batch files also suffer from a lack of user input. You can run a batch file, and it can tell you some things (like with the "echo …" command); but it can’t ask questions. You have to specify everything it needs to know, on the command line when you run the batch file.<\/p>\n

That’s not great, but it does work – provided you are at a command prompt. That doesn’t work at all if you double-click a batch file from Windows Explorer.<\/p>\n

What if you could ask questions in a batch file? You wouldn’t have to remember all the settings that are available for every batch file you have. You wouldn’t have to get their order right on the command line. You could just double-click a batch file and answer the questions.<\/p>\n

How to Build Better Batch Files<\/h1>\n

The BatchTools programs include: say.exe, ask.exe and run.exe. They allow you to:<\/p>\n