FreeDOS 1.1 Ships, Six Years After 1.0

FreeDOS 1.1 was published on January 2, 2012, more than five years after FreeDOS 1.0. The official announcement lists concrete technical changes: kernel 2040, Michael Brutman’s mTCP applications, initial USB controller support, a generic PCI IDE driver, updated memory managers, 4DOS, Flashrom, and a revised CD installation menu. It also openly records incomplete media and installer behavior, making 1.1 a substantive but imperfect release rather than a generic maintenance rollup.

Kernel 2040 addressed a high-risk FAT32 problem

The announcement identifies FreeDOS kernel 2040 and says it should fix FAT32 file corruption. The accompanying release notes say the FAT32-enabled kernel had moved beyond its experimental stage, while warning that not every FreeDOS program handled FAT32 correctly. Both statements are needed for an accurate reading: the kernel’s FAT32 path was considered stable, but applications and utilities still had their own filesystem assumptions.

FreeDOS 1.1 removed the unstable 2039 kernel in favor of 2040. It also noted that NLS support through NLSFUNC and CHCP was not yet present in that kernel and was expected in a later one. A release can therefore improve data safety while still carrying a documented functional regression or missing subsystem.

Networking gained mTCP

FreeDOS 1.1 added mTCP, Michael Brutman’s suite of TCP/IP applications for x86 DOS computers. This did not mean every machine automatically joined a network after installation: DOS networking still requires a compatible packet driver and correct network configuration. It did provide maintained applications designed for constrained real-mode systems, alongside software built around the older Wattcp ecosystem.

The distinction is practical. A distribution can include network clients without including a universal hardware driver, and Ethernet hardware varies widely across the PCs and virtual machines capable of running FreeDOS. The release expanded the networking toolbox; it did not promise plug-and-play connectivity for arbitrary adapters.

USB support was explicitly initial and narrow

The announcement calls its USB controller work an “initial attempt.” It covered UHCI controllers associated with Intel and VIA USB 1.1 implementations, not OHCI, EHCI, or xHCI. It also described USB flash-disk support as very limited and warned that an installer booted from USB might see that device as drive C:.

That warning is critical because DOS drive letters do not communicate device identity as clearly as modern storage tools. Selecting the wrong target could overwrite installation media or existing data. Any summary that simply says “FreeDOS 1.1 added USB support” removes the limitations the project deliberately placed beside the feature.

UIDE consolidated disk and CD access

Jack R. Ellis’s generic PCI IDE cache and CD-ROM driver brought PIO and UDMA modes for PATA and SATA disks and optical drives. The distribution removed separate UDMA, GCDROM, and QCDROM components in favor of UIDE. That was a meaningful driver-stack change, not merely a new bundled application.

The release also updated HMA/XMS and UMB/EMS memory drivers. On DOS, conventional, upper, expanded, and extended memory configuration directly determines whether larger applications and drivers can coexist. Updated managers therefore affect real usability even when they do not alter the DOS API exposed to a simple program.

The installer reduced menus but retained rough edges

FreeDOS 1.1 introduced a new startup installation menu intended to reduce the number of prompts. Its own announcement then documents several problems: CD detection did not work correctly, the old installation method could hang after keyboard selection, the boot-disk menu was not working, and some operations required mounting the ISO contained on the disc manually.

The project provided a recovery path through basic DOS tools: create an active primary FAT16 or FAT32 partition with FDISK, erase and format it with FORMAT C:, and make it bootable with SYS C:. Those commands are destructive and were presented as a simple manual method, not as permission to run them without confirming the target disk.

The release shipped only the BASE set

Unlike the broader media choices of 1.0, the 1.1 announcement says only the BASE set had been packaged and that a LiveCD environment was missing. This directly contradicts a vague description of 1.1 as a comprehensive refresh of the whole FreeDOS package repository. The release prioritized a bootable core and selected new components while leaving additional sets for later work.

The package format itself advanced. FreeDOS documentation explains that 1.1 moved from separate binary and source packages to a single ZIP capable of containing both, while allowing the installer to skip source extraction. It also defined locations for package metadata, documentation, help, localization, source, applications, games, drivers, and development tools.

The small official errata file shows post-release auditing in action: DEBUG’s license label was corrected from GPL to MIT, and DOSLFN’s label was corrected from GNU GPL to the broader “open source.” Those corrections matter because distribution metadata must accurately state the terms under which software can be copied and modified.

A release best understood through its boundaries

FreeDOS 1.1 delivered important kernel, storage, memory, networking, packaging, and installation work after the long gap from 1.0. It also published a candid limitations and TODO list. That combination gives a more credible history than calling it either a minor refresh or an entirely polished successor.

The release’s value lay in moving the maintained base forward while documenting what had not yet caught up: broader package sets, reliable CD detection, complete USB controller coverage, a LiveCD, and finished localization support in the kernel. FreeDOS 1.1 was usable software with known edges, and the primary documents make those edges auditable.

Related:

Sources: