FreeDOS T2603 Starts Public Testing of the New Kernel and Windows 3.x Support

FreeDOS published monthly test release T2603 on March 1, 2026 and promoted it on March 7 as a way to test the new kernel and Windows 3.x compatibility. The chronology needs one correction: kernel 2044 had already entered February’s T2602. T2603 increased visibility and continued integrated testing; it was not the kernel’s first monthly-distribution appearance.

Kernel 2044 was released before T2603

The FreeDOS kernel project published version 2044 on January 25, 2026. Its release notes call it an incremental maintenance release covering build systems, boot and runtime edge cases, environment processing, filesystem and disk I/O, old FCB APIs, redirectors, path handling, tools, and Windows 3.x Enhanced Mode compatibility.

The release included source plus multiple binaries: 8086 and 80386 builds, with FAT12/16-only and FAT32-capable choices. That matrix matters because “kernel 2044” does not identify one binary suitable for every configuration. An 8086 machine and a 386 Enhanced Mode Windows setup need different capabilities.

The notes also warn through their scope: compatibility work was “aimed at improving” Windows 3.x Enhanced Mode, not a certification that all editions, drivers, memory managers, and hardware combinations would succeed.

T2602 first integrated the 2044 package

Jerome Shidel’s T2602 announcement records the kernel update to 2044 on January 27 and published the February test media on February 1. Jim Hall later wrote that he had downloaded T2602 and that it contained the new kernel.

This directly contradicts a literal reading of T2603 as the start of distribution testing. The defensible interpretation of the title is that T2603 began a more visible public campaign around the feature. The FreeDOS website added a direct monthly-test link and a March news item inviting broader testing.

T2603 carried the kernel forward. Its change list relative to T2602 focused on other updates, including FDNPKG16, LABEL, translations, and COUNTRY.SYS 2.0. The March announcement nevertheless described kernel 2044 as a major difference users would encounter compared with stable FreeDOS 1.4.

Stable FreeDOS 1.4 had deliberately retained the older kernel

FreeDOS 1.4 shipped in April 2025 with the same kernel version as FreeDOS 1.3. The project said the replacement was not ready and needed substantial testing before inclusion in another stable distribution. It also stated that 1.4 could run Windows 3.1 in Standard Mode but not Windows for Workgroups in Enhanced Mode.

Monthly releases supplied the missing risk boundary. Maintainers could place 2044 beside current FreeCOM, JEMM, drivers, packages, installers, and boot media without silently changing stable 1.4. Users who needed predictability retained the stable images; testers received an integrated preview with a date-coded name.

Windows 3.x support is mode-specific

Windows 3.x offered several execution modes with different CPU and memory-management behavior. Standard Mode and 386 Enhanced Mode do not exercise DOS identically. Enhanced Mode uses virtual 8086 facilities and deeper coordination with memory managers, DOS multiplex interrupts, critical patch tables, and device behavior.

FreeDOS had demonstrated experimental Enhanced Mode progress in 2021. At that time, Jeremy Davis described missing INT 2Fh functions and kept the significant changes behind a WIN31SUPPORT compile-time definition while rough edges remained. Kernel 2044 integrated later compatibility work and mentions critical patch-table and IOCTL adjustments.

“Runs Windows 3.x” must therefore be tested with the exact Windows version, mode, kernel build, HIMEM/EMM386 combination, configuration files, and drivers. A successful Standard Mode launch does not prove Enhanced Mode, and Windows 3.1 is not identical to Windows for Workgroups 3.11.

Early T2603 reports showed why testing mattered

A March 20 user report tested T2603 in QEMU on a Raspberry Pi 400 and on a Dell Inspiron 510m. Installation eventually succeeded in both environments, although the reporter saw slow behavior and an initial package-copy failure in the emulated test. On the Dell, Windows 3.11 still crashed or rebooted after configuration changes.

One report cannot establish a general defect or success rate. It does demonstrate that an announcement-level compatibility feature was not universal on day one. Hardware, emulation speed, memory size, page-overcommit settings, and startup files can change the outcome, which is precisely why the kernel belonged in a test stream.

Kernel 2044 changed much more than Windows handling

The release tightened writes around the 4 GiB boundary to avoid wrapping and corruption, hardened absolute disk I/O paths, fixed FAT and BPB/DPB edge cases, improved FCB parsing and rename behavior, adjusted redirector interactions, and corrected TRUENAME handling. It also changed environment initialization and SET processing during configuration.

Those fixes can affect ordinary DOS software even when Windows is never installed. A Windows-focused headline should not obscure filesystem, boot, network-redirector, and compatibility changes that carry their own regression risk.

Testers should therefore exercise file copies near size boundaries, boot media, network drives, batch startup, old FCB-using applications, and SYS, not only launch Program Manager. Kernel validation is a matrix, not one screenshot.

How to test the monthly build responsibly

T2603 should be installed in a cloned virtual machine, a copy of a disk image, or expendable hardware state. The tester should record the media type, kernel filename and build, CPU target, FAT variant, memory managers, Windows version and mode, emulator or machine, and relevant FDCONFIG.SYS and FDAUTO.BAT lines.

Reproducing the same setup with stable 1.4 or T2602 helps locate a regression. The monthly changes.log distinguishes differences introduced after T2602 from the already-integrated 2044 kernel. Verification hashes should be checked before interpreting a failed copy or boot as a software bug.

The corrected significance of T2603

T2603 matters because FreeDOS put the monthly stream in front of more users and explicitly asked them to validate kernel 2044 and Windows behavior. It continued a conservative path begun with the kernel release and T2602 integration while leaving stable 1.4 unchanged.

The accurate sequence is: experimental Enhanced Mode work was public in 2021; FreeDOS 1.4 retained the old kernel in 2025; kernel 2044 shipped January 25, 2026; T2602 integrated it February 1; and T2603 continued and publicized that testing in March. That chronology makes the release-engineering decision more—not less—meaningful.

Related:

Sources: