Speeding Up MS‑DOS Workflows with DOSKEY Aliases

Problem: Repetitive Typing in a 640 KB World

In a plain MS‑DOS prompt every command is typed manually. Common patterns—listing directories, copying files, deleting temporary data—quickly become a source of keystrokes and errors. The built‑in DOSKEY utility offers a lightweight way to create short aliases and macros, but many users discover that the aliases disappear after closing the prompt or that they cannot be used inside batch files without extra work.

Thesis: DOSKEY is the right tool, but you must understand its syntax, persistence, and inheritance rules to avoid pitfalls.

1. Alias Syntax and Macro Arguments

The basic form is:

DOSKEY alias=command

Examples:

• DOSKEY ll=DIR /B /A:D – lists only directories in bare format.
• DOSKEY copyfile=COPY $1 $2 – copies the first argument to the second.

When a macro uses arguments, $1 through $9 represent the first to ninth words typed after the alias. $* expands to the entire argument string. Special tokens include $T (current time), $E (escape character), and $G (the ‘>’ character).

2. Making Aliases Persistent

Aliases live only in the current command session. To make them available every time MS‑DOS boots, add the DOSKEY lines to AUTOEXEC.BAT (or a script that AUTOEXEC.BAT calls). The file must reside in the root of the active drive and be executed before the command prompt appears.

1. Open AUTOEXEC.BAT in a plain text editor.
2. Add the alias definitions, e.g. DOSKEY ll=DIR /B /A:D.
3. Save and reboot.
4. Open a command prompt and type ll to confirm the alias works.
5. Run DOSKEY /L to list all active aliases and verify persistence.

Checking the Result

After booting, the command DOSKEY /L will print each alias on its own line. If an alias is missing, double‑check that AUTOEXEC.BAT is on the correct drive and that no syntax errors (e.g. stray spaces around the equals sign) exist.

3. Using Aliases Inside Batch Files

Batch files do not automatically inherit DOSKEY aliases. To use an alias inside a batch script you must first define it in that context or use the full command. A common pattern is:

@echo off
REM Define the alias for this batch run
DOSKEY copyfile=COPY $1 $2

REM Now the alias is usable
copyfile %1 %2

Because the alias is defined only for the current batch execution, it does not affect other command prompts. If you need the alias globally, keep it in AUTOEXEC.BAT.

4. Practical Example: A Minimal AUTOEXEC.BAT

Below is a ready‑to‑copy example that defines three useful aliases and demonstrates persistence. Place this file on the root of your boot drive before rebooting.

@echo off
REM --- Alias definitions ---
DOSKEY ll=DIR /B /A:D
DOSKEY ls=DIR /B
DOSKEY copyfile=COPY $1 $2
REM --- End of aliases ---

After reboot:

• Typing ll lists only directories.
• Typing ls lists all files and directories.
• Running copyfile file1.txt file2.txt copies file1.txt to file2.txt.

5. Trade‑offs and Limitations

• Session‑Only by Default: Without AUTOEXEC.BAT the aliases vanish after the prompt closes.
• Memory Footprint: Each alias consumes a few bytes of conventional memory. On very small systems you may hit the 640 KB ceiling if you define many aliases.
• Batch Inheritance: Batch files must explicitly define the alias or use the full command; otherwise the alias is unknown.
• Availability: DOSKEY ships with MS‑DOS 5.0 and later, and also with the Windows NT/2000/XP command prompt. The syntax is identical, but the environment may differ (e.g., Windows uses a different memory model).
• Comment Syntax: In batch files comments start with REM or ::; the hash symbol (#) is not a comment character.

6. Actionable Checklist

1. List the commands you use most frequently.
2. Draft DOSKEY lines with appropriate macro arguments.
3. Add them to AUTOEXEC.BAT (or a dedicated startup script).
4. Reboot and run DOSKEY /L to confirm persistence.
5. Test each alias in a fresh command prompt.
6. If you need to use an alias inside a batch file, include a DOSKEY definition at the top of that file.
7. Monitor memory usage on very small systems; if you hit the 640 KB limit, reduce the number of aliases.

By following these steps you can turn a clunky MS‑DOS prompt into a quick‑access toolbox that saves keystrokes and reduces typing errors.