Corrected incorrect information on step 2 (to do with limitations with parameters).
Added a couple of lines about an auto-installer in step 4.
This instructable will cover the basics of creating your own commands (and even installing them on others computers) which you can use to further cut down the amount of work you need to do.
Some things you should have:
- A Windows computer (preferably modern)
- A USB (for transporting the files around)
- A basic to advanced understanding of the syntax involved with batch commands (this is not a tutorial to help you learn about commands, this is a tutorial about making your own
- Basic computer know how (for instance, knowing how to navigate through folders)
If you don't have a basic understanding of the syntax involved with batch scripts and the like, feel free to either search for a tutorial, ask questions or comment on something you don't understand.
Step 1: What to make?
Most commands have one specific purpose (such as the REN command), and each switch adds some more functionality to that command. Most of these commands were made because it would be impossible to do a certain task (that batch files are commonly used for) without them. Unfortunately, you cannot make a command that will make something possible that has never been possible before (because if you're making it, it's possible). So, the best thing to base your command around is to save time.
So, ask yourself, What do I do frequently that takes a long time to program in?
If you're not that much of the typical "hardcore programmer" (you're using batch here, so not many of you will match that term, it was purely to get my point across), then you might not need a function to save time, because you don't do that much.
In that case, ask yourself something along the lines of Which command lacks something?
That basically means, what command are you not happy with and you think you can do better?
Unfortunately, you can't just modify the code within the commands, so you have to resort to making a new command (such as SETX).
I probably should have explained how the command line (cmd.exe) parses commands. Well, looks like I found my topic for the next section.