tag
29 posts
A complete walkthrough installing a C compiler and assembler on FreeDOS and building your first program — for anyone wanting to write software for DOS rather than just run it.
A complete walkthrough getting sound, mouse, and memory configured correctly for DOS-era gaming — the three things almost every classic game setup guide assumes you already have working.
Released January 2, 2012, FreeDOS 1.1 filled a long gap since the 1.0 release, refining package management and driver support without changing the project's core commitment to MS-DOS compatibility.
Released April 5, 2025, FreeDOS 1.4 updated FreeCOM, FDISK, and the mTCP networking suite, while deliberately keeping the same kernel as 1.3 until the next kernel version is fully tested.
Marking a quarter-century since the June 1994 announcement, FreeDOS's 25th anniversary in 2019 brought renewed attention from Slashdot, Opensource.com, and Linux Journal to a project still actively releasing new versions.
On June 29, 1994, a Usenet post to comp.os.msdos.apps proposing a public-domain DOS kicked off what would be renamed Free-DOS weeks later — a direct response to Microsoft's plans to fold MS-DOS into Windows 95.
FreeDOS reached its first stable 1.0 release on September 3, 2006 — twelve years after Jim Hall's original 1994 call to build a free DOS.
FreeDOS 1.3 shipped February 20, 2022, continuing the project's roughly five-year major release rhythm with an updated package set.
A practical tour of FreeDOS batch scripting: variables, control flow, argument handling, and the quirks that differ from a modern shell.
How a FreeDOS machine goes from the boot sector to a command prompt, and how CONFIG.SYS and AUTOEXEC.BAT configure everything along the way.
How character and block device drivers register with the DOS kernel through a standard request-header protocol, loaded declaratively from CONFIG.SYS.
How the File Allocation Table represents files as linked chains of clusters, and why that simple design has both strengths and hard limits.
A sound card, network card, or serial device doesn't work, or the system hangs when two devices are used together. Classic IRQ conflicts, and how to actually resolve them.
SET commands or a long PATH suddenly fail with 'Out of environment space.' The environment block has a fixed size, and here's how to actually fix it.
You edited CONFIG.SYS, rebooted, and now the system hangs or won't load drivers correctly. Here's how to get back to a bootable state without reinstalling.
The single most common real-world reason to boot FreeDOS today: a complete walkthrough building a bootable USB stick to run a vendor's DOS-based firmware update tool.
A complete walkthrough getting a CD-ROM drive recognized and assigned a drive letter on FreeDOS — the driver-plus-MSCDEX layering that DOS CD-ROM support was always built on.
A complete walkthrough installing a text editor and a couple of common utilities on FreeDOS, and wiring them into your PATH and environment properly.
A complete walkthrough creating a primary partition, an extended partition with logical drives, and setting the active boot partition — the way DOS disks have always been organized.
A complete walkthrough installing FreeDOS onto a virtual machine or real hardware, from booting the installer to a working CONFIG.SYS and AUTOEXEC.BAT.
A complete walkthrough getting real TCP/IP networking working on FreeDOS using mTCP and a packet driver, enough for FTP, Telnet, and a basic web browser.
How DOS exposes its entire system call interface through the software interrupt mechanism, with INT 21h as the single most important entry point.
Why DOS memory is split into distinct regions with different rules, and how HIMEM.EXE and EMM386.EXE make more of it usable.
FreeDOS 1.2 shipped in December 2016, refreshing the distribution's package set and installer nearly five years after 1.1.
How FreeDOS distributes and installs software as discrete packages, and the tools used to manage them, decades before Linux package managers existed.
The practical ways people actually run FreeDOS in 2026 — from firmware-flashing USB sticks to full virtual machines — and how to pick the right one.
DOS had no scheduler and no processes in the modern sense — so how did pop-up utilities, mouse drivers, and print spoolers run 'in the background'? By staying resident and hooking interrupts.
Where FreeDOS achieves genuine binary compatibility with MS-DOS, where it deliberately diverges, and what that means for running real DOS software.
The history, goals, and real-world use cases behind FreeDOS, the open-source, actively-maintained continuation of the MS-DOS-compatible operating system line.