{"id":14054,"date":"2026-06-10T02:00:00","date_gmt":"2026-06-10T06:00:00","guid":{"rendered":"https:\/\/www.both.org\/?p=14054"},"modified":"2026-05-20T10:37:55","modified_gmt":"2026-05-20T14:37:55","slug":"a-gentle-introduction-to-freedos-commands","status":"publish","type":"post","link":"https:\/\/www.both.org\/?p=14054","title":{"rendered":"A gentle introduction to FreeDOS commands"},"content":{"rendered":"
\r\n
\r\n \r\n <\/i>\r\n <\/a>\r\n 1 <\/span>\r\n<\/div><\/div>\n

If you’ve tried FreeDOS and have any familiarity with Linux, you might have been confused a bit by the command line. The DOS commands are slightly different from how you might use the Linux command line, so getting around on the command line requires learning a few new commands.<\/p>\n\n\n\n

But it doesn’t have to be an “all new” experience for Linux users. We’ve always included some standard Unix commands in FreeDOS, in addition to the DOS commands that are already similar to Linux. So if you’re already familiar with the Linux command line, try these commands to help ease into FreeDOS:<\/p>\n\n\n\n

Getting Around<\/h2>\n\n\n\n

Use the CD<\/code> command to change directory in the FreeDOS filesystem. Like all DOS commands, the command name is actually case insensitive<\/em>, so you can use CD<\/code> or cd<\/code> it will work the same; I’ll use lowercase for these examples. The usage is basically the same on FreeDOS as it is on Linux. To change into a subdirectory called apps<\/code>, type cd apps<\/code>. Or type cd ..<\/code> to go back to the previous directory.<\/p>\n\n\n\n

One key difference when navigating through directories and paths is that on FreeDOS, the directory separator is \\<\/code> (“backslash”) instead of \/<\/code> (“forward slash”) that you use on Linux. For example, let’s say you were in the \\devel<\/code> directory and you wanted to move to the \\fdos<\/code> directory. Both of those are at the same “level” relative to the root directory. So you could type cd ..\\fdos<\/code> to “back up” one directory level (with ..<\/code>) and then “go into” the fdos<\/code> directory.<\/p>\n\n\n\n

To change to a new directory, you could instead give the full path with the leading backslash. This is handy if you are already deep into another path, and just want to switch immediately to the new location. For example, you can type cd \\temp<\/code> to change to the \\temp<\/code> directory.<\/p>\n\n\n\n

In FreeDOS, like most DOS systems, you can see your current path as part of the DOS prompt. On Linux, your prompt is probably something like $<\/code>. On FreeDOS, the prompt lists the current drive, the current path within that drive, then ><\/code> as the prompt.<\/p>\n\n\n\n

Listing and Displaying Files<\/h2>\n\n\n\n

On Linux, the standard command to list files in the current directory is the ls<\/code> command. On FreeDOS, the command is named dir<\/code>.<\/p>\n\n\n\n

But if you prefer the behavior that you get with ls<\/code>, you can use an alias to use different command line options to the dir<\/code> command to make it look more like the output from ls<\/code>.<\/p>\n\n\n\n

To create an alias to another command, use the built-in alias<\/code> command. For example, use this command to define an alias for ls<\/code> that will display a directory listing in a similar way to using ls<\/code> on Linux:<\/p>\n\n\n\n

C:\\>alias ls=dir \/o:ne \/w \/b \/l\nC:\\>ls    \n[apps]         command.com    [devel]        fdauto.000     fdauto.bak\nfdauto.bat     fdconfig.sys   [freedos]      kernel.sys     [util]\nC:\\>ls freedos\n[.]            [..]           [appinfo]      [bin]          boot.bss\nboot.mbr       [cpi]          [doc]          [help]         [nls]\n[packages]     [source]       [temp]         version.fdi<\/code><\/pre>\n\n\n\n
The command option format is slightly different on FreeDOS than on Linux. On Linux, you start options with a hyphen character (-). But on FreeDOS, options start with a forward slash. The alias command above uses the slash character. In my alias<\/code> example, the \/o:ne<\/code> option tells dir<\/code> to order (o) in a certain way: sort any files and directories by name (n) and then by extension (e). Using \/w<\/code> says to use a “wide” directory listing, \/b<\/code> uses a “bare” display without the other information that dir<\/code> usually prints, and \/l<\/code> will display files and directories in lowercase.<\/p>\n\n\n\n
Note that the command-line options for the FreeDOS dir<\/code> command are quite different from the options to Linux ls<\/code>, so you can’t use this ls<\/code> alias exactly like you would on Linux. For example, typing ls -l<\/code> with this alias on FreeDOS will result in a “File not found” error, because the underlying FreeDOS dir<\/code> command will be unable to find a file called -l<\/code>. But for basic “see what files I have on my system,” this ls<\/code> alias is good enough to help Linux users get started with FreeDOS.<\/p>\n\n\n\n
Similarly, you can create an alias for the FreeDOS type<\/code> command, to act like the Linux cat<\/code> command. Both programs display the contents of a text file. While type doesn’t support the command-line options you might use under Linux, the basic usage to display a single file will be the same.<\/p>\n\n\n\n
C:\\>alias cat=type<\/code><\/pre>\n\n\n\n
Other Unix-like Commands<\/h2>\n\n\n\n
FreeDOS includes a selection of other common Unix-like commands, so Linux users will feel more at home. To use these Linux commands on FreeDOS, you may need to install the Unix Like Tools<\/strong> packages using the FDIMPLES package manager. You can find this package group on the BonusCD if you use the CD images, or as part of the FullUSB image if you used the USB installer.<\/p>\n\n\n\n
\"A<\/figure>\n\n\n\n
Not all of the Unix-like utilities work exactly like their Linux counterparts. That’s why we call them “Unix-like.” You might want to check the compatibility if you’re using some esoteric command-line options, but typical usage should be fine. Start with these common Unix-like commands on FreeDOS:<\/p>\n\n\n\n
The cal<\/code> command is the standard Unix calendar program. For example, to display the calendar for the current month, just type cal<\/code>. To view a specific month, give the month and year as arguments:<\/p>\n\n\n\n
C:\\>cal 6 1994\n\n      June 1994     \nSu Mo Tu We Th Fr Sa\n          1  2  3  4 \n 5  6  7  8  9 10 11 \n12 13 14 15 16 17 18 \n19 20 21 22 23 24 25 \n26 27 28 29 30       <\/code><\/pre>\n\n\n\n
View your disk usage with the du<\/code> command. This is a simple version of the Linux disk usage command and doesn’t support any command-line options other than a path.<\/p>\n\n\n\n
C:\\>du apps\n    158784 C:\\APPS\\FED\n         0 C:\\APPS\nTotal from C:\\APPS is 158784<\/code><\/pre>\n\n\n\n
The head<\/code> command displays the first few lines of a file. For example, this is a handy way to determine if a file contains the correct data.<\/p>\n\n\n\n
C:\\>head fdauto.bat\n@ECHO OFF\nset DOSDIR=C\"\\FDOS\nset LANG=EN\nset TZ=UTC\nset PATH=%dosdir%\\BIN\nif exist %dosdir%\\LINKS\\NUL set PATH=%path%;%dosdir%\\LINKS\nset NLSPATH=%dosdir%\\NLS\nset HELPPATH=%dosdir%\\HELP\nset TEMP=%dosdir%\\TEMP\nset TMP=%TEMP%<\/code><\/pre>\n\n\n\n
To view an entire file, use the more<\/code> command, which is the default file viewer on FreeDOS. This displays a file one screenful at a time, then prints a prompt to press a key before displaying the next screenful of information. The more<\/code> command is a very simple file viewer; for a more full-featured viewer like you might use on Linux, try the less<\/code> command which has the ability to scroll “backwards” through a file, in case you missed something. You can also search for specific text.<\/p>\n\n\n\n
If you have a lot of directories in your program PATH<\/code> variable and aren’t sure where a certain program is running from, you can use the which<\/code> command. This scans the program path variable, and prints the full location of the program you are looking for.<\/p>\n\n\n\n
C:\\>which less\nless    C:\\>FDOS\\BIN\\LESS.EXE<\/code><\/pre>\n\n\n\n
FreeDOS includes other Unix-like commands that you might use in other, more specific situations. Try them out and see if they fit your needs.<\/p>\n\n\n\n