Releases

DOSBox-X March 2026 Update Fixes EXEPACK Errors, Adds Configurable BEL Duration

DOSBox-X's March 2026 build squashes the dreaded "packed file is corrupt" EXEPACK error and adds a dosbox.conf knob for PC speaker BEL timing.

Sam Ortega2 min read
Published
Listen to this article0:00 min
Share this article:
DOSBox-X March 2026 Update Fixes EXEPACK Errors, Adds Configurable BEL Duration
Source: www.generationamiga.com

The 2026.03.29 build of DOSBox-X landed on March 29 with a set of fixes aimed squarely at correctness: compressed executable handling, memory allocation behavior, and a new configuration option that lets you control how long the PC speaker rings when a DOS program fires a BEL (0x07) character.

That last one is smaller than it sounds only if you've never chased down a timing-sensitive DOS program behaving strangely. The BEL character, the old ASCII beep trigger baked into console output since the earliest PC days, has a duration that varies across hardware. Some programs tested for it. Some relied on it as a crude timing mechanism. DOSBox-X now exposes that duration as a tunable dosbox.conf parameter, which means archivists and preservation-minded users can dial it to match whichever machine they're trying to reproduce.

The EXEPACK fix is the one that will unblock the most people immediately. EXEPACK was Microsoft's executable compression format, widely used in the late 1980s and early 1990s to ship installers and tools in smaller footprints. When DOSBox-X mishandled the decompression logic, it threw a "packed file is corrupt" error that made perfectly intact binaries look damaged. That false negative has sent more than a few preservationists on unnecessary hunts through archive integrity checks and alternate disk images. The 2026.03.29 release corrects the handling so those executables run without manual workarounds.

AI-generated illustration
AI-generated illustration

The accompanying memory allocation fixes round out a release that prioritizes behavioral fidelity over visible feature additions. That's consistent with DOSBox-X's design philosophy: the fork exists precisely because accuracy across diverse PC configurations, VGA and SVGA variants, multiple Sound Blaster generations, and various DOS versions, demands fixes that look minor in a changelog but have real consequences when you're running original software.

If you maintain curated disk images or collections where subtle sound timing matters, the 2026.03.29 build is worth pulling now. The full changelog is on the DOSBox-X releases page alongside the tagged GitHub build.

Know something we missed? Have a correction or additional information?

Submit a Tip

Never miss a story.
Get Retro Game Emulation updates weekly.

The top stories delivered to your inbox.

Free forever · Unsubscribe anytime

Discussion

More Retro Game Emulation News