Memory models, FAT, interrupts, and the open-source continuation of the original PC OS.
A complete walkthrough configuring a RAM disk with the built-in RAM driver — a fast, volatile drive letter backed entirely by memory, useful for temporary files and speeding up disk-heavy tasks.
A complete walkthrough building a batch-file boot menu that correctly manages memory-hungry TSRs — loading only what a chosen task actually needs, freeing conventional memory for everything else.
A complete walkthrough configuring the USBASPI/ASPIDISK driver chain to give FreeDOS a working drive letter for a USB flash drive — DOS-era drivers bridging a much newer standard.
A complete walkthrough installing DOSLFN, understanding what it can and can't do, and verifying long filenames actually work with your specific FreeDOS utilities.
FreeDOS boots with the wrong date or time every session, or DATE/TIME commands don't stick. Here's how to distinguish a dying CMOS battery from a software configuration issue.
A USB flash drive doesn't show up as a drive letter under FreeDOS. Since there's no native USB support, this comes down to getting USBASPI's driver chain correctly configured, or falling back to BIOS-level access.
Long filenames show up truncated to 8.3 format in some programs but not others, even with DOSLFN loaded. This is expected, driver-specific behavior — here's how to tell which programs actually support it.
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 December 31, 2001, Microsoft stopped supporting and patching MS-DOS 6.22 and older versions — though DOS embedded within Windows 95/98/Me lingered in support for years afterward.
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.