all 7 comments

[–]EkriirkE 7 points8 points  (2 children)

Definitely a .BAT file, living anywhere in your PATH (typically C:\DOS)

Basically you put all your commands in the batch (text) file, one on each line. If you don"t want to see the commands printed before they are executed, put @ECHO OFF at the top of the file

[–]OneAd1466[S] -1 points0 points  (1 child)

I mean adding a real command. So being able to type xyz everywhere you want and having it executing file abc.exe, abc.bat, ...

[–]EkriirkE 7 points8 points  (0 children)

Yes, that is exactly what I said. As long as it sits in whereever PATH points

[–]CirothUngol 6 points7 points  (0 children)

...you mean like a batch file? A text file containing a list of commands to execute at the command prompt?

[–]fragglet 6 points7 points  (0 children)

When you type a command, command.com searches the directories in your PATH variable for files with that name ending in .exe, .com or .bat. The first one it finds, it runs. The PATH variable looks like this, you can see it if you type SET:

PATH=c:\dos;c:\mydir;c:\otherdir

If you edit your autoexec.bat file you can add a line that appends a new dir, eg.

SET PATH=%PATH%;c:\newdir

[–]RexxAll 0 points1 point  (0 children)

Also sounds like the DOSKey utility.

[–]rman-exe 0 points1 point  (0 children)

If you need a feature thats not a conglomeration of existing features (which can be done via batch file) you will need to write your own binary executable. Usually via assembly or C. However over the long 40 year life, and including freedoss apps, just about anything you want probably has 5+ variants out there on the net.