FreeDOS 1.3 Released

FreeDOS 1.3 was released on February 20, 2022. The project’s announcement names specific changes: kernel 2043, FreeCOM 0.85a, an 8086 kernel build with FAT32 support, the return of networking packages, compressed floppy installation media, new applications and games, package updates, localization work, and installer improvements around the master boot record, country data, and CD initialization.

Kernel 2043 and FreeCOM 0.85a updated the core pair

A DOS installation depends on both its kernel and command interpreter. FreeDOS 1.3 shipped kernel 2043 and FreeCOM 0.85a, the COMMAND.COM-compatible shell. They are separately maintained components: a shell update should not be described as a kernel feature, and a kernel version does not identify every command in the distribution.

The release also provided an 8086-targeted kernel with FAT32 support. That pairing is notable because FAT32 is often associated with later PCs while an 8086 build targets original PC-class instruction sets. It does not mean every program on every 1.3 medium runs on an 8086. Installers, applications, drivers, memory requirements, and selected package builds can impose higher requirements even when an appropriate kernel exists.

Networking returned as a distribution category

The official announcement describes the “return of networking.” FreeDOS 1.1 had already included mTCP, but release-media organization changed over time and 1.2’s package selections varied by image and profile. The 1.3 statement is best read as restored networking content in the official distribution, not as the invention of TCP/IP support in 2022.

DOS networking still depends on a packet driver compatible with the network adapter or emulated hardware. Applications such as DHCP clients, FTP tools, and web clients use that layer; they cannot make an unsupported interface work by themselves. The release made a curated networking set available again while preserving the hardware boundary.

The Floppy-Only Edition used compression

FreeDOS 1.3’s Floppy-Only Edition compressed its package payload, requiring roughly half as many diskettes as the prior uncompressed approach. Its README lists image sets for 720 KiB, 1.2 MiB, and 1.44 MiB media. Each set contains a boot disk and numbered data disks, with the exact count varying by disk capacity.

The floppy edition used a different installer from the CD and USB media and carried a limited selection aimed at classic hardware. It omitted package source code to conserve space; users could obtain source through the website or larger media. That tradeoff is more precise than saying the edition was simply a miniature copy of the LiveCD.

The README also records a CPU-detection issue in the floppy installer’s V8Power Tools. Some systems could be misidentified as 80186-class, so the installer accepted an explicit CPU parameter such as 8086, 286, 386, QEMU, or VBX. This was an installer workaround, not a command to overclock or transform the hardware.

Installation and localization received targeted fixes

The release announcement highlights improved handling of the master boot record, automatic COUNTRY.SYS configuration in some cases, and better CD initialization for both boot media and installed systems. These are small-sounding changes at the points where an installer can most easily leave a system unbootable or incorrectly localized.

MBR handling determines whether BIOS firmware can transfer control to the installed system. CD initialization needs a working driver and redirector arrangement so packages remain reachable during setup and optical media works afterward. COUNTRY.SYS influences country-specific conventions and code-page behavior. None is a cosmetic installer detail.

The release media documented capacity and purpose

The official README recommends the LiveCD for most users and provides a Legacy CD for older boot implementations, a non-bootable BonusCD for extra packages, lite and full USB images, and the floppy-only archive. VMDK versions accompanied USB images to simplify attachment in VirtualBox, VMware, and other virtual-machine software.

The release report counts 65 BASE packages and 205 FULL packages. It estimates 20 MiB for a plain DOS system without source, 30 MiB with source, 275 MiB for a full installation, and 375 MiB for full software plus source. Those are release-build measurements, not universal free-space guarantees once users add data or update packages.

Hashes in verify.txt covered the published release files. Checking a downloaded archive before extracting or writing it distinguishes media corruption from installer bugs and confirms that a mirror delivered the same bytes as the recorded build.

Licensing received an explicit review

While preparing 1.3, the project reviewed package licenses and aimed to include software meeting the Open Source Definition. Jim Hall’s 1.3 RC4 overview acknowledged that previous distributions had included a few programs that were free to use or distribute but not fully open source, or lacked source in the expected form.

That review is a material distribution change. FreeDOS is a collection whose packages can use different licenses, so the kernel’s GPL license cannot be generalized automatically to every editor, game, driver, or utility. Accurate metadata and available source are necessary for users and redistributors to understand their rights.

A release with measurable changes

FreeDOS 1.3 was more than a periodic package refresh. It updated the kernel and shell, restored a networking selection, compressed the floppy path, improved boot and localization steps, documented several media profiles, and tightened the distribution’s licensing criteria.

It also retained clear limits. Hardware still needed compatible BIOS behavior and drivers; the floppy edition was intentionally smaller; and an 8086-capable kernel did not certify every optional package for an original IBM PC. The official announcement, README, and generated build report make it possible to describe those strengths and boundaries without guessing from the version number.

Related:

Sources: