At my 1st job using computers, they used to call me "Batch File Billy" because I discovered batch files. The manufacturer of the machines we used left behind a few rudimentary batch files and we used them for a couple of years without knowing anything about them until one day I discovered "Notepad" and opened one up. There was hardly anything there, so then the goal became to add more stuff. So I discovered "commands" and "command line" and "switches" and all sorts of stuff and that is when I realized that the manufacturer really kind of screwed us because with a little bit more effort they could have given us a lot more functionality and saved us a lot of time. Example we were hand copying files by the dozen one at a time from local computers to the network computer when a batchfile could have done them all at the end of the day.
So I wrote one and it worked.
And I used it when I was on the evening shift for a few weeks and when my partner and I switched and I went to Day Shift I told him about my time-saving batch file and he thought it was a good idea and so he used it for a few days until he told his brother on a different machine and his partner was named ROBERT and as soon as ROBERT found out I had initiated something new and "unauthorized" he went squealing like a pig to the Worst Production Manager in the World (our Boss) and ratted me out like the stool pigeon he was.
Was I rewarded? Promoted? Given a raise? A pat on the back? No, no, no and no. I was given an "informal verbal warning" and was told that it could become a "formal verbal warning" and from there a "written warning" if I did not stop with my HOT, BATCH FILE ACTION.
This, btw was the beginning of my entrepreneurial and self-employed identity. I always feel weird when some politician says something like how we need to help people that don't have jobs find jobs and become employees because I really hate employees. All of them. Lazy, stupid, and back-stabbing low-lifes. Every time I read a story about "work place violence" I always hope that the perpetrator got the worst ones first before he was killed "in a hail of gunfire by law enforcement officers".
So yeah, the OP knows me. I also have the nostalgia for the good 'ol days of batch files. So much so that I figured out how to use one and thought I'd post it here. This is a maintance routine that I would use on one of my client's computer systems after their Server started showing hard drive errors. The idea was, instead of leaving the Server on all night long for no reason, and leave it exposed to possible hack attempts on the internet, to shut it down each night at a safe hour, say 8:00 pm, and to schedule a chkdsk to run each morning when "Scheduler" turned it back on. Either the HD would fail or the HD errors would disappear. Once I started running chkdsk every morning, we never saw a single HD error ever again.
So here's the little script I used on a Win2000 Server, in conjunction with the native Windows "Task Manager" or whatever that scheduler program is:
echo y | chkdsk.exe c: /r
shutdown.exe -r -t 01 -f -c "Routine Daily Shutdown"
If I remember right, the "echo y" was to answer the MS pop-up window "Are you sure you want to shut down?" or maybe it was to answer the chkdsk pop-up "Are you sure" (that you want to run chkdsk). I'm just posting it to give an example of how a batch file can still be used today no matter what the Operating System. Now that I think of it, I wonder if I could have shut-down both the Modem and the Wireless router at the same time I sent the Server down, in order to prevent/reduce the window of opportunity for hack attempts on those components also.