{"id":14044,"date":"2026-06-08T03:00:00","date_gmt":"2026-06-08T07:00:00","guid":{"rendered":"https:\/\/www.both.org\/?p=14044"},"modified":"2026-05-04T16:37:50","modified_gmt":"2026-05-04T20:37:50","slug":"using-variables-in-freedos","status":"publish","type":"post","link":"https:\/\/www.both.org\/?p=14044","title":{"rendered":"Using variables in FreeDOS"},"content":{"rendered":"
\r\n
\r\n \r\n <\/i>\r\n <\/a>\r\n <\/span>\r\n<\/div><\/div>\n

A useful feature in almost every command-line environment is the environment variable. Some of these variables allow you to control the behavior or features of the command line, and other variables simply allow you to store data that you might need to reference later. Environment variables are also used in FreeDOS.<\/p>\n\n\n\n

Variables on Linux<\/h2>\n\n\n\n

On Linux, you may already be familiar with several of these important environment variables. In the Bash shell on Linux, the PATH<\/code> variable identifies where the shell can find programs and commands. For example, on my Linux system, I have this PATH<\/code> value:<\/p>\n\n\n\n

bash$ echo $PATH\n\/home\/jhall\/bin:\/bin:\/usr\/bin:\/usr\/local\/bin<\/code><\/pre>\n\n\n\n
That means when I type a command name like cat<\/strong>, Bash will check each of the directories listed, in order:<\/p>\n\n\n\n
    \n
  1. \/home\/jhall\/bin<\/li>\n\n\n\n
  2. \/bin<\/li>\n\n\n\n
  3. \/usr\/bin<\/li>\n\n\n\n
  4. \/usr\/local\/bin<\/li>\n<\/ol>\n\n\n\n
    And in my case, the cat<\/strong> command is located in the \/bin<\/code> directory. (Actually, Fedora Linux merged the \/bin<\/code> and \/usr\/bin<\/code> directories a while ago, so my PATH<\/code> is actually an anachronism. But I keep it that way because it’s still technically correct<\/em>, which is the best kind of correct.)<\/p>\n\n\n\n
    To set an environment variable on Linux, you type the name of the variable, then an equals sign (=) and then the value to store in the variable. To reference that value later using Bash, you type a dollar sign ($) in front of the variable name.<\/p>\n\n\n\n
    bash$ var=Hello\nbash$ echo $var\nHello<\/code><\/pre>\n\n\n\n
    Variables on FreeDOS<\/h2>\n\n\n\n
    On FreeDOS, environment variables serve a similar function. Some variables control the behavior of the DOS system, and others are useful to store some temporary value.<\/p>\n\n\n\n
    To set an environment variable on FreeDOS, you need to use the SET<\/code> keyword. FreeDOS is case insensitive, so you can type that using either uppercase or lowercase letters. Then set the variable as you might on Linux, using the variable name, an equals sign (=), and the value you want to store.<\/p>\n\n\n\n
    However, referencing or expanding an environment variable’s value in FreeDOS is quite different from how you do it on Linux. You can’t use the dollar sign ($) to reference a variable in FreeDOS. Instead, you need to surround the variable’s name with percent signs (%).<\/p>\n\n\n\n
    C:\\>echo %PATH%\nC:\\freedos\\bin<\/code><\/pre>\n\n\n\n
    It’s important to use the percent signs both before and after the name because that’s how FreeDOS knows where the variable name begins and ends. This is very useful, as it allows you to reference a variable’s value while immediately appending (or prepending) other text to the value. Let me demonstrate this by setting a new variable called REPLY<\/code> with the value yes<\/code>, then referencing that value with the text “11” before and “22” after it:<\/p>\n\n\n\n
    C:\\>set REPLY=yes\nC:\\>echo 11%REPLY%22\n11yes22<\/code><\/pre>\n\n\n\n
    Because FreeDOS is case insensitive you can also use uppercase or lowercase letters for the variable name, as well as the SET<\/code> keyword. However, the variable’s value will use the letter case as you typed it on the command line.<\/p>\n\n\n\n
    Finally, you can see a list of all the environment variables currently defined in FreeDOS. Without any arguments, the SET<\/code> keyword will display all variables, so you can see everything at a glance:<\/p>\n\n\n\n
    C:\\>set\nCONFIG=2\nDOSDIR=C:\\FreeDOS\nCOMSPEC=C:\\FreeDOS\\BIN\\COMMAND.COM\nPATH=C:\\freedos\\bin\nTEMP=C:\\freedos\\temp\nTMP=C:\\freedos\\temp\nLANG=en\nNLSPATH=C:\\freedos\\nls\nHELPPATH=C:\\freedos\\help\nTZ=utc\nDIRCMD=\/O:GNE<\/code><\/pre>\n\n\n\n
    Environment variables are a useful staple in command-line environments, and the same applies to FreeDOS. You can set your own variables to serve your own needs, but be careful about changing some of the variables that FreeDOS uses. These can change the behavior of your running FreeDOS system:<\/p>\n\n\n\n