German train company are looking for a Windows 3.11 Administrator
A German rail contractor is advertising for a Windows 3.11 administrator to support legacy control systems in high‑speed trains, highlighting how decades‑old software still underpins critical infrastructure. Commenters weigh the trade‑offs between keeping a certified, working MS‑DOS/Windows 3.x stack versus the enormous cost, risk, and regulatory burden of rewriting and recertifying safety‑critical systems on modern platforms. The thread also touches on security (air‑gapped vs. networked access), the scarcity and cost of niche legacy skills, and broader questions about long software lifecycles and Germany’s approach to IT and engineering stability.
Role and Context of the Job
- Position is for administering or updating Windows 3.11–based systems used in German trains, likely tied to Siemens SIBAS 32–style control hardware.
- Some see it as a fun, niche “software archaeology” role, especially for rail or retro-computing enthusiasts.
- Confusion over whether “administrator” implies driver development, low-level coding, or mostly installation/maintenance work.
- Job is outsourced; some argue this implies low pay, others note contractors can earn a risk premium, especially when they hold unique knowledge.
Legacy Systems in Rail and Industry
- Multiple anecdotes about very old systems (Windows 3.11, 95, NT, DOS, BASIC, Lotus 1‑2‑3, mainframes, Siemens PLCs) still running critical business or infrastructure tasks.
- Trains and industrial systems are expected to function for decades; recertifying new software/hardware is described as extremely costly and paperwork-heavy.
- Many argue that as long as the hardware and software work, upgrading old trains nearing end-of-life is not worth it.
Networking, Security, and Stability
- Discussion over whether such systems should ever be networked; some recommend strict isolation, others propose secure KVM-over-IP setups.
- Windows 3.11 networking is described as add-on and fragile (DOS TCP/IP stacks, Novell NetWare, Trumpet Winsock), but also obscure enough that few modern exploits exist.
- Debate over stability: some recall Win 3.11 as “rock solid” if drivers/apps behave; others remember frequent hangs, especially under networking or X server loads.
Why Not Port to Modern Systems?
- One camp claims a competent engineer could re‑implement the functionality in weeks or months by treating the legacy app as a black box.
- Others strongly dispute this, citing:
- Safety-critical context and recertification costs.
- Hidden edge cases and quirks accumulated over decades.
- Second‑system effect and organizational/cultural inertia.
- General agreement that rewriting may be technically feasible but organizationally and regulatorily expensive.
Broader Commentary on Technology Choices
- Some criticize Germany as technologically behind and undervaluing IT; others counter that long-lived industrial systems are normal and not a sign of backwardness.
- Debate around using Linux: praised for low bloat and long-term kernels, but criticized for distro churn and ecosystem instability compared to “30 years of the same Windows.”