Ask HN: Who's still keeping a DOS machine up because the business depends on it?
An "Ask HN" post unexpectedly unearths a goldmine of astonishing tales about businesses stubbornly relying on ancient DOS-era hardware and software. From nuclear power plant monitoring to factory controls, Hacker News users reveal the bewildering inertia, certification hurdles, and sheer cost preventing upgrades to these deeply embedded, often mission-critical, systems. The discussion highlights that, in many sectors, if it ain't broke (and certified), it simply isn't fixed.
The Lowdown
The "Ask HN" prompt delves into a fascinating, anachronistic corner of the tech world: businesses that, even today, depend on decades-old DOS-era hardware and software. It quickly became a magnet for a wide array of anecdotes and insights into why these digital dinosaurs persist, often in critical operational roles, and the complex challenges of keeping them alive and integrated into a modern computing landscape.
- Industrial and Scientific Reliance: Numerous users shared examples of systems controlling manufacturing processes (CNC mills, paint booths), operating scientific instruments (spectrometers, liquid chromatographs, wool testing imagers), and even military avionics test benches, all powered by DOS, Windows XP, or proprietary older Unix.
- The Nuclear Power Plant Anomaly: A particularly captivating story detailed a nuclear power plant in 2007 still employing a Pentium 1 system running Windows NT 4.0, which hosted an AmigaOS emulator. Its purpose was to display control rod status, and its continued use stemmed from newer Windows versions breaking critical hardware access required by the now-defunct emulator vendor, making a compliant upgrade prohibitively expensive and regulatory-heavy.
- Unyielding Business Justifications: Common reasons for this technological inertia included prohibitive upgrade costs, the opportunity cost of days-long system downtimes, a perceived lack of benefit in upgrading (
The Gossip
Industrial Iron & Enduring Environments
A significant portion of the discussion centered on industrial and scientific applications that continue to rely on vintage hardware and operating systems. Users shared examples ranging from CNC mills and military avionics test benches to wool testing imagers and radio programming stations. The consensus highlighted the high cost of replacement, the specialized nature of the equipment, and the lack of incentive to upgrade "if it ain't broke."
Nuclear Nerves & NT 4.0
One particularly captivating anecdote involved a nuclear power plant in 2007 still using a Pentium 1 running Windows NT 4.0 with an AmigaOS emulator to monitor control rod status. The system's persistence was due to newer OS versions breaking critical hardware access, making recertification an impossible hurdle. Commenters discussed the implications of such critical infrastructure relying on antique tech and the regulatory complexities involved.
Emulation Efforts & Migration Methods
Many users explored various strategies for keeping legacy software alive, often through emulation. Solutions ranged from QEMU, DOSBox, and specialized commercial emulators like vDos, to the original poster's concept of an "intelligent" DOS runtime that could translate old I/O operations (e.g., dBase to SQLite, GPIB to USB). The challenges of achieving cycle-accurate emulation and dealing with latencies for physical hardware interactions were also discussed.
Obstinate Operations & Overcoming Obsolescence
This theme addressed the fundamental reasons behind the longevity of these systems and the practical approaches to manage them. The high cost of upgrading, the sheer opportunity cost of downtime, and legal or certification requirements were cited as major deterrents to modernization. Discussions also covered practical aspects like network isolation for security, using Linux machines with Samba to bridge old network protocols, and the constant hunt for spare parts.