pastermil@sh.itjust.works to Open Source@lemmy.ml · 2 months agoMicrosoft Just Released MS-DOS Source Code!github.comexternal-linkmessage-square19fedilinkarrow-up11arrow-down10
arrow-up11arrow-down1external-linkMicrosoft Just Released MS-DOS Source Code!github.compastermil@sh.itjust.works to Open Source@lemmy.ml · 2 months agomessage-square19fedilink
minus-squarekaty ✨@lemmy.blahaj.zonelinkfedilinkarrow-up1·2 months agoi remember writing .bat files and pretending they were really fancy update scripts when i was like ten they did nothing but it was still fun :)
minus-squareMs. ArmoredThirteen@lemmy.mllinkfedilinkarrow-up1·2 months agoLike half of my job is writing .bat files to automate stuff locally and not tell my boss that all I do anymore is double click the right things in the right order…
minus-squareviking@infosec.publinkfedilinkarrow-up1·2 months agoYou can put in a timeout command at the end, and then call the next .bat file. For example “TIMEOUT /T 60” waits for 60 seconds before resuming, or you can override it by pressing any key. So if you know how long the wait time between scripts is, just write a master.bat and call them in order, with adequate waiting time in between.
i remember writing .bat files and pretending they were really fancy update scripts when i was like ten they did nothing but it was still fun :)
Like half of my job is writing .bat files to automate stuff locally and not tell my boss that all I do anymore is double click the right things in the right order…
You can put in a timeout command at the end, and then call the next .bat file.
For example “TIMEOUT /T 60” waits for 60 seconds before resuming, or you can override it by pressing any key.
So if you know how long the wait time between scripts is, just write a master.bat and call them in order, with adequate waiting time in between.