{"id":9175,"date":"2025-01-07T02:00:00","date_gmt":"2025-01-07T07:00:00","guid":{"rendered":"https:\/\/www.both.org\/?p=9175"},"modified":"2025-01-02T19:23:28","modified_gmt":"2025-01-03T00:23:28","slug":"looking-ahead-to-freedos-1-4","status":"publish","type":"post","link":"https:\/\/www.both.org\/?p=9175","title":{"rendered":"Looking ahead to FreeDOS 1.4"},"content":{"rendered":"
\r\n
\r\n \r\n <\/i>\r\n <\/a>\r\n 1 <\/span>\r\n<\/div><\/div>\n

The FreeDOS Project<\/a> is an open source implementation of the classic DOS<\/em> operating system. If you haven\u2019t heard of it, DOS was a very popular 16-bit operating system throughout the 1980s and into the 1990s. I grew up with DOS, learning to write BASIC programs from an early age, and leveraging the rich collection of DOS apps available at the time.<\/p>\n\n\n\n

By 1993, I had installed Linux at home, dual-booted with DOS, and was impressed by what Linux offered: a Unix-like operating system where anyone could examine the source code. That meant anyone could contribute to it and make Linux and its tools even better by fixing bugs and adding features. But Linux didn\u2019t have many applications; so while I booted into Linux to do some things, I still spent most of my time in DOS.<\/p>\n\n\n\n

Unfortunately, that would soon come to an end. In early 1994, I heard that Microsoft\u2019s next version of Windows<\/em> would completely replace DOS\u2014DOS was dead. But I decided \u201cIf people can work together to create their own Unix, and share the source code for everyone to use, surely we could do the same for DOS?\u201d And that\u2019s how the FreeDOS Project started in June 1994.<\/p>\n\n\n\n

Building a modern DOS<\/h2>\n\n\n\n

Our early versions of FreeDOS targeted replacing the core features of DOS, quickly adding a command.com<\/em> shell called \u201cFreeCOM\u201d and a collection of DOS utilities. Soon after, Pat Villani contributed his DOS kernel, which set us on a fast trajectory.<\/p>\n\n\n\n

We followed a mantra of release early, release often<\/em> and shared a new FreeDOS distribution<\/em> every few months or weeks. Alpha 1 (September 1994) was a collection of a few core tools, followed by Alpha 2 (December 1994), Alpha 3 (January 1995), Alpha 4 (June 1995), Alpha 5 (August 1996), and Alpha 6 (November 1997).<\/p>\n\n\n\n

Until the Alpha 6 release, every FreeDOS distribution required the user to install things \u201cby hand.\u201d Each distribution was effectively composed of zip files and a boot floppy, and the user had to run fdisk<\/strong> and format<\/strong> and sys<\/strong> to set up a hard disk with FreeDOS, and manually run unzip<\/strong> to install the programs. I created a very simple \u201cinstaller\u201d to automate most of the steps, which was the boost we needed to enter a \u201cBeta\u201d phase.<\/p>\n\n\n\n

We released Beta 1 (code-named \u201cOrlando\u201d) in March 1998, shortly before I visited my brother and his family (who lived in Orlando). By this time, FreeDOS had become more stable, and with DOS no longer a moving target<\/em> since 1995 with the release of Windows95, we didn\u2019t need to make such frequent releases. Most of the \u201cBeta\u201d distributions had code-names, including Beta 2 \u201cMarvin\u201d (October 1998), Beta 3 \u201cVentura\u201d (April 1999), Beta 4 \u201cLemur\u201d (April 2000), Beta 5 \u201cLara\u201d (August 2000), Beta 6 \u201cMidnite\u201d (March 2001), Beta 7 \u201cSpears\u201d (September 2001), Beta 8 \u201cNikita\u201d in April 2002, and Beta 9 in September 2004.<\/p>\n\n\n\n

By the time of the \u201cBeta\u201d releases, FreeDOS was already a modern DOS. Where classic DOS provided a bare command line experience with just enough features to support larger applications and games, FreeDOS provided expanded utilities, extra tools to enhance the command line, and compilers and assemblers so you could create your own programs.<\/p>\n\n\n\n

We had a series of release candidates<\/em> as we worked our way up to a FreeDOS 1.0<\/strong> distribution, which we finally released in September 2006. We followed with a few minor \u201chotfix\u201d releases and other release candidates as we worked towards the major version numbers, such as FreeDOS 1.1 in January 2012 (5 years and a few months after \u201c1.0\u201d), FreeDOS 1.2 in December 2016 (5 years after \u201c1.1\u201d), and FreeDOS 1.3 in February 2022 (5 years plus a few months since \u201c1.2\u201d).<\/p>\n\n\n\n

Monthly test releases<\/h2>\n\n\n\n

After that, FreeDOS didn\u2019t need a very frequent release cycle because FreeDOS had already become very stable and compatible with classic DOS. However, FreeDOS remains under development, and developers keep adding new features and fixing old bugs.<\/p>\n\n\n\n

Since taking on the role of FreeDOS distribution coordinator<\/em> several years ago, Jerome Shidel had a great idea about how to automate building the FreeDOS distributions. Until Jerome joined us, creating each FreeDOS distribution required a ton<\/em> of manual steps. Jerome automated all of that, starting in summer 2015. Along the way, Jerome also created a new install process that was more streamlined and easier to maintain.<\/p>\n\n\n\n

After the FreeDOS 1.3 distribution in 2022, Jerome realized that we could create a regular \u201ctest release\u201d cycle, which would collect all of the changes and updates shared by the developers, making it easier for folks to test everything without having to download and apply each new update. Since then, Jerome has posted a monthly test distribution<\/a> labeled for the year and month of its release, such as T2412<\/strong> for the version released in December 2024.<\/p>\n\n\n\n

With a monthly test release, and with the process to generate a new distribution almost entirely automated, we had a new starting point to generate the next FreeDOS distribution. At some point, we could \u201cpromote\u201d a test release as a new release candidate, and so on for the next several release candidates until we were ready for the next official FreeDOS distribution. And that time is now.<\/p>\n\n\n\n

FreeDOS 1.4 Release Candidate 1<\/h2>\n\n\n\n

Thanks to everyone who contributes to FreeDOS, we are excited to share that the FreeDOS 1.4 Release Candidate 1<\/a> is now available! This has a ton of new changes and fixes, and the updates in FreeDOS 1.4 RC1 should address the annoying bugs that folks have found and reported since FreeDOS 1.3. including updates to the installer and feature updates for many programs such as fdisk<\/strong>, format<\/strong>, jemm<\/strong>, ldebug<\/strong>, bwbasic<\/strong>, dojs<\/strong>, dog<\/strong>, nasm<\/strong>, curl<\/strong>, mkeyb<\/strong>, edlin<\/strong>, blocek<\/strong>, htmlhelp<\/strong>, fdnet<\/strong>, more<\/strong>, fdimples<\/strong>, \u2026 the list goes on. Read the change log<\/a> for the complete list.<\/p>\n\n\n\n

We encourage everyone to download FreeDOS 1.4 RC1 and help test it. If you find any issues or compatibility problems, please report a bug<\/a> to let us know.<\/p>\n\n\n\n

Most users run FreeDOS in a virtual machine, and we\u2019ve made it easy to do so with FreeDOS 1.4 RC1. To install FreeDOS 1.4 RC1 in a virtual machine, first set up the virtual machine environment you want to use. For example, you can use VirtualBox<\/a>, which provides a graphical front-end to managing virtual machines. I like to use QEMU<\/a>, which should be available by default on most Linux distributions. However, note that QEMU requires you to set up everything via the command line; it does not have a graphical interface where you can define the machine settings, although you can install Virtual Machine Manager<\/a>, which takes care of the configuration steps for you.<\/p>\n\n\n\n

Installing FreeDOS 1.4 RC1<\/h2>\n\n\n\n

The installer can recognize when it\u2019s running in a virtual machine and set up some things for you, although the install process is largely the same for a virtual machine as when installing on real hardware. Follow these steps to install FreeDOS 1.4 RC1 on your system:<\/p>\n\n\n\n

First, download<\/a> the FreeDOS 1.4 RC1 LiveCD image. This is the preferred installer for most users, and you can use the LiveCD on any virtual machine or hardware system that supports a CD-ROM or DVD drive. If you\u2019re installing on \u201cbare metal,\u201d you\u2019ll also need to write the LiveCD image to a CD-R writeable disc.<\/p>\n\n\n\n

Boot your system with the LiveCD and select \u201cInstall to harddisk.\u201d<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

After selecting your language, you\u2019ll be greeted by the install program:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

The installer can partition and format the disk for you. Use the prompts to let the installer partition the disk for you:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

FreeDOS will need to reboot so it can re-read the disk information. After rebooting, use the prompt to format the new partition. This creates a DOS filesystem<\/em> that FreeDOS will use to store files:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

After that, the installer will ask for your keyboard layout, then ask you for what FreeDOS packages you want to install. To make it easy for new users, we\u2019ve set up the prompts to install a minimal DOS system (\u201cPlain DOS system\u201d) or a more complete installation (\u201cFull installation including applications and games\u201d). You can also select if you want to install a copy of the FreeDOS source code at the same time.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Use the prompts to select how you want to install FreeDOS 1.4 RC1, and the installer can do everything else on its own after that:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

When the install process is done, you can use the prompts to reboot your system and start using FreeDOS 1.4 RC1:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Congratulations! You\u2019ve installed FreeDOS 1.4 RC1:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Testing FreeDOS 1.4 RC1<\/h2>\n\n\n\n

If you chose the \u201cFull install\u201d option when installing FreeDOS 1.4 RC1, you should have everything that\u2019s included in the LiveCD. If you used the \u201cPlain DOS\u201d install option, then you\u2019ll need to use the fdimples<\/strong> package manager program to install other FreeDOS programs. Just type FDIMPLES<\/code> at the command line to start it, and use the arrow keys and Tab key to navigate and select what packages you want to install.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

You can also download<\/a> the BonusCD image to install a ton of extra tools including editors and assemblers. Depending on your virtual machine, you may need to reboot FreeDOS after selecting a different CD-ROM image.<\/p>\n\n\n\n

You can also install and run your favorite DOS applications and games on FreeDOS! Any program that works on classic DOS should also run on FreeDOS. If you\u2019re using a virtual machine, you will need to copy the DOS application to the virtual disk, such as using the guestmount program<\/a> to access the virtual disk from Linux. Copy your DOS program installer (usually a zip file, but sometimes as a standalone install program) to the virtual disk, then boot FreeDOS to use it.<\/p>\n\n\n\n

For more information about FreeDOS, you might want to read these 5 articles to explore FreeDOS<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"

Help test the next version of FreeDOS with the FreeDOS 1.4 Release Candidate 1 distribution.<\/p>\n","protected":false},"author":33,"featured_media":2815,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_lmt_disableupdate":"","_lmt_disable":"","footnotes":""},"categories":[340,106,461],"tags":[267],"class_list":["post-9175","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-freedos","category-history","category-installation","tag-freedos"],"modified_by":"Jim Hall","_links":{"self":[{"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/posts\/9175","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/users\/33"}],"replies":[{"embeddable":true,"href":"https:\/\/www.both.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=9175"}],"version-history":[{"count":1,"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/posts\/9175\/revisions"}],"predecessor-version":[{"id":9186,"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/posts\/9175\/revisions\/9186"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/media\/2815"}],"wp:attachment":[{"href":"https:\/\/www.both.org\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=9175"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.both.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=9175"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.both.org\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=9175"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}