The runtime · Preservation
Keep the old software running — and keep the ability to run it.
Perslis Software Preservation runs legacy Windows and DOS software on modern machines, and preserves the ability to operate it — with receipts.
Some software outlives the hardware and the operating system it was built for, but the work still depends on it. Preservation is the offering that keeps that software usable: Perslis runs the old Windows or DOS binary on a modern machine, detects and maps its controls, and drives it through the runtime — the same deny-by-default operational layer the rest of Perslis uses. Each session produces verification receipts, so what was operated, and how, can be checked afterward rather than taken on faith.
What preservation covers
Run it
Legacy Windows and DOS binaries run on modern machines through the runtime, without rewriting them.
Map it
The runtime detects and maps the program's native controls, so its interface becomes something that can be driven.
Prove it
Sessions carry verification receipts — a record of what was operated that can be checked independently, later.
An honest boundary
This is the preservation offering, not a guarantee that every binary from every era runs unchanged. What is supported is what has been detected, mapped, and driven — named, not implied. There are no version numbers, benchmarks, or guarantees claimed on this page; the discipline is the same as the rest of Perslis: label what is proven, name what isn't.
Related
Preservation keeps the software operable; two neighbouring products go further on either side. Legacy System — reviving the application itself →, and Win95 USB — running and testing input on Windows 95 →.